Skip to main content

Creating crash-consistent snapshot because application-consistent snapshot has failed

Thread needs solution

Warning

Creating a crash-consistent snapshot of virtual machine 'OxleySQL01' because the creation of its application-consistent snapshot has failed.

The guest OS has reported an error during quiescing. The error code was: 5 The error message was: 'VssSyncStart' operation failed: IDispatch error #8454 (0x80042306) 

 

This backup plan is not even application aware to start with as I am backup up the databases in a seperate plan.

Error code 5 makes me think of an access denied somewhere.

Also this plan has quiescing turned of and the snapshot provider manually set as Microsoft.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

The quiesced snapshot for this VM doesn't work from vSphere level (you can check it by trying to capture quiesced snapshot manually from vSphere client), which results in automatic failover to non-quiesced snapshot during backup. If you want to enforce non-quiesced snapshots by default and thus get rid from the warning, then disable the "Volume Shadow Copy (VSS) for Virtual Machines" option in Backup Options (the "Volume Shadow Copy (VSS)" option which you seem to tried is not applicable to VM backups).

One possible solution to make quiesced snapshots working is to disable processing of failing VSS writers inside the backed up VM - see https://communities.vmware.com/thread/401786 where similar problem is discussed with this solution.

Thank you.