Hyper-V failed to enable replication on the Replica server for the Virtual Machine


Hyper-V is not in a state to accept replication on the replica server for virtual machine 

Message appears at the end of the replication Wizard. A replica for this virtual machine had previously existed on the Replica server.


Cause

The previous successful or unsuccessful replicated virtual machine may be still exist at the replica server. 


Solution

Remove the old virtual machine at the  replica server and enable replication again.  Yes this pushes a fresh replication to the replica server.

Additional notes

Under the details of the error message on the source server a Virtual machine ID is listed, and using this ID to find the replication files from the previous replication on the Replica server (under \Virtual Hard Disks\Hyper-V Replica\Virtual hard disks\<ID>\ and under \Virtual Hard Disks\Hyper-V Replica\Virtual Machines\<ID>. These files may be locked while a previous replica exists on the Replica server



Comments

  1. WilkyJuly 23, 2014 at 4:43 PM

    It'd be great if Microsoft could add a little GUI for assisting with replication set up. Replication setup problems are harder to resolve when using certificate based authentication.

    ReplyDelete
  2. NishantApril 29, 2019 at 7:38 PM

    The solution resolved my issue. Thanks for the core solution.

    ReplyDelete

Post a Comment

Popular posts from this blog

Server Manager Refresh completed with one or more warning

The system cannot access one or more event logs because of insufficient rights The Problem: Configuration refresh message. The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider error log on the target server. Problem occurred on Server 2012 servers that have been upgraded to Server 2012R2 servers. Servers are also clustered. The Solution: Following the event logs leads to a few registry keys. You can eliminate the messages by: 1. Export the following registry keys (for safety) 2. Delete the following keys: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DxpTaskRingtone/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-Roaming/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-SCDICCOMPILER/Analytic HKLM\SOFTWARE\Mic...
Read more

Hyper-V could not replicate changes for virtual machine as replication is suspended on the Replica server

Image
EVENT ID 32088 for all VMs After running out of disk space on the Replica host server, all VMs stopped replicating.  Replication cannot simply be started by right clicking on the source VM and selecting Resume Replication. No console error message just the event log event 32088.  I considered removing replication and re-replicating but this seemed an awful lot of work for simple problem. Tried stopping the Hyper-V service on the replica host and restarting, but this also did not work. THE FIX 1. Go to the destination replica server, right click each VM and select Resume Replication.  2. Now you can go to the source server, right click each VM and select Resume Replication. For some strange reason this works. Just trying one end or the other will fail without a console error message (but shows in the event log).
Read more

Shrewsoft VPN client - can't open Access Manager

Shrewsoft VPN client - can't open Access Manager Problem Access Manager is not visible Occurred after adjusting using dual monitors. Reinstall does not fix the issue. The Fix Use regedit to rename or delete the following key: HKEY_CURRENT_USER\Software\ShrewSoft\vpn\user Had a look around the Shrewsoft support site - nothing useful in there to fix this problem.
Read more