> >The backup that I need restored is 20010213.sda5.0 from deepblue ...
> >... the files located in /var/log/amanda/DailySet1/index/deepblue/sda5,
> >which are 20010213_0 (0 byte file) and 20010213_0.gz. ...
>
> Huh? 20010213_0 is zero bytes? That's why amrecover is not happy.
> Something went wrong with the decrompress.
>
> What happens if you "zcat 20010213_0.gz | head"? Is there anything
> in there?
>
> >... Any help that anyone can provide is greatly appreciated,
> >(and needed severely, as in the case of all backup recoveries ! 8)
>
> If it's so severe, why not stop trying to use amrecover and go to
> amrestore?
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
The gzipped files are empty.
As far as amrestore goes, I have experienced issues there as well, and
decided to try to find the solution to amrecover first, for whatever
reason. The problem with amrestore is as follows:
[root@mother /bkup03]# /usr/local/amanda/sbin/amrestore
/bkup03/amanda/20010213/deepblue.sda5.0
amrestore: 0: restoring deepblue.sda5.20010213.0
gzip: stdout: File too large
Error 32 (Broken pipe) offset 1756921856+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
amrestore: skipping ahead to start of next file, please wait...
...and then it just drops back to a console prompt. If this is any clue,
the backup file(s) is rather large, the sda5.0 and sda5.0.1 files are just
over a GB each, and sda5.0.2 is almost half a gig.
I will attempt to make work first whichever I can, of course. Thanks as
always for the help, John. It is sincerely appreciated.
