Installing and configuring Cluster Server with Microsoft Hyper-V virtual-to-virtual clustering

The Microsoft Hyper-V role is a hypervisor-based server virtualization technology for the x86_64 architecture. It provides you with the software infrastructure and management tools that you can use to create and manage a virtualized server computing environment.

To enable VCS support for in-guest clustering, before you install VCS on the guest virtual machines, you must set up a private network between them. This involves the following steps:

To create a virtual network on the physical host

  1. From the Hyper-V manager, create two virtual networks for private LLT heartbeat communication.
  2. Assign appropriate physical interfaces to the newly-created virtual networks.

To configure the network for the virtual machines

  1. Create two network interfaces of 'Legacy Network Adaptor' type, and associate them with the newly-created virtual networks.
  2. Repeat step 1 for each virtual machine where you want to monitor application availability with VCS.

To set up a cluster of virtual (guest) machines with Cluster Server (VCS), perform the following procedures:

Note:

The installation and configuration of VCS inside a virtual machine is similar to that of the physical system. No additional VCS configuration is required to make it work inside the virtual machine.

For more details, see the Cluster Server Administrator's Guide.

Fencing support for VCS in-guest clusters

VCS supports non-SCSI3, CP server-based fencing in virtual machines to prevent corruption of data disks. SCSI3 fencing is not supported.

For information on configuring fencing, see the Veritas InfoScale Installation Guide.

Live migration support

VCS in-guest clustering continues to provide high availability of applications on virtual machines, in live migration scenarios initiated by the virtualization technology.

Veritas has tested for live migration support in the Hyper-V environment under the following conditions: