While implementing a couple SCR solutions, I noticed a common error I have seen while reviewing the copy status of a SCR source and target Exchange 2007 server. I noticed this problem while monitoring the health of a SCR configuration, as an example, run the following command:
Ø Get-StorageGroupCopyStatus –Identity <SourceServerStorageGroup> –StandByMachine <TargetServer> | FL
If you see storage group copy status showing “Initializing” instead of “Healthy”, check to ensure all services are running properly on both servers. You may want to consider restarting the Information Store and Replication service on both servers, if you continue to see this problem. Worst case scenario, you may have to recreate the SCR configuration for that storage group. Here is an example of how to perform those tasks:
Start by disabling SCR for the Storage Group in question:
Ø Disable-StorageGroupCopy <source server><SG in Question> –StandbyMachine <target server>
Recreate SCR for that Storage Group
Starting replication from the source server:
Ø Enable-StorageGroupCopy <source server><SG in Question> -StandbyMachine <target server> -ReplayLagTime 0.0:0:0 -TruncationLagTime 0.0:0:0
(*Note, set the replay and truncation lag time with the delay you previously defined.)
Ø Suspend-StorageGroupCopy <source server><SG in Question> –StandbyMachine <target server>
(*Note, the replication service may not respond, causing the command to not run successfully. You may have to wait five minutes before running this command.)
Seeding the target server:
Ø Update-StorageGroupCopy <source server><SG in Question> –StandbyMachine <target server>
Finalizing replication on the source server:
Ø Resume-StorageGroupCopy <source server><SG in Question> –StandbyMachine <target server>
