SUMMARY: Problems with restore after installing PK8

From: Milligan, Eric T. (Eric.Milligan_at_ngc.com)
Date: 11/23/04

  • Next message: Bryan Mills: "Removing individual C2 user auth"
    Date: Tue, 23 Nov 2004 11:59:20 -0600
    To: "Tru64-Unix-Managers (E-mail)" <tru64-unix-managers@ornl.gov>
    
    

    Thanks to Chris Eubank and Dr. Tom Blinn for their excellent advice.

    Chris wrote:
    Create a Tar header with your fstab, sysconfig, and dump and restore
    commands used to create the backup prior to using dump on the tape :)

    Then you can just tar xvf the header and any files required for the restore,
    knowing they'll always be current.

    Dr. Blinn wrote:
    I can't speak to the details, but I strongly suspect that what you
    propose (reverting "dump" to one that was working OK for you) is
    likely to be the best and simplest solution. Be sure to test this,
    but since the patches are at least in theory subsettable, you are
    not likely to run into problems with your method. (I personally
    have found on some occasions that using older versions of layered
    components solves a problem introduced by a "bug fix" in a later
    version, and in general, older versions turn out to be completely
    compatible with a newer kernel and libraries; so using the "dump"
    from the original V4.0F kit or the one from an older patch kit is
    likely to be just fine.)

    We ended up actually doing the former, but placed it on a modified version of the OS Boot CD so as not to confuse our users with tape commands.

    ---
    Eric
    -----Original Message-----
    Hello gurus - 
    	This is a call for suggestions more than a dire need for help.  Basically, we base one of our products on machines running 4.0F with PatchKit 8 installed, and as part of the disaster recovery instructions we send out to our customers we use dump & restore on the UFS filesystems.  As recently as PatchKit 7, we've not had any problems running dump in single-user mode to backup the systems, booting off the OS CD, and using restore from there to recover the data.
    However, we're hitting an error now on restores.  The error message is "Cannot malloc space for property list."  From the release notes (http://h30097.www3.hp.com/docs/patch/40F/bl22/ReleaseNotes.pdf) I see that patch 1193 "fixes" that problem.  That patch updates not only restore but dump as well, so our theory is that problems arise when the "virgin" version of restore on the OS CD acts on files created by the patched version of dump.
    Has anyone else ran into similar problems, and if so how did you work around it?
    Our current plan of attack is to just back out patch 1193 from our PK8 systems.  That way, dump and restore would be at the "virgin" state again, as on the OS boot CD.  Suggestions?
    Thanks all,
    Eric Milligan
    

  • Next message: Bryan Mills: "Removing individual C2 user auth"

    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: 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)