My SCR log cant be purged. Test-replicationhealth cant find any error. SCR replication shows health. Does anyone meet this problem

Its very common have been seen in SCR scenario :). There may be several reason for this issue. I would suggest you to do below steps to fix it. 1. Check event log 2. Check whether you have enough free disk space in drive where LOG sits (If needed you can remove old logs which is already commited , Use eseutil /mh) 3. Restart SCR node if above option do not work 4. Finally you may need to go with reseed, which would be a lengthy work for you. Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

My SCR log cant be purged. Test-replicationhealth cant find any error. SCR replication shows health. Does anyone meet this problem Are you talking about the transaction logs? If you didn't specify the ReplayLagTime when you configured your SCR it will default to 1 day. Also, the replay will always lag behind 50 transaction logs, a hardcoded limit that you can't change. So in other words, you will always see transaction logs in the "queues" See: Standby Continuous Replication (SCR): Replay and Truncation Lag When logs will be purged is depended on your full backup schedule so make sure they run. Martina Miskovic

Hi 1. Manual delete of replayed Log Files on SCR server to free up space to allow troubleshooting. 2.Confirmed ReplayLagTime and TruncationLagTime settings. Get-mailboxdatabase |fl ReplayLagTime and TruncationLagTime value 3.First disabled SCR and than enabled leaving existing files on single DB. 4. Took full back confirmed logs on source truncated. SCR truncaiton did not start. 5. Disabled SCR on half of the SG/DB on the server. 6. Manualy deleted EDB and Log files for these SG on the Target Server. 7. Renabled SCR for these SG's using replay lag of 0.1:00:00 and trunclag 00:00:10 8. Compled full backup of all SG on source cluster. 9. confirmed Truncation and cluster.replayService truncation on source. Terence Yu TechNet Community Support

Hi 1. Manual delete of replayed Log Files on SCR server to free up space to allow troubleshooting. 2.Confirmed ReplayLagTime and TruncationLagTime settings. 3.First disabled SCR and than enabled leaving existing files on single DB. 4. Took full back confirmed logs on source truncated. SCR truncaiton did not start. 5. Disabled SCR on half of the SG/DB on the server. 6. Manualy deleted EDB and Log files for these SG on the Target Server. 7. Renabled SCR for these SG's using replay lag of 0.1:00:00 and trunclag 00:00:10 8. IS/SA/Repl services were all restarted. 9. Compled full backup of all SG on source cluster. 10. confirmed Truncation and cluster.replayService truncation on source.Terence Yu TechNet Community Support