Complete the following tasks before you perform the upgrade:

• Review the Veritas Storage Foundation Cluster File System High Availability Release Notes for any late-breaking information on upgrading your system.

• Review the Symantec Technical Support website for additional information:

  http://www.symantec.com/techsupp/

• Perform the following system-level settings:

  • Set diag-level to min to perform the minimum amount of diagnostics when the system boots. Depending on the configuration of your systems you may want to re-enable this after you perform the upgrade.

    {1} ok setenv diag-level min

     diag-level=min

  • Set auto-boot? to false. For tight control when systems reboot, set this variable to false. Re-enable this variable after the upgrade.

    {1} ok setenv auto-boot? false

    auto-boot?=false

  • Deactivate cron to make sure that extraneous jobs are not performed while you upgrade the systems. Do one of the following:

    Solaris 9:

    # /etc/init.d/cron stop

    Solaris 10:

     # svcadm disable -t system/cron:default
    			

• For Solaris 10, make sure that all non-global zones are booted and in the running state before you use the Veritas product installer to upgrade the Storage Foundation products in the global zone. If the non-global zones are not mounted and running at the time of the upgrade, you must upgrade each package in each non-global zone manually.

  For Live Upgrade, if the alternative root environment also has a zone, you cannot install VRTSodm. You must remove the VRTSodm package first then install the Storage Foundation product. After you reboot the alternative root, you can install VRTSodm.

• Make sure that the administrator who performs the upgrade has root access and a good knowledge of the operating system's administration.

• Make sure that all users are logged off and that all major user applications are properly shut down.

• Make sure that you have created a valid backup.

• Ensure that you have enough file system space to upgrade. Identify where you want to copy the packages, for example /packages/Veritas when the root file system has enough space or /var/tmp/packages if the /var file system has enough space.

  Do not put the files under /tmp, which is erased during a system reboot. Do not put the files on a file system that is inaccessible prior to running the upgrade script.

  You can use a Veritas-supplied disc for the upgrade as long as modifications to the upgrade script are not required. If /usr/local was originally created as a slice, modifications are required.

• Unmount all the file systems not on the root disk. Comment out their entries in /etc/vfstab. Stop the associated volumes and deport the associated disk groups. Any file systems that the Solaris operating system or Storage Foundation assumes should be in rootdg but are not, must be unmounted and the associated entry in /etc/vfstab commented out.

• For any startup scripts in /etc/rcS.d, comment out any application commands or processes that are known to hang if their file systems are not present.

• Make sure that the current operating system supports version 6.0 of the product. If the operating system does not support it, plan for a staged upgrade.

• Schedule sufficient outage time and downtime for the upgrade and any applications that use the Veritas products. Depending on the configuration, the outage can take several hours.

• Any swap partitions not in rootdg must be commented out of /etc/vfstab. If possible, swap partitions other than those on the root disk should be commented out of /etc/vfstab and not mounted during the upgrade. Active swap partitions that are not in rootdg cause upgrade_start to fail.

• Make sure the file systems are clean before upgrading.

• Symantec recommends that you upgrade VxFS disk layouts to a supported version prior to installing VxFS 6.0. Unsupported disk layout versions 4, 5, and 6 can be mounted for the purpose of online upgrading in VxFS 6.0. You can upgrade unsupported layout versions online before installing VxFS 6.0.

• Upgrade arrays (if required).

• If replication using VVR is configured, Symantec recommends that the disk group version is at least 110 prior to upgrading.

  # vxdg list diskgroup

• If replication using VVR is configured, make sure the size of the SRL volume is greater than 110 MB.

  Refer to the Veritas Storage Foundation and High Availability Solutions Replication Administrator's Guide.

• If replication using VVR is configured, verify that all the Primary RLINKs are up-to-date on all the hosts.

  # vxrlink -g diskgroup status rlink_name

  Note:

  Do not continue until the primary RLINKs are up-to-date.

• If VCS is used to manage VVR replication, follow the preparation steps to upgrade VVR and VCS agents.

• Make sure that you have worked out all terminal emulation issues. Make sure that the terminal you use is fully functional for OpenBoot prompts and single-user and multi-user run levels.

• To reliably save information on a mirrored disk, shut down the system and physically remove the mirrored disk. Removing the disk in this manner offers a failback point.

• Determine if the root disk is encapsulated.

  See Determining if the root disk is encapsulated.