Veritas High Availability 7.4.2 Solution Guide for VMware - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Linux
  1. Introducing the Veritas High Availability solution for VMware
    1. How the Veritas High Availability solution works in a VMware environment
      1.  
        How the Veritas HA Plug-in for vSphere Web Client works with VCS
      2.  
        How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
      3.  
        Getting started with vCenter-integrated Veritas High Availability solution
      4. Getting started with the VIOM-integrated Veritas High Availability solution
        1.  
          About administering high availability with VOM
      5. Understanding Veritas High Availability terminology
        1.  
          Understanding operation names
      6.  
        Supported VMware versions
      7.  
        Important release information
  2. Deploying the Veritas High Availability solution
    1.  
      Managing storage
    2.  
      Installing the Veritas High Availability guest components
    3.  
      Upgrading Veritas High Availability guest components
  3. Administering application availability from the vSphere Client
    1.  
      Accessing the Veritas High Availability view
    2. Administering application monitoring from the Veritas High Availability view
      1. Understanding the Veritas High Availability view
        1.  
          To view the status of configured applications
      2.  
        Configuring a cluster by using the VCS cluster configuration wizard
      3.  
        To configure or unconfigure application monitoring
      4.  
        Adding a system to a VCS cluster
      5.  
        To start or stop applications
      6.  
        To switch an application to another system
      7.  
        To add or remove a failover system
      8.  
        To suspend or resume application monitoring
      9.  
        To clear Fault state
      10.  
        To resolve a held-up operation
      11.  
        To determine application state
      12.  
        To remove all monitoring configurations
      13.  
        To remove VCS cluster configurations
    3.  
      Administering application monitoring settings
    4. Administering application availability using Veritas High Availability dashboard
      1. Understanding the dashboard work area
        1.  
          Aggregate status bar
        2.  
          ESX cluster/host table
        3.  
          Taskbar
        4.  
          Filters menu
        5.  
          Application table
      2. Accessing the dashboard
        1.  
          Prerequisites for accessing the dashboard
        2.  
          How to access the dashboard
        3.  
          Who can access the dashboard
      3.  
        Monitoring applications across a data center
      4.  
        Monitoring applications across an ESX cluster
      5.  
        Searching for application instances by using filters
      6.  
        Selecting multiple applications for batch operations
      7.  
        Starting an application using the dashboard
      8.  
        Stopping an application by using the dashboard
      9.  
        Entering an application into maintenance mode
      10.  
        Bringing an application out of maintenance mode
      11.  
        Switching an application
      12.  
        Resolving dashboard alerts
  4. Appendix A. Roles and privileges
    1.  
      About the roles and privileges assigned in vCenter
    2. Assigning customized privileges to VMwareDisks agent
      1.  
        About assigning privileges to VMwareDisks agent
      2.  
        Creating a role with customized privileges for VMwareDisks agent
      3.  
        Creating an ESX user account
      4.  
        Integrating an ESX user account with Active Directory
      5.  
        Assigning a role to an ESX user account
  5. Appendix B. Troubleshooting
    1.  
      Agent logging on virtual machine
    2. Troubleshooting wizard-based configuration issues
      1.  
        Veritas High Availability Configuration wizard displays the "hadiscover is not recognized as an internal or external command" error
      2.  
        Running the 'hastop -all' command detaches virtual disks
      3.  
        Validation may fail when you add a failover system
      4.  
        Adding a failover system may fail if you configure a cluster with communication links over UDP
    3. Troubleshooting issues with the Veritas High Availability view
      1.  
        Veritas high availability view is not visible from a cluster system
      2.  
        Veritas High Availability view does not display the application monitoring status
      3.  
        Veritas High Availability view may freeze due to special characters in application display name
      4.  
        If the Console host abruptly restarts, the high availability view may disappear
      5.  
        Veritas high availability view may fail to load or refresh
      6.  
        Operating system commands to unmount resource may fail

Understanding the Veritas High Availability view

The Veritas High Availability view displays the consolidated health information for applications running in a Cluster Server (VCS) cluster. The cluster may include one or more systems.

The Veritas High Availability tab displays application information for the entire VCS cluster, not just the local system.

Note:

If the local system is not part of any VCS cluster, then the Veritas Application High Availability view displays only the following link: Configure a VCS cluster.

If you are yet to configure an application for monitoring in a cluster of which the local system is a member, then the Veritas Application High Availability view displays only the following link: Configure an application for high availability.

The Veritas High Availability view uses icons, color coding, dependency graphs, and tool tips to report the detailed status of an application.

The Veritas High Availability view displays complex applications, in terms of multiple interdependent instances of that application. Such instances represent component groups (also known as service groups) of that application. Each service group in turn includes several critical components (resources) of the application.

The following figure shows the Veritas High Availability view, with one instance of Oracle Database and one instance of a generic application configured for high availability in a two-node VCS cluster:

1. Title bar

2. Actions menu

3. Aggregate Status Bar

4. Application dependency graph

5. Application table

6. Application-specific task menu

7. Component dependency graph

 

The Veritas High Availability view includes the following parts:

  • Title bar: Displays the name of the VCS cluster, the Actions menu, the Refresh icon, the Alert icon. Note that the Alert icon appears only if the Veritas High Availability view fails to display a system, or displays stale data.

  • Actions menu: Includes a drop-down list of operations that you can perform with effect across the cluster. These include: Configuring a cluster, Configuring an application for high availability; Unconfigure all applications; and Unconfigure VCS cluster.

  • Aggregate status bar: Displays a summary of applications running in the cluster. This includes the total number of applications, and a breakdown of the number of applications in Online, Offline, Partial, and Faulted states.

  • Application dependency graph: Illustrates the order in which the applications or application instances, must start or stop.

    If an application must start first for another application to successfully start, the earlier application appears at a lower level in the graph. A line connects the two applications to indicate the dependency. If no such dependency exists, all applications appear in a single horizontal line.

  • Application table: Displays a list of all applications configured in the VCS cluster that is associated with the local system.

    Each application is listed in a separate row. Each row displays the systems where the application is configured for monitoring.

    The title bar of each row displays the following entities to identify the application or application instance (service group):

    • Display name of the application (for example, Payroll application)

    • Type of application (for example, Custom)

    • Service group name

  • Application-specific task menu: Appears in each application-specific row of the application table. The menu includes application-specific tasks such as Start, Stop, Switch, and a dropdown list of more tasks. The More dropdown list includes tasks such as Add a failover system, and Remove a failover system.

  • Component dependency graph: Illustrates the order in which application components (resources) must start or stop for the related application or application instance to respectively start or stop. The component dependency graph by default does not appear in the application table. To view the component dependency graph for an application, you must click a system on which the application is running.

    The track pad, at the right-bottom corner helps you navigate through component dependency graphs.

    If you do not want to view the component dependency graph, in the top left corner of the application row, click Close.