To: ict technician <ict@cardinalnewman.coventry.sch.uk>, freebsd-questions@freebsd.org
Date: Fri, 1 Oct 2004 01:49:04 +0930
On Thu, 30 Sep 2004 06:15 pm, ict technician wrote:
> I have a broken fs dump I need to fix. Is there a diagnostic/repair tool I
> can use? I know about restore -N.
>
> <No I didn't verify, and yes that was a mistake>
>
> Dump was taken on 4.10. Restoring on 5.3BETA, although I can change that.
>
A question rather than an answer:----
Is it valid to dump a ufs file system and try to restore it to a ufs2
system?
Malcolm
> Content is our Samba server home directories. I need to extract the data so
> that I can copy it to our new 2k3 server. File is big (50Gb). A full
> listing looks okay but the extract fails, apparently while skipping.
>
> supplementary question: How do I compile restore for debugging. I cannot
> find 'the magic'.
>
> Thanks
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: 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)
how to find files which are accessed at a particular time in RH8 ...agentless monitoring... Only thing is that you are better of using the command line to configure the nagios config files. ... restoring only the data that has changed from this dump.... This is to reduce the restore time as the dump is currently 15gig ... (RedHat)
how to find files which are accessed at a particular time in red hat 8 ...agentless monitoring... Only thing is that you are better of using the command line to configure the nagios config files. ... restoring only the data that has changed from this dump.... This is to reduce the restore time as the dump is currently 15gig ... (RedHat)
