Veritas™ High Availability 8.0.2 Solution Guide for VMware - Linux
- Introducing the Veritas High Availability solution for VMware
- How the Veritas High Availability solution works in a VMware environment
- Deploying the Veritas High Availability solution
- Administering application availability
- Accessing the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Understanding the Veritas High Availability view
- Configuring a cluster by using the VCS cluster configuration wizard
- To configure or unconfigure application monitoring
- Adding a system to a VCS cluster
- To start or stop applications
- To switch an application to another system
- To add or remove a failover system
- To suspend or resume application monitoring
- To clear Fault state
- To resolve a held-up operation
- To determine application state
- To remove all monitoring configurations
- To remove VCS cluster configurations
- Administering application monitoring settings
- Appendix A. Roles and privileges
- Appendix B. Troubleshooting
- Agent logging on virtual machine
- Troubleshooting wizard-based configuration issues
- Veritas High Availability Configuration wizard displays the "hadiscover is not recognized as an internal or external command" error
- Running the 'hastop -all' command detaches virtual disks
- Validation may fail when you add a failover system
- Adding a failover system may fail if you configure a cluster with communication links over UDP
- Troubleshooting issues with the Veritas High Availability view
- Veritas high availability view is not visible from a cluster system
- Veritas High Availability view does not display the application monitoring status
- Veritas High Availability view may freeze due to special characters in application display name
- If the Console host abruptly restarts, the high availability view may disappear
- Veritas high availability view may fail to load or refresh
- Operating system commands to unmount resource may fail
Understanding operation names
Table: Task disambiguation chart describes lists the names of VCS administrative operations/tasks that you can perform from the VMware vSphere Client GUI, as well as the equivalent operation names used in Cluster Server documentation:
Table: Task disambiguation chart
vSphere Client GUI-based operations | VCS operations |
|---|---|
Start Application | Online Service Group |
Stop Application | Offline Service Group |
Switch | Switch To |
Add Failover System | Add Node |
Remove Failover System | Remove Node |
Enter Maintenance Mode | Freeze Service Group |
Exit Maintenance Mode | Unfreeze Service Group |
Clear Fault State | Clear Fault |
Resolve a Held-up Operation | Flush |
Unconfigure Application Monitoring | Delete Service Group |
Determine Application State | Probe |
Stop/Start dependent components in order | Propagate (option for online/offline SGs) |
Suspend application monitoring after reboot | Persistent (option for freeze) |