Cluster Server 8.0.1 Configuration Guide for Custom Applications - Windows

To configure the application

1. Launch the vSphere Client and connect to the vCenter Server that manages the virtual machine. On the Inventory view of the vCenter Server, in the left pane, select the virtual machine where you want to configure application monitoring. Then, in the right pane, select the Veritas High Availability tab.
2. On the Veritas High Availability tab, click Configure Application for High Availability. This option is available only after a cluster has been configured. Unless you configure a cluster, you cannot configure an application for monitoring.
3. On the Welcome panel of the Veritas High Availability Configuration wizard, review the pre-requisites and then click Next.
4. On the Application Selection panel, select the application from the Supported Applications list and then click Next.

   Alternatively, you can use the Search box to find the application and then click Next.

   If you want to download any of the High Availability Agents, click the Download Application Agents (SORT) link to download the agents from the Veritas Operations Readiness Tools (SORT) site.

   https://sort.veritas.com/agents

5. On the Windows Service Selection panel, select the services that you want to monitor and then click Next.

   Alternatively, you can use the Search box to find the service and then click Next.

   The wizard automatically discovers the services on the system. If a selected service depends on some other services, you must also select those services. You can define the dependencies between those services on the Define Start-Stop Order panel later.

   If you do not want to monitor any services, click Next without selecting any service.

6. On the Windows Process Selection panel, specify the processes that you want to monitor.

   To specify a process, click Add Process.

   On the Process Parameters dialog box, select the type of monitoring that you want to configure, specify the required details, and then click OK.

   For direct process monitoring, specify the following details:

   Process Full Path	Specify the complete path of the process executable file including its extension.
   Arguments	Specify the command line arguments, if any, for the process to be monitored.
   Run process in local system account context	By default the specified process runs in the context of the local system account.
   Run process in specified user account context	Select to run the process in a different user's context, and then specify the user name and password in the respective fields. The user name must be in the format user@domain.com or domain.com\username. Note: Ensure that you specify a valid user name and that the user account has adequate privileges on the system where you want to configure application monitoring. Otherwise, application monitoring may fail.

   For program-based process monitoring, specify the following details:

   Start program	Specify the full path of the program that starts the process to be configured for monitoring.
   Arguments	Specify the command line arguments, if any, for the start program.
   Monitor program	Specify the full path of the program that monitors the process to be configured for monitoring.
   Arguments	Specify the command line arguments, if any, for the monitor program.
   Stop program	Specify the full path of the program that stops the process to be configured for monitoring.
   Arguments	Specify the command line arguments, if any, for the stop program.
   Run process in local system account context	By default the specified process runs in the context of the local system account.
   Run process in specified user account context	Select to run the process in a different user's context, and then specify the user name and password in the respective fields. The user name must be in the format user@domain.com or domain.com\username. Note: Ensure that you specify a valid user name and that the user account has adequate privileges on the system where you want to configure application monitoring. Otherwise, application monitoring may fail.

   The process or the programs that you add is displayed on the Windows Process Selection panel. Repeat this step for all the processes that you want to configure for monitoring.

   If you do not want to monitor any processes, click Next without specifying any process.

7. On the Mount Point Selection panel, select the mount points that you want to monitor and then click Next.

   If you do not want to monitor any mount points, click Next without selecting any mount points.

8. On the Define Start-Stop Order panel, specify the order in which you want the selected services, processes, and mount points to be started or stopped.

   To define the dependency between the components, select an application component from the Parent Component box and then select the components from the Depends on box.

   While starting the service or process, the components are brought online in the defined order. For example, if a service is dependent on a mount point, then while starting the service, the mount point is first brought online and then the service itself.

   Click Next to proceed with the configuration.

9. On the Configuration Inputs panel, select the VCS cluster systems on which you want to configure the application for high availability and move them to the Application failover targets list. The local system is selected by default.

   Using the up-down arrow keys, you can define the priority order for the failover systems.

   For each system that you assign as a failover target, you must specify the domain user account details in the appropriate fields on the Edit System dialog box. The VCS agents use these details to perform domain operations (such as Active Directory updates).

10. On the Virtual Network Details panel, specify the virtual IP and the network details for the application to be configured and then click Next.

    To specify the virtual IP and network details, select the IP version and then specify the following details for each failover system:

    Note:

    You must select the same IP version as the one that was selected during the VCS cluster configuration.

    Virtual IP address	Specify a unique virtual IP address.
    Subnet mask	Specify the subnet mask to which the IP address belongs.
    Virtual name	Specify a virtual name.
    Network Adapter column	Select the network adapter that will host the virtual IP.

11. On the Storage HA Inputs panel, specify the ESX/ESXi hosts and the administrative user account details for each host, and then click Next.

    Note:

    This panel appears only if you have specified a mount point, or multiple application failover targets, or both for the selected custom application.

    To specify the ESX/ESXi hosts, click Add ESX/ESXi Host and on the Add ESX/ESXi Host dialogue box, specify the following details:

    ESX/ESXi hostname or IP address	Specify the target ESX hostname or IP address. The virtual machines will fail over on this ESX host during vMotion. The mount points configured on the ESX host where the application is currently running must be available on the target ESX host.
    User name	Specify a user account for the ESX host. The user account must have administrator privileges on the specified ESX host.
    Password	Specify the password for the user account provided in the User name text box.

    Note:

    By default, the wizard sets up a communication link with the ESX/ESXi server. You can modify the configuration to set up the communication link with vCenter Server instead. To set up a link with a vCenter Server, you must modify the ESXDetails attribute after this application monitoring configuration workflow is complete.

    See Modifying the ESXDetails attribute.

12. On the Configuration Summary panel, review the application configuration details.

    The wizard assigns a unique name to the application service group. Click Rename to rename the service group.

    Click Next to initiate the application monitoring configuration.

13. On the Implementation panel, the wizard performs the application configuration tasks.

    The wizard displays the status of each task. After all the tasks are complete, click Next.

    If the configuration tasks fail, click Diagnostic information to check the details of the failure. Rectify the cause of the failure, and run the wizard again to configure application monitoring.

14. On the Finish panel, click Finish to complete the wizard workflow. This configures the application for high availability on the selected VCS cluster systems.

    The Veritas High Availability view now displays the application status and its component dependency.

    If the application status shows as not running, click Start to start the configured components on the system.