Backup Error after Hardware/ESXi Version Upgrade

Hi
I have some problems with the Backup of Windows Server VM's since i upgraded my Hardware. Before the Upgrade i used the VMware ESXi Version 5.5 U2 without any problem. Everything works fine, but after changing my Hardware to HP Microserver Gen8 with HP VMware Version 5.5 U3 installed i get some errors every 3-4 days.
I get some different errors, but the most errors are VSS errors. The first VM is a Domain Controller and the second VM is a SQL Server. The following errors comes after 3-4 days and persists until i reboot the server.
Domain Controller Error:
--------------------
Fehlercode: 253
Module: 83
Zeileninfo: c7610e0a857bedf4
Felder:
Nachricht: VMware-Fehler: 'Remote-Methodenaufruf ist fehlgeschlagen.'.
--------------------
Fehlercode: 32
Module: 0
Zeileninfo: c7610e0a857bedf4
Felder:
Nachricht: Erwarteter Task 'CreateSnapshot' fehlgeschlagen. Ursache: An error occurred while saving the snapshot: Failed to quiesce the virtual machine..
--------------------
and later this one:
--------------------
Fehlercode: 3003
Module: 538
Zeileninfo: 38b2393b56c5aa77
Felder: StringAlertId : ntds vss writer disabled
Nachricht: Alarm 'Konvertierter Agent'
SQL Server Error:
--------------------
Fehlercode: 253
Module: 83
Zeileninfo: c7610e0a857bedf4
Felder:
Nachricht: VMware-Fehler: 'Remote-Methodenaufruf ist fehlgeschlagen.'.
--------------------
Fehlercode: 32
Module: 0
Zeileninfo: c7610e0a857bedf4
Felder:
Nachricht: Erwarteter Task 'CreateSnapshot' fehlgeschlagen. Ursache: An error occurred while saving the snapshot: Failed to quiesce the virtual machine..
--------------------
Fehlercode: 3003
Module: 538
Zeileninfo: 38b2393b56c5aa77
Felder: StringAlertId : sql vss writer disabled
Nachricht: Alarm 'Konvertierter Agent'
I tried the following things:
1. VMware Tools reinstall (many times)
2. VMware ESXi Update to Version 5.5 U3a (HP Version)
3. Create Snapshot via vCenter without any problem.
I have check the status of the vss writers and noticed that some writers hat the state "Timeout".
Can you help me to solve this problem?
kind regards
Rico

Hi Vasily
I have noticed also that after the creation of a manual snapshots through vCenter VSS writers of vm change the status of timeout to no fault. I use the error handlich with 5 retrys after backup failure (same problem).
One Question: How much memory is required for the host to take a snapshot? The reason i ask that is because the max. memory of the host has changed too.
I have 16 GB RAM on the Host side and the available free space is now after migration only 512 MB or less. Before i changed the host hardware i had 24 GB Host RAM and 4 GB available free memory. Is it possible that the problem is caused by not enough Host memory?
Best regards
Rico
- Accedi per poter commentare

Hi Rico,
In fact there is no such strict RAM value that I'm aware of (probably VMware can advise - see troubleshooting recommendations) - all depends on particular machine state, how resources consuming are DBs operations, how much VSS requires to successfully create a volume shadow copy, etc. In general yes the RAM insufficiency may be the root cause (one of possible causes).
Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager
- Accedi per poter commentare
Best regards,
Vasily
Acronis Virtualization Program Manager
Information provided AS-IS with no warranty of any kind.
To contact support, please follow http://www.acronis.com/en-us/support/

Hi Vasily
I performed some tests yesterday. There are no errors if i take a snapshot via vCenter. Backups with Acronis still fails. In the Event Viewer of Windows i see the following error message: VSS Error 12298 (maybe a disk I/O problem).
Than i make some more tests with the result that high I/O in the VM causes Backup Error. I scheduled a backup at that time when low I/O exists and the Backup was sucsessfully.
The only problem now is, what has changed in the VM since the Upgrade?!
Thanks for your help.
Best regards
Rico
- Accedi per poter commentare
Best regards,
Vasily
Acronis Virtualization Program Manager
Information provided AS-IS with no warranty of any kind.
To contact support, please follow http://www.acronis.com/en-us/support/