Event ID 33680 > 32086 > 32022 Hyper V Replication Failed

Kevin Bailey 1 Reputation point
2021-01-23T21:52:40.547+00:00

Hello,

I had a replication environment setup between two server. Replication was proceeding fine until we installed Windows Security updates last Thursday. KB4535680, KB4598230, KB4598480. After we installed the windows updates (the server restarted as expected) the replications didn't resume automatically (the VM's were sitting at Replication Paused). Attempting to resume the replications immediately fail and give the following 3 errors found in the event log. 33680, 32086, 32022. I can provide the full event details if helpful.

Some investigation later, I believe it is because the System Center Virtual Machine Manager Agent service is not running. When I try to start the service I get a "Windows could not start the System Center Virtual Machine Manager Agent on Location Computer...refer to specific error code -2147217394." error. I have not been successful in resolving this. This is a production server so I am hamstring on how brute force I can approach this.

Thing's I've tried:

  • Made sure I have no more outstanding Windows Security updates.
  • Rolled back the Windows Updates install above (could not uninstall KB4598480. Windows doesn't give me the option to).
  • No HDD space issues on either the primary or replication server
  • No access issues as far as I can tell
  • Google-fu. Haven't found anything similar for 5+ years.

Environment:
Windows Server 2019 Standard version 10.0.17763 build 17763
HP ProLiant DL380p Gen8 server

System Center Virtual Machine Manager
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,545 questions

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kevin Bailey 1 Reputation point
    2021-01-23T22:40:09.067+00:00

    Update: I create a test VM on this server and was able to replicate it to a different destination successfully. When I tried to setup replication to the original pair of servers it fails complaining that the replication server must have the same or newer version of the OS that the primary server has (It does not. The replication server is Windows Server 2012 R2, primary is Windows Server 2019 Standard). My confusion is that this has been running as-is for over a year now. No other changes were made to either server except for Windows Updates the night this broke.

    0 comments
  2. Xiaowei He 9,871 Reputation points
    2021-01-25T06:42:49.583+00:00

    Hi,

    Please check if the VM configuration version in the source host is supported on the replica Server:

    If the VM's configuration version is higher on Server 2019, that not supported on Server 2012 R2, then we are unable to replicate the VM to it. The replication should be upward compatible. It's not recommended to replicate VM to lower version Hyper V host.

    60122-image.png

    https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. Kevin Bailey 1 Reputation point
    2021-01-25T12:38:13.337+00:00

    Hi Anne,

    Thanks for the reply. I checked the configuration versions on the VM's of interest, and they are all 5.0, which should be supported (and were supported) on either operating system.

    The only thing I can think of is that the windows updates broke this backwards compatibility. This is pure speculation on my part, but I just am looking at what was actually changed.

  4. Betts, Brian 1 Reputation point
    2021-03-25T16:53:28.87+00:00

    Did you find a solution for this yet?
    I have 275 store locations with 2 physical Hyper-V Hosts at each location doing replication between each other that are rebooted every 3 weeks. The primary host reboots on Thursday mornings and the secondary host reboots on Wednesday mornings. No Veeam backups are going at this time and its really random. replication is all default except for "Automatically start resynchronization" instead of using the default desired hours. 81651-image.png

    But this did not help either.

    The VM's are set to "Always Start" and "Shut Down" in the Automatic Start and Stop Actions.

    It is only when the Primary host is rebooted that we see this issue happen and Hyper-V replication is in a paused state.

    I do have a centralized script that runs daily that attempts to fix this issue but if replication gets paused on the larger VM in our environment then space issues occur on the secondary host servers.

    This seems to be a timing issue when the primary host goes down for the scheduled reboot and the VM is actively syncing data to the replica.

    I am wondering is Pausing replication before the server reboots might resolve this.

    Let me know what you find.
    Thank you,
    Brian

    0 comments
  5. Joelson Nascimento | Nowtek Soluções em Tecnologia 1 Reputation point
    2021-03-28T21:31:35.88+00:00

    Dear,

    Did you find a solution ? I have the same problem