Is there a slick way to have the completion of on migration kick off the
next? I've added a RunAfterJob but that appears to be run after each backup
is migrated instead of at the end of the migration "set." As in:
Job {
Name = "elbe-migrate"
Type = Migrate
Level = Full
Client = volga-fd
Write Bootstrap = "/u1/bacula/working/elbe-migrate.bsr"
FileSet = "Exchange"
Schedule = "Never"
Messages = Standard
Pool = elbe
Maximum Concurrent Jobs = 4
Selection Type = Volume
Selection Pattern = ".*"
Priority = 12
RunAfterJob = "/usr/pkg/libexec/bacula/next-migrate.local loire-migrate"
}
I'm trying to avoid spinning the host system out of resources as it runs to
add jobs for the 30 hosts that each have 6 or more backups. It can only
stream to tape so fast anyway...
Thanks,
peter
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
