Administering the Replicated Data Set

As part of administering an RDS, you may be required to remove a Secondary or a Primary from an RDS. This section describes how to perform these tasks:

• Removing a Secondary from an RDS
• Removing a Primary RVG

Removing a Secondary from an RDS

Use the Remove Secondary task to remove a Secondary RVG from the RDS to which it belongs. You must stop replication to the specified Secondary before removing it.

  To remove a Secondary

1. Select the Secondary host name from the tree view, and then choose Replication > Remove Secondary. To use the pop-up menu, right-click the name of the Secondary, and then select Remove Secondary.
2. Click OK. A message indicates whether the Remove Secondary task succeeded or failed.

   Notes:
   Replication must be stopped to the Secondary that is being removed. The Remove Secondary task fails if replication to the Secondary is not stopped. The Remove Secondary task does not delete data volumes; it only dissociates them from the Secondary. The Replicated Data Set View displays the updated RDS configuration.

Removing a Primary RVG

The Remove Primary task removes a Primary RVG from an RDS and thus deletes the corresponding RDS.

Prerequisite for deleting a Primary RVG:

  Make sure that all the Secondary RVGs have been removed from the RDS before performing the Remove Primary task. For instructions, see Removing a Secondary from an RDS.

---

  Note    This task can only be performed from the Primary host.

---

  To remove a Primary RVG from its RDS

1. Select the Primary host name from the tree view, and then choose Replication > Remove Primary. To use the pop-up menu, right-click the name of the Primary in the tree view, and then select Remove Primary.
2. To remove the Primary RVG while the application using the Primary data volumes is active, select Force Remove.
3. Click OK. A message indicates whether the Remove Primary task succeeded or failed.

   Note:
   The Remove Primary task does not delete data volumes or the SRL from the VERITAS Volume Manager configuration.

Incrementally Synchronizing the Secondary After SRL Overflow

If the SRL overflows and log overflow protection is set to autodcm or dcm, the Secondary can be incrementally synchronized using the Replay DCM task. After the Primary and all the Secondaries reconnect, the DCM resynchronization process must be started to transfer data from the Primary to the Secondary. The Replay DCM task enables you to replay an active DCM and incrementally resynchronize the Secondary after SRL overflow.

During DCM resynchronization, VVR does not maintain the order of updates to the Secondary. As a result, the Secondary remains inconsistent until the resynchronization operation is complete. Note that if the Primary becomes unavailable during resynchronization, the applications cannot be restarted on the Secondary.

If the Secondary volumes are mirrored, you can break off mirrors to retain consistent (though out-of-date) copies of data until the resynchronization is complete. Use the snapshot feature to do this if snapshots exist.

  To incrementally resynchronize the Secondary after SRL overflow

1. From the tree view, select the name of the RDS for which you want to resynchronize the Secondary RVGs. For example, hr_rvg.
2. Choose Replication > Replay DCM. To use the pop-up menu, right-click the name of the RDS.
3. In the Replay DCM dialog box, click OK. A message indicates whether the resynchronization process succeeded or failed.

   Notes:
   Data is transmitted to the Secondaries only after all the Secondaries are connected to the Primary. All the Secondaries taking part in the resynchronization must remain connected for the resynchronization to continue. The resynchronization pauses if any of the Secondaries disconnects or is manually paused. While resynchronization is in progress, the RDS View displays the value DCM in the Logging To column.

For details about each method, refer to Transferring the Primary Role.