Aller au contenu principal

Error CreateSnapshot

Thread needs solution

after passing from vmware 5.1 to 5.5 I have the following problem on all virtual machines when I have to perform backups.
The problem occurs only when the virtual machine is powered on, otherwise the backup is performed regularly. I tried to re-install acronis vm protect and re-install the vmware tools but without any positive result.
What can be the cause of the problem?

Attività 'Backup Server XP Terminalini' fallita: 'Impossibile creare un backup.
Informazioni aggiuntive:
--------------------
Codice errore: 3
Modulo: 435
LineInfo: 555b5abba0950337
Campi:
Messaggio: Impossibile creare un backup.
--------------------
Codice errore: 32786
Modulo: 114
LineInfo: 28314c961de7d337
Campi:
Messaggio: Impossibile preparare per il backup.
--------------------
Codice errore: 353
Modulo: 149
LineInfo: a71592046cb2c5f6
Campi:
Messaggio: Impossibile eseguire il backup del gruppo.
--------------------
Codice errore: 2
Modulo: 218
LineInfo: 338a407ad20e0987
Campi:
Messaggio: Si è verificato un errore durante l'esecuzione del motore di backup e ripristino.
--------------------
Codice errore: 1080
Modulo: 1
LineInfo: d1ab7fa1e56ec8e7
Campi:
Messaggio:
--------------------
Codice errore: 13
Modulo: 149
LineInfo: d1ab7fa1e56eca74
Campi:
Messaggio: Impossibile eseguire l'operazione richiesta.
--------------------
Codice errore: 103
Modulo: 83
LineInfo: a859dd78cc91df11
Campi:
Messaggio: Apertura macchina virtuale ([Datastore] Windows Xp Terminali/Windows Xp Terminali.vmx) non riuscita.
--------------------
Codice errore: 253
Modulo: 83
LineInfo: c7610e0a857bedf4
Campi:
Messaggio: Errore di VMware: 'Chiamata metodo remoto fallita.'.
--------------------
Codice errore: 32
Modulo: 0
LineInfo: c7610e0a857bedf4
Campi:
Messaggio: Attesa attività '

CreateSnapshot' non riuscita. Motivo: An error occurred while saving the snapshot: Failed to quiesce the virtual machine..
--------------------'.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Matteo,

The error thrown is a standard VMware one: "An error occurred while saving the snapshot: Failed to quiesce the virtual machine." . The typical reasons are described in http://kb.acronis.com/content/4559 . Since it worked in your case with 5.1, but stopped working with 5.5 likely the problem is related to VMware Tools installation. You can troubleshoot the issue by trying to create the snapshot of this VM from vSphere client (with quiesced=on, memory=off parameters) and then check Windows Event log in the guest VM once the snapshot fails. It should gives some clues on what exactly went wrong. Another thing to check is the vmware.log from the datastore of this VM - it may contain additional errors.

P.S. If it's Windows XP VM then it makes sense to disable the VSS processing (since VSS is not really applicable to this OS) by setting disk.EnableUUID value to "false" in VM parameters (in .vmx file) - this should allow snapshot to be created with "quiesced=on", however in this case application-aware backup of the VM won't be possible.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

thanks for the reply. I had already seen those links but all refer vmware 3.x or 4.x.
I've posted here only the error of a virtual machine with windows xp but the same problem I have with 3 other virtual machines running windows server 2008.
The absurd thing is that I did the exact same update operation from 5.1 to 5.5 and its update vmware vmware tools on another server from the same client, and there has not been any kind of problem!
I also tried to uninstall and re-install the vmware tools from all the virtual machines but the problem persists.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Matteo,

Thank you for the additional info. If checking the vmware.log + analysing the Windows event logs won't give you any additional clues, I'd recommended to contact VMware support. It might be even something specific to hardware (for example I've seen a case when snapshot didn't work since the 2 physical NICs configured with teaming on the underlying ESXi host were running one on 100Mb/s and another on 1Gb/s).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Resolved:
Option 2 - Disable VSS application quiescing using VMware Tools:

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.
Add these lines to the file:

[vmbackup]
vss.disableAppQuiescing = true

Save the file.
Exit the editor.
Restart the VMware Tools Service for the changes to take effect. Click Start > Run, type services.msc, and click OK.
Right-click the VMware Tools Service and click Restart.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm…

I am not clear, however, what is involved in this operation!

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Matteo,

In fact it's disabling VSS processing inside the guest OS during the quiesced snapshot creation - this means that VSS-aware applications will be in crash-consistent state after recovery (just like after hard reset of this VM). It's a viable workaround if you don't run any crash-sensitive databases inside the VM.

P.S. I would still submitted a support case to VMware so that they can advise how to make the snapshot work with VSS utilization, since the solution described in that KB is not a real one - it's just a workaround.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Unfortunately, this system worked only once! I was resubmitted the error! and therefore the inability to perform backups!

This is one of the toughest issues. I mean being intermittent. We can only try to fix this when it has a problem. But do you have any updates on this yet?