Hello Adam,
There is a misunderstanding here. The volumes in bacula are "tied" to devices. This way you cannot have a volume in the directory mount point specified for the Zentyal-File device being used by another device with a different directory mount point (archive device).
It is possible to have groups of devices grouped into the same storage (in bacula-dir.conf) using the same mount point or a virtual autochanger (you can find both strategies in
http://blog.bacula.org/whitepapers/CommunityDiskBackup.pdf). This way, all your volumes will be in the same directory and they can be accessed by any of the devices (grouped or virtual autochanger). Because some operations will not work well in the group configuration, virtual autochangers are preferable.
If you want to use different devices with different mount points, as you have configured, you will need different pools with volumes tied to them (you can define this in the pool and not in the schedule resource), for example:
Pool ThuPool-1 for Zentyal-File storage and ThuPool-2 for Backup-File storage:
Pool {
Name = ThuPool-1
Pool Type = Backup
Recycle = Yes
AutoPrune = Yes
Volume Retention = 6d
Volume Use Duration = 1d
Storage = Zentyal-File
Label Format = "Thu-"
}
Pool {
Name = ThuPool-2
Pool Type = Backup
Recycle = Yes
AutoPrune = Yes
Volume Retention = 6d
Volume Use Duration = 1d
Storage = Backup-File
Label Format = "Thu-"
}
