I'm using a "Daily" pool for incremental backups on weekdays, and a "Weekly" pool for full backups on weekends. The "Weekly" pool has "Volume Use Duration = 8h" because the full backup goes into off-site storage.
Now if Bacula hits the end of a "Weekly" tape, the weekend's remaining jobs will block waiting for the next tape. Come monday, the operator finally labels a new tape - which Bacula immediately transitions from "Append" to "Used" because it sees the maximum duration of use as exceeded. Apparently that duration is counted from the start of the job, not as I thought from the start of using that volume. So the volume's state has to be manually updated in order for the backup to proceed - something which is much too complicated for the tape operator, so I end up doing that myself. :-( Worse, if monday is a holiday, monday's jobs will queue up behind those of the weekend. When the tape change has finally been performed, the weekend jobs finish - except for the BackupCatalog job, which has "Priority = 11" to make it run after the others, and is now postponed until *monday's* file backup jobs have run. Consequence: Bacula asks for the "Daily" tape, writes the incremental backups, and then asks for the "Weekly" tape again to append the catalog data - of course marking it "not appendable" again as soon as it sees it, see above. Obviously I'm doing something wrong. Can someone help my ignorance? Thanks Tilman -- Tilman Schmidt Phoenix Software GmbH www.phoenixsoftware.de 53227 Bonn, Germany Amtsgericht Bonn HRB 2934
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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
