>>and... what about changing /dev/sg0 and /dev/nst0 and /dev/st0 (which >>are my devices) permissions? > > As long as you're not running as root, I guess this is OK. Seems like > a lot of work and potential for messing up to me, but whatever you're > comfortable with. > > BTW, you shouldn't be using /dev/st0 anyplace. > >>Or better to touch /dev/nosuchdevice and then? Point to it the >>changer-device or the tape-device? > > Why touch it? The whole point of the excercise is to point at a device > that does not exist, which will cause the open to fail, which Amanda > already handles. > > And you'll want to leave your tape changer out of all this. Just > comment out tpchanger in amanda.conf when going to the holding disk. > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
This is the error amanda reports when running amcheck with nosuchdevice as tapedev and changerdev... Amanda Tape Server Host Check ----------------------------- Holding disk /data0/backup-dump: 39044072 KB disk space available, that's plentyamcheck-server: could not get changer info: badly formed result from changer: "cannot open SCSI device '/dev/nosuchdevice' - No such file or directory" Amanda Backup Client Hosts Check -------------------------------- Client check: 4 hosts checked in 0.641 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) So, that will force to leave backups on holding disk till they are flushed out to a tape with amflush.. Am I right?
