asked on

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?

Thanks

Cliff

ASKER CERTIFIED SOLUTION

Lee W, MVP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

crp0499

ASKER

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 Elder

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.