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 restart 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 restarts both log copying and replay of the CCR copy.

Before You Begin

To perform the following procedure, 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.


To use the Exchange Management Shell to restart replication on a cluster continuous replication copy

  1. Run the following command to restart replication for a storage group:

    Copy Code
    Resume-StorageGroupCopy -Identity:<Server\StorageGroup>
  2. Run the following command to verify that replication is restarted:

    Copy Code
    Get-StorageGroupCopyStatus -Identity:<Server\StorageGroup> |fl
    Check for the value of Suspend. If the value is False, the storage group is restarted.

For More Information

For detailed syntax and parameter information, see Resume-StorageGroupCopy and Get-StorageGroupCopyStatus.

For information about halting CCR database changes, see How to Halt Replication for a Passive Copy in a CCR Environment and Suspend-StorageGroupCopy.

For more information about managing your CCR environment, see Managing Cluster Continuous Replication.