There's no reason they cannot use the same pool. They just cannot write to the same volume concurrently. With a tape device, that would be a problem because there can only be one volume in the tape drive. However with a disk device, a volume is a file, so there can be numerous volumes being written concurrently. One way is to use Maximum Volume Jobs = 1 in the Pool resource definition. This will cause a new volume (ie. file) to be used for each job that is run.
Kyle Tucker wrote: > Hi, > I have a new Bacula 2.0.2 setup and I am backing up to > disk. I have remote clients that are very slow to backup and > often prevent my more important local clients from being backed > up due to concurrency being set to 1 as I don't want to get into > the issues with interleaving as it's suggested to avoid in the > warning section on concurrent jobs. > I already have things so my remote clients are in separate > pools and I understand I can set these pools into separate Device > resources and Bacula will allow 2 concurrent jobs to run. Is there > a way that I can limit the 2 concurrent jobs to not run within the > same pool, causing the interleaving blocks issue? I looked at using > priorities, but that didn't look like it would control what I am > trying to do here. Thanks. > > ------------------------------------------------------------------------- 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
