Cluster Server 7.4.2 Configuration Guide for Custom Applications - Windows
- Introducing the Veritas High Availability solution for VMware
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- About the various interfaces available for performing application monitoring tasks
- Administering application monitoring using the Veritas High Availability tab
- Understanding the Veritas High Availability tab work area
- To configure or unconfigure application monitoring
- 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
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Monitoring applications across a data center
- Monitoring applications across an ESX cluster
- Searching for application instances by using filters
- Selecting multiple applications for batch operations
- Starting an application using the dashboard
- Stopping an application by using the dashboard
- Entering an application into maintenance mode
- Bringing an application out of maintenance mode
- Switching an application
- Resolving dashboard alerts
- Appendix A. Troubleshooting
- Troubleshooting application monitoring 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 Veritas High Availability view issues
- Veritas High Availability tab not visible from a cluster node
- Veritas High Availability tab does not display the application monitoring status
- Veritas High Availabilitytab may freeze due to special characters in application display name
- Veritas High Availability view may fail to load or refresh
- Operating system commands to unmount resource may fail
- Troubleshooting application monitoring configuration issues
Configuring application monitoring
Configuring an application for monitoring involves the following tasks:
Configuring the VCS cluster
This task involves selecting the virtual machines on which you want to configure monitoring and setting up the network communication links between those virtual machines.
Configuring the application
This task involves configuring the application in one of the following modes:
Start/stop mode on a single system: In the event of a failure, the application is restarted on a virtual machine for a configured number of times.
Failover mode on multiple systems: In the event of a failure, the application is first restarted on a virtual machine for a configured number of times. If the application does not restart, the virtual machine fails over to another ESX host.
When you configure an application in the failover mode, you need to select the ESX hosts where the virtual machines can fail over.