Freigeben über

Hyper-V Replica and Name Resolution

  • Artikel

I have been running Hyper-V Replica in my house for a while now.  A while ago I noticed that some of my virtual machines kept on going into a critical replication state.  It took a while for me to figure out what was happening:

1

2

Can you spot the difference between the working virtual machine and the failed one?  The failed virtual machine is replicating using the fully qualified domain name – while the working one is using the short network name.  Looking at the event log for this virtual machine confirmed that something was going wrong with name resolution:

5

Now for a confession.  I am a bit of a klutz when it comes to configuring name resolution.  For this reason my initial thought was to just change my virtual machines to all use the short network name for replication.  But there was a problem with this approach.  When you perform a planned failover using Hyper-V Replica we automatically switch to using the fully qualified domain name.

So I bit the bullet and tracked down some colleagues who were able to help me sort out my DNS server – and once that was done Hyper-V Replica was rock solid again.

Cheers,
Ben

Comments

  • Anonymous
    June 13, 2013
    The comment has been removed

  • Anonymous
    June 13, 2013
    The comment has been removed

  • Anonymous
    July 08, 2013
    I'm not seeing any issues with name resolution however I am seeing something much more imposing. Occasionally when starting a new replication the initial Replica will get to about 30 % or so then the main server the VM is on will suddenly crash.  Nothing definitive in the logs either.  

  • Anonymous
    September 01, 2013
    The comment has been removed

  • Anonymous
    December 03, 2013
    The comment has been removed