>The gzipped files are empty.
Then the indexing didn't work and you won't be able to use amrecover.
I don't know why that would have happened. I'd start by looking at
the sendbackup*debug file on the client and see if there is anything
odd about the index pipeline. Then I'd make sure the server side has
proper access to gzip.
Are all your index files empty, or just some of them?
>[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
Let me guess. You're running on Linux.
You told amrestore to bring back the image as a file in the current
directory. But Linux (at least the file system you're in) has a 2 GByte
file size limit. So you can't do that with the large image you're trying
to work with.
The general solution is to use the -p option to amrestore and send the
output to a pipe. You can either send that into your restore program
and recover the files right there, or send it into split to break the
file into chunks the OS can handle, then use cat to pipe them into the
restore program later.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
