I noticed a strange behavior.
When a run command is issued to backup one of the configured clients from the bconsole after module installation/deployment , you always get the Cannot find any appendable volumes message. If you manually create a volume using the label command in bconsole the first time you get this message, subsequent runs (manual or auto) will work and the required volume is created automatically.
However this doesn't hold true for the BackupCatalog job that is preconfigured. An intervention is required for each run. If you create some volume in the pool:catalog it will complete ok.
23-Sep 13:29 myserver.com:s JobId 19: Job BackupCatalog.2014-09-23_13.29.55_35 is waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "DefaultFileStorage" (/mnt/bacula/default)
Pool: myserver.com:pool:catalog
Media type: File
Any ideas about this?
I noticed a strange behavior.
When a run command is issued to backup one of the configured clients from the bconsole after module installation/deployment , you always get the Cannot find any appendable volumes message. If you manually create a volume using the label command in bconsole the first time you get this message, subsequent runs (manual or auto) will work and the required volume is created automatically.
However this doesn't hold true for the BackupCatalog job that is preconfigured. An intervention is required for each run. If you create some volume in the pool:catalog it will complete ok.
23-Sep 13:29 myserver.com:s JobId 19: Job BackupCatalog.2014-09-23_13.29.55_35 is waiting. Cannot find any appendable volumes. Please use the "label" command to create a new Volume for: Storage: "DefaultFileStorage" (/mnt/bacula/default) Pool: myserver.com:pool:catalog Media type: FileAny ideas about this?