Thank you both for your replies. I had seen that script included with the source files, and have been playing around with it. Doesn't look like it will work for us, though. For it to work, it seems to want one 'Offsite job' to either allow or cancel. We have 15 different jobs, and what determines what pool the backup is written to are the pool overrides in the Scheduler, so an exit code would indiscriminately kill the backup job even on 'regular' backup cycles.
The week of the year idea sounds like a decent work-around for the moment; at least to buy us time. Don't know any Python myself, but I can't imagine it would be too time consuming to add an appropriate option to the scheduler instead. I'll look into how to submit that as a feature request. Again, thanks! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Simmons Sent: Friday, February 24, 2006 08:11 To: [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Scheduling question >>>>> On Thu, 23 Feb 2006 20:42:09 +0100, Arno Lehmann <[EMAIL PROTECTED]> said: > > Hello, > > On 2/23/2006 8:11 PM, Jeremy Koppel wrote: > > > > > > Hello, > > > > > > > > We've been using Bacula in our company since the beginning > > of the year with a good deal of success, but I had a scheduling question > > that I hadn't anticipated earlier. As part of our backup rotation, I > > have 2 additional pools, Offsite1 and Offsite2 (just 1 tape each for > > now), that are scheduled to be written to on alternating Saturdays. How > > it actually breaks down is: > ... > > * The Question: * > > > > But I see that we have a problem coming up in April; 5 Saturdays. So if > > I specify either pool for the 5^th Saturday, we loose our rotation. I > > see that what we actually need to do is to set these up for 'every other > > Saturday' regardless of when it falls during the month. My question is, > > how do you do that? > > I'd try using the week of year specification in the schedule. You'd > simply schedule like > > run = pool=offsite1 w01,w03,w05,... sat at 2:00 > > the problems here: I don't know if this actually works :-) and you still > have to worry about the odd number of weeks per year. At least only one > a year, and simply by swapping the pool definitions in the job overrides > of the schedules... > > The better solution, also absolutely untested, would be to use the > python interface and implement a simple script that determines which > pool to use. I even assume it's impossible at the moment, because in the > manual it states that the Pool attribute of a job object in python is > read-only... but that might change one fine day :-) Another way is to run both jobs every week and have a RunBeforeJob script that returns an non-zero exit status if it is the wrong week (which causes the job to abort). __Martin ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmdk&kid0944&bid$1720&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
