复制操作系统或Hyper-V可以节省大量时间。但是，Hyper-V的(Hyper-V)复制(Replication)（也称为“ Hyper-V 副本(Hyper-V Replica)”）是不同的。复制过程允许您从一个虚拟机复制到另一个虚拟机环境。简而言之，它创建了一个在线虚拟机到离线虚拟机的副本。它通常对灾难恢复策略很有用。在这篇文章中，我们将分享一些常见的 hyper-v 复制错误的修复。
修复 Hyper-V 复制错误
Hyper-V复制失败的原因可能有多种。它可能是网络问题、过时的主机、完整性或其他任何问题。以下(Below)是一些常见问题和解决方法：
- 虚拟机的 Hyper-V(Hyper-V)暂停复制由于不可恢复的故障。（虚拟机 ID）。
- Hyper-V阻止启动虚拟机，因为它已准备好进行故障转移
- Hyper-V无法解析副本服务器(Replica Server)名称
- Hyper-V未处于接受虚拟机副本服务器上的复制的状态(Replica Server)
- 执行操作失败。Hyper-V未处于有效的复制状态以执行操作
有趣的是，大多数 Hyper-V 错误的发生是因为它们之间存在同步问题。主机处于维护状态，或者副本服务器离线或未准备好。
1]由于不可恢复的故障，Hyper-V暂停了虚拟机的复制。(Hyper-V)（虚拟机 ID(Machine ID)）
完整描述包括 ——Hyper-V无法复制虚拟机的更改因为副本(Replica)服务器拒绝了连接。这可能是因为副本(Replica)服务器中存在针对同一虚拟机的挂起复制操作，该操作花费的时间比预期的要长，或者存在现有连接。（虚拟机ID)
要解决，请检查以下几点：(To resolve, check on the following points:)
- 右键单击(Right-click)VM，然后选择恢复复制过程。
- 确保(Make)复制服务器在线。
- 副本(Replica)服务器应该始终有足够的空间
- 足够的(Enough)网络带宽以确保复制过程可以在一个周期内完成。
这些通常可以解决问题，但如果不能，则删除副本，然后再次重新设置复制，Microsoft建议。您必须等到同步完成。如果复制服务器长时间离线，源服务器会适应太多数据，以至于无法将其发送过来。
2] Hyper-V阻止启动虚拟机，因为它已准备好进行故障转移
设置副本服务器页面(Replica Server page)时，您需要输入副本(Replica)服务器的NetBIOS 或 FQDN( NetBIOS or FQDN)。如果副本(Replica)服务器是故障转移群集的一部分，请输入Hyper-V 副本代理(Hyper-V Replica Broker)的名称。
如果除了我们上面共享的内容之外还有其他内容，那么您将遇到此错误，因为故障转移过程无法找到它。要修复它，您必须编辑复制设置页面并将名称替换为NetBIOS或FQDN(FQDN.Once)。修复完成后，您将不会收到Hyper-V 复制错误(Hyper-V Replication Error)。
3] Hyper-V无法解析副本服务器(Replica Server)名称
与(Same)上面相同，这是一个明显的错误。如果Hyper-V 无法解析副本服务器名称( Hyper-V is not able to resolve the replica server name)，您需要检查您使用的是NetBIOS 还是 FQDN。如果您使用正确的格式，那么它是一个DNS问题。您必须检查DNS 服务器(DNS server)以找出它无法解析预期服务器(Server)地址的原因。
4] Hyper-V不处于接受虚拟机副本服务器上的复制的状态(Replica Server)
在 VM 上启用复制后，该过程会创建副本(Replica)虚拟机文件，其中存储了所有内容。这些文件夹中的每一个都有一个代表GUID的名称。它对于每个源服务器都是唯一的。如果由于某种原因，Hyper-V设置向导具有相同的UID，因为它已经配置过一次，那么您将收到此错误。由于该过程在完成之前会检查任何重复的虚拟机，因此会出现错误。
此方法的替代方法是不使用GUID。Microsoft Docs建议以下内容：
- Enable replication for the virtual machine, and ensure initial replication is not started immediately (You can choose to schedule the initial replication for a later time)
- Once Replica virtual machine is created, use the Move wizard to move the storage of the virtual machine to the path of your choice (Storage migration)
- Once the storage migration is complete, you can start the initial replication for the virtual machine
5] 执行操作失败，Hyper-V未处于有效复制状态以执行操作
它的发生有两个原因。第一种是服务器未配置为副本服务器时。因此，当源启动复制过程时，另一端不知道必须对输入做什么。第二个(Second)是服务器阻止对Rep0lication服务器上的Hyper-V的访问。(Hyper-V)
虽然第一个原因可以通过准备副本服务器来解决，但第二个原因更多的是 IT 管理员可以为您解决的防火墙问题。
我希望您能够解决这些常见的 Hyper-V 复制错误(Hyper-V Replication Errors)。我相信还有更多，所以如果您遇到任何问题，请告诉我们，我们会找到解决方案。
How to fix common Hyper-V Replication errors
Replicating an OS or Hyper-V saves a lоt of tіme. However, Replication of Hyper-V also called “Hyper-V Replica,” is different. The replication process allows you to replicate from one virtual machine to another virtual machine environment. In simple words, it creates a copy of a live virtual machine to an offline virtual machine. It is typically useful for a disaster recovery strategy. In this post, we will share fix to some of the common hyper-v replication errors.
Fix Hyper-V Replication errors
There can be multiple reasons why Hyper-V Replication may fail. It can be network issues, an outdated host, integrity, or anything else. Below are some of the common problems and resolutions:
- Hyper-V suspended replication for virtual machine <VMName> due to a non-recoverable failure. (Virtual Machine ID <VMId>).
- Hyper-V prevented starting virtual machine because it is prepared for failover
- Hyper-V Failed to resolve the Replica Server name
- Hyper-V is not in a state to accept replication on Replica Server for virtual machine <VM Name>
- Failed to perform the operation. Hyper-V is not in a valid replication state to perform the operation
It is interesting to note that most of the Hyper-V errors occur because there is a sync issue between them. Either the host is in maintenance, or the replica server is offline or not ready.
1] Hyper-V suspended replication for virtual machine due to a non-recoverable failure. (Virtual Machine ID)
The full description includes— Hyper-V could not replicate changes for virtual machine <VMName> because the Replica server refused the connection. It may be because there is a pending replication operation in the Replica server for the same virtual machine, which is taking longer than expected or has an existing connection. (Virtual machine ID <VM ID>)
To resolve, check on the following points:
- Right-click on the VM, and choose to resume the replication process.
- Make sure the replication server is online.
- Replica server should always have enough space
- Enough network bandwidth to make sure the replication process can complete in one cycle.
These can fix the problem, usually, but if it doesn’t, then delete the replica, and re-setup replication again, suggests Microsoft. You will have to wait until the synchronization is complete. If the replication server was offline for a long time, the source server acclimates so much data that it becomes impossible to send it over.
2] Hyper-V prevented starting virtual machine because it is prepared for failover
When setting up the Replica Server page, you need to enter either the NetBIOS or FQDN of the Replica server. If the Replica server is part of a failover cluster, enter the name of the Hyper-V Replica Broker.
If there is anything apart from what we shared above, then you will have this error because the failover process is not able to find it. To fix it, you will have to edit the replication setup page and replace the name with NetBIOS or FQDN.Once the fix is made, you will not receive the Hyper-V Replication Error.
3] Hyper-V Failed to resolve the Replica Server name
Same as above, and it’s a clear error. If the Hyper-V is not able to resolve the replica server name, you need to check if you are using the NetBIOS or FQDN. If you are using the correct format, then its a DNS issue. You have to check with the DNS server to find out why it is not able to resolve the expected Server address.
4] Hyper-V is not in a state to accept replication on Replica Server for virtual machine
When replication is enabled on a VM, the process creates Replica virtual machine files where everything is stored. Each of these folders has a name that represents the GUID. It is unique for each source server. If, for some reason, Hyper-V setup wizard has the same UID, because it was already configured once, then you will receive this error. Since the process checks for any duplicate virtual machine before finalizing, the error shows up.
The alternative to this method is not to use the GUID. Microsoft Docs suggests the following:
- Enable replication for the virtual machine, and ensure initial replication is not started immediately (You can choose to schedule the initial replication for a later time)
- Once Replica virtual machine is created, use the Move wizard to move the storage of the virtual machine to the path of your choice (Storage migration)
- Once the storage migration is complete, you can start the initial replication for the virtual machine
5] Failed to perform the operation, Hyper-V is not in a valid replication state to perform the operation
It happens because of two reasons. The first is when the server is not configured to be a replica server. So when the source initiates the replication process, the other end doesn’t know what has to be done with the input. Second is when the server blocks access to Hyper-V on the Rep0lication server.
While the first cause can be fixed by preparing the replica server, the second is more of a firewall issue that an IT admin can resolve it for you.
I hope you were able to resolve these common Hyper-V Replication Errors. I am sure there can be more, so if you face any, let us know, and we will find a resolution for it.
