Cluster Server 7.4.2 Configuration Guide for Custom Applications - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Windows
  1. Introducing the Veritas High Availability solution for VMware
    1. How does the Veritas High Availability solution work
      1.  
        How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
      2.  
        Typical VCS cluster configuration in a virtual environment
      3.  
        How does the Veritas High Availability solution integrate with vSphere Web Client
    2.  
      Supported VMware versions
    3.  
      Managing storage
  2. Configuring application monitoring using the Veritas High Availability solution
    1.  
      Deploying the Veritas High Availability solution for configuring application monitoring
    2. Notes and recommendations
      1. Assigning privileges for non-administrator ESX/ESXi user account
        1.  
          Creating a role
        2.  
          Integrating with Active Directory or local authentication
        3.  
          Creating a new user
        4.  
          Adding a user to the role
    3. Configuring application monitoring
      1.  
        Configuring the VCS cluster
      2.  
        Configuring the application
    4.  
      Modifying the ESXDetails attribute
  3. Administering application monitoring
    1.  
      About the various interfaces available for performing application monitoring tasks
    2. Administering application monitoring using the Veritas High Availability tab
      1. Understanding the Veritas High Availability tab work area
        1.  
          To view the status of configured applications
      2.  
        To configure or unconfigure application monitoring
      3.  
        To start or stop applications
      4.  
        To switch an application to another system
      5.  
        To add or remove a failover system
      6.  
        To suspend or resume application monitoring
      7.  
        To clear Fault state
      8.  
        To resolve a held-up operation
      9.  
        To determine application state
      10.  
        To remove all monitoring configurations
      11.  
        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.  
        Monitoring applications across a data center
      3.  
        Monitoring applications across an ESX cluster
      4.  
        Searching for application instances by using filters
      5.  
        Selecting multiple applications for batch operations
      6.  
        Starting an application using the dashboard
      7.  
        Stopping an application by using the dashboard
      8.  
        Entering an application into maintenance mode
      9.  
        Bringing an application out of maintenance mode
      10.  
        Switching an application
      11.  
        Resolving dashboard alerts
  4. Appendix A. Troubleshooting
    1. Troubleshooting application monitoring 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
    2. Troubleshooting Veritas High Availability view issues
      1.  
        Veritas High Availability tab not visible from a cluster node
      2.  
        Veritas High Availability tab does not display the application monitoring status
      3.  
        Veritas High Availabilitytab may freeze due to special characters in application display name
      4.  
        Veritas High Availability view may fail to load or refresh
      5.  
        Operating system commands to unmount resource may fail

Administering application monitoring settings

The Veritas High Availability tab lets you define and modify settings that control application monitoring with Cluster Server (VCS). You can define the settings on a per application basis. The settings apply to all systems in a VCS cluster, where that particular application is configured for monitoring.

The following settings are available:

  • App.StartStopTimeout: When you click the Start Application or Stop Application, or Switch Application links in the Veritas High Availability tab, VCS initiates an application start or stop, respectively. This option defines the number of seconds that VCS must wait for the application to start or stop, after initiating the operation. You can set a value between 0 and 300 seconds for this attribute; the default value is 30 seconds.

    If the application does not respond in the stipulated time, the tab displays an alert. The alert states that the operation may take some more time to complete and that you must check the status after some time. A delay in the application response does not indicate that the application or its dependent component has faulted. Parameters such as workload, system performance, and network bandwidth may affect the application response. VCS continues to wait for the application response even after the timeout interval elapses.

    If the application fails to start or stop, VCS takes the necessary action depending on the other configured remedial actions.

  • App.RestartAttempts: This setting defines the number of times that VCS must try to restart a failed application. The value of App.RestartAttempts may vary between 0 and 5; the default value is 0. If an application fails to start within the specified number of attempts, VCS fails over the application to a configured failover system.

  • App.DisplayName: This setting lets you specify an easy-to-use display name for a configured application. For example, Payroll Application. VCS may internally use a different application name to uniquely identify the application. However, the internal string, for example OraSG2, may not be intuitive to understand, or easy to recognize while navigating the application table.

    Moreover, once configured, you cannot edit the application name, while you can modify the application display name as required. Note that the Veritas High Availability tab displays both the application display name and the application name.