Elie Azar wrote: > Hi, > > we're using vchanger, but bacula never seems to use more than the first > virtual drive, even though we have 10 defined in the storage Autochanger > directive for it. why won't bacula use drive1, drive2, etc. It does at > least look at these higher-numbered drives when the update slots command > is used, so it's not a config problem in terms of defining the virtual > drives within the autochanger. > I don't believe bacula's volume reservation worked well with multiple drive autochangers before version 2.2.0. If you are using a pre-2.2.0 release, then that is likely why bacula is not selecting another drive on the autochanger, even though it is loaded with a usable volume. For a single vchanger to be able to run multiple concurrent jobs (one on each virtual drive), you need bacula 2.2.0 or greater.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
