VssSyncStart' operation failed

[sunleung]

Hi,

I just face a event log as below:

Warning message from localhost.localdomain:

The guest OS has reported an error during

quiescing. The error code was: 5 The error

message was: 'VssSyncStart' operation failed:

IDispatch error #8449 (0x80042301)

warning

it caused the Acronis Backup software fail to backup

In Communities information, it seem relate to disk space and i/o speed.

For disk space, we should have enough disk space for OS.

Also i trust it is not heavy duty when backup, i/o should be enough

In knowledge base 1018194, resolution is reboot the virtual machine.

is it reboot the acronis appliance or our production os?

Any method to prevent the same?

Existing our version is EXSi 5.1 built 799733.

Thank you

Rgds,

Sun

[spravtek]

Hi,

What OS/Application is the VM running?

Maybe you could check the VSS of the VM, if VSS is used of course, check: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103129...

Test if the backup works without quiescing... The KB mentions the disabling of the feature.

If the machine is producing too much IO during the backup, the quiescing can fail.

[SBMtmiller]

Have you figured out this issue? I am having the exact same error w/ Symantec Netbackup.

[SBMtmiller]

"If the machine is producing too much IO during the backup, the quiescing can fail."

What does this really mean? How much is too much and how would I know?

[Udaayan]

I am having the exact issue with our Exchange 2010 server VM with Acronis as backup tool. It also leaves the VM locked and powered off after the backup fails.

OS: Windows Server 2008 x64

Any help would be appreciated.

Thanks!

[tkolbe]

Anyone figure this out yet?

Same issue here using Commvault Simpana 10 to back up various Windows 2008 R2 hosted on FC 8Gbps datastores on an EMC VNX5700. We don't generally have guest IO issues during backups, but I am seeing this occur more frequently on vSphere 5.5 than I did in 5.0.

[AuComNZ]

I had the same issue. Fixed it by running the VMWare installer and disabling "Volume Shadow Copy Service"

[Sanktuary]

Any News here?

[jonbuddy]

After much searching on this issue, AuComNZ's suggestion worked for me.

[melbatista]

reinstall vm tools > custom > uncheck Volume Shadow Copy Services Support!

[Sudarshan_Bhart]

Ensure that there is no snapshot appearing in Snapshot Manager.

[keith2399]

AuComNZ suggestion worked for me, thanks!

[bansne]

AuComNZ suggestion worked, i was facing this issue in Netbackup and backup was getting partially successful.

[Kisan_VMware]

Hi,

This is could issue due VSS writers failing, check all VSS writers showing now error ran following command from cmd to see vss writer status if any error showing fix this first. Normally backup fail due to VSS issues.

vssadmin list writers

follow the following KB for more info.

VMware KB: Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit ...

[lsaluze]

Thank you, it helped me a lot.

[wanttoknow]

Re-install VMware Tools on your VM.

[---__---]

Reinstall / Configure Vmware tools and remove the VSS feature. You don't even have to perform a reboot and you will be able to take a snapshots again.

Per:  https://kb.vmware.com/s/article/1018194

"If you are using a third-party backup product that does not allow you to configure for non-quiescent snapshots, remove the VSS component from the Windows guest operating system, provided as part of VMware Tools. This results in VMware Tools attempting to use an older sync driver. When you request a quiescent snapshot, VMware Tools does not find and utilize the VSS driver and then attempts to quiesce using the sync driver. "

[ACS-IT]

Can you elaborate on what you mean by running the VMware installer?  I tried going into the Windows Guest OS and disabling the Volume Shadow Copy Service, and doing so caused more problems than we had to begin with, so I am assuming this was not the correct action to take.