On Mon, Jan 10, 2011 at 18:18, Phil Stracchino <ala...@metrocast.net> wrote:
> On 01/10/11 16:49, Mike Ruskai wrote: > > So simply having the catalog backup be a different priority ensures that > > no other job can run at the same time, provided mixed priorities are > > disallowed (that would allow the higher-priority backup jobs to start > > while the catalog backup is under way). Which is just as well, since I > > don't like the idea of relying on database or table locks. > > Yes, disabling mixed priorities would prevent any higher-priority job > from starting while the catalog update was running. > > > -- > Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 > ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org > Renaissance Man, Unix ronin, Perl hacker, Free Stater > It's not the years, it's the mileage. > What you may wish to request (I can't imagine it would be difficult) is a maximum mixed priority level option, where anything above that number ignores mixed priorities being allowed and waits till everything else is stopped. I would certainly vote for such a feature. I will look into doing it myself, but I cannot guarantee anything, as my boss would first have to agree with our internal business need for such an additional feature, and I'm not sure we need it at the moment though I certianly see the appeal of the capability.
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
