Hyper-v无法启用复制,错误代码0x00002EE2 RRS feed

  • 问题

  • 在虚拟机环境下安装 两台 server 2016 搭建 Hyper-v 单机对单机复制。两台服务器均加入域,并各安装一个 Hyper-v 虚拟机,运行 server 2016。主域控在其中一台 Hyper-v 服务器上。两台服务器相关的防火墙均开放 80、443 端口,两台 Hyper-v 虚拟机中也勾选了允许作为副本机,并使用 Kerberos 的验证方式。四台服务器可以相互 ping 通。但始终无法启用复制,找了很多国内外的解决方法均没成功。例如组策略检测是否允许网络访问该主机,DNS 后面添加后缀,服务器各个时间是否对上等。 不知是否和 AD 上提示的错误信息有关,望大神指教。
    2019年5月27日 2:07


  • 终于找到了原因,副本服务器指的是承载着另一个 Hyper-v 的服务器,而不是 Hyper-v 本身。
    2019年5月27日 9:58
  • 您好,






    1. Describe the configuration of Hyper-V Replica.

    Enabling Replication on the Replica Server:

    • In Server Manager, click Tools, and then click Hyper-V Manager.
    • In the Actions pan, click Connect to Server (right pane), type ServerName, and then click OK.  (or just click the server name if it is already there)
    • Click Hyper-V Manager.
    • Click ServerName.
    • Click Hyper-V Settings(right pane)
    • Click Replication Configuration(left pane)
    • Turn on Checkbox to “Enable this computer as a Replica server”
    • Make sure Use Kerberos (HTTP): is checked Specify the port:  80
    • Click Allow replication from any authenticated server
    • Type the location you would like to put replicas
    • Click OK

    Initial Virtual Machine Replication:

    • In Hyper-V Manager, Select the Virtual Machine you wish to replicate
    • In Task Pane (right Pane) select Enable Replication (this is also available on the right click menu)
    • Click Next on Before You Begin
    • Type or Browse to the Replica Server (remember, this is the name of the destination server that will receive the replica) then Click Next
    • Make sure Compress the data that is transmitted over the network is turned ON then Click Next
    • Replica Server Authentication – After Replica server for virtual machine replication is enabled, configuration of specific authentication types and ports for incoming replication traffic is required.
    • Two authentication options are available. Kerberos authentication (using HTTP), which does not allow the data you send across the network will not be encrypted or certificate-based authentication (using HTTPS), which does encrypt the data sent across the network.
    • Chose Recovery History options as desired (ex. Additional Recover Points = 4, Replicate incremental VSS every 4 hours)

    Recovery points contain one or more snapshots. The options presented allow for keeping the latest recovery point for restoring your primary virtual machine on the Replica server, or allow the ability to maintain multiple recovery points on your server. When choosing the multiple recovery points option, remember that more storage would be required on the Replica server. Additionally, when specification at to the number of recovery points is utilized, the Enable Replication Wizard specifies how much storage is needed. Recovery points are created every hour, but the Replica server receives frequent and regular changes from the primary server, so that your primary and Replica servers stay synchronized.

    • Click Send initial copy over the network and Start replication immediately then Click Next
    • Turn on the drives you want to replicate then Click Finish

    2. Describe the requirements about Hyper-V Replica.

    • Hardware that supports the Hyper-V role on Windows Server 2012. Keep in mind that hardware-assisted virtualization is available in processors that include a virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology. In addition, hardware-enforced Data Execution Prevention (DEP) must be available and enabled.
    • Sufficient storage on both the primary server and Replica server to host the files used by virtualized workloads.
    • Network connectivity between the locations hosting the primary and Replica servers.
    • Properly configured firewall rules to permit replication between the primary and Replica sites.
    • You need to use certificate-based authentication if you want transmitted data to be encrypted. Use an X.509 v3 certificate to support mutual authentication with certificates.

    3. Why the function can be enable after Windows Server 2012?

    When it comes to high-availability in Hyper-V Server 2012, two options are available:

    • Quick migration – this option was already available in Windows Server 2008 and is built on top of Windows failover-clustering. Basically it is a failover cluster where the Virtual Machines are configured as cluster resources. In the case of a failover, the Virtual Machines are stopped, they failover to the other cluster node and are started again. This always comes with some downtime;
    • Live migration – Live migration was introduced in Windows Server 2008 R2 and is also built on top of Windows failover-clustering. In this case, a failover cluster is built and, again, the Virtual Machines are cluster resources as well. But in a failover, the VMs do not stop but keep running during the failover. The entire running machine is brought to the other cluster node without any downtime.

    Both options are intended to improve availability for Hyper-V but there still is no rapid Disaster Recovery with either of them. To make good this omission, Windows Server 2012 brings a rapid Disaster Recovery solution by means of Hyper-V Replica. 

    4. Which port is used for HTTP and which port is used for HTTPS? Can these port numbers be changed?

    HTTP Port: 80

    HTTPS Port: 443

    We can change these Port number.

    5. Which are firewall exception about Hyper-V Replica?

    Hyper-V Replica HTTP Listener(TCP-In)

    Hyper-V Replica HTTPS Listener(TCP-In)

    6. Why we need to select VHD during enable replication?

    The Virtual Machine configuration file (XML) will be replicated to the Replica Server in any case but if you select VHD files unnecessarily, it will put extra overhead on the Replication Engine on the Primary Server and more network bandwidth will be used for a VHD file which need not be replicated. The wizard cannot work out which VHD file belongs to the Operating System and which one belongs to the data. You might have noticed that “Choose Replication VHDs” configuration page talks about excluding the “Paging file”. Well, you can configure a second VHD on the IDE controller and move the paging file to that location and then do not select the paging file VHD during “Choose Replication VHDs” configuration page.

    All VHD files including paging VHD file must be replicated once. Once the initial replication is completed, break and re-enable the replication but this time, do not select the paging VHD file. This way, the paging file VHD will not be replicated to the Replica Server which saves a lot of bandwidth.

    7. How many types of the operation in Hyper-V replica failover operations?

    For any Primary and Replica Virtual Machine in a Hyper-V Replica environment, there are three types of failover operations available. Some of the failover tests can be used for the Primary Virtual Machine and some can be used for Replica Virtual Machine.

    • Test Failover (TFO)
    • Planned Failover (PFO)
    • Unplanned Failover (UFO)

    Reference link:

    8. What is the difference between Hyper-V Replica and Live Migration?

    Live Migration is a synchronous replication, Hyper-V Replica is an asynchronous synchronous replication, Live Migration has only one data, Hyper-V Replica has two data.

    9. What is the difference between Hyper-V Replica and export/import VM?

    Export and import virtual machines can only copy the current state of virtual machines, can not be updated, and there is no disaster recovery function.

    10. Why define Hyper-V Replica as asynchronous replication?

    After Completing the initial replication, Hyper-V Replica sends VM changes on a frequent schedule. These changes are tracked in a log file, which is compressed before it is sent to the Replica server. On the primary server, changes are maintained in an .hrl file that is in the same location as the VHDS that are being replicated.

    11. Troubleshooting about Hyper-V Replica.

    • Check the bandwidth of the network
    • Collect VMMS Trace and process monitor.
    • Check the requirements for Hyper-V Replica.

    12. When will the checkpoint be deleted during the initial replication phase?

    It will be deleted after the initial replication is completed.

    13. What are the ways to transfer the initial replicated VHD to the replica server?

    • Send initial copy over the network.
    • Send initial copy using external network.
    • Use an existing virtual machine on the Replica server as the initial copy.

    14. How do we see the status of the virtual machine on the replica server? Where can we see the status of the last replicated virtual machine?

    15. For the VMs in cluster, why do we need to use Hyper-V Replica Broker?

    Failover clustering gives us a role called the Hyper-V Replica Broker. The role of the broker is:

    Primary Site Identification: The entire primary site cluster will be identified for Hyper-V Replica purposes using the computer name of the broker. This simplifies policy creation in the secondary site; you authorize the broker instead of each cluster node.

    Secondary Site Administration: The secondary site is configured once, in the broker’s settings, instead of managing the Hyper-V Settings of each node in the cluster. The settings are automatically synchronized throughout the entire cluster.

    There is an additional use of the Hyper-V Replica Broker; you normally should configure inbound replication from the secondary site to the primary site. This allows you to reverse replication, which is required for a planned failover




    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    2019年5月28日 2:13
  • 您好,




    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    2019年5月30日 6:15