Right now, I'm backing up to a drive array with one concurrent job. I'd like to increase that, and really need to for a new backup environment I'm creating soon.
With the single concurrent job, getting a consistent catalog backup is trivial - I just schedule it to run one minute after the last data backup job, and give it the lowest priority, so it always runs after everything else. How do I accomplish the same general thing with multiple concurrent jobs? That means the catalog backup needs to run by itself, so the database is consistent, and needs to run after all other jobs have completed. Thanks in advance for any answers. ------------------------------------------------------------------------------ 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