 | ||
| VCS in host monitoring the Virtual Machine as a resource | ||
|---|---|---|
| Prev | Virtual machine availability | Next |
In this scenario, Cluster Server (VCS) runs in the host, enabling host-level clustering. Running VCS in the host also enables the monitoring and fail-over of individual guest virtual machines. Each guest virtual machine is simply a process in the KVM architecture and hence can be monitored by VCS running on the host. This capability allows us to monitor the individual virtual machine as an individual resource and restart/fail-over the VM on the same (or another physical) host. To enable support for guest live migration, Veritas recommends that you run Cluster Volume Manager (CVM) in the host.
In this configuration, the physical machines (PMs) hosting VM guests form a cluster. Therefore, VCS does not monitor applications running inside the guest virtual machines. VCS controls and manages the virtual machines with the help of the KVMGuest agent. If a VM guest faults, it fails over to the other host.
Note: |
The VM guests configured as failover service groups in VCS must have same configuration across all hosts. The storage for the VM guests must be accessible to all the hosts in the cluster. |
Network configuration for VCS cluster across physical machines (PM-PM)