----- "Tilman Schmidt" <[EMAIL PROTECTED]> wrote: > Am 11.02.2008 04:10 schrieb Drew Bentley: > > But then again, it's backups and how important is your data? I'd > > suggest just letting them run til complete. Unless backups impact > your > > systems when users are using them. And if that's the case, perhaps > you > > need to re-evaluate your systems as I never have any issues kicking > > off a backup while a system is being used. > > Trouble is, the waiting job will wreak havoc with future scheduled > jobs. > For example, if the operator forgot to insert a tape one day but > comes > in the next day to insert the tape for *that* day, the waiting job > will > either grab that tape and use it, or complain that it wants a > different > one. In the first case, the next job will again hang waiting for a > tape. > In the second one, both jobs will hang.
This was solved by making sure the backup jobs get "auto-cancelled" before anyone even gets in in the morning. Like 5 O'clock or something. The backup starts at 23:00 and get canceled after 6 hours of non-starting. Currently this works beautifully. If they forget the tape, a non knowledgeable person can simply ignore the whole thing and put the tape for that day in. Someone with a clue can always start a backup during work hours if they wish. Thanks, Mark ------------------------------------------------------------------------- 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
