On Wed, 2 Oct 2024 at 16:13, Víťa Čapek <
vita...@gmail.com> wrote:
>
> The Bacula versions on both servers are the same. Below, I am adding the update log:
>
> backup_server_1 (bacularis rpm based):
>
> Upgrade bacularis-4.0.0-1.el9.noarch
> Upgraded bacularis-3.2.1-1.el9.noarch
> Upgrade bacularis-nginx-4.0.0-1.el9.noarch
> Upgraded bacularis-nginx-3.2.1-1.el9.noarch
> Upgrade bacularis-selinux-4.0.0-1.el9.noarch
> Upgraded bacularis-selinux-3.2.1-1.el9.noarch
> Upgrade bacula-libs-13.0.4-24021221.el9.x86_64
> Upgraded bacula-libs-13.0.2-23022019.el9.x86_64
> Upgrade bacula-postgresql-13.0.4-24021221.el9.x86_64
> Upgraded bacula-postgresql-13.0.2-23022019.el9.x86_64
>
> backup_server_2 (compose install based)
> Bacularis: Version: 4.2.1
>
> Installed Packages
> bacula-libs.x86_64 13.0.4-24021221.el8
> bacula-postgresql.x86_64 13.0.4-24021221.el8
>
> I tried to modify the autochanger by adding /dev/null to ChangerCommand, and below I am attaching the log.
>
> backup-sd JobId 40418: Marking Volume "FullPool-40187" Read-Only in Catalog.
> backup-sd JobId 40418: Warning: mount.c:216 Open of File device "FileStorage" (/mnt/backup-raid5/bacula/) Volume "FullPool-40187" failed: ERR=file_dev.c:189 Could not open(/mnt/backup-raid5/bacula/FullPool-40187,OPEN_READ_WRITE,0640): ERR=Permission denied
> backup-casa-dir JobId 40418: Created new Volume="FullPool-40187", Pool="FullPool", MediaType="File" in catalog.
> backup-sd JobId 40418: Marking Volume "FullPool-40186" Read-Only in Catalog.
[cut]
> bacula-sd.conf
>
> Autochanger {
> Name = "FileChgr1"
> Device = "FileChgr1-Dev1"
> Device = "FileChgr1-Dev2"
> ChangerDevice = "/dev/null"
> ChangerCommand = "dev/null"
> }
>
>
> Permissions on folder are bacula:disk. The problem remains the same, the volumes are not created on the disk at all. They are only in the Catalog.
Hello Vita,
Thanks for providing more details.
It looks that there were two errors. This error after adding /dev/null has gone:
backup-sd JobId 40411: 3991 Bad autochanger "loaded? drive 0" command:
ERR=Child exited with code 1.
Results=ERROR: usage: mtx-changer ctl-device command [slot
archive-device drive-index]
Insufficient number of arguments given.
Mimimum usage is first two arguments ...
and it is correct because your Bacula version is 13.0, so the virtual
autochanger requires /dev/null there.
The second problem with permissions is still available. Now it has changed from:
backup-sd JobId 40411: Warning: label.c:404 Open File device
"FileStorage" (/mnt/backup-raid5/bacula/) Volume "FullPool-40132"
failed: ERR=file_dev.c:189 Could not
open(/mnt/backup-raid5/bacula/,CREATE_READ_WRITE,0640): ERR=Is a
directory
into this:
backup-sd JobId 40418: Warning: label.c:404 Open File device
"FileStorage" (/mnt/backup-raid5/bacula/) Volume "FullPool-40184"
failed: ERR=file_dev.c:189 Could not
open(/mnt/backup-raid5/bacula/FullPool-40184,CREATE_READ_WRITE,0640):
ERR=Permission denied
The only thing that I don't understand is that your Autochanger
Devices paths are /tmp and the Device in the log is
/mnt/backup-raid5/bacula/
How does the Device resource look with this directive in the bacula-sd.conf?
Archive Device = "/mnt/backup-raid5/bacula/"
and how does the Storage resource look in the bacula-dir.conf?
For the permission error, I would propose to do a quick test. On the
root user account could you check if these commands are able to create
and remove a file?
# sudo -u bacula -g tape touch /mnt/backup-raid5/bacula/testfile
# sudo -u bacula -g tape rm /mnt/backup-raid5/bacula/testfile
This test is for checking if the SELinux context can cause any problem
here. If yes, then it might be good to look at
/var/log/audit/audit.log as well.