> Hello,
>
> I thought I had everything working. After four days of configuring her. I
> ran
>
> su amanda -c "amdump daily" and my machine started chugging away. The tape
> lights started
>
> flashing, I thought I had it. below is the report sent by amanda, and the
> amdump.log. I
>
> am not able to find the actual *.tar.gz files. I get a tape read error when
> trying to view
>
> the contents of the tape. I tried tar tvf /dev/rmt/0bn .
First, although Amanda uses GNU tar to create the dump images, the files on
the tape are not exactly tar files; they have a 32k Amanda header at the
beginning of each image. If you want to make sure the data on the tape is
Ok, you might try using amverify or something like this:
mt rewind # Make sure tape is rewound
mt fsf 1 # Skips over the Amanda tape label/header
dd if=/dev/rmt/0n bs=32k skip=1 | /path/to/gnu_tar tvf -
That'll skip the Amanda header and feed the rest into tar for a table of
contents.
Second, there's something strange about the mail report and amdump.1 files
you included below. There should have been some hint in the email message
about why the /usr partition didn't make it onto tape. The amdump.1 file
is truncated too -- did you send the whole thing?
If that was the whole file, I'd bet that something crashed/dumped core. You
should try specifying the SysV tape device (perhaps /dev/rmt/0n) rather than
the BSD-type /dev/rmt/0bn... I seem to remember a message from John Jackson
to the effect of Amanda on Solaris expecting SysV tape semantics.
> FAILED AND STRANGE DUMP DETAILS:
>
> /-- mail.xxxx. /export lev 0 STRANGE
> sendbackup: start [mail.xxxx.org:/export level 0]
> sendbackup: info BACKUP=/usr/local/bin/gnutar
> sendbackup: info RECOVER_CMD=/usr/local/bin/gnutar -f... -
> sendbackup: info end
> ? gtar: ./home/dumps/20010814/mail.xxxx.org._export.0.tmp: file changed as
> we read it
> | Total bytes written: 283238400 (270MB, 1.1MB/s)
> sendbackup: size 276600
> sendbackup: end
> \--------
>
Third, it looks like you are backing up your Amanda holding disk. That is
bound to lead to misery! At the very least you will always get the message
above since tar is trying to archive the backup image that is being created.
Depending on how things go during an amdump run, it could also be trying to
archive the backup images of the rest of the filesystems. I think you got
lucky this time because /export was the first filesystem dumped.
If you can't put the Amanda holding disk on its own partition, you'll need
to come up with an exclude-list to make sure that tar doesn't try to dump
it. Since the art of creating an exclude-list that works is tricky, there's
a handy tool for helping to test exclude-lists, written by John Jackson,
available from:
ftp://gandalf.cc.purdue.edu/pub/amanda/gtartest-exclude
I hope this helps,
-Ben
--
Benjamin Lewis Thank goodness modern convenience is a
Database Analyst/Programmer thing of the remote future.
Purdue University Computing Center -- Pogo, by Walt Kelly
[EMAIL PROTECTED]
