how to troubleshoot hyper-v replication issues...

I'm running four hyper-v servers hosting about 20 virtual servers and I'm using replication.

Currently, my exchange server is in a critical replication state and the report is that it has not replicated since December 6, 2017!!!

When I right click and resume replication, I get a message that a resent is needed, but when I try that, the merge starts and then goes back to error state.  I DO see a message that reads Last successful replication for virtual machine Exchange has been delayed.  Delay has exceeded the defined critical limit.  Replication might be encountering problems.

What I have done in the past is remove replication and then re-enable it.  I'm tired of that lazy approach but I'm not sure how to go about troubleshooting replication issues in Hyper-V.

Can someone give me a few basic steps to troubleshoot this?


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Unfortunately, Exchange is not supported with Hyper-V Replica.
So your problem MAY be related to this lack of support/the reason it's not supported.  

Instead of Replica, you should setup another Exchange Server and DAG support.

That said, I have replica working on an SBS 2011 server with Exchange 2010.  But there could be configuration differences that allow mine to work while yours doesn't.  Or there could be an entirely different reason yours doesn't.

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
crp0499CEOAuthor Commented:
WOW...that's interesting to know.  It's been running like this for three years and we have even failed over to it before.  It's just this random break and my fix has always been to just remove replication and start it over.  I did that last night and it's normal now.  I'll read the link and see what's up.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Check the Hyper-V and Hyper-V Replication specific event logs to see what the error is. There should be some sort of indication in there.
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

From novice to tech pro — start learning today.