How to change IP address used by VVR in Veritas Storage Foundation for Windows. Volume Replicator Option.

Problem

How to change IP address used by VVR in Veritas Storage Foundation for Windows. Volume Replicator Option.

Solution

If it becomes necessary to change an IP address after the RDS (Replicated Data Set) has been created, perform the following steps:

Precautions

Before following this procedure, review the following:

1. Bind both the new and old IP addresses to a NIC before following this procedure. If an IP address that is not already bound is assigned to VVR (Veritas Volume Replicator), replication will stop and the RVGs will lose contact with each other.

2. If VVR is clustered, use the procedure that is found in the following article: https://www.veritas.com/docs/000088745

3. Create a checkpoint. The procedure for creating a checkpoint can be found here: https://www.veritas.com/docs/000088746. A checkpoint is not required to complete this procedure. However, if there is a problem restarting replication, having a valid checkpoint may avert the need for a full resynchronization.

Procedure
Using VEA (Veritas Enterprise Administrator):

1. From VEA (Veritas Enterprise Administrator), expand Replication Network.

2. Expand the RDS (Replicated Data Set).

3. Right-click on the secondary RVG (Replicated Volume Group), and select Change Replication Settings.

4. Update Primary side IP and/or Secondary side IP to reflect the new IP address(es) and click OK.

5. The rlink will be disconnected and reconnected using the new IP address and replication will be resumed, picking up where it left off.

Using the CLI (Command Line Interface):

1. Determine the rlink name for the remote host from a command line (CLI), as follows:

vxprint -l -g <diskgroup>

This lists all record information in the disk group, including Rlinks, in a verbose format. On the secondary, there can be only one Rlink per RDS. The primary may have more than one Rlink, depending on the number of secondaries.

2. Confirm that the rlink is up to date by running the following command on the primary:

vxrlink -g <diskgroup> -i <interval> status <rlink>

 

* where -i represents the interval in seconds.

 

Example: vxrlink -g oradg -i 10 status rlk_1718023

3. Pause the rlinks as follows:

On the primary:

vxrlink pause <rlink_to_seconday>

 

On the secondary:

vxrlink pause <rlink_to_primary>

4. Change the IP addresses for the rlink(s) of the primary:

On the Primary Server:

a. Change the primary IP address: vxedit set local_host=<new_primary_IP> <rlink_to_sec>

b. Change the secondary IP address: vxedit set remote_host=<new_secondary_IP> <rlink_to_sec>

5. Change IP addresses for the Rlink of the secondary:

On the secondary Server:

a. Change the secondary IP address: vxedit set local_host=<new_secondary_IP> <rlink_to_pri>

b. Change the primary IP address: vxedit set remote_host=<new_primary_IP> <rlink_to_pri>

6. Resume the rlinks as follows:

a. On the primary: vxrlink resume <rlink_to_sec>

b. On the Secondary: vxrlink resume <rlink_to_pri>