How to change the copy queue threshold in exchange 2010 DAG

Hello,

It sounds like you do not have enough bandwith between your sites. Please use the Exchange Mailbox Role Calculator, which can be found here - http://blogs.technet.com/b/exchange/archive/2010/01/22/updates-to-the-exchange-2010-mailbox-server-role-requirements-calculator.aspx, to determine the bandwidth requirements for your environment.

JJ

how would replay queue length wary cause of WAN issues?

Regards,
Exchange_Geek

Replay queue length has nothing directly to do with WAN issues but Copy queue length does. Copy queue length represents the number of logs that are waiting to be shipped to the passive node. If you don't have enough bandwidth, new logs are generated faster than they can be shipped and you end up with the passive database being too far behind the active database. The Replication service will suspend log replay until the queue length is below the max threshold to ensure all database copies remain in sync.

JJ

12 log files is nothing 1 email can generate that in no time. The bandwidth is fine it is more a function of latency than bandwidth. I have 100mb/s connection between the sites which can replicate the logs faster than they populate but it still jumps to 12 for a few seconds and pauses log replay regularly. the start stop of the log replay is causing my log replay queues to backup to 100k+ on some databases and the only way i can get them caught back up is to reseed the database but that is a temp fix. I find it hard to believe i can't change the threshold but if that is the case the only option i see is to increase the disk I/O on the server to the point it can replay the logs even with the constant start stop of log replay. If anyone has any other ideas preferably one that can be done in software instead of hardware, i would appreciate your input. Thanks.

my utilization doesn't exceed 50% on a 30second average. As i said the copy queue isn't staying high it just hits 13 when the database gets are large email or similar activity many times during the day. The Queue goes back down to zero with in a minute but the constant start stop is where the problem is.

The replication network isn't completely seperate in the sense that i didn't purchase a dedicated circuit for exchange replication. I have a single 100mb/s point to point ENLAN connection between my primary and DR datacenters that is shared for replication of everything not just exchange. But if that was the problem i would expect to see sustained numbers in the copy queues but most of the time when i look in EMC i see 0 all the way down the list of databases.

thanks all for contributing i will upgrade the hardware to be able to replay the logs even with the start and stop.