Hello, My backup schedule is such that I do a full on the first Sunday of the month, diffs every other sunday, and incrementals every other day. The first time I run a client Bacula upgrades the backup to a full as it should. This typically results in two full backups happening in the same month. So when I have gone through my pool of three full backup volumes and it's time to recycle the first one, the retention period does not allow the first volume to be recycled. This is all to be expected and I could solve the problem by marking the dates on my calendar and manually recycling the backup volume before this cycle starts again, but I forget sometimes.
So I have implemented "max wait time = 300" to cancel a job if it waits for 5 minutes on the storage resource to recycle a volume. This works fine, but the problem is that if others jobs are started at the same time who also use "max wait time" they also get canceled because they also have been waiting too long. But in this case the clients are waiting for "maximum concurrent jobs" and not the storage daemon per se. Is there a way I can specifically say "cancel this job if it's waiting for the storage daemon for too long" versus "cancel this job if it waits for anything too long"? Thanks, Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
