VERITAS
Volume Manager Recovery Strategy
Scenarios...
|
More Resources by
Google: |
|
|
|
|
Gathered
By:
John Kazerooni
VERITAS
Volume Manager Recovery Strategy
Important Note: Always encapsulated and
mirror the boot disk.
To get more information about how to
encapsulate and mirror a
Boot disk click here.
IMPORTANT:
For more information, please read VERITAS Volume Manager Manuals.
Recovery
Scenarios:
-
Non-encapsulated boot disk; one disk in rootdg that
fails,
-
Non-encapsulated boot disk failure,
-
Encapsulated, un-mirrored boot disk failure and assuming
boot disk is the only disk in rootdg,
-
Encapsulated, un-mirrored boot disk failure and assuming
other disks exist in rootdg.
Non-encapsulated
boot disk; one disk in rootdg that fails:
#
vxdg init rootdg
#
vxdisksetup –i c3t9d0
#
vxdg –g rootdg adddisk disk01=c3t9d0
#
vxconfigd –k –m enable
or
#
vxdctl enable
Non-encapsulated
boot disk failure:
-
Replace your physical disk.
-
Install Solaris OS using the same host name.
-
Add VxVM packages.
-
Add VxVM licenses.
-
Delete the install-db flag file
#
rm /etc/vx/reconfig.d/stat.d/install-db
#
vxiod set 10
#
vxconfigd –k –d
#
vxdctl init host name
#
vxdctl enable
-
Edit the /etc/vfstab to
reflect the changes.
-
Mount all the necessary file systems.
-
Restore all binaries.
-
Shutdown and start the server.
Alternative:
restore the boot disk file system from backup. The VxVM binaries and all
Configuration
files, including the volroot file and VxVM licenses.
Encapsulated
un-mirrored boot disk failure and assuming boot disk is the only disk in rootdg:
Encapsulated,
un-mirrored boot disk failure and assuming other disks exist in rootdg:
#
vxlicinst
#
rm /etc/vx/reconfig.d/stat.d/install-db
#
vxiod set 10
#
vxconfigd –k –d
#
vxdctl init hostname
#
vxdctl enable
Alternative:
restore the boot disk file system from backup. The VxVM binaries and all
Configuration
files, including the volroot file and VxVM licenses.
|