Hi, John:
Thanks very much for your reply!
O.K., I tried that "dd" command, and my output looks a little more
civilized (no "drive busy" messages now):
# dd if=/dev/rmt/0mn bs=32k skip=1 | ufsrestore -tvbf 2 -
Verify volume and initialize maps
0+0 records in
0+0 records out
Volume is not in dump format
Do you think there may be a problem with the way I did the dump?
I used this command:
amsdump Daily
Thanks!
Lisa
> To: Lisa Becktold {CADIG STAFF} <[EMAIL PROTECTED]>
> cc: [EMAIL PROTECTED]
> Subject: Re: questions about amsdump/ufsrestore
> Date: Mon, 27 Nov 2000 16:42:19 -0500
> From: "John R. Jackson" <[EMAIL PROTECTED]>
>
> >I'm assuming that the "program "DUMP"" parameter will utilize the
> >local dump utility, which is "ufsdump". ...
>
> It will use the local dump utility associated with the file system type
> as determined at run time. For instance, it (automatically) flips around
> between ufsdump and vxdump on my Solaris systems.
>
> >If this is so, shouldn't
> >I be able to use "dd" to access tape contents, and pipe it to
> >"ufsrestore"? I've tried this:
> >
> > dd if=/dev/rmt/0mn bs=64k skip=1 | ufsrestore -tv
>
> You **must** use 32k on the dd. That's the block size Amanda uses and
> anything is is not going to work right.
>
> The main problem, though, is that you forgot a parameter on ufsrestore,
> and it's trying to read the tape at the same time dd is. Do it this way:
>
> dd if=/dev/rmt/0mn bs=32k skip=1 | ufsrestore -tvbf 2 -
>
> It's the 'f' and '-' flag and argument that tell ufsrestore to read
> from stdin. The 'b' and '2' flag and argument tell it to read in small
> chunks (1 KByte), which is needed by some restore programs when dealing
> with piped input.
>
> >Lisa
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
----------------------------------------------------------
Lisa M. Becktold - [EMAIL PROTECTED], (410) 293-6480
United States Naval Academy - CADIG
590 Holloway Road, Rickover Hall, Annapolis, MD 21402-5000
