Simon Mayr wrote:
>
> And hopefully the holding disk is not crashing at the same time as the
> backup client crashes.
Maybe this is not exactly what you meant, but I will report it anyway,
just to make clear what can happen in this world...
I *never* put a tape (or the right tape for that matter ;-)) in the
drive when AMANDA starts. This way I force all images to be copied to
the holding disk and remain there till next day. After AMANDA finishes,
a trivial script copies the files from the holding disk to an MO disk. I
use as many MO disks as tapes for this purpose. They have roughly the
same capacity too, which comes handy. When I run amflush next day, I
will have the images on both the tape and the MO disk :-)
Some days ago I started the usual daily amflush operation. In the middle
of this, a power outage occured :-(((. What happens in this case is that
some of the files in the holding disk have already been transfered to
tape, so they are not on the holding disk any more. The tape, on the
other side, did not have its headers updated (not the AMANDA headers,
but its low level headers - on my system this is done at the end of the
flushing, after the rewind command is issued), so the drive will not
find the transfered files on it. The result was that all the transfered
images were lost :-(
My double net strategy saved me: I copied the images from the MO disk
back to the holding disk and started amflush again :-)
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
