Check permissions on the disk, including SELinux or other ACLs. The
bacula-sd user must have read/write permissions.
On 9/19/2018 3:40 PM, Gary Dale wrote:
I'm running bacula 7.4.4 on a Debian/Stretch AMD64 server.
When I try to create a new disk volume for my steadily increasing
amount of data needing to be backed up, it usually fails after I
create the first new volume. There is lots of free space on the disk,
so it's not that. Eventually I might be able to create another new
volume (possibly because of an intervening reboot) but in the
meanwhile I only have the one new volume (25G) which is about 1/10 the
size of a full backup...
Here's an example of what I see in bconsole when executing the label
command:
Sending label command for Volume "weekly-backup-pool-30" Slot 0 ...
3934 Device ""FileStorage" (/home/shares/backup)" is being initialized.
Label command failed for Volume weekly-backup-pool-30.
Do not forget to mount the drive!!!
Any ideas on what is happening and how to fix it?
Thanks.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
