ssh hangs when restoring

From: Nicolas Ecarnot (nicolas.ecarnot_at_alussinan.org)
Date: 07/28/03 

Date: 28 Jul 2003 10:26:05 GMT

Hello,

I'm using dump and restore to backups my systems.
I dump a filesystem on host1 in a file /tmp/myFile.dump with the command :
dump -af /tmp/myFile.dump /var (for example)

Then, I try to restore it on another host (host2).
>From host2, I use :

ssh someUser@host1 cat /tmp/myFile.dump | restore -tvf -

All this works, restore actually displays the listing, but at the end, it
hangs.

Some people told me the problem came from ssh not closing a 'buffer', and
restore waiting ssh to close this stream.

I don't know how to avoid that, and don't exactly know who to ask for.

Maybe some of you already had this problem ? 

-- 
Nicolas Ecarnot

Relevant Pages

  • Re: DFSMSdss Data Loss Exposure (UPDATE)
    ... PATCH BYTE FOR DS1DSCHA / DS1IND20 ON FULL AND TRACKS RESTORE ... TRACKS RESTORE when DFSMSdss is not invoked via the API. ... This future enhancement would possibly include a change in default RESTORE behavior based on use of "RESET" in DUMP, with a new RESTORE option to allow for overriding default behavior. ... The crux of the problem is that the only practical way to make a physical copy of a volume with DFSMSdss for moving the volume or recovering it elsewhere is with "DUMP FULL" physical dump, and if this is recovered to another device with the obvious counterpart "RESTORE FULL", the result is currently not an identical volume, but a volume with all the VTOC "changed" bits on the volume reset. ...
    (bit.listserv.ibm-main)
  • DFSMSdss Data Loss Exposure (Was Re: DFSMSdss DOC APAR OA20117)
    ... which is the default usage, indicating the dump is not intended as a replacement for individual dataset dumps -- to save the image of a DASD volume and expecting at some point to use this dump with a "RESTORE FULL" to move the volume to another DASD drive, as part of a Data Center move or migration to new equipment, or for Data Center recovery at a remote site, THEN MOST LIKELY YOU ARE CURRENTLY EXPOSED TO SOME FORM OF DATA-LOSS! ... The crux of the problem is that the only practical way to make a physical copy of a volume with DFSMSdss for moving the volume or recovering it elsewhere is with "DUMP FULL" physical dump, and if this is recovered to another device with the obvious counterpart "RESTORE FULL", the result is currently not an identical volume, but a volume with all the VTOC "changed" bits on the volume reset. ...
    (bit.listserv.ibm-main)
  • Re: Recommendations for home backup solution
    ... > backup if possible. ... Dump is a great command to dump file systems to just about ... To restore files, ...
    (Fedora)
  • Re: problems with Nice and Dump in FreeBSD 6.1-Current (Stable-#5)
    ... nice: shell built-in command. ... I use this for a dump ... and then on a restore ... which fills up the screen with seemingly corruption ...
    (freebsd-questions)
  • Re: DFSMSdss Data Loss Exposure (UPDATE)
    ... APAR OA20907 was opened by IBM to provide a temporary fix to the DFSMSdss RESTORE problem in the form of ADRDSSU patch byte that can be set by an installation or on a specific invocation of ADRDSSU to inhibit the reset of the DS1DSCHA bit on "RESTORE FULL" or "RESTORE TRACKS". ... This future enhancement would possibly include a change in default RESTORE behavior based on use of "RESET" in DUMP, with a new RESTORE option to allow for overriding default behavior. ... The crux of the problem is that the only practical way to make a physical copy of a volume with DFSMSdss for moving the volume or recovering it elsewhere is with "DUMP FULL" physical dump, and if this is recovered to another device with the obvious counterpart "RESTORE FULL", the result is currently not an identical volume, but a volume with all the VTOC "changed" bits on the volume reset. ...
    (bit.listserv.ibm-main)