Adding or removing the DCM logs from the data volumes
Prev Administering the RVG Next

Adding or removing the DCM logs from the data volumes

By default, Volume Replicator adds DCM logs to all the volumes that are part of the RVG. The DCM log is used for automatically synchronizing the Secondary, when a new Secondary is added to the RDS. If the Replicator Log overflows when the Replicator Log protection has been set to DCM or AutoDCM then the DCM logs are used for resynchronizing the Secondary. The DCM log is also used for fast-failback logging and resynchronizing the original Primary when it comes up after a disaster.

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

If a volume has a DCM log, then the right-click menu displays only the Remove DCM Log option. However, if the volume does not have a DCM log then the Add DCM Log option is available.

Note:

The Add DCM Log or Remove DCM Log option is available only if the hosts to which the volumes belong is connected to VEA.

To remove the DCM log

  1. Select the data volume and right-click. Select the Remove DCM Log option from the menu that appears.
  2. The Remove DCM Log dialog box appears.

    Click Yes to Remove the DCM Log from the selected volume. Click No to cancel the operation.

    This option is a toggle and only if the volume has a DCM log is the Remove DCM Log option displayed.

To add a DCM log

  1. Select the data volume and right-click. Select the Add DCM Log option from the menu that appears.
  2. The Add DCM Log dialog box appears.

    Click Yes to add the DCM Log from the selected volume. Click No to cancel the operation.

    This option is a toggle and only when the volume does not contain a DCM log, the Add DCM Log option displayed.

Prev Up Next
Shrinking a data volume Home Adding or removing the DCM logs for all volumes in an RVG