I'm running Amanda 3.4 (3.4.1?) from the zmanda RPM, on an RHEL 
7.2 machine.  My client is an RHEL 6.8 machine, running the same generation of 
client, also from the zmanda RPM.

                My disklist file was as follows:

backuptest         /slash    / {
    comp-gnutar-ssh
    exclude append "./boot"
    exclude append "./var"
}
backuptest         /boot    gnutar-ssh
backuptest         /var        comp-gnutar-ssh-full

                with the thought that everything in /boot is compressed already 
anyway, and wanting to test the idea of splitting DLEs up and use different 
backup methods and the like.

                Well, the backup went OK, and running amcheckdump on the backup 
showed as OK, but when I went to recover, attempting to recover /slash for 
example, it would start trying to extract the files, and then just hang 
forever.  (Forever in this case being defined as 24 hours.)  However, when I 
tried to recover the /boot DLE, that actually worked.  So, I changed my DLEs to 
all be just plain "gnutar-ssh" type, re-ran the backup, and then attempted to 
recover again, and was successful recovering.

                I ran "ps -ef" while the amrecover process was hung, and saw 
that it had spawned a "gzip -dc" process.  So, I presume it was trying to pipe 
compressed data to that process, but somehow, either before or afterwards, it 
was getting lost on its way to the tar process.  Indeed, looking at the debug 
file, I see "amrecover: Spawning "/usr/bin/gzip /usr/bin/gzip -dc" in pipeline".

                The last thing in the debug file is "amrecover: 
send_to_tape_server: DATA-READY" until I hit ctrl-C in the amrecover window, at 
which point a "QUIT" was sent by amrecover, presumably to the amandad process 
that it was connected to.

                Any thoughts on why this wouldn't be working?  Any thoughts on 
other things I can look at?

                -Sandro

Reply via email to