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

Managing storage

Configure the storage disks to save the application data.

VMware virtualization manages the application data by storing it on SAN LUNs (RDM file), or creating virtual disks on a local or networked storage attached to the ESX host using iSCSI, network, or Fibre Channel. The virtual disks reside on a datastore or a raw disk that exists on the storage disks used.

For more information, refer to the VMware documentation.

The application monitoring configuration in a VMware environment requires you to use the RDM or VMDK disk formats. During a failover, these disks can be deported from a system and imported to another system.

Consider the following to manage the storage disks:

  • Use a networked storage and create virtual disks on the datastores that are accessible to all the ESX servers that hosts the VCS cluster systems.

  • In case of virtual disks, create non-shared virtual disks (Thick Provision Lazy Zeroed).

  • Add the virtual disks to the virtual machine on which you want to start the configured application.

  • Create volumes on the virtual disks.

Note:

If your storage configuration involves NetApp filers that are directly connected to the systems using iSCSI initiator, you cannot configure application monitoring in a virtual environment with non-shared disks.

The following VCS storage agents are used to monitor the storage components involving non-shared storage:

  • If the storage is managed using SFW, the MountV, VMNSDg, and VMwareDisks agents are used.

  • If the storage is managed using LDM, the Mount, NativeDisks, and VMwareDisks agents are used.

Before configuring the storage, you can review the resource types and attribute definitions of these VCS storage agents. For details refer to the Cluster Server Bundled Agents Reference Guide.