Escolar Documentos
Profissional Documentos
Cultura Documentos
http://support.veritas.com/docs/275374
How to preserve the root mirror disk before applying patches or upgrading
Details:
This procedure is designed to preserve the root mirror disk before applying
patches or upgrading. It provides an efficient path for recovery if the upgrade or
patch installation is unsuccessful
The volumes associated with the root disk should have a single subdisk for each of
the root disk and root mirror plexes.
Note: The root disk-B0 subdisk is a special case, its impact can be investigated
via TechNote http://support.veritas.com/docs/231259
Disks:
rootdisk is c1t0d0s2
root mirror disk is c1t1d0s2
Note: If you have separate volumes for opt, export, home on the root disk, it is
required to define the partitions for those volumes using vxmksdpart:
# /usr/lib/vxvm/bin/vxmksdpart
Usage: vxmksdpart [-f] [-g diskgroup] subdisk sliceno [tag flags]
e.g. In following example, the opt volume subdisk is on rootmirror-05, and slice 7
is free on the mirror disk:
4. Edit the following files to make the root mirror disk bootable without VERITAS
Volume Manager (tm):
Change the c#t#d# number in above file to ensure the correct partitions will be
referenced in the vfstab file:
# touch /mnt/etc/vx/reconfig.d/state.d/install-db
Edit /mnt/etc/system and comment out following lines using the "*" character:
Before changes:
rootdev ..
set vxio ..
After changes:
* rootdev ..
* set vxio ..
If the upgrade or patching was successful, attach back mirror plex to root disk:
or
If the upgrade or patching was not successful and want to go back to mirror disk,
then follow this procedure:
Remove the partition having tag 14 and 15 from mirror disk using format
completely. Do not just change tag type, zero out these partitions and labels
before exiting from format.
The procedure if you are running VERITAS Volume Manager 3.5 and below:
# vxinstall => custom installation => choose to encapsulate current bootdisk (eg.
c1t1d0) => leave other disk alone.
It will ask whether you want to preserve Volume Manager information on another
disk, answer yes to this question
# /etc/vx/bin/vxrootmir rootdisk
# /etc/vx/bin/vxmirror rootmirror rootdisk
The procedure if you are running VERITAS Volume Manager 4.0 and above:
a. Manually start up vxconfigd to allow for the encapsulation of the root mirror:
# vxiod set 10
# vxdconfigd -m disable
# vxdctl init
# vxdisk -f init c1t0d0
# vxdctl enable
# rm /etc/vx/reconfig.d/state.d/install-db
# vxdiskadm => option 2 Encapsulate one or more disks => choose c1t1d0 (old
rootmirror) => put under rootdg
# shutdown -i6 -g0 -y
Related Documents:
Products Applied:
Volume Manager for UNIX/Linux 3.5 (Solaris), 3.5 MP1(Solaris), 3.5 MP1+PP3.1
(Solaris), 3.5 MP2 (Solaris), 3.5 MP3 (Solaris), 4.0 (Solaris), 4.0 MP1 (Solaris),
4.1 (Solaris)
Subjects:
Solaris
Application: Faq, How To, Installation, Upgrade
Volume Manager for UNIX/Linux
Application: Faq, How To, Installation, Upgrade
Languages:
English (US)
Operating Systems:
Solaris
2.6, 7.0, 7.0 (32-bit), 7.0 (64-bit), 8.0, 8.0 (32-bit), 8.0 (64-bit), 9.0, 9.0
(32-bit), 9.0 (64-bit)
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES,
EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE
LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC
SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.