Prerequisites for Microsoft Hyper-V checkpoint replication

Prerequisites for Microsoft Hyper-V checkpoint replication The following prerequisites apply to VM replication in Microsoft Hyper-V standalone and cluster configurations: Application consistent checkpoints For application consistent checkpoints, ensure that Hyper-V Integration Services is installed on the guest operating system of the virtual machine.

Prerequisites for Microsoft Hyper-V checkpoint replication

Prerequisites for Microsoft Hyper-V checkpoint replication

The following prerequisites apply to VM replication in Microsoft Hyper-V standalone and cluster configurations:

Application consistent checkpoints — For application consistent checkpoints, ensure that Hyper-V Integration Services is installed on the guest operating system of the virtual machine.

Required Hyper-V Server user privilege — You must provide user credentials for the DS-Client to access the Hyper-V Server during the replication process. Ensure that the user either has administrative privileges or has been assigned Full Control permission to all folders on both the source and destination Hyper-V Servers that will be used for replication. This includes hard disk locations of virtual machines on the source and destination Hyper-V Servers.

Examples of folders that require Full Control permission are as follows:

Standalone and cluster – C:\ProgramData\Microsoft\Windows\Hyper-V

Cluster – C:\ClusterStorage\Volume1

The following prerequisite applies to Microsoft Hyper-V checkpoint replication for standalone Hyper-V Servers:

Same drive letters — The disks in the destination Hyper-V Server must have the same set of drive letters (e.g., C:\, D:\, E:\) as the source Hyper-V Server that you plan to replicate.

The following prerequisites apply to Microsoft Hyper-V checkpoint replication for Hyper-V clusters:

Same CSV — The hard disks of highly available Hyper-V virtual machines are located in Cluster Shared Volumes (CSV). The destination Hyper-V Cluster Server must have the same set of CSV as the source Hyper-V Cluster Server. That means drive letters and paths must be identical. An example of CSV:

C:\ClusterStorage\Volume1\

C:\ClusterStorage\Volume2\

Virtual machine in current host — DS-Client can only replicate virtual machines from the current host of the Hyper-V cluster. To replicate a virtual machine from other nodes, first migrate the virtual machine to the current host of the cluster.

Existing mount point of cluster — Only use the existing mount point of the Hyper-V cluster, which was established when the cluster was created. Example: C:\ClusterStorage\Volume1 Do not use additional CSV mount points because the Failover Cluster Manager will change its mount point access while deleting a virtual machine checkpoint.

Processor compatibility (Optional) — When replicating virtual machines between two Hyper-V Servers that run on different types of processors, enable the feature Migrate to a physical computer with different processor version in the Compatibility settings of the source virtual machine.


ncG1vNJzZmirY2Ourq3ZqKWar6NjsLC5jpqqop%2Bilnqlu8KupJ6mpJbBqrvNaH%2BepKBkw3KAjWpmfYtdeLmqsc2tXGtoeJq5sXujjGR8pJmau7Wrp56jqWeAp7KzsdCuoKyhpJrAoLLOq5aGoZOnvLS7xa2WgbGgmr9uor6cn56bm6W8qrrTmKlnoKSiuQ%3D%3D

 Share!