Date: Thu, 2 Dec 2004 07:54:19 -0600
To: "Nick Barnes" <Nick.Barnes@pobox.com>, "Ken Smith" <kensmith@cse.Buffalo.EDU>
>There's no theoretical reason why the formats used by dump and
>restore shouldn't be forward and backward compatible, allowing
>an older restore (to an older filesystem type) to pick out the
>parts of the dump which make sense to it while ignoring parts
>which it doesn't understand.
>
>But they aren't, so it can't, so you're out of luck.
This is a pretty interesting issue that I didn't realize. I've
regularly
restored dumps from a Solaris 8 machine to my FreeBSD 4.x machines. (We
had data volumes on some old Solaris machines that I replaced with
FreeBSD.) I guess FreeBSD and Solaris volumes are similar enough that
the restore just worked.
Re: dump/restore dont work, handbook lies ... this all on a 7.0 freebsd system.... Did you mount the large USB file system to /mnt? ... Otherwise it wrote the dump to /mnt on the old disk which you wiped. ... Try looking at that dump file on the USB unit using 'restore -vf' ... (freebsd-questions)
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: backup ... >> get tricky if your new system that you need to restore the data to isn't ... >> sized the same as the old and isn't using the same version of dump.... eg a dump in FreeBSd 3.xx can be restore in FreeBSD 4.xx, ... And, really, for most cases of making a backup against disk failures ... (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)
