Please enter search query.
Search <book_title>...
Veritas™ High Availability 8.0.2 Solution Guide for VMware - Linux
Last Published:
2023-06-05
Product(s):
InfoScale & Storage Foundation (8.0.2)
Platform: 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
Creating a role with customized privileges for VMwareDisks agent
This section provides the steps to create a role with adequate privileges that the VMwareDisks agent can use in an ESX cluster. The assigned privileges do not include administrative or root user privileges:
To create a role
- Using the VMware vSphere Client, log on to the ESX host, and navigate to Home > Administration > Roles.
- Click Add Role.
- On the Add New Role panel, specify a name for the new role. For example, "VMwareDisks Resources Manager".
- To select privileges for the VMwareDisks Resources Manager role, in the Privileges tree, click the following check boxes.
All Privileges > Datastore > Low level file operations.
All Privileges > Virtual Machine > Configuration > Adding existing disk.
All Privileges > Virtual Machine > Change resource.
All Privileges > Virtual Machine > Configuration > Remove disk.
- Click OK.