Hello,
Dave Reeves <[EMAIL PROTECTED]> wrote:
[...]
> I guess I want
> to see what is on the second tape to see for sure if anything was dumped
> to it and figure out how to get amanda to write to the second tape. BTW,
> the entire dump is about 26 gigs, the tapes are 20 gigs.
There's all sorts of ways to look at what's on the tape. One way is to
put the tape in the drive, make sure it's rewound, and then do something
like this:
% amrestore /dev/nrsa0 no-such-host
Replace the device name as appropriate, of course. Assuming that you don't
have a host named "no-such-host", this will cause amrestore to scan the
entire tape looking for a non-existent file. As it goes merrily on its
way, it'll print out interesting stuff, including a list of the files that
are actually on the tape. Something like this:
amrestore: 0: skipping start of tape: date 20010829 label DLT000
amrestore: 1: skipping urchin.wossname.net._.20010829.1
amrestore: 2: skipping minime.wossname.net._.20010829.1
[etc.]
amrestore: 24: skipping akira.wossname.net._usr_src-all.20010829.1
amrestore: 25: skipping akira.wossname.net._usr_local.20010829.1
amrestore: 26: reached end of tape: date 20010829
If any scary errors are reported, you can probably figure that Amanda won't
be able to use the tape for restores.
Another way is to use the "dd" command. You can look at the various Amanda
headers on the tape, or even pull the files back onto disk. Here's the kind
of thing I do:
mt rewind
dd if=/dev/nrsa0 bs=32k # read the Amanda tape label
dd if=/dev/nrsa0 bs=32k count=1 # read the header for the first image
mt fsf 1 # skip the rest of the first image
dd if=/dev/nrsa0 bs=32k count=1 # read the header for the second image
dd if=/dev/nrsa0 of=/tmp/bkup.img bs=32k # read the second image into a file
dd if=/dev/nrsa0 of=/dev/null bs=32k # read and discard the entire third image
# just tests to make sure image is readable
dd .... # Keep on going through the tape
Again, scary errors are bad.
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]
