How to Halt Replication for a Passive Copy in a CCR Environment
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2006-12-20
This topic explains how to use the Exchange Management Shell to stop log copying and log replay in a cluster continuous replication (CCR) environment. You may need to temporarily stop replication to seed the storage group or perform some other administrative operation. Log copying is part of the CCR replication mechanism. Transaction log replay is the mechanism for advancing the database copy. It reads the log data and updates the database file with changes from the log data. CCR changes the database copy by replaying log files whenever new log files are available.
|This procedure halts both log copying and replay of the CCR copy.|
To perform the following procedures, the account you use must be delegated the following:
Exchange Server Administrator role and local Administrators group for the target server
For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
|Suspending replication activities on a storage group prevents the replication support from replaying any logs into the database and prevents log copying from the source to the target. Try to minimize the amount of time that a copy has replication halted. The passive copy is not providing the best protection from failure during this time.|
Run the following command to suspend replay for the storage group:
Suspend-StorageGroupCopy -Identity:<Server\StorageGroup> -suspendcomment:<Comment>
|The Suspend-StorageGroupCopy cmdlet halts all replication activities to the storage group copy.|
Run the following command:
|Check for the value of Suspend. If the value is True, the storage group is suspended.|
For information about restarting CCR database changes, see How to Restart Replication for a Passive Copy in a CCR Environment and Resume-StorageGroupCopy.
For more information about managing your CCR environment, see Managing Cluster Continuous Replication.