We used this, as a temporary fix. This is a file named GZIP.NULL.KLUDGE It worked when we tested it, in what I think are the circumstances you describe. The comments in it describe how to use it — but feel free to ask, if they aren’t clear.
gzip.null.kludge: #!/bin/bash # # null gzip command to fake out amanda when restoring an old dump # from an old amanda server where the server gunzips before sending # and then the client also tries to gunzip the data... which fails # # to use: # cp this-file /usr/bin/gzip.null (if not already in place) # mv /usr/bin/gzip /usr/bin/gzip.real # mv /usr/bin/gzip.null /usr/bin/gzip # amrecover ... # mv /usr/bin/gzip /usr/bin/gzip.null # mv /usr/bin/gzip.real /usr/bin/gzip # /bin/cat My “make it not happen” fix was to tell all backups to do the compression on the server. Jean-Louis was telling us that it shouldn’t be needed any more. I’ve never removed it, so I don’t know. I don’t want to chance it! Deb Baddorf Fermilab On Apr 17, 2015, at 4:16 AM, Michael Schmitz <[email protected]> wrote: > > Finally I managed to do a test with our old Amanda v2.5.2 > installation. It really worked fine with this version (using > passwordlesss SSH) although it really took a lot of time, but that's > fine. Therefore I will have to check what's been changed, that will > take some time. > >>>>>> "Michael" == Michael Schmitz <[email protected]> writes: > > Michael> Ok, I can of course do what you suggested to do a > Michael> complete restore. That's fine for now, but will there be > Michael> a real fix for this problem? > > Michael> Our old backup server is still somewhere waiting for a > Michael> new "job", and I will re-check whether the problem is > Michael> really "new".
