Backup & Recovery 11 does not delete VMDK Snapshots created for Backups
After Upgrading to B&R 11, VMDK-Snapshots are not deleted anymore after backup-job is done although log-file is showing that snapshots had been removed?! Looking in vSphere Client, the current harddisks are beeing counted after every backup consuming more and more harddisk space...

- Log in to post comments

After some research it has been shown that the cause for nondeleted snapshots is a backup set: "Simultaneous VM backup" in the backup options!
After disabling this option, snapshots are correctly removed after job is done.
Disadvantage: Backup-Jobs have to be created per each VM (1 VM per Job). Trying to backup multiple VMs in one job with deactivated "simulaneous VM backup-option" results in failure during backup process immediatly after the first of x VMs has been backuped. The backup aborts!
Informational Appendix:
Current ESX Version is 4.1 (348481). VMs are stored on VMFS 3.3 Filesystem. VMs in this article had no manually created VM-snapshots before first backup with B&E 11 (after migration from B&E 10).
Error/Warning Messages
-------------------------------
Multiple VMs in one job / Simultaneous VM backup activated / Created Snapshot not deleted after backup:
--------------------
Details
--------------------
Typ: Warnung
Datum und Zeit: 25.07.2011 20:37:53
Backup-Plan: [Keine]
Task: [Keine]
Typ der verwalteten Einheit: [Keine]
Verwaltete Einheit: [Keine]
Maschine: VM4.HLGMBH.LOCAL-VA
Code: 15(0xF)
Modul: 0
Besitzer: root
Nachricht:
The file is already in use
Zusätzliche Info:
--------------------
Fehlercode: 15
Module: 0
LineInfo: c61573f663f5d74e
Felder:
Nachricht: The file is already in use
--------------------
Details
--------------------
Typ: Warnung
Datum und Zeit: 25.07.2011 20:37:53
Backup-Plan: [Keine]
Task: [Keine]
Typ der verwalteten Einheit: [Keine]
Verwaltete Einheit: [Keine]
Maschine: VM4.HLGMBH.LOCAL-VA
Code: 15(0xF)
Modul: 0
Besitzer: root
Nachricht:
The file is already in use
Zusätzliche Info:
--------------------
Fehlercode: 15
Module: 0
LineInfo: c61573f663f5d74e
Felder:
Nachricht: The file is already in use
===========================================
Multiple VMs in one job / Simultaneous VM backup deactivated / Error is generated when trying to backup second VM in ONE JOB...
--------------------
Details
--------------------
Typ: Fehler
Datum und Zeit: 17.08.2011 12:27:35
Backup-Plan: [Keine]
Task: [Keine]
Typ der verwalteten Einheit: [Keine]
Verwaltete Einheit: [Keine]
Maschine: VM5.HLGMBH.LOCAL-VA
Code: 20.250.627(0x1350003)
Modul: 309
Besitzer: root
Nachricht:
TOL: Eine Aktivität von 'Backup' ist fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 3
Module: 309
LineInfo: 4a8728dc8a1c94f8
Felder:
Nachricht: TOL: Eine Aktivität von 'Backup' ist fehlgeschlagen.
--------------------
Fehlercode: 22
Module: 309
LineInfo: 8d165e86fb819606
Felder: TraceLevel : 1
Nachricht: TOL: Failed to execute the command. Der Befehl 'Backup' erstellt ein Backup der spezifizierten Daten zu dem spezifizierten Speicherort.
--------------------
Fehlercode: 32834
Module: 114
LineInfo: c35c04057128fd60
Felder:
Nachricht: 'Virtuelle Maschine'-Backup fehlgeschlagen.
--------------------
Fehlercode: 32853
Module: 114
LineInfo: c35c04057128fd95
Felder:
Nachricht: Es wurden nicht alle virtuellen Maschinen per Backup gesichert.
--------------------
Fehlercode: 32852
Module: 114
LineInfo: c35c04057128fdda
Felder:
Nachricht: Backup der virtuellen Maschine 'TMCONTROL' fehlgeschlagen.
--------------------
Fehlercode: 32786
Module: 114
LineInfo: 28314c961de7d1db
Felder:
Nachricht: Vorbereitung auf das Backup fehlgeschlagen.
--------------------
Fehlercode: 3
Module: 329
LineInfo: 1cd98aae889424f9
Felder:
Nachricht: Backup ist fehlgeschlagen.
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode
Ereignis-Code: 0x01350003+0x01350016+0x00728042+0x00728055+0x00728054+0x00728012+0x01490003
--------------------
Details
--------------------
Typ: Fehler
Datum und Zeit: 17.08.2011 12:27:35
Backup-Plan: [Keine]
Task: [Keine]
Typ der verwalteten Einheit: [Keine]
Verwaltete Einheit: [Keine]
Maschine: VM5.HLGMBH.LOCAL-VA
Code: 9.764.877(0x95000D)
Modul: 149
Besitzer: root
Nachricht:
Ausführen der angeforderten Aktion fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 13
Module: 149
LineInfo: d1ab7fa1e56ec76e
Felder:
Nachricht: Ausführen der angeforderten Aktion fehlgeschlagen.
--------------------
Fehlercode: 103
Module: 83
LineInfo: a859dd78cc91dd18
Felder:
Nachricht: Öffnen der virtuellen Maschine fehlgeschlagen ([VM5STORE] W2K8R232BIT/W2K8R232BIT.vmx).
--------------------
Fehlercode: 64
Module: 83
LineInfo: c7610e0a857bed87
Felder:
Nachricht: Erwarteter Task 'CreateSnapshot' fehlgeschlagen. Ursache: Operation timed out..
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode
Ereignis-Code: 0x0095000D+0x00530067+0x00530040
- Log in to post comments

I had the same problem. Another Workaround is to use the "ESXI Windows Agent". he can "Simultaneous VM backup" + delete the snapshot files...
btw this problem is already reported to acronis support but this doesnt mean anything (please send logs - send more logs - escalated to lvl 2 support - send logs again - 8 weeks without any solution is the default procedure)
- Log in to post comments

Hello all,
Thank you for your posts. I will do my best to help you.
We have fixed most of these issues in update 0 which we recently released, however, if they still occur I would recommend this workaround.
If you continue to have this problem please contact our Support so that we can help you resolve it.
Please let me know if you have additional questions.
Thank you.
- Log in to post comments

This is *STILL* a problem with the latest builds. Acronis seems to be leaving breadcrumb delta files everywhere for some VMs, particularly if there has been an error in the backup job for some reason, or maybe if the backup job had to be killed using the abr_backup_plans_activities_fix program??
- Log in to post comments

How about updating to the latest version, did it help resolve the issue.
- Log in to post comments