< Previous  | TOC | Index | Next  >

Upgrading VxVM only

This section explains how to upgrade VxVM. Refer to the VxVM and Solaris release support matrix to determine if upgrading the operating system is required.

If you are planning to use the installvm script to upgrade VxVM, go to Upgrading VxVM using the product installer.

There are several options to choose from if you want to use the pkgadd method to upgrade VxVM:

• An upgrade with one reboot.
  SeeUpgrading VxVM using pkgadd.
• An upgrade method which may require more than one reboot.
  See Upgrading VxVM using upgrade scripts.
• An upgrade with one reboot, which requires an alternate boot disk.
  See VxVM Live Upgrade commands and usage.

Upgrading VxVM using the product installer

You can use the product installer (installvm script) to upgrade VxVM with an encapsulated or unencapsulated root disk.

To upgrade VxVM on a remote host, rsh or ssh must be set up. See Completing the installation procedure for more information.

Upgrading VxVM using the product installer includes the following general steps:

• Run installvm to load the packages
• Do a reboot
• Run installvm to configure the 5.0 items

  ---

    Note   If you are performing a multihost installation, note that the installvm script does not support a mixture of new installations and upgrades. You should either install on all hosts or upgrade all hosts. In addition, every host to be upgraded in a multihost installation must be running the same older version of VxVM.
  
  If you use this installvm script to upgrade, do not use the upgrade_start and upgrade_finish scripts.

  ---

 To upgrade using the installvm script

1. Mount the software disc; see Mounting the software disc for instructions.
2. Remove the older VRTS packages using the pkgrm command:

   # pkgrm VRTSvras VRTSlic VRTSvmsa

   ---

     Note   Some of the above packages may not exist on your system.

   ---

3. Insert the DVD in the DVD-ROM drive.

   Once the DVD is inserted, the Solaris volume management software automatically mounts it. Change directory:

   # cd /cdrom/cdrom0/volume_manager

4. To install the software on a single host, run the following command:

   # ./installvm

   Alternatively, copy the VxVM packages and patches to a network-shared file system. You can then install the software on any systems that have mounted this file system.

   # cd /cdrom/cdrom0

   # cp -r * $NFS_FS

   # cd volume_manager

   # ./installvm -pkgpath $NFS_FS/volume_manager/pkgs

   where the NFS-mountable file system is $NFS_FS.

   If a patch is available, the installvm command must also include the patchpath as follows:

        # ./installvm -pkgpath $NFS_FS/volume_manager/pkgs \

          -patchpath $NFS_FS/volume_manager/patches
 

5. At the prompt, enter the name of the system or systems on which you want to install VxVM:

       Enter the system names separated by spaces on which to

        install VxVM:
 
  The installvm script will carry out an initial system check, and will confirm success by displaying information regarding the OS version, whether the VRTSvxvm package is installed and whether the necessary patches are installed. The initial system check might tell you that you need to obtain Solaris OS patches. If this happens, you need to see "Solaris Patch Requirements" in the Veritas Storage Foundation Release Notes.

  When the system check is complete, the installvm script displays this message:

        Initial system check completed successfully.


        Press Return to continue.

6. You will now be asked which set of packages should be installed.

   1) Required Veritas Volume Manager packages - 698MB required

   2) All Veritas Volume Manager packages - 838 MB required

   3) Storage Foundation Enterprise HA packages - 1192 MB required.

7. Select the packages to be installed.
8. After displaying a list of packages as they are copied to the system, confirm that you want to proceed with the upgrade:

   Press [return] to continue:

   installvm is now ready to upgrade VxVM

   Are you sure you want to upgrade VxVM? [y,n,q]

9. Existing VxVM packages will now be removed prior to replacement by the VxVM 5.0 packages.
10. The VxVM packages are then installed. You will see a listing of the packages displayed.
11. VxVM is now upgraded, and you should see a message stating that VxVM 5.0 has been successfully installed. You will see a message advising you to reboot.
    Reboot your system by entering:

    # /usr/sbin/shutdown -y -i6 -g0

12. To take advantage of the new features in this release, upgrade to the latest disk group version. See Upgrading CVM protocol and disk group version To confirm that the VxVM upgrade has been successful, see Verifying the Veritas Storage Foundation upgrade.
13. Now configure VxVM as described in Configuring VxVM using the installvm script.

Configuring VxVM using the installvm script

 To configure VxVM after installing the packages

1. Enter the following command

   # ./installvm -configure

   The script runs an initial system check, and will tell you that you cannot configure already configured features such as enclosure-based naming and default disk groups. However, it will lead you through the process of configuring 5.0 features, such as centralized management.

   For information about centralized management, refer to the Veritas Storage Foundation Management Installation Guide.

2. The next phase of the configuration procedure consists of setting up a centrally managed host:

   Enable Centralized Management? [y,n,q]

3. Finally, if you selected centralized management, you will be asked a series of questions relating to host names. You will also be asked the VEA agent password.
4. You should see the following message:

   Startup completed successfully on all systems

5. You are now prompted to enter an encryption key.

Upgrading VxVM using pkgadd

This section describes the procedure for upgrading using the pkgadd command. This works with both an encapsulated and unencapsulated root disk. The procedure requires only one reboot, but it overwrites the new VxVM package on the existing VxVM package.

  Note   This procedure describes how to upgrade the software on a standalone host. The system can be converted to a managed host at a later stage.

 To upgrade using pkgadd

1. If you have not already obtained and installed a VxVM 5.0 license key, do so now. See Symantec product licensing for details.
2. Bring the system down to single-user mode using the following command:

   # init S

3. If /opt is configured as a separate file system, ensure that it is mounted.
4. Stop all applications that are using VM.
5. Stop the VEA server if it is running.

   For release 3.5 MP4, use the following command:

   # /opt/VRTSob/bin/vxsvc -k

   For release 4.0 and 4.1, use the following command:

   # /opt/VRTSob/bin/vxsvcctrl stop

6. Remove all VxVM packages except for VRTSvxvm. The packages to be removed depend upon the product release.

   For release 3.5 MP4, use the following commands:

   # pkgrm VRTSvlic VRTSvmman VRTSvmdoc VRTSvmpro

   # pkgrm VRTSfspro VRTSobgui VRTSob

   For releases 4.0 and 4.1, use the following commands:

   # pkgrm VRTSvlic VRTSvmdoc VRTSvmman VRTScpi

   # pkgrm VRTStep VRTSap VRTSvrdoc VRTSvrw

   # pkgrm VRTSweb VRTSjre VRTSvcsvr VRTSvrpro

   # pkgrm VRTSfspro VRTSalloc

   # pkgrm VRTSvmpro VRTSddlpr VRTSjre VRTSperl

   # pkgrm VRTSobgui VRTSob

7. Mount the software disc. See Mounting the software disc.
8. Copy the packages to a location to which you can write and then uncompress and untar the packages:

   # cp -R /cdrom/cdrom0/volume_manager/pkgs/* /mytmp/pkgs

9. Uncompress and extract the packages using the gzcat command:

   # cd /mytmp/pkgs

   # gzcat *.gz | tar xvf -

10. The -a adminfile option should be specified to pkgadd. This adminfile must be created in the current directory, and contain the following entries:

    mail=

    instance=overwrite

    partial=nocheck

    runlevel=quit

    idepend=quit

    rdepend=nocheck

    space=quit

    setuid=nocheck

    conflict=nocheck

    action=nocheck

    basedir=default

11. Install the packages.

    While installing the VRTSobc33 package, enter n when prompted if the host will be centrally managed.

    On Solaris 10, these packages must be installed while in the global zone. If a package's pkginfo file contains the variable SUNW_PKG_ALLZONES set not equal to true, the -G option should additionally be specified to the pkgadd command.

    # pkgadd -a adminfile -d . VRTSvlic VRTSperl VRTSicsco \

      VRTSpbx VRTSsmf

    # pkgadd -a adminfile -d . VRTSat VRTSobc33 VRTSob \

      VRTSobgui VRTSccg VRTSmh

    # pkgadd -a adminfile -d . VRTSaa VRTSspt SYMClma \

      VRTSvxvm VRTSdsa VRTSfspro

    # pkgadd -a adminfile -d . VRTSvmdoc VRTSvmman VRTSdcli \

      VRTSalloc VRTSvmpro VRTSvsvc

    # pkgadd -a adminfile -d . VRTSvdid VRTSddlpr VRTSvrpro \

      VRTSvcsvr VRTSspt VRTSvsvc

    # pkgadd -a adminfile -d . VRTSjre VRTSjre15 VRTSweb \

      VRTSvrw VRTSvrdoc

12. Reboot the host:

    # shutdown -i6 -go -y

13. Start the VEA server:

    # /opt/VRTSob/bin/vxsvcctrl start

14. Register the agents:

    # /opt/VRTSobc/pal33/install/cfgsecurity.sh -a StorageAgent

    # /opt/VRTSobc/pal33/install/cfgsecurity.sh -a actionagent

    # /opt/VRTSobc/pal33/install/cfgsecurity.sh -a gridnode

15. Start the agents:

    # /opt/VRTSobc/pal33/bin/vxpalctrl -a StorageAgent -c start

    # /opt/VRTSobc/pal33/bin/vxpalctrl -a actionagent -c start

    # /opt/VRTSobc/pal33/bin/vxpalctrl -a gridnode -c start

16. Configure the license manager agent:

    # /opt/SYMClma/bin/lmautil --Config --SecurityEnabled 1 \

      --RootBrokerHostname "1" --CollectorNodeUsername "2" \

      --CollectorNodeUserDomainType "3" \

      --CollectorNodeUserDomain "4"

After you have upgraded VxVM using pkgadd, you should configure VxVM. See Configuring VxVM using the installvm script

To migrate a standalone host to a managed host, see Migrating a standalone host to a managed host.