vxconfigrestore does, as you state, restore the disk group configuration onto the disks private region. The content of the restoration should match the most recently saved disk group configuration. The save is done automatically when any VM object (v, pl, sd, etc., in the vxprint output) is modified.
You might need to do recovery at the volume level in order to mount the file system. The file system may need checking. No restoration of data is necessary. However (here it comes, the famous "it depends"), it depends on what you are trying to do. If the reason you need to use vxconfigrestore is that you are trying to recover public region content, then data restore might be necessary. If it is a problem you suspect has been caused by VM a data restore wouldn't be necessary. Bill On Sun, May 1, 2011 at 2:42 PM, Asiye Yigit <[email protected]> wrote: > Hello All; > > The following is in SF Troubleshooting guide. > > As far as I understood, even VxVM objects (volumes, plex, subdisks, etc.) > are recreated? > > Soi what about the data on them? We need to restore? > > Regards, > > > > If any of the disk headers are reinstalled, a saved copy of the disks’ > attributes > > is used to recreate their private and public regions. These disks are also > > assigned new disk IDs. *The VxVM objects within the disk group are then* > > *recreated using the backup configuration records for the disk group.*This > > process also has the effect of creating new configuration copies in the > disk > > group. > > _______________________________________________ > Veritas-vx maillist - [email protected] > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx > > -- William (Bill) Havey Symantec Certified HA Professional 917 515-3385
_______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
