I do a restore at the end of each month to make sure my archival backups
are doing okay. I've noticed that they've been having a problem the past
couple of months and I'm stumped as to the cause since it used to work just
fine.
Upon issuing the following command:
"amrestore /dev/nst0"
it begins restoring, creating a tar file for the first header on the tape
(/usr/src). However, when it gets to the next header (/tmp), it does not
start a new tar file. Instead, it continues appending to the same file. The
resulting tar file is enormous, and contains all of the amanda headers of the
various partitions.
The only output is:
amrestore: 0: skipping start of tape: date 20020629 label full1
amrestore: 1: restoring snoopy.mcs.drexel.edu._usr_src.20020629.0
This runs for a _long_ time, beyond the end of the actual backups on the
tape. The headers that are in the file are not corrupted in any way that I
can see:
AMANDA: FILE 20020629 snoopy.mcs.drexel.edu /tmp lev 0 comp N program /bin/tar
To restore, position tape at start of file and run:
dd if=<tape> bs=32k skip=1 | /bin/tar -f...
Funny enough, amrecover works just fine. I can recover any partition on the
tape without a problem whatsoever. This seems odd to me since it's just using
amrestore in the background, right? Also, requesting that amrestore restore
a specific partition begins at that partition (i.e. it find the start header
fine), but it does not stop at the end of that partition on the tape. What
could be causing amrecover to work okay, but amrestore to malfunction like
this?
I am running Amanda 2.4.2p2 on a redhat linux box. The version I'm running
is from the redhat rpm. I have a SDLT tape drive. I'm not sure what other
information anyone out there in Amanda-land might want to know. Any ideas
would be greatly appreciated.
