Fast Check May Fail if VMware Snapshot Provider Is Present

Follow

Summary

This Knowledgebase article provides information about a known issue that may occur when VMware Snapshot Provider is installed.


More Information

Symptoms

When a Neverfail Heartbeat server is restarted after a Controlled Shutdown, Fast Check fails.

Cause

For Fast Check to properly work, all protected services must be stopped when the file check is started. If VMware Snapshot Provider is installed, it will automatically start after the server restarts and will also start Distributed Transaction Coordinator (MSDTC) service. If the Distributed Transaction Coordinator service is protected by Neverfail Heartbeat (for example, Neverfail for SQL Server) this will cause Fast Check to fail.

Resolution

To avoid this issue, Neverfail Heartbeat must be configured to protect the VMware Snapshot Provider service. This allows VMware Snapshot provider to be started by Neverfail Heartbeat together with all the other protected services after the Fast Check has been performed.

To configure Neverfail Heartbeat to protect VMware Snapshot Provider, follow these steps:

  1. Login to the Neverfail Heartbeat Management Client.
  2. Navigate to Applications: Services .
  3. Click the Add button.
  4. Locate VMware Snapshot Provider in the services list.
  5. Change Target State on the Passive to Running and leave all the other settings as default.
  6. Click OK to save the changes.

The service will be listed under User Defined in the Neverfail Heartbeat Management Client.


Applies To



Neverfail Heartbeat v6.5.[n] and Later

Related Information



Knowledgebase article #2295 - Using the Neverfail Heartbeat Fast Check Feature

KBID-2481

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.