>>> Put /dev/null in for your tape device when running the amdumps, then >>> set it to a real tape and do an amflush. >> >>Wasn't there a comment on this list before about using something non- >>existent (like /dev/nosuchdevice) instead of /dev/null because amanda >>was somehow 'aware' of /dev/null and would perform backups differently? > > Absolutely correct. Do **not** set tapedev to /dev/null unless you > really want Amanda to throw all your data away. That "feature" is > meant for debugging, performance test, etc. > > At 2.4.3 this changes to "null:" and "/dev/null" goes back to an older > behavior of throwing an error (since you cannot rewind it :-). But I > would still strongly recommend the "/no/such/device" technique -- you > know for certain what's going on with that. > >>Frank > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
and... what about changing /dev/sg0 and /dev/nst0 and /dev/st0 (which are my devices) permissions? c--------- 1 root tape 9, 128 Aug 8 2001 /dev/nst0 c--------- 1 backup root 21, 0 Aug 8 2001 /dev/sg0 c--------- 1 root tape 9, 0 Aug 8 2001 /dev/st0 Would this work? Or better to touch /dev/nosuchdevice and then? Point to it the changer-device or the tape-device? Thanks....
