Familiarity with Microsoft Windows Server, Microsoft Windows Failover Cluster Server Management and Hyper-V Virtual Management procedures and commands is highly recommended.

Note: DataKeeper ClusterCluster Edition does not support Cluster Shared Volumes; therefore, when configuring Hyper-V with DataKeeper Cluster Edition, you must have one volume per virtual machine.

  1. Before you begin, all the Microsoft Windows Servers in your cluster must be installed and configured as outlined in other topics for this product (refer to “Creating a DataKeeper Volume in WSFC”). In addition, the following products must be installed and configured on each server in your cluster.
Operating Systems Microsoft Windows Server 2008 R2 or Later
Hardware Platform 64-bit environment and supports hardware-assisted virtualization (Intel VT) technology
Virtual Management Software Hyper-V role and all Hyper-V updates
SIOS DataKeeper License A DataKeeper ClusterCluster Edition license key is required for every server on which DataKeeper runs. This applies to both physical and virtual servers
Network Configuration

A high speed WAN link between the primary data center and the DR site (see performance benchmark on bandwidth configuration)
IMPORTANT: Make sure that Virtual Network Names for NIC connections are identical on all cluster nodes.

Cluster Server Software Windows Server 2008 R2, Server 2012, or later Failover Cluster Management
  1. Use the SIOS DataKeeper GUI to configure a job that includes all mirrors and shared relationships for the nodes that are part of the cluster. Wait until the mirrors are in the Mirroring state. For more information about setting up your SIOS DataKeeper environment, see the Getting Started topic.
  1. Using Hyper-V, configure the first virtual machine and make sure to specify E:\ in the Store the virtual machine in a different location text box. This setting is in the Specify Name and Location window.

  1. Select Finish and then shut down the virtual machine.
  1. Use WSFC to create a Virtual Server resource choosing to protect the first virtual machine. This option is available under Configure a Service or Application.

  1. Add a SIOS DataKeeper volume resource. Right-click on the virtual server resource created in Step #5 and choose Add a Resource, then More Resources -> Add DataKeeper Volume from the context menu.

  1. Right-click on the SIOS DataKeeper volume resource and choose Properties – DataKeeper Volume Parameters. Denote which drive letter it is associated with the DK resource (e.g. Volume E)

  1. Use Microsoft WSFC Manager, right-click on the Virtual Machine Configuration VM1 and choose Properties. In the Properties window, choose the Dependencies tab and add the New DataKeeper Volume as a dependency. Click OK.

  1. Right-click on the Virtual Machine VM1 resource and choose Start.

  1. The virtual machine is now online and highly available.

  1. Verify that Quick Migration works by right-clicking on the virtual machine resource and choose Move Virtual Machine(s) to Another Node.
  1. Verify that the virtual machine is now running on the secondary server.

  1. Simulate a catastrophic failure by pulling the power cord on secondary server and verify that the virtual machine automatically restarts on primary server.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment