To handle changing device names use ex /dev/tape/by-id/scsi-HUE12340E22-nst and /dev/tape/by-id/scsi-DEC1234567
Anton "exuvo" Olsson [email protected] On 2022-05-25 14:50, Stefan G. Weichinger wrote:
Am 25.05.22 um 14:41 schrieb Nuno Dias:My conf (the relevant parts) tpchanger "robot" define changer robot { tpchanger "chg-robot:/dev/changer" changerfile "/etc/amanda/XXXX/changer-state" property "tape-device" "0=tape:/dev/nst0" property "eject-before-unload" "no" property "use-slots" "1-100" property "load-poll" "0s poll 3s until 120s" } amrecover_changer "/dev/changer" and /dev/changer is a sym link to /dev/sg11 So let me explain what is /dev/sg11 ... this is the device that allows the manipulation and see the tapes and drives of the robot, for example can be used with the command mtx $ mtx -f /dev/sg11 statusSure, thanks, I know what /dev/sg11 is ;-) in my case /dev/sg21 (although that seems to change with reboots sometimes .. another topic) The difference between your and my conf is only that symlink. I directly have tpchanger "chg-robot:/dev/sg21" and amrecover_changer "/dev/sg21" - Currently I have another amrecover running. It restored from tape1 .. and now I only see these lines in the current debug file "amidxtaped.20220525123652.debug": Wed May 25 14:48:25.078884308 2022: pid 705002: thd-0x556f690aca00: amidxtaped: /usr/lib64/perl5/vendor_perl/5.32/Amanda/Restore.pm:1719:info:4900000 12472320 kb Wed May 25 14:48:40.090891256 2022: pid 705002: thd-0x556f690aca00: amidxtaped: /usr/lib64/perl5/vendor_perl/5.32/Amanda/Restore.pm:1719:info:4900000 12472320 kb Wed May 25 14:48:55.102880465 2022: pid 705002: thd-0x556f690aca00: amidxtaped: /usr/lib64/perl5/vendor_perl/5.32/Amanda/Restore.pm:1719:info:4900000 12472320 kb ... for hours now. Is that OK? Maybe tar still "scans" through that first tarball on tape ... ?
