Just upgraded from bacula 9.6 to bacula 13.01.
There has been a change in behaviour, possibly a bug, in the way
Storage is selected.
When a schedule overrides a Pool and the new Pool doesn't have a
Storage. It is selecting
the old original Job Pool Storage and not the Storage in the Job. Under
9.6 it defaulted back
to the Job Storage. This seems the correct behaviour as why use a
Storage from a Pool you have
told it not to use.
Example below.
Under 9.6 the scheduled job used pool: Full-Pool, Storage: backup-lto-1
Under 13.1 the scheduled job used pool: Full-Pool Storage: ad1-file
Job {
Name = "ad1-backup"
Storage = backup-lto-1
Pool = ad1-file-pool
Schedule = TEST
}
Pool {
Name = Full-Pool
Pool Type = Backup
# Storage = backup-lto-0 # No Storage
}
Pool {
Name = ad1-file-pool
Pool Type = Backup
Storage = ad1-file
}
Schedule {
Name = TEST
Run = Full FullPool=Full-Pool mon at 08:00
}
Best Regards,
Royce_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
