To ensure failover of critical applications running inside virtual machines in a VMware environment, you must install Veritas Cluster Server 6.0.2 or later on the virtual machines (guests). VCS is distributed as part of the Storage Foundation and High Availability (SFHA) stack of products.
Prior to the 6.0.2 release, if you installed VCS in a VMware virtual environment, application failover could not co-exist with VMware vMotion. The limitation existed because application failover requires shared storage between failover systems, while vMotion does not support shared storage.
VCS 6.0.2 introduces the VCS VMwareDisks agent which works around this limitation. The agent performs a storage disk attach-detach operation as required to support application failover on VCS cluster nodes.
For more information on the VCS VMwareDisks agent:
See the Storage agents section of the VCS Bundled Agents Reference Guide.
Another important feature of VCS 6.0.2 for the VMware environment is that you can perform several VCS installation, configuration, and administrative tasks directly from your vSphere Client.
Before you can perform the tasks from the vSphere Client, you must install the Symantec High Availability Console on an independent Windows system in your datacenter. When installed, the Symantec High Availability Console registers a plug-in with the vCenter Server. As a result, the Symantec High Availability tab appears in the vSphere Client Inventory view. You can perform most VCS tasks from the tab.
To learn how to install the Symantec High Availability Console, see:
Installing the Symantec High Availability Console
For more information on the Symantec High Availability Console, see:
You can perform the following tasks from the vSphere Client Symantec High Availability tab:
The complete VCS 6.0.2 documentation set is available here,
VCS documentation for other releases and platforms can be found on the SORT website.
