Tilman Schmidt pisze: > Andrzej Zawadzki schrieb: [...] > > Btw, I think it is a mistake to put the BackupCatalog job after the > Tape-Eject job. How can it backup the catalog if the tape has already > been ejected? I'm making BackupCatalog to, a different place in different location on disk - so I don't need Tape to be mounted. :-)
> How to resolve the deadlock? Two possibilities: > > a) If you want to complete the 2008-02-19 backup correctly: > Cancel job 7489 and any jobs after 7501 that might already be in a > "waiting" state. Then cancel job 7501. Job 7490 will be the next to > run, and back up your catalog, so the backup of 2008-02-19 will be > complete. Then unmount and eject the tape manually, mount the next > tape, and let the cycle resume. Yes I did something like that but... [...] > How to avoid that in the future? I have put that question to the list > once already. The only answer was to run jobs that might require > operator intervention (read: any backup job) only at times when an > operator is present (read: not on weekends or holidays). IOW: Bacula > doesn't like waiting. :-) That's my question ;-) How to avoid such deadlocks? Maybe bacula need something like "group of jobs" So, in my case I will have Group "Full" and last one will be my Tape-Eject and even lower priority then next Job, Tape-Eject job belongs to Group Full and must finished before Next Group. Maybe that's overkill ;-) I don't know ;-) -- Andrzej Zawadzki ------------------------------------------------------------------------- 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
