In most configurations, a DCM (Data Change Map) is used when a RL (Replicator Log) overflows. Unlike the RL; which is a transaction log, the DCM log is a simple bitmap. Each "bit" in this bitmap corresponds with a region of blocks on the replicated volume. When a write occurs within a particular region of the volume, the corresponding bit is marked as "changed" (Figure 1).
Even if the amount of data that is written to the volume is very small, the entire region will be marked as "changed" and will need to be replicated.
In some cases, a process that is running on the primary may periodically write data to the same region of a volume. If the next write occurs before the DCM has finished draining, the region may be marked as "changed" again. This may result in a situation where the same region must be replicated repeatedly and the DCM is unable to completely drain.
Note: During an initial synchronization, some or all regions are marked as "changed." The initial resynchronization is similar to cases where an SRL overflow has occurred, except that all regions containing non-zero filesystem data are marked as "changed".
WARNING: Before disabling access to a volume, verify that no open handles exist. Forcibly ending open handles will have unpredictable results, including possible data corruption.
Disabling access to a Volume (non-clustered):
1. From VEA (Veritas Enterprise Administrator), expand Replication Network.
2. Expand the RDS (Replicated Data Set).
3. Expand the primary RVG.
4. Right-click on the replicated volume(s). Select Disable Data Access.
Disabling access to a Volume (clustered):
keywords: stuck in DCM, DCM mode
Storage Foundation for Windows Volume Replicator option