How to change an IP address that is used by VVR (Veritas Volume Replicator) in Veritas Storage Foundation for Windows - Volume Replicator Option

Introduction

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: http://www.veritas.com/docs/000088745
3. Create a checkpoint. The procedure for creating a checkpoint can be found here: http://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). Select Change Replication Settings.
4. Update Primary side IP or Secondary side IP, as needed, to reflect the new IP addresses and click OK. The Rlink will be disconnected and reconnected using the new IP address.

If replication does not start automatically, use the following steps to restart replication automatically:

1. Right-click on the secondary RVG. Select Start Replication.
2. Select Synchronize from Checkpoint.


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:
 

where -i represents the interval in seconds.

3. Pause the Rlinks as follows:
 

On the primary:  

 

On the secondary:  

4. To change IP addresses for the Rlink of the primary:

   On the primary:
   To change the primary IP address:

Note: The new primary IP that you specify must exist on the local host. This can be verified by running the command ipconfig on the primary host.

   To change secondary IP address:

Note: The new secondary IP that you specify must exist on the remote host. This can be verified by running the command ipconfig on the secondary host.

5. To change IP addresses for the Rlink of the secondary:

   On the secondary:
   To change the secondary IP address:

   To change the primary IP address:

6. Resume the Rlinks as follows:

   On the primary:

   On the Secondary:

7. If the secondary does not connect and replication does not start after step 6, perform the following operations:

   On the primary, detach the secondary :

   Attach the secondary with the checkpoint taken in step 2 :

Keywords: 245929, a245929, changing IPs, changing VVR IPs