Virtual to Virtual clustering and failover

Running VCS in multiple guest virtual machines enables guest-to-guest clustering. VCS can then monitor individual applications running within the guest and then fail over the application to another guest in the virtual - virtual cluster.

Figure: Clustering between guests for application high availability

Clustering between guests for application high availability

Note:

I/O fencing support for clustering between guests for application high availability: Non-SCSI3, CP server based fencing is supported. SCSI3 fencing is not supported.

You can run VCS within each guest machine to provide high availability to applications running within the guest.

A VCS cluster is formed among the VM guests in this configuration. The VM guests in the cluster can be either on the same physical host or on different physical hosts. VCS is installed in the VM guests in the cluster. This VCS is similar to the VCS installed in the physical machine clusters. This VCS cluster manages and controls the applications and services that run inside the VM guests. Any faulted application or service is failed over to other VM guest in the cluster. This configuration does not take care of the VM guest fail-overs since VCS runs inside the VM guest.

Figure: VCS cluster across VM guests on the same physical machine

VCS cluster across VM guests on the same physical machine

Note:

I/O fencing support for a VCS cluster across VM guests on the same physical machine: Non-SCSI3, CP server based fencing is supported. SCSI3 fencing is not supported.