< Previous  | TOC | Index | Next  >

Upgrading Veritas Storage Foundation on an encapsulated root disk

This section explains how to upgrade Veritas Storage Foundation if the root disk is encapsulated.

The following procedures are for Veritas Storage Foundation, Veritas Storage Foundation for DB2, Veritas Storage Foundation for Oracle, and Veritas Storage Foundation for Sybase.

  Note   If your root disk is not encapsulated, see Upgrading Veritas Storage Foundation on Solaris 8, 9, or 10.

If you are upgrading a Veritas Storage Foundation product on a system with an encapsulated root disk, you must first remove the previous release of Veritas Volume Manager.

  Note   It is important that you follow these steps in the specified order.

 To upgrade on a system with an encapsulated root disk

1. Load and mount the disc as described in Mounting the software disc. Then, follow the installation instructions.
2. Run the upgrade_check command to see the status of the root disk.

   # upgrade_check

3. Run the upgrade_start script to prepare the previous release of Veritas Volume Manager for removal:
   • If the disc is mounted automatically, enter:

     # cd /cdrom/cdrom0/storage_foundation/scripts

     # ./upgrade_start

   • If the disc is mounted manually, enter:

     # /mount_point/storage_foundation/scripts

     # ./upgrade_start

     The upgrade_start script looks for volumes containing file systems. If certain key file systems must be converted back to using partitions, the script indicates that a reboot is necessary. If any volumes are in use, you must either unmount those volumes or reboot to single-user mode.

     If any error messages are encountered during the upgrade_start process, run the upgrade_finish script immediately to restore the system. Examine the error messages and address them accordingly. Then, run the upgrade_start script again. Do not proceed to Step 3 until upgrade_start runs without producing any errors.

4. Boot the machine to single-user mode (using a command such as shutdown).
5. If the VxFS NetBackup libraries package (VRTSfsnbl) is installed, remove it before you install the new packages.

   To remove the package, use the pkgrm command as follows:

   # pkgrm VRTSfsnbl

   Respond to any system messages as needed.

   The libraries contained in this package are included in the VRTSvxfs package in 4.0.

6. Remove any existing VxVM packages.

   For example, if you are removing older VxVM packages, which could be stand-alone or part of Veritas Foundation Suite 3.5, follow this sequence:

   # pkgrm VRTSvmdoc VRTSvmman VRTSvmpro VRTSvxvm

   or

   If you have multiple versions of VxVM loaded, remove the packages using this sequence:

   # pkgrm VRTSvmdoc VRTSvmman VRTSvmpro VRTSvxvm.\*

   ---

     Note   If you have made any additional modifications or have applied any patches, remove these before removing the VRTSvxvm package. If you are using SUNWvxvm and SUNWvxva packages, see the Sun documentation for details on how to remove SUNWvxvm and SUNWvxva patches and packages.

   ---

7. If your system has separate /opt and /var file systems, make sure they are mounted before proceeding with installation. When the system is in single user mode, /opt and /var are not normally mounted.
8. Remount the disc manually.

   # mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mount_point

   where c0t6d0s2 is the default address for the DVD-ROM drive. For more information, see Mounting the software disc.

9. To invoke the common installer, run the install command on the disc as shown in this example:

   # cd /cdrom/cdrom0

   # ./installer

10. Depending on your existing configuration, various messages and prompts may appear. Answer the prompts appropriately.

    If you do not intend to view or print the online documentation, you can omit the VRTSdbdoc, VRTSfsdoc, and VRTSvmdoc packages. If you do not intend to use the GUI, you can omit the VRTSobgui package.

11. If VxFS file systems are commented out in the /etc/vfstab file, uncomment them.
12. To disable the hot-relocation feature, comment out the vxrelocd line.

    For Solaris 8 and 9, this line is in the startup file /etc/init.d/vxvm-recover.

    # vxrelocd root & commented out to disable hot-relocation

    For Solaris 10, this line is in the startup file /lib/svc/method/vxvm-recover:

    # vxrelocd root & commented out to disable hot-relocation

13. Complete the upgrade using the upgrade_finish script.

    # /mount_point/storage_foundation/scripts/upgrade_finish

14. Perform a reconfiguration reboot.

    # reboot -- -r

    At this point, your pre-upgrade configuration should be in effect and any file systems previously defined on volumes should be defined and mounted.

15. Importing a pre-5.0 Veritas Volume Manager disk group does not automatically upgrade the disk group version to the VxVM 5.0 level. You may need to manually upgrade each of your disk groups following a VxVM upgrade. See Upgrading the disk group version separately.
16. Follow the instructions in Veritas Enterprise Administrator to set up and start VEA.