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 suspend or resume application monitoring
After configuring application monitoring you may want to perform routine maintenance tasks on those applications. These tasks may or may not involve stopping the application but may temporarily affect the state of the applications and its dependent components. If there is any change to the application status, Cluster Server (VCS) may try to restore the application state. This may potentially affect the maintenance tasks that you intend to perform on those applications.
If stopping the application is not an option, you can suspend application monitoring and create a window for performing such maintenance tasks. When application monitoring is suspended, VCS freezes the application configuration.
The link is automatically dimmed if the application is already in maintenance mode. Conversely, if the application is not in maintenance mode, the link is dimmed.
The Veritas High Availability tab provides the following options:
To enter maintenance mode
- In the appropriate row, click More> Enter Maintenance Mode.
During the time the monitoring is suspended, Veritas high availability solutions do not monitor the state of the application and its dependent components. The Veritas High Availability view does not display the current status of the application. If there is any failure in the application or its components, VCS takes no action.
- While in maintenance mode, if a virtual machine restarts, if you want application monitoring to remain in maintenance mode, then in the Enter Maintenance Mode panel, check the Suspend the application availability even after reboot check box, and then click OK to enter maintenance mode.
To exit the maintenance mode
- In the appropriate row, click More> Exit Maintenance Mode, and then click OK to exit maintenance mode.
- Click the Refresh icon in the top right corner of the Veritas High Availability view, to confirm that the application is no longer in maintenance mode.