Our set up is generally an Active/Passive SCC Exchange 2007 SP3 with an SCR target in another data centre. For some of our servers, if I run Get-StorageGroupCopyStatus, I notice that the Replay Queue Length is quite high (approx 1000), for other servers, it's quite low, about 50-100. Strangely, even the same CMS can have varying levels. We use the default Replay Lag Time. Does this indicate any problem? The Copy Queue Length is always zero. Is there anything I need to do to reduce the Replay Queue Length?

You mean to say queue length for SCR target is high for some server. Howe many SCR target you are using here. copy queue length high directly related with low band width. Do you see any BW issue between SCR source and target sites. I will suggest you to just disable and enable one databse SCR and check else you need to check BW between sites. Does event log in servers says anything ??. To enable/disable SCR DB please check below article. http://exchangepedia.com/blog/2007/12/standby-continuous-replication-replay.html http://exchangepedia.com/blog/2007/06/some-more-details-on-scr.htmlAnil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

As the copy queue lenth is 0, this indicated that the logs are shipped across tothe SCR without issues. So,probably wouldnt say it's a BW issue. Exch has a hard coded Replay Queue Length of 50 logs, i.e it wont replay logs anything smaller than this. So for those DB where you see 50 they are fine. Where you see 50-100, this woud probably be default lag time, i.e 24 hours from the time of the logs has been copied The ones I'd be worried about are ones which are 1000, I'd check the replay lag time, Get-storagegroupcopystatus and confirm. I'd check the event logs on the SCR target to see if any event are in there. Consider turning on event logging for the replication service and see what it's doing. Maybe restart the replication service (this would effect all on that targer). Might want to consider setting the lag time to something lower for thoese databases , dont forget to disable/enable SCR. The last thing you may want to do is a reseed of those DB which have a high replay log time and start fresh. Sukh

Hi, Sukh has given the details and you can try to them. And do you have any update? ThanksSophia Xu