Attempting to Deploy a Secondary or Tertiary Server Results in a Quiescing Error

Follow

Summary

This Knowledgebase article provides a workaround for deployment when the Secondary or Tertiary server cannot be deployed due to the quiescing error.


More Information

Symptoms:

During the deployment of Neverfail Engine on Secondary and Tertiary, the Engine Management Web Client may show that the deployment of the Tertiary server failed with the following message:

ERROR: 100% Failed to clone TERTIARY server from SECONDARY (An error occurred while quiescing the virtual machine). See the virtual machine's event log for details .

Cause:

This is a known VMware issue. Additional details about this can be found in VMware Knowledge Base.

Resolution:

Resolution #1

    1. Uninstall Neverfail Engine on the Primary (and Secondary if deployed as a Trio) from the Engine Management Web Client.
    2. On the source virtual machine, open the C:\ProgramData\VMware\VMware Tools\Tools.conf file in a text editor, such as Notepad. If the file does not exist, create it.
    3. Add the following lines to the file (on the clone source server, for example, Primary or Secondary):

      [vmbackup]
      vss.disableAppQuiescing = true
    4. Save the file.
    5. Exit the editor.
    6. Restart the VMware Tools Service to allow the changes to take effect. Click Start > Run , type services.msc , and click OK .
    7. Right-click the VMware Tools Service and click Restart .
    8. Restart the Neverfail Engine Pair/Trio deployment from the Engine Management Web Client.

Resolution #2

Disable time synchronization on the source Virtual Machine as described in VMware KB http://kb.vmware.com/kb/1189


Applies To

All Versions


Related Information

http://kb.vmware.com/kb/1031298
http://kb.vmware.com/kb/1007696
http://kb.vmware.com/kb/2009065

KBID-2788

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.