2010/11/30 Matthew Seaman <msea...@squiz.co.uk>: > > Hi, > > We have a setup with two storage director machines at different > locations. Most of the clients are in one hosting center, and use the > local SD, while several are scattered at various locations around the > net and use the other SD. There's a single director driving all this, > and one catalogue for everything. > > One annoying feature we've noticed is that should the 2nd SD block > [which has happened due to filling up a partition] it holds up all > backups to the 1st SD. Is there any way of avoiding this effect? I > can't see why a failure backing up client X to SD 2 should prevent > client Y from backing up to SD 1. >
This is not the default behavior. I mean I have no problems running concurrent jobs to 1 or more storage devices. Have you allowed concurrent jobs? John ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
