El mié, 29-08-2007 a las 19:28 +0200, Kern Sibbald escribió: > This is something that I have on my personal list to implement, but probably > should be added to the projects file. > > ---------- Forwarded Message ---------- > > Subject: Bacula Feature Request > Date: Wednesday 29 August 2007 13:30 > From: Martin Schmid <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > Item n: feature to prevent jobs from starting twice > Date: Date submitted > Origin: Martin Schmid [EMAIL PROTECTED] > Status: New > > What: I have short term jobs that are run every 90 minutes and a first > full backup that takes significantly longer than the > following incremental jobs is started near midnight. I am > aware of the maximum wait parameters and I'm using them > extensively. > But by chance a following job is well in the allowed maximum > delay while the previous full backup job has > not finished yet . This will start the second job as full > backup even though the preceding job may terminate successfully. > In the end there are two subsequent full backup jobs that > have run. Wouldn't it be possible to forbid any > subsequent job at all? Maybe in the schedule resource.. > > Why: Space is limited on the drives and and unnecessary full backup > delays other jobs. It would also help recovery after a previous > full backup terminated with error or was canceled or > encountered a long delay > > Notes: Example: between two 'Quickbackup' jobs there are 90 minutes. > There is a full backup at 00:30 and the first incremental > at 07:00, the next at 08:30, ... > The full backup job takes some 150 minutes > The full backup may be delayed and end at 07:10. By this > time the first incremental is already started as full backup. > Tuning the maximum start delay parameter or the schedule > just reduce the chance of subsequent full backups without > solving the problem > > -- > Martin Schmid > APS systems AG, Neumatt 4, CH-4626 Niederbuchsiten > Tel: +41 62 389 8888, Fax: +41 62 389 8880 > www.aps-systems.ch >
As workaround, pre and post job actions could be used to create some semaphore files Pre script something like : Begin backup job if Semaphore file exists then abort or something else create semaphore file endif Post backup script like : if semaphore file exists then delete semaphore file endif ? Best regards D. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
