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
To view the status of configured applications
In the application dependency graph, click the application for which you want to view the status. If the appropriate row is not already visible, the application table automatically scrolls to the appropriate row. The row displays the state of the application for each configured failover system in the cluster for that application.
If you click any system in the row, a component dependency graph appears. The graph uses symbols, color code, and tool tips to display the health of each application component. Roll the mouse over a system or component to see its health details.
The health of each application/application component on the selected system is displayed in terms of the following states:
Table: Application states
State | Description |
|---|---|
Online | Indicates that the configured application or application components are running on the virtual machine. If the application is offline on at least one other failover system, an alert appears next to the application name. |
Offline | Indicates that the configured application or its components are not running on the virtual machine. |
Partial | Indicates that either the application or its components are being started on the virtual machine or VCS was unable to start one or more of the configured components If the application is offline on at least one other failover system, an alert appears next to the application name. |
Faulted | Indicates that the configured application or its components have unexpectedly stopped running. |