Resynchronizing the Secondary hosts
Prev Administering the RVG Next

Resynchronizing the Secondary hosts

If the Replicator Log overflows when log protection is set to DCM or AutoDCM, then, the writes to the Primary RVG are tracked on the DCM log. To start sending these writes that are tracked on the DCM log to the Secondary, you need to perform the Resynchronize Secondaries operation.

Note:

To use this option, the Secondary must be connected to the Primary, that is they must be able to communicate with each other.

If the Primary RVG is part of cluster setup, you must connect to the host which is the cluster virtual server by using the virtual name or IP address that was used when configuring the server.

Note:

The Secondary is inconsistent from the time the resynchronization starts and until it is completed.

To resynchronize the Secondaries

  1. Select the Primary RVG and right-click. Select Resynchronize Secondaries option from the menu that appears.
  2. In the Resynchronize Secondaries dialog box, click Yes to resynchronize the Secondary hosts with the Primary node. Click No to cancel the operation.
Prev Up Next
Adding or removing the DCM logs for all volumes in an RVG Home Associating or dissociating the Replicator Log volume