On Tue, Feb 18, 2014 at 03:13:27PM +0000, Steven Hammond wrote: > Here is the scenario. We kick off a daily DISK-TO-DISK backup at 18:00. We > then kick off a DISK-TO-TAPE Backup (COPY) at 23:59 assuming the early job is > finished. This works for the daily incrementals, but the differentials and > full backups take longer. Yes, I could change the schedule for the > DISK-TO-TAPE backup but I was wondering if it is possible, somehow, to kick > off the DISK-TO-TAPE after the last job in the DISK-TO-DISK backup is > complete (the catalog backup)? I assume it would be in the RunAfterJob on > the catalog backup job, but I'm not for sure how to kick it off. Any > suggestions would be appreciated. > > Steven Hammond > I.T. Manager > Technical Chemical Company >
Hi Steven, you could use different job prios to ensure the (lower priority) d2t-Jobs starts off only when all other higher-prio jobs are finished. Uwe -- NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
