This Knowledgebase article provides information about Neverfail vAppHA for VMware V6.1.2.
For more information about this version of vAppHA, see the Reference Guide for Neverfail vAppHA V6.1 .
Supported Virtual Platforms and Technologies
VMware vSphere 4.0 and 4.1
- ESX 4, ESX 4.1, ESX 4.i, and ESX 4.1i
- vCenter 4.0 and 4.1
- VMware FT, HA, VMotion and DRS
Supported Operating Systems
- Windows 2003 SP2 x86 and x64
- Windows 2003 R2 x86 and x64
- Windows 2008 SP2 x86 and x64
Virtual Machine Requirements
- Install the latest version of VMware Tools in VMs protected by vAppHA
- Health checks for the vSphere Infrastructure require VMs running vAppHA to be on the same subnet as vCenter
Please refer to Knowledgebase article #2089 - Neverfail vAppHA for VMware v6.1.2 - Configuration Guide and documentation for more details.
- Fault Tolerance (FT) Availability Check (enabled by default)
- High Availability (HA) Check (enabled by default)
- Integrates with VMware HA Application Monitoring (disabled by default) available on vSphere 4.1 platform only
- vCenter Availability Check (enabled by default)
Rule Actions are available to application plug-ins installed with vAppHA; when the rule action triggers, the event is logged in vCenter
- VMotion and Restart Application
- A destination target host. This is the ESX host name or the IP address.
- A Resource Pool as the VMotion destination.
Neverfail vAppHA Foundation
Provides the foundation for protecting any virtualized applications; Neverfail provide “starter” plug-ins that deliver service monitoring, server and application performance monitoring for the following:
- System Performance Monitoring Rules
IIS 6.0 and IIS 7.0
- Web Site Availability Check
- Web Site Response Time Check
Windows File Server 2003 and 2008
- File Server Performance Monitoring
Neverfail vAppHA for Application Plug-ins
vAppHA can be deployed in production with the following application versions:
- BlackBerry Enterprise Server 4.1.6 MR7 and 5.0 MR3
Exchange 2007 SP2 and Exchange 2010
- ForeFront for Exchange
- Sophos PureMessage for Exchange
- TrendScan Mail for Exchange
- Symantec for Exchange
- IIS 6.0 and IIS 7.0
- Lotus Domino 8.0.2
- SQL Server 2005 SP3 and SQL Server 2008 SP1
- SharePoint Server 2003 SP2 and 2007 SP2
- Windows File Server 2003 and 2008
All other Neverfail Plug-ins or application versions that have not been listed are compatible with vAppHA but are not currently approved for deployment in production environments.
The following are known issues in Neverfail vAppHA V6.1:
Clusters containing a mix of ESX 4.0, ESX 3.x
- Untested at EAR, vAppHA should not be deployed in a live production environment if the Cluster contains ESX 3.x
- Clusters containing a mix of ESX 4.0, ESX 3.x
- Application Plug-ins can be installed post install but this is only possible from a local management client running on the VM
If ESX 4i Lock Down is used
- This should not include the user account used by VMAdaptor
- If ESX 4i Lock Down is used
Repeated VM Restarts
- vAppHA will not trigger VMRestarts within 30 mins of a previous VM Restart Action. vCenter time is used to determine whether another restart should occur.
- If the VM time is more than 30 mins behind the time on vCenter then the server may restart again if a rule fails.
VMotion Rule action does not result in a VMotion to a new ESX Host
- If the specified Resource Pool contains the ESX Host that vAppHA is currently running on then DRS will not request a VMotion.
- VMadaptor does not warn the user if they configure vAppHA in this way.
Environments configured to use VMware Integrated Application HA protection and VMotion
- Please configure so that the average time to perform a VMotion is less than the Clusters setting for Application HA Failure Interval (default 30 sec). If in doubt, configure the Failure Interval to 60 sec to avoid a VM restart during a VMotion
- The message logged does not mention the application restart ‘Finished in t ms with status Migrate VM task’
VMotion Rule action fails with an unspecified target error
- If the Target Host and Resource Pool are left empty
Clusters must not contain multiple VMs with the same windows host name
- Even if the duplicates are in the powered off state
- Alerts will state the server host name twice and the role as Active.
Time trial license expiry
- If the license expires, when the application is in the stopped state, then this will cause vAppHA to the remove service protection when upon restart.
- Ensure that the application is in the started state before restarting vAppHA.
The System Tray Icon references Primary and Active server
- The following states appear next to the tray icon P/- or P/A
- Repeated VM Restarts
The vAppHA Management Client Online Help
- Includes pre screen shots from the Beta version
Alerts Panel contains alerts relevant to the Neverfail Heartbeat product
- Alerts for Switch Over, Fail Over, Full System Check etc are not relevant for vAppHA deployments
- The vAppHA Management Client Online Help
- vAppHA appears as "Neverfail Heartbeat" in Add/Remove Programs
- Uninstall will not remove the Neverfail Folder from the Start Menu
The Reference Guide for Neverfail vAppHA V6.1 provides installation instructions. If Integrate with VMware Application HA is enabled, please consult Knowledgebase article #2089 - Neverfail vAppHA for VMware v6.1.2 - Configuration Guide for advice on appropriate recovery actions for the Neverfail Server r2 service.
Neverfail vAppHA for VMware V6.1.2