Hi Guys,
I have a doubt either to Reboot the server after Replacing the disk0.
I have two disks under vxvm root mirrored and i had a problem with primary disk so i replace the disk0 failed primary disk and then mirrored. After mirroring is it reboot required ?
How did you replace the disk? (i.e) which method did you use? vxdiskadm? Well, if the disk has been replaced and mirrored, no, you need not reboot!
But, just make sure everything's fine with it.
-DB
agreed. reboot is unnecessary. however, if you can schedule downtime, you can give it a reboot to assure it is disaster proof.
no need for the reboot at all.
simply use vxdiskadm option 4 to remove the disk and then option 5 to insert the new one.
the only thing that will be different is that you will not longer see the boot-block wrapper on the root volume.
That's not the only difference. You will NOT be able to unencapsulate root if ever you need to. Refer to Veritas' documentation for workarounds.
Principally you're right. There is no need for a reboot. Thus how can you be sure, that the replace was successfull, reboot during a downtime should be done.
the in-abaility to un-encapsulate after replacing the drive must be new then because I have never seen this in almost 10 years of working with Volume Manager (since version 2.3).
As to the necessity to reboot, I am not with you there. I do not recall ever having to do a reboot after replacing the system disk when it was mirrored under VxVM and I don't recall any of the Field Engineers when I worked at Sun having to do this either. If you were forced to make a reboot, that would defeat the objective of having a mirrored root disk.
Come to think about it, when I used to teach the five day VxVM course to Suns field Engineers, I never saw this documented in their notes. Also, if this was a necessary step - no-one with mission critical servers would use the product.
Grippo,
The way we setup our root disks/mirrors, we end up with an encapsulated root disk and an initialized mirror. If the root disk goes bad, we replace it and now we are left with 2 initialized devices that hold the roovol. How do we un-encapsulate in such a scenario? vxmksdpart voodoo?