On 19/06/2019 19:19, Jasen Lentz wrote:
> Revised...
>
> [3:0:2:0] tape IBM ULT3580-TD4 C7QH /dev/st0 /dev/sg47
> [3:0:2:1] mediumx IBM 3573-TL C.20 /dev/sch0 /dev/sg48
>
> Use the sg names instead?
>
Yes. More specificially:
bacula-sd.conf
Autochanger {
Name = IBM-3573-TL
Device = ULT3580-TD4
# Device = Drive-2
Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg48
}
Device {
Name = ULT3580-TD4 #
Drive Index = 0
Device Type = Tape
Media Type = LTO-4
Archive Device = /dev/st0
Control Device = /dev/sg47
LabelMedia = yes; # lets Bacula label unlabeled media
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Autoselect = yes
Alert Command = "sh -c 'smartctl -H -l error %c'"
Volume Poll Interval = 600
#
Spool Directory = /var/bacula/spool/TAPE
Maximum File Size = 50G
Maximum Network Buffer Size = 262144
Maximum block size = 1M
# tune these to suit your spool
Maximum Spool Size = 700G
Maximum Job Spool Size = 50G
# WARNING: this next parameter is not what it seems at first glance.
# (or is used for anywhere else in bacula configuration)
# HERE, if more jobs are started for a pool than the number given
# (eg, 300+ nightly incrementals)
# AND more than one drive is available
# AND this number is lower than the director's max concurrent jobs setting
# for the storage-daemon, the number of jobs for THIS drive will be limited,
# but the system will try to grab another drive for the same pool to start
# the remaining jobs.
#
# ONE pool's backups can grab ALL your drives if you set this figure too low.
#
# In general you don't want that happening when using spooling
# (Or should only do it with judicious tuning)
Maximum Concurrent Jobs = 80
}
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
