Exchange 2013 copy queue length problem

I have an Exchange 2013 three node DAG. The servers are Mail 1, Mail 2 and Mail 3. We have several databases on Mail 1 and two are on Mail 3. Mail 2 is reporting a copy queue length of 400 and it is growing for the databases that are on Mail 3.

Does this indicate that the problem is on Mail 2 or Mail 3?  What causes a copy queue length?
wayy2beAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam FarageEnterprise ArchCommented:
You have two queues, copy queue and replay queue...

The copy queue is basically the number of logs that need to be shipped from the active copy to the passive, and the replay queue is the number of logs that are awaiting replay into the passive copy.

If you are having issues with a passive copies copy queue length, this means that there is an issue with log shipment between the Active copy and the Passive copy. This could be the MAPI / Replication network (e.g: networking issues), IPv6 being disabled or something else that is stopping the Active copy from replaying to the Passive copy.

In this situation I would try the following:

- Run Test-ReplicationHealth against the server in which the active and passive copies are hosted on:

Test-ReplicationHealth -Identity ActiveMailboxServer | FL

Open in new window


Test-ReplicationHealth -Identity PassiveMailboxServer | FL

Open in new window


- Review the Event Viewer: Application logs for replication issues between the two servers
- Look at the network layer to ensure that communication is up on the enabled REPLICATION network. You can find out which network is which by running the following:

Get-DatabaseAvailabilityGroupNetwork | FL

Open in new window


From here, look to make sure that replication is enabled on one of the two (or if a single network, make sure replication is enabled) and that the two nodes can communicate.

- Check AV on the local servers, along with firewall rules and the switches themselves for any errors.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
wayy2beAuthor Commented:
So would the problem be the passive copy on Mail 2. All the test check out ok.
0
Adam FarageEnterprise ArchCommented:
Run the following:

Get-MailboxDatabaseCopyStatus | FL 

Open in new window


Post it here..
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

wayy2beAuthor Commented:
Now we are seeing these errors from parent domain to child domain:

The call to Microsoft Exchange Active Directory Topology Service on server 'Topology ClientTcpEndpoint(localhost)' returned an error. No suitable domain controller was found in doamin 'xxx.com'

This error wqas received from a CAS server in the parent domain. The domain the error references is the child domain.

What can cause this?
0
Adam FarageEnterprise ArchCommented:
I would check that the AD Sites and Services is set properly, and that domain controllers and a global catalog server are local to the site in which Exchange is located. Remember: the site and domain in which exchange resides in requires at least one domain controller and one global catalog server.

If this is fine, then two other things I would check:

- make sure audit logging and security logging permissions are set for the Exchange Servers AD Security Group (http://bloke.org/windows/exchange-2003-2007-2010-topology-discovery-failed-error-0x80040a02-dsc_e_no_suitable_cdc/#comment-3982)
- Make sure that you did not disable IPv6 on accident
0
wayy2beAuthor Commented:
What is best practice for Exchange Windows updates?  Do you have a Microsoft cited reference that I can show to our team?
0
Adam FarageEnterprise ArchCommented:
Nothing. Just test them first, and then if all works well install them into production.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.