Opinions: root mirror recovery

[Bliss, Kevin L]

I am currently running Veritas vxvm version 2.5.5.  If I compare the
partition layout of my original boot disk to the mirrored disk they are not
the same.  Depending on what is being done by who (this assumes a facility
with multiple SAs), what is your comfort that everyone is going to work on a
problem in the same way with a similar knowledge base.  Add to this comfort
factor that in previous versions of Volume Manager these underlying
partitions were not all duplicated and so you were dependent on sometimes
inconsistent scripts to do the unroot.  If you are comfortable with the your
version and all of the SAs working with you then I agree.  I personally, am
comfortable with the unroot capability with version 2.5.5.

> -----Original Message-----
> From:	Richard Yates SPG [SMTP:R.J.Yates@open.ac.uk]
> Sent:	Tuesday, July 20, 1999 1:13 AM
> To:	bliss.kevin@emeryworld.com
> Cc:	ssa-managers@Eng.Auburn.EDU
> Subject:	Re: Opinions: root mirror recovery
> 
> Bliss, Kevin L writes:
> > If you are mirrored using VM and your root drive fails you should stay
> up
> > and running on the mirror.  VM should notify you that the disk has
> failed.
> > You follow the directions for removing and replacing the disk.  Once the
> > disk is replaced, format the drive using the prtvtoc you have saved.
> Now
> > there are different ways to get where you want to be (restore from tape
> and
> > encapsulate, your preferred copy method and encapsulate, or my
> preference -
> > remirror).  To remirror, at a convenient time (probably scheduled with
> > users/management) you encapsulate the disk.  After the required reboots
> for
> > encapsulation, drag the plexes out of the new bogus volumes (created by
> the
> > re-encapsulation) and drop them in the corresponding original volumes.
> One
> > the mirrors sync you are back to normal.
> 
> Why? Why? ISTR I've replaced root disks in our SSAs by simply
> replacing the disk, initialising it, & adding it as a (bootable)
> mirror. Why all this prtvtoc stuff?
> 
> Richard.
> -- 
> The Open University is not responsible for content herein, which may
> be incorrect and is used at reader's own risk.