Well, the executing of multiple jobs doesn't work with my setup. A short hardware spec: Overland tape library, 15 tapes, 2 DLT drives.
At the moment, I have a full backup running on a remote server writing on Drive01. It would estimate to last for 3 days. Currenly the backup process lasts for about a day. The backup schedule for my local servers is suppose to start today at 1:00 am. These jobs have priorities of 10 to 15, whereas the remote backup as priority of 20. These backups should have been written today on Drive00 to different tapes with different volume names. However, the local backup jobs are still wait for the remote one to finish. So, I will have about 3 days of missed backup, which I can't really afford. Does anyone know what I am doing wrong? -- Andrei On Sun, 2005-07-03 at 18:57 +0200, Kern Sibbald wrote: > On Sunday 03 July 2005 16:25, Andrei Mikhailovsky wrote: > > Hello bacula users, > > > > I was wondering if the latest development 1.37 version of bacula has > > support for executing more then one job at a time. > > This has been possible for at least 4 years (in many versions). > > > In case if there are > > multiple drives in the tap library, you should be able to record two > > tapes in one go. Is this supported in 1.37 branch? > > This is supported since a long time with a few minor (perhaps annoying) > restrictions (providing you are talking about autochangers) such as requiring > you to provide a locking mtx-changer script and ensure that the same Volume > is not mounted on two drives at the same time -- see the manual for more > details. > > Version 1.37 as it stands *should* remove most of those restrictions, but has > yet to be extensively tested. > > If by "tape library" you are simply talking about different tape drives > rather > than autochangers, then there are no restrictions on multiple jobs writing at > the same time regardless of the Bacula version. >
signature.asc
Description: This is a digitally signed message part
