No, I don't use JobDefs. I'll do some research on JobDefs to see how useful this option can be.
Thanks for the pointer. -----Original Message----- From: Dan Langille [mailto:[email protected]] Sent: Tuesday, February 05, 2013 1:03 PM To: Conrad Lawes Cc: [email protected] Subject: RE: [Bacula-users] Bacula deficiency On 2013-02-05 12:54, Conrad Lawes wrote: > -----Original Message----- > From: Dan Langille [mailto:[email protected]] > Sent: Tuesday, February 05, 2013 11:29 AM > To: Conrad Lawes > Cc: [email protected] > Subject: Re: [Bacula-users] Bacula deficiency > > On 2013-02-05 10:44, Conrad Lawes wrote: >> Overall, I'm fairly happy in with Bacula. It has saved me thousand >> of >> $$ migrating from Arkeia Network Backup software. However, there is >> one shortfall that is causing me some grief and I don't see any easy >> solution to: Bacula does not provide a "last <day> of the month" >> feature in its scheduling option. >> >> I wish to run an offsite backup to tape on the last Friday of each >> month. Bacula provides 1st-5th day of the week option. Although, >> most >> months contain only 4 Fridays, some contain 5 (last January for >> example). If I set the schedule to include the 4th and 5th Friday, I >> will get 2 offsite backups for the months containing 5 Friday. I >> don't >> want this because it wastes limited disk space in my D2D2T >> configuration. Manual intervention seems to be only solution but >> this >> defeats the "set it and forget it" paradigm that I'm seeking. >> >> I am hoping someone has solution to this dilemma. > > Script it. Run the job on both the 4th and the 5th Fridays. > > Add a run before script. In the script, check to see if there is a > 5th > Friday. > If so, and we're on the 4th Friday, cancel the job. On 2013-02-05 12:54, Conrad Lawes wrote: > Ouch! I was afraid of this option. Since the RunBefore script is > defined at the job level, this would mean that I will have to define > additional backup jobs for each client (20). Presently, my main > schedule contains multiple run times: > > Schedule { > Name = WeeklyCycle > Run = Level=Incremental Pool=DailyBackupPool mon-thu at 19:00 > Run = Level=Full Pool=WeeklyBackupPool 1st-3rd fri at 17:00 > Run = Level=Full Pool=OffsiteBackupPool 4th-5th fri at 17:00 > } > > .. and so my job definitions are simple: > > Job { > Name = Server1-BackupJob > Client = server1-fd > Type = Backup > Level = Incremental > Schedule = WeeklyCycle > .... > } > > The scripting approach is going to require new schedule and job > definitions for EACH client resulting in a larger and more complex > configuration file. > A simple, "Run = Level=Full Pool=OffsiteBackupPool last fri at 17:00" > would be much more efficient... Each job? Can't you add a Run directive to your JobDefs? Are you using JobDef? Or am I misunderstanding the issue? -- Dan Langille - http://langille.org/ ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
