Hi Mark,
I'll put it back to the list, it might be interesting for others, too.
> > Can you amrestore the complete image to disk?
> >
> > amrestore $TAPE host /partition
>
> Yup. I have 2 level 0 amrestore images to disk, one in compressed and the
> other a whopping 10gb file (only 2.43 kernel and reiserfs would handle this).
you can do two other tricks:
- use split(1) to do nice chunks
- use a raw disk device, e.g. /dev/hdd oder /dev/hdd6
amrestore -p $TAPE host /partition | split -b 2000M
cat x* | restore rf -
amrestore -p $TAPE host /partition > /dev/hdd6
restore rf /dev/hdd6
> > Did you try the "v" flag on restore?
> >
> > amrestore -p $TAPE host /partition | restore rvf -
>
> This is where I'm at now, I'm using restore to get the files out. I'm not
> really familiar dump/restore, but it seems a bit like tar. I can list the
> files with tvf option, but this doesn't seem to be an adaquate test, as
> restore seems to store a table of contents at the beginning of the image
> rather than read thru the whole image like tar tvf will. If this latest
> version of dump/restore doesn't fix the problem, I'm stuck.
Did you already use "C" with restore to compare the dump image on tape
with the disk's content?
amrestore -p $TAPE host /partition | restore Cf -
Well, dump takes a completely different approach to backup than tar. Tar
walks through your directories. Dump unterstands the ext2 filesystem. It
searches for allocated inodes and backs up the data blocks they are
referencing to.
