Passive CCR copy must be reseeded after recovery to continue replication
- You recover an information store from a backup to its original location in Cluster Continuous Replication (CCR) cluster;
- After the recovery the storage groups have the Failed status. Windows Event Logs display errors similar to the following ones:
The log file 462 for MBX\test is missing on the production copy.
Continuous replication for this storage group is blocked.
If you removed the log file, please replace it.
If the log is lost, the passive copy will need to be reseeded using the Update-StorageGroupCopy cmdlet in the Exchange Management Shell.
Passive CCR copy must be reseeded after recovery to continue replication. Reseeding requires all transaction logs (even the ones that were committed to the database).
However Acronis Backup 11.5 backs up (and therefore restores) only the uncommitted logs.
Because of that the uncommitted logs are missing after recovery and hence the replication error is shown in the Windows Event Logs.
There are two workarounds:
- Reseed the copy manually as described in Microsoft Knowledge Base: How to Seed a Cluster Continuous Replication Copy. See Section: To use Exchange Management Console to manually seed the passive node by copying an offline database file.
- Run a full backup and then a transaction log backup of the recovered database right after the recovery. After the backup you can simply use the Update Storage Group Copy wizard to reseed passive copy as described in Microsoft Knowledge Base: How to Seed a Cluster Continuous Replication Copy. Section: To use the Update Storage Group Copy wizard to seed the passive node.