Exchange 2007 CCR Database copy status becomes “suspended”
Due to various reasons your CCR replication could get stopped and your Database copy status becomes “suspended”. Even though Active Database is online and working normal,
This Article will help you to manually seed the passive database and re-start your CCR replication and to change the copy status to “Healthy”
In this scenario I have my Active CCR node call “Node A” and passive node call “Node B”, and my Exchange virtual server name is “EgyEngDotCom”
Assume that your current status of the CCR copy is “suspended” if not you can use the following command to suspend the replication.
1. Suspend-StorageGroupCopy -Identity: “
Example : Suspend-StorageGroupCopy -Identity: “EgyEngDotCom\First Storage Group”
If you check your exchange management console you will see the status changed to “suspended”
2. Remove database files, all log files, and checkpoint files from the passive node.
Delete *.log, *.jrs, *.chk, and the .edb files from the configured directories (logs directory, the system files directory, and the directory hosting the database file).
3. On the passive node run the following command to seed the passive database using command shell
Example : Update-StorageGroupCopy -Identity: “EgyEngDotCom\First Storage Group”
You will see a progress bar similar to the following image
4. Once its finishes you can use following cmdlet command to resume the replication
Example : Resume-StorageGroupCopy -Identity: “EgyEngDotCom\First Storage Group”
Seeding is required under the following conditions:
- When a new passive node is introduced into a cluster continuous replication (CCR) environment and the first log file of the production storage group is not available.
- After a failover occurs in which data is lost as a result of the now passive copy having become diverged and unrecoverable.
- When the system has detected a corrupted log file that cannot be replayed into the passive copy.
- After an offline defragmentation of either copy of the database occurs.
- After a page scrubbing of the active copy of a database occurs, and you want to propagate the changes to the passive copy.
- After the log generation sequence for the storage group has been reset back to 1.