On Fri, May 24, 2002 at 03:23:02PM +0200, Ulrik Sandberg wrote: > On Fri, 24 May 2002, C R Ritson wrote: > > > I use (as a cron job) for both the backup and its following amverify > > run:- > > > > /usr/local/amanda/current/sbin/amdump ncl && \ > > /usr/local/amanda/current/sbin/amverify ncl \ > > >/tmp/amanda/amverify.debug 2>&1 > > What happens if you eject and then forget to switch tapes? Like in: > > amdump && amverify ; mt -f /dev/rmt/1n offline > > I think amverify prompts for a tape and then just sits there. This might > affect the following amdump in a bad way. Processes already running and > such.
Indeed it does. I had a situation (public holiday) where the tape wasn't put in for the backup. So the dumps happened to the holding disk - no problems so far. But then amverify was run (from my backup script). It found no tape and just sat there. The next day I inserted a tape to run amflush. Of course amverify saw the tape but knew that it wasn't what it wanted so exited with an error and then the script ejected the tape. Then of course amflush failed because there was not tape in the drive when it went looking for it :-) I normally manage the office in question from > 1000 km away - fortunately I was present when all this rigmarole happened, otherwise it might have been quite confusing. Next thing was to edit my script to do an 'mt status' and check the return code and only run amverify if it appears that there is a tape. Kindest regards, Niall O Broin
