Hi Bacula gurus,
We are loving using Bacula on Debian 11 - have been long time users.
Thank you to all who are supporting this great code base
Using Debian 11, Bacula version 9.6.7-3, and the Oracle SL150 tape
loader with both SAS and Fiber channel tape drives (2 of each)
From time to time we reconfigure the tape loader and it makes the
device names move around for the tape and the autochanger devices.
Note that "ordinary reboots" of the linux machine without loader changes
doesnt change the nst and sg device paths
In Bacula's /etc/bacula/sd.conf, we are using device names such as:
Device {
Archive Device = /dev/nst4
Changer Device = /dev/sg5
Device { # top loader
Archive Device = /dev/nst1
Changer Device = /dev/sg9
Device {
Archive Device = /dev/nst0
Changer Device = /dev/sg7
Device {
Archive Device = /dev/nst2
Changer Device = /dev/sg6
Device {
Archive Device = /dev/nst3
Changer Device = /dev/sg8
Apologies if this is more of a Debian Linux question than a Bacula
question - but if we change these device names from /dev/nstX and /dev/sgX
to the devices in /dev/tape/by-id that symlink to these originals -
will that protect us from the remapping of device paths after loader
changes ?
Specific example:
root@bacula-server:/dev/tape/by-id# ls -la | grep nst0
lrwxrwxrwx 1 root root 10 Apr 5 11:59 scsi-3500104f000d1e0d0-nst ->
../../nst0
So change:
Archive Device = /dev/nst0
to:
Archive Device = /dev/tape/by-id/scsi-3500104f000d1e0d9-nst
Could we expect that doing this will make our by-id device paths
survive library tape drive reshuffling?
Thank you,
Matt Weatherford
UW - CSDE
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
