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 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/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.
VCS stops the application on the system where the application is running, and starts it on the system you specified.