When the wrong tape is in the drive, the dump suspends - it gets all the
estimates from the other servers but when I check amstatus, I get "wait for
dumping" for each filesystem (even after manually putting the correct tape
in the drive). I ended up killing each process and running amcleanup. Once I
re-ran amdump (with the right tape), everything worked fine.
Shane
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jens Bech Madsen
Sent: Tuesday, January 02, 2001 1:43 PM
To: Amanda-Users
Subject: Re: Wrong tape / amdump question
"Shane T. Ferguson" <[EMAIL PROTECTED]> writes:
> Hi, how do I get Amanda to dump the filesystems to holding disk if it
finds
> the wrong tape in the drive (which I can manually flush them to tape at a
> later time)? I am running Amanda 2.4.2 on RH6.1 (2.2.18). The dumps work
> fine when the 'proper' tape is in the drive. It is almost like the dumps
> start but freeze up when it finds the wrong tape (even putting the correct
> tape in the drive doesn't trigger it to continue).
>
> Shane T. Ferguson
This should be the default behaviour if you have a holding disk
configured. One thing to note, though, is that Amanda doesn't do level
0 dumps to disk. Only incrementals will be dumped to holding disk if
the wrong tape is detected.
D�s the backup freeze completely and need to be terminated abnormally
or does it terminate without doing any backups? What does
amandad.debug say?
/Jens
--
Jens Bech Madsen
The Stibo Group, Denmark
