Hi, On 6/8/2007 1:00 AM, Kyle Marsh wrote: > Hello again, > > On 6/7/07, Arno Lehmann <[EMAIL PROTECTED]> wrote: >> Hi, >> >> On 6/7/2007 11:05 PM, Kyle Marsh wrote: >> ... >>> That's an interesting suggestion -- I could have a Python script that >>> gets called and parses the config file to determine the full name from >>> the client name. That gets rid of the magic, at least (or replaces it >>> with worse magic, depending on your perspective). >> Well, personally, I like bad magic, but not in production systems :-) >> >> I was rather thinking of making the client resource available to to the >> python event, but I have no idea how that would be done. >> >>>> For my setups, the clients affected by possible non-availability are >>>> only a minority, so I just added the line to the jobs as needed. >>>> >>> Unfortunately I'm not sure how the boxes are to be set up -- most are >>> machines for students doing research with their professors and they >>> will change hands and configuration every semester. I don't know if >>> users will decide to shut them down overnight or what, so I was hoping >>> to find a blanket that could cover them all. >> Ok, that is a nihtmare for anyone responsible for backups. I'd use the >> aproach with a ping, set a high number of retries with long intervals in >> between (something like 1 hour interval, 12 retries), NOT rerun failed >> jobs, and set a maximum job wait time etc. > > So a RunBeforeJob to do the ping, then RescheduleOnError = yes, > RescheduleInterval = 1 hour, and RescheduleTimes = 12?
> What do you > mean by not rerun failed jobs? Sorry, my fault... I meant "Rerun failed levels" but it was probably too late or too hot here to actually write what I meant :-) By the way: this is set to no as the default. Also, you should check the manual description and think about your objectives - setting it to yes will make sure you get your full backups eventually, but in case the users turn off the computers while jobs run you might end up wasting lots of space for incomplete jobs. Not rerunning failed levels might give you longer-than-wanted times between full backups but will keep the jobs running more smoothly overall. In my experience, and so on :-) > Don't we want to rerun it if they miss > one? Definitely. > Or does that mean if it gets rescheduled 12 times, not to > reschedule it for another 12 and just let tomorrow's try? No, that's already accomplished by your numbers - 12 retries in 12 hours, and the give up and wait for the next round of scheduled jobs. > Also where > would I specify that? In the job definition. >> This should get you usable backups from time to time, probably during >> the day, but whoever wants a work day without backup load can simply >> leave the computer on during the night (which is, ecologically as well >> as economically, not so good...). >> >> You could refine this with tries to wake-on-lan the machines and turn >> them off after backups, if you woke them up yourself. Just a nice >> practice in writing a script in your favorite language :-) > > Hmm...you intrigue me :-). I'll have to see about this -- I'll let > you know if I do it and it works out well. > >> ... >>> Thanks for the help, Arno. Is there any chance of you taking a look >>> at my other post about the pool configuration? That's really the more >>> pressing now. >> Sure, for money I do quite a lot :-) > > :-) > >> I even do things for free, only I don't know which mail you refer to :-( > > I sent another mail right after this one asking how well the sample > configuration for pools of disk backups (here: > http://bacula.org/rel-manual/Automated_Disk_Backup.html) scales, since > the example only has one client and I fear horrible things if I simply > up the number of clients without changing anything else. Hmm... I don't see that mail here. You might point me to a list archive URL, or resend the mail. Arno > Thanks a bunch for all your help, > > ~Kyle Marsh > > >> Arno >> >> -- >> IT-Service Lehmann [EMAIL PROTECTED] >> Arno Lehmann http://www.its-lehmann.de >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
