<div>
Any errors on the event viewers on both servers? That's the starting point for all exchange server troubleshooting
</div>


Any errors on the event viewers on both servers? That's the starting point for all exchange server troubleshooting

vmich

<div>
I found the issue.<br />
There was a problem with the DAG network that we had the replication running across so once I removed it from there and had it go across the MAPI network, all was good.<br />
We only have 1 database and 2 servers in the DAG, so Microsoft always says that if the environment is small like 2 servers in the dag, you can run it across the mapi network.
</div>


I found the issue.
There was a problem with the DAG network that we had the replication running across so once I removed it from there and had it go across the MAPI network, all was good.
We only have 1 database and 2 servers in the DAG, so Microsoft always says that if the environment is small like 2 servers in the dag, you can run it across the mapi network.

<div>
seems that I mentioned issue with network and storage. this should have assisted with resolution. good deal.
</div>


seems that I mentioned issue with network and storage. this should have assisted with resolution. good deal.

<div>
<div class="content wysiwyg-content">
We have 2 servers running exchange 2013 in a DAG setup. All of a sudden the passive server keeps having its copy queue length continuing to go up after I run the commands to get it back to 0. <br />
What do I need to look at to see what is causing the passive server to have its copy queue length to continue to go up?<br />
Also if I restart the cluster service on both servers, then all goes back to good for a while
</div>
</div>


We have 2 servers running exchange 2013 in a DAG setup. All of a sudden the passive server keeps having its copy queue length continuing to go up after I run the commands to get it back to 0. 
What do I need to look at to see what is causing the passive server to have its copy queue length to continue to go up?
Also if I restart the cluster service on both servers, then all goes back to good for a while

Issue with exchange 2013 Passive server in DAG having its copy queue length continue to go up

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Golang, also called Go, is an open source programming language that is a statically-typed language with syntax loosely derived from C, adding automatic memory management, type safety, some dynamic-typing capabilities, additional built-in types such as variable-length arrays and key-value maps, and a large standard library. Go is a general-purpose systems programming language that aims to be efficient both for development and execution with a focus on fast compilation and increased maintainability of large projects. Go was originally targeted at systems programming tasks such as building server/web applications, high throughput middleware and databases.