VMware

VMware vSphere® App HA — 1.0 Release Notes

VMware vSphere App HA 1.0 | 22 September 2013 | Build 1316229

Last Document Update: 15 September 2013

These release notes cover the following topics:

About vSphere App HA

App HA is a plug-in to the vSphere Web Client. App HA enables you to define high availability for the applications that are running on the virtual machines in your environment.

Key vSphere App HA Features

This version includes the following features:

  • Displays location and availability status of applications.
  • Performs user-defined remediation if a service is unavailable or unstable. Remediation actions include restart service and reset virtual machine.
  • Triggers alerts and notifications when services become unavailable or unstable.
  • Enables a remediation action to be suspended while maintenance is performed.
  • Integrates with vSphere HA for reset virtual machine functionality and compatibility with vMotion.

vSphere App HA Documentation

Additional documentation is available through the vSphere App HA 1.0 Documentation Center.

Limitations and Known Issues

The following limitations and known issues affect this App HA release:

Installation

  • The vSphere App HA license is configured at ESX level. As long as you have a vSphere App HA license feature on one of your ESX servers, it applies to the vCenter environment.
  • You can only install one vFabric Hyperic server on one vCenter server with one vSphere App HA plug-in installed (1:1:1).
  • vSphere App HA has a scale limitation of 400 agents.

Remediation

  • When you power off or suspend a virtual machine, during the first minute of the process the vSphere HA protection is disabled remediation limitation is displayed instead of the VM is powered off or suspended limitation.
  • When you put a service in maintenance mode, the process takes up to a minute to be fully applied, even though the Application Availability table already shows that the service is in maintenance mode. During this time, remediation actions might still be triggered.
  • If you configure a Reset VM action on a virtual machine that is not part of a cluster and you then move it to a cluster, the action does not work if the action was triggered while the machine was outside the cluster.
  • If you apply Reset VM remediation to two or more services on a virtual machine and one of the services requires a reset virtual machine action, the other services are determined to be stopped or unstable, and a reset loop might be created.
    Only apply this remediation action to one service on a virtual machine.
  • You cannot assign a remediation policy to a service whose availability is unknown. However, in the case in which the service is unknown because of configuration issues, you can create a policy with correct configuration properties and assign it.
  • Occasionally, a virtual machine might reset even though the service on that machine is running.
    vSphere App HA provides a remediation plan that resets a virtual machine when a service running on that machine is determined to be unstable. Unstable is defined as the service having changed its state between available and unavailable, X times in Y seconds. The issue occurs when the last state change that triggers the Reset VM action is is from unavailable to available.

General

  • Occasionally, a #1010 internal error appears in the Applications Availability tab. You can safely ignore the message.
  • On virtual machines running a Windows operating system, occasionally you might see two instances of Apache HTTP Server displayed in the Availability tab although there is actually only one instance. Check that the path to the instances are identical to verify that there is only one instance of the server.
  • If the clock of a vFabric Hyperic agent is not synchronized with the vFabric Hyperic server clock, the information that is retrieved from the vFabric Hyperic server is inaccurate. As a result, vSphere App HA actions are unreliable.