How to Upgrade VERITAS Volume Replicator (VVR, formerly VERITAS Storage Replicator for Volume Manager (SRVM)

Article:TECH9618  |  Created: 2001-01-26  |  Updated: 2002-01-12  |  Article URL http://www.symantec.com/docs/TECH9618
Article Type
Technical Solution

Environment

Issue



How to Upgrade VERITAS Volume Replicator (VVR, formerly VERITAS Storage Replicator for Volume Manager (SRVM)

Solution



If VVR (SRVM) is already installed, perform the following steps:

Upgrading Volume Replicator From 1.x to 3.1.1

Do the following steps on all the Primary and Secondary nodes, except for step 4.

Caution: Do not omit steps 2-5. It is important to follow all the steps given below, otherwise, the system will panic repeatedly.

1. If Dynamic Multi-Pathing Software (DMP) is disabled, enable DMP before upgrading to this release of VVR (SRVM) as follows:

    a. To verify whether DMP is disabled or not, use the following command:

      # ls -l /dev/vx/dmp /dev/vx/rdmp

    If DMP is disabled, the output looks like this:
    (If it does not, DMP is already enabled.)
    lrwxrwxrwx 1 root other 8 Jan 5 12:48 /dev/vx/dmp -> /dev/dsk
    lrwxrwxrwx 1 root other 9 Jan 5 12:48 /dev/vx/rdmp ->/dev/rdsk

    b. If DMP is disabled, enable DMP. To enable DMP, run the following command:

      # rm /dev/vx/dmp /dev/vx/rdmp

2. Stop all the applications involved in replication. For example, if a data volume contains a file system, unmount it.

3. Stop all the Replicated Volume Groups (RVGs).

      # vxrvg -g <dg_name> stop <rvg_name>

4. On the Primary, verify that all the RLINKs are up-to-date.

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

    # vxrlink -g <dg_name> status <rlink_name>

5. To make sure that there is no replication until the upgrade is complete, detach the RLINK from the RVG.

    # vxrlink -g <dg_name> det <rlink_name>

6. Disassociate the Storage Replicator Log (SRL) volume from the RVG.

    # vxvol -g <dg_name> dis <srl_name>

7. If DRL logs exist on any of the data volumes or SRL volumes, remove them.

    # vxassist remove log <log_name> nlog=0

8. After step 7, the procedure for upgrading SRVM is the same as the procedure for upgrading Volume Manager.

To upgrade VVR (SRVM)

Refer to the VERITAS Volume Manager Installation Guide, and follow the steps in the section, "Upgrading VxVM Only."

To upgrade VVR (SRVM) and Solaris

Refer to the VERITAS Volume Manager Installation Guide, and follow the steps in the section, "Upgrading to VxVM and Solaris."

To upgrade Solaris only

Refer to the VERITAS Volume Manager Installation Guide, and follow the steps in the
section, "Upgrading Solaris Only."

Notes:

a. VERITAS Volume Manager Installation Guide says to install the new version using the pkgadd command. It is a better idea to install this version over the existing version. Do not remove the existing version before installing the package if root is encapsulated. If removing  the existing version first, reboot the system before adding the new package.

b. The tunables, nmcom_max_memory, volio_max_memory, and volnm_rdbk_max_memory that were used in the previous release of SRVM no longer exist. These tunables have been replaced by voliomem_max_nmcompool_sz, voliomem_max_memory, and voliomem_max_readbackpool_sz. Replace the old tunable names in the /etc/system file with the new tunable names. For details, see the Storage Replicator for Volume Manager Configuration Notes and the Storage Replicator for Volume Manager Administrator's Guide.

c. If the pkgrm command on VxVM fails in single user mode, perform the pkgrm command in multiuser mode.

9. Obtain the VVR (SRVM) license key and install the VVR (SRVM) license. If this has been done, skip this step.
   
            # vxlicense -c

10. If the system was not rebooted in step 8, reboot the system.

    # reboot -- -r

11. Associate the SRL to the RVG.

    # vxvol -g <dg_name> aslog <rvg_name> <srl_name>

12. Recover the RLINK.

    # vxrlink -g <dg_name> recover <rlink_name>

If the following error message comes up, ignore it:

    RLINK rlinkname is already recovered.

13. Attach the RLINK to the RVG.

    # vxrlink -g <dg_name> -f att <rlink_name>

14. Start the RVG.

    # vxrvg -g <dg_name> start <rvg_name>

Note: Importing a pre-3.x Volume Manager disk group does not automatically upgrade the disk group version to the VxVM 3.x level. Manually upgrade each disk group following a VxVM upgrade.To use the Automatic Synchronization and SRL Overflow Protection with DCM features, upgrade all disk groups to the VxVM 3.x level.

List all disk groups using:

    #vxdg list

Upgrade all disk groups to the latest version using:

    #vxdg upgrade <dg_name>

Upgrading Volume Replicator From 3.0.2 and 3.1 to 3.1.1

1. Pause the Primary RLINK using the following command:

    # vxrlink pause rlink_name

The RLINK does not need to be up-to-date.

2. To upgrade from VVR 3.0.2 or VVR 3.1 to VVR 3.1.1, upgrade VxVM on the Primary and Secondary nodes. For instructions, see the section, "Upgrading to VxVM 3.1.1" in the
VERITAS Volume Manager Installation Guide.

3. Resume the Primary RLINK using the following command:

    # vxrlink resume rlink_name

Note: The upgrade procedure allows the retaining of the existing VxVM configuration. After upgrading, VxVM can be used as before without running the vxinstall command.


Legacy ID



234167


Article URL http://www.symantec.com/docs/TECH9618


Terms of use for this information are found in Legal Notices