On 12/10/2019 2:42 PM, John H Nyhuis wrote:
I have noticed that my config of bacula only seems to ever use one drive. For example, when labeling a large pool of volumes, it mounts and labels each volume sequentially using only a single drive. As each volume label is independent of the other volumes, it seems like this would be much faster if the volumes were split between the drives. (Or at least wear would be evened out between the drives). Is this the typical behavior, or can my config be improved in some way to better use multiple drives? Our tape library is configured thusly in bacula-sd.conf
Typical behavior for the label command, yes, but the label command itself is not typical. It is only used once on a volume. The label command is a special case and there is no automatic device selection. For normal backup jobs, a write device is selected at job start time using a device selection algorithm. By default, Bacula looks for an appendable volume in the pool.that is already mounted in a device and assigns that device to the job, otherwise it assigns an empty device and attempts to load an appendable volume from the pool, etc. There are a few directives that control aspects of the volume and device selection algorithm, for example see the PreferMountedVolumes directive in the Job resource documentation.
...
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
