< Previous  |  Next  >  
Product: Volume Replicator Guides   
Manual: Volume Replicator 4.1 Installation Guide   

Upgrading from VVR 3.5 or Later using the Product Installer

Note that Volume Replicator Administrative Services (VR-AS) has been integrated with VVR, that is, VR-AS is no longer a separate package; VR-AS is upgraded when VVR is upgraded.

This section describes the procedure for upgrading, using the VERITAS product installer. You can use the VERITAS product installer to upgrade from VVR 3.5 or later. This is the recommended method of upgrading. Prior to this however you must make sure that you have upgraded the operating system the .

To upgrade VVR only, use the VERITAS product installer and select the VERITAS Volume Replicator option. You can also use the installvvr script.

If you have multiple VERITAS products, select the option for the appropriate VERITAS product suite, and refer to the corresponding installation guide for more details. For example, if you have VERITAS Storage Foundation installed, select VERITAS Storage Foundation in the VERITAS product installer, or use the installsf script. For details, see the VERITAS Storage Foundation Installation Guide.Refer to the Getting Started Guide for a complete list of VERITAS products, including the associated installation script names and where to find documentation about installation.

If required, refer to Configuring VERITAS Volume Replicator to configure VVR after the upgrade.

Note   Note    If you have multiple VERITAS products, we strongly recommend using the option to upgrade the entire product suite rather than upgrading each product individually. This ensures that upgrade steps are done in the proper order and product interdependencies are met.

Preserving the Original VVR Configuration Using Upgrade Scripts

To upgrade to the latest version of VVR you will need to perform an OS upgrade. After OS upgrade, the VxVM version 3.5 is available. Install VxVM from the product disc to overwrite the 3.5 version with version 4.1. For more information, see the VERITAS Storage Foundation Installation Guide. Enable VVR by using the appropriate license.

This section describes the procedure that you must perform before and after upgrading to the latest VxVM version. This can be done with or without the scripts. We recommend that you perform the pre and post upgrade tasks using upgrade scripts. If you do not intend to upgrade to VVR 4.1 using upgrade scripts, refer to the section Preserving the Original VVR Configuration Without Using Upgrade Scripts.

Note   Note    The upgrade procedure retains the existing VxVM configuration. After upgrading, you can use the existing VxVM configuration, without running the vxinstall command.

To upgrade VVR, perform the following tasks in the order presented below:

  1. Preparing for the Upgrade
  2. Upgrading the VERITAS Packages
  3. Restoring the Original Configuration

Preparing for the Upgrade

  1. Make sure that the disk groups that contain RVGs are at disk group version 80 or 90, if you are upgrading from any earlier version.
  2. Make sure the size of the SRL volume is greater than 110 MB. For instructions on resizing the SRL, refer to the VERITAS Volume Replicator Administrator's Guide.
  3. Stop all the applications involved in replication. For example, if a data volume contains a file system, unmount it.
  4. Verify that all the Primary RLINKs are up-to-date on all the hosts.
      # vxrlink -g diskgroup status rlink_name
    Caution  Caution    Do not continue until the Primary RLINKs are up-to-date.
  5. Run the vvr_upgrade_start script on all hosts to save the original VVR configuration using the following command:
      # /dvd_path/volume_replicator/scripts/upgrade/vvr_upgrade_start
    Note   Note    The vvr_upgrade_start script will fail and revert back to the original configuration if it finds that the SRL size is less than 110 MB. It will stop with a message that prompts you to modify the SRL size. For detailed instructions on changing the SRL size, refer to the VERITAS Volume Replicator Administrator's Guide.
  6. Remove the existing optional packages as described in Removing the VVR Packages.

Upgrading the VERITAS Packages

  On all hosts on which the upgrade is to be performed:

  1. You must upgrade the OS to if you have an earlier version of the Operating System.
    Note   Note    After OS upgrade, the VxVM version 3.5 is available. Install VxVM from the product disc to overwrite the 3.5 version with version 4.1. For more information, see VERITAS Storage Foundation Installation Guide.

    If you are upgrading from a version of VVR prior to VVR 3.5, make sure you change the default port number to 4145, which is an IANA assigned number. To retain the existing port numbers, issue the vrport heartbeat command.

    After upgrading to VxVM 4.1 on all the required hosts, reboot the system if it has not already rebooted, using the following command:


       # /usr/sbin/shutdown -y 
  2. If the software disc is not mounted, mount it using the instructions provided in the section Mounting the Software Disc.
  3. Start the product installer:
      # cd /dvd_path
      # ./installer
  4. Select Install a Product.
  5. Select the appropriate product name:

    • If you are upgrading VVR only, use the VERITAS Volume Replicator option.
    • If you are upgrading multiple VERITAS products, select the appropriate option in the product installer to update all the VERITAS products at the same time.
      • Note   Note    If you have multiple VERITAS products, we strongly recommend using the option to upgrade the entire product suite rather than upgrading each product individually. This ensures that upgrade steps are done in the proper order and dependencies are met.

        Refer to the appropriate installation guide for detailed instructions.

  6. Follow the prompts.

    The script displays the name of the directory used for the upgrade. The upgrade directory is created in /var/tmp on the host from which the upgrade procedure was begun. The upgrade directory has the name vvr_upgrade_hostname$timestamp where the hostname is the machine being upgraded, and $timestamp is the same digit sequence as the suffix of the log file created for the current session.

    For example, the directory /var/tmp/vvr_upgrade_seattle126061743 contains the upgrade files for the host seattle.

    Note   Note    We strongly recommend you back up the upgrade directory created here, because it is used to restore the configuration.
  7. The script prompts you whether you want to configure the product at this time. If you are upgrading VVR, configure VVR after rebooting your machine.

    When the script completes, it displays messages similar to the following:


    CPI WARNING V-9-111-1114 You have completed upgrading VxVM on some or all of the systems. Reboot your systems at this time. During the reboot your default disk group will be set to rootdg for you. After a system has come up, you may configure the default disk group using the command, vxdctl defaultdg. Review the manual page for vxdctl(1M) for further details.
  8. When the upgrade completes, the hosts that are being upgraded must be rebooted. After the hosts reboot, follow the steps in Restoring the Original Configuration.

Restoring the Original Configuration

  1. On all Secondary hosts, make sure the data volumes on the Secondary are the same length as the corresponding ones on the Primary. To shrink volumes on the Secondary that are no longer of the same length as those on the Primary, use the following command on each volume on the Secondary:
      # vxassist -g diskgroup shrinkto volume_length

    where volume_length is the length of the volume on the Primary.

  2. Issue the following command on all the hosts to complete the upgrade. If a host contains only Secondary RVGs, we recommend that you first run the following command on that host:
      # /dvd_path/volume_replicator/scripts/upgrade/vvr_upgrade_finish

    The vvr_upgrade_finish script upgrades only the SRL, after which, the RVG cannot work with the earlier versions of VxVM or VVR. Also, the vvr_upgrade_finish script does not automatically upgrade the disk group version. To use the new features in this release, upgrade the disk group using the vxdg upgrade diskgroup command.

  3. Starting with VVR 4.1, a new tunable, vol_rvio_maxpool_sz, serves the same purpose as the voliomem_maxpool_sz tunable.
    Note   Note    If you have previously tuned the value of the voliomem_maxpool_sz tunable for your installation, we recommend that you set the vol_rvio_maxpool_sz tunable to be the same value for this release.
    1. Type sam to bring up the SAM interface.
    2. Use the Tab key to move the control to the SAM Areas display.
    3. Select the Kernel Configuration area to display a list of options from which you must select Kernel configuration <character Mode>. From the Kernel Configuration display select Tunables.
    4. Scroll to the required parameter and select it. Use the Modify Configurable Parameter from the Actions option to modify the parameter as follows:

      5.     vol_rvio_maxpool_sz=value;

        where the value is the same as the existing value for voliomem_maxpool_sz. If you are upgrading from any prior release, the value for voliomem_maxpool_sz is found in SAM database. The change will take effect only after the next system reboot.

    5. To use this value in the current session before reboot, run the following command on the Primary:

      6.     # vxtune vol_rvio_maxpool_sz value

        where the value is the same as the existing value for voliomem_maxpool_sz.

        Note   Note    Do not remove the voliomem_maxpool_sz tunable from the SAM database, file if VxVM is using this tunable to set the MAXPOOL size.
 ^ Return to Top < Previous  |  Next  >  
Product: Volume Replicator Guides  
Manual: Volume Replicator 4.1 Installation Guide  
VERITAS Software Corporation
www.veritas.com