I’m using Bacula server 5.2.3 for backing up my data, actually backing up more than 20 servers. The last days I am getting this message in bacula server from one of my jobs:
--
12-ene 10:46 bacula-sd JobId 5799: Job Backup-server15.2012-01-12_09.41.51_28 is waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "FileStorage-server15" (/pools/vol0/server15)
Pool: server15-file
Media type: File-server15
--
My backups are disk based, each server has it’s own storage and device, and are configured to label volumes automatically. I am getting this error only from one of my jobs, the others are finishing correctly.
I’ve rechecked all configuration for this client, looking for errors but it had the same settings than the others clients and in the past has been running ok. I’ve checked also, that LabelMedia option has set to yes in it’s device config:
#
Device {
Name = FileStorage-server15
Media Type = File-server15
Archive Device = /pools/vol0/server15
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
#
When I listed the pool’s volumes for this client I could see one volume in APPEND state, I have configured bacula to use one volume per job.
*list media pool=server15-file
-- +---------+-----------------------+-----------+---------+----------------+----------+--------------+---------+------+-----------+--------------+---------------------+ | MediaId | VolumeName | VolStatus | Enabled | VolBytes | VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | | 7,178 | disk-server157178 | APPEND | 1 | 0 | 0 | 1,209,600 | 0 | 0 | 0 | File-server15 | 0000-00-00 00:00:00 | --
I’ve checked that this volume does not exist physically in disk, so I’ve manually purged this volume in bacula catalog. Anyway when a new job is run it has to create a new volume in bacula catalog.
*purge volume=disk-server157178 yes
When I’ve relaunched this job again, a new volume has been added and the job has finished Ok.
I don’t know exactly why I’ve reached this situation, may be because a few days ago I’ve run out of disk space, but I am not sure.