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
To switch an application to another system
If you want to gracefully stop an application on one system and start it on another system in the same cluster, you must use the Switch link. You can switch the application only to a system where it is not running.
Note that the Switch link is dimmed in the following cases:
If you have not configured any application components for monitoring
If you have not specified any failover system for the selected application
If the application is in maintenance mode
If no system exists in the cluster, where the application can be switched
If the application is not in online or partial state on even a single system in the cluster
To switch an application
- In the appropriate row of the application table, click Switch.
- If you want VCS to decide to which system the application must switch, based on policies, then in the Switch Application panel, click Any system, and then click OK.
To learn more about policies, see the Cluster Server Administrator's Guide.
If you want to specify the system where you want to switch the application, click User selected system, and then click the appropriate system, and then click OK.
Cluster Server stops the application on the system where the application is running, and starts it on the system you specified.