Hello Everyone, I've got slight problem, due to inattentiveness to backups.. Everybody ignores backups until they are needed, right? In this case I've got a bacula server with a single DLT drive connected, that does full and incremental backups for a couple of hosts on my network. When the tape fulls up it the jobs are blocked until the tape is changed. If the designated tape changer is inattentive, jobs continue to queue up until the tape is finally changed. This will result in lots of duplicate incremental jobs and occasionally duplicate full jobs queued up for the same client, so that when the tape is changed if the operator does not first 'cancel' all the redundant queued jobs bacula will then run through the queue doing duplicate full/incremental backups of the same client.
Is there any way to configure bacula that if a job of the same type/client is already in the queue then the scheduler does not place another instance of the same job in the queue? -- Greg -- Greg Retkowski / I.T. Infrastructure Consultant | RAGE [EMAIL PROTECTED] http://www.rage.net/~greg/ C:408-455-3913 | .NET ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
