Best Practices

While it is technically possible to specify multiple volumes in a single FileSet resource configuration (by using multiple plugin command lines), this is not necessarily the best way to perform multiple volume backups. It is strongly recommended that one FileSet definition is created per each filer volume being backed up.
By default, if one of your volume fails to back up in a “multi-volume” backup job, the main Bacula job will terminate “Backup OK – with warnings.” The JobStatus for jobs that terminate “Backup OK” and “Backup OK – with warnings” are not differentiated in the Catalog. They are both ‘T’, so this means that you will have to carefully monitor your backup job logs in case some volume backups fail and pay attention to the JobErrors field in the job summaries.
To address this issue, there is a plugin option called “abort_on_error”, which causes Bacula to immediately fail the job as soon as an error is detected while backing up a volume. However, if you use this option, and the backup of volume number 5 in a list of 10 volumes fails, then the whole job will be failed, and volumes 6-10 will not be backed up during that job’s run.
A 1:1 configuration (one volume backed up per job) means that the “abort_on_error” option will make more sense to enable in each job, so you will immediately know when a volume fails to backup since the Bacula job will terminate with a “Backup failed” message and ‘f’ in the Catalog for the job.
With a 1:1 volume/job configuration, re-running a specific volume backup job is simple to do after the cause of the failure is investigated and fixed.
In the example about the 10 volumes, without a 1:1 configuration, there is no way to re-run a backup of just the one volume that failed to back up.

All the above best practice are applied when using Automatic Objects Integration.