Hey all, just finished setting up a SCR DR server for our main CCR cluster. All is well except I am getting an error on one SG:Standby Continuous Replication for storage group 'server\sg'is in a 'Failed' state on server 'scrsever'. The error message is: The log file 692005 for server\sg 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.The error confuses me asmy log naming convention starts with E0A000xxxxx.log not 692005It looks like the logs on the CCR box commited on the 7th.. but the log file date on SCR is the 3rd.

The log file referenced in that error is the decimal conversion of thehex log number (removing the zero padding).If the log is truly gone, then I would follow its advice and reseed with update-storagegroupcopy.Be sure to get a full backup beforehand.

To expand on what Andy is saying because he is dead on is in the error you are getting an output that the missing log is 692005. To get the log number that you are missing is open up calc (programmer mode)from windows past 69205. Change the output to Hex and you will get the number A8F25. So you can look for this log file or you can reseed you database like Andy is saying. To reseed you database please please remember that you will be copying the database file to the SCR server again. Depending on the size of the data this could take some time. suspend-storagegroupcopy <storage group name> -standbymachine <SCR server name>delete files on scr serverupdate-storagegroupcopy -id <storage group name> -standbymachine <SCR server name>resume-storagegroupcopy -id <storage group name> -standbymachine <SCR server name>Get-StorageGroupCopyStatus <storage group name> -StandbyMachine <SCR server name>Let me know if you have any questions.PS one thing you can do if you have issues finding the log files is suspending the SCR replication, copying all the log files from the mailbox server to the SCR server and hoping the log file is present. you can then try to resume SCR. This might or might not work but is worth a shot.If you have any questions please let me know. Good luckChristopher Crandallhttp:\\cbfive.comChristopher C

hey Guys... suspending and reseeding resolved the issue. I am not sure why though. I would think the seeding to a DR SCR box would have no impact on the backup of a production CCR server.

I have a similiar issue for LCR except I have tried the Update-StorageGroup Copy to reseed the LCR but it still comes up with the same error in the Event Logs.Any ideas cause I'm running out of them.....ThanxDave