On Thu, Dec 11, 2003 at 02:08:22PM -0000, Tom Brown wrote:
> Hi,
>
> I'm trying to restore from one machine onto another - The backup was created
> on a linux box running 2.4.4p1 and the backup runs fine from what i can
> tell.
>
> If i transfer one of the tapes from the autochanger and put it into a
> different machine with another tape drive attached and try and restore i get
> the following.
>
> $ amrestore -p /dev/nst0 xxxxxx /u05/backup/export | tar xfp -
> amrestore: 0: skipping start of tape: date 20031210 label xxxxxx01
> amrestore: 1: skipping xxxxxx._u05_archive.20031210.0
> amrestore: 2: skipping xxxxxx._u05_backup_rman.20031210.5
> amrestore: 3: restoring xxxxxx._u05_backup_export.20031210.0
>
> gzip: stdin: not in gzip format
> Error 32 (Broken pipe) offset 32768+512, wrote 0
> amrestore: pipe reader has quit in middle of file.
> [operator@xxxxxx amanda]$
>
> The odd thing here is that the restore works fine on the machine that made
> the backup. They are both running the same version of RedHat and Amanda. One
> drive manufacturer is HP and the other is Sony.
>
> What i don't understand is why the error points to a gzip type error when
> the backup was created using tar without compression and the extraction
> syntax does not mention that the archive should be gunzipped?
IIRC, amrestore, having no idea about the original config ..., reads the
32KB amanda header (the 32768 offset noted above) to see if tar or dump
was used and if compression was used.
I'd look at that header. You can use mt to position at the start of
file 3 on the tape, then "dd" a 32K chunk (bs=32k count=1).
Again, IIRC, amrestore has options to output the header only and to output
the dump image in raw form in a file named ...RAW. The latter would make
no attempt to uncompress or unarchive the dump. So you could use commands
like "file" to determine the type of data in the raw image.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
