There is no access to a shared resource
Hello together,
our Backup fails constantly with follwoing Error:
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB","$module":"mms_vsa64_10130"}
Nachricht: TOL: Failed to execute the command. Backup-Plan 'W8KSERV03'
------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB","$module":"agent_protection_addon_vsa64_10130"}
Nachricht: TOL: Failed to execute the command. Backup-Plan 'W8KSERV03'
------------------------
Fehlercode: 41
Modul: 307
Zeileninfo: 0xE6792A5EE190DE2C
Felder: {"$module":"agent_protection_addon_vsa64_10130"}
Nachricht: Ausführen des Befehls fehlgeschlagen.
------------------------
Fehlercode: 53
Modul: 309
Zeileninfo: 0x2E7E9E174F1FB719
Felder: {"$module":"agent_protection_addon_vsa64_10130","FailCount":"2"}
Nachricht: 2 Aktivitäten konnten nicht erfolgreich abgeschlossen werden. Eine davon wird angezeigt.
------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4","$module":"service_process_vsa64_10130"}
Nachricht: TOL: Failed to execute the command. Backup
------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4","$module":"gtob_backup_command_addon_vsa64_10130"}
Nachricht: TOL: Failed to execute the command. Backup
------------------------
Fehlercode: 32827
Modul: 114
Zeileninfo: 0xC35C04057128FEAE
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Backup von virtuellen Maschinen ist fehlgeschlagen.
------------------------
Fehlercode: 32846
Modul: 114
Zeileninfo: 0xC35C04057128FEF1
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Es wurden nicht alle virtuellen Maschinen per Backup gesichert.
------------------------
Fehlercode: 32845
Modul: 114
Zeileninfo: 0xC35C04057128FF35
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Backup der virtuellen Maschine 'W8KSERV03' fehlgeschlagen.
------------------------
Fehlercode: 32786
Modul: 114
Zeileninfo: 0x28314C961DE7D6F8
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Vorbereitung für Backup fehlgeschlagen.
------------------------
Fehlercode: 3
Modul: 329
Zeileninfo: 0x1CD98AAE889424F9
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Backup ist fehlgeschlagen.
------------------------
Fehlercode: 1060
Modul: 1
Zeileninfo: 0xB43E776571144DF0
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Ausführen der Aktionen fehlgeschlagen.
------------------------
Fehlercode: 3
Modul: 7
Zeileninfo: 0x8BA4FA0BAC28BEE2
Felder: {"$module":"disk_bundle_vsa64_10130"}
Nachricht: Lesefehler
------------------------
Fehlercode: 314
Modul: 83
Zeileninfo: 0x7A2D2FB04E730299
Felder: {"$module":"hv_srv_vsa64_10130"}
Nachricht: Interner Fehler: Es besteht kein Zugriff auf eine freigegebene Ressource.

- Log in to post comments

Hi,
following Konfiguration is made:
Backupjob One: Source is an virtual Machine - Target is on \\NASBackup-Server\Terget1
Backupjob Two: Sours is an virtual Machine 2 - Target is on \\NAS\Backup-Server\Target2
Both Job have the Same Konfiguration. I cloned the first one and changed only the Source and Target. As explained, Backupjob 1 works. The second did not work.
The log of the not working Backup please find attached.
Attachment | Size |
---|---|
454420-149275.txt | 70.38 KB |
- Log in to post comments

Hi,
The root cause appears to be related to the fact that regular Hyper-V production checkpoint (snapshot) cannot be created properly for the problematic VM:
2018-07-04T07:47:03:381+02:00 13348 I0053008A: Fehler 0x53008a: Fehler beim Erstellen des Snapshots der virtuellen Maschine (Maschine: '45967B66-2024-4FAE-8439-4BC44AA089E6'; Name: 'AcronisBackup').
| Ablaufverfolgungsebene: Information
| Channel: tol-activity#97FBAFA4-633D-4BD6-AD59-A420549A73B6
| Zeile: 0xfb98212d12086c2f
| Datei: e:\196\enterprise\virtualware\raw\microsoft\hyperv\hv_vm.cpp:1571
| Funktion: `anonymous-namespace'::HyperVVirtualMachineImpl::CreateMachineSnapshot
| $module: hv_srv_vsa64_10130
|
| Fehler 0x53008a: Fehler beim Erstellen des Snapshots der virtuellen Maschine (Maschine: '45967B66-2024-4FAE-8439-4BC44AA089E6'; Name: 'AcronisBackup').
| Zeile: 0xfb98212d12086c3d
| Datei: e:\196\enterprise\virtualware\raw\microsoft\hyperv\hv_vm.cpp:1585
| Funktion: `anonymous-namespace'::HyperVVirtualMachineImpl::CreateMachineSnapshotBase
| $module: hv_srv_vsa64_10130
|
| Fehler 0x53008b: Der Task wurde mit Fehlern abgeschlossen.
| Zeile: 0x7a272029c66c6578
| Datei: e:\196\enterprise\virtualware\raw\microsoft\hyperv\hv_utils.cpp:244
| Funktion: VirtualWareRaw::WaitForJob
| TaskDescription: Creating Virtual Machine Checkpoint
| ErrorCode: 0x8000
| ErrorDescription: Checkpoint operation for 'W8KSERV03' failed. (Virtual machine ID 45967B66-2024-4FAE-8439-4BC44AA089E6)
| $module: hv_srv_vsa64_10130
The bolded error is thrown from Hyper-V itself when Acronis Backup agent "asks" it for checkpoint creation. The details should in Windows Event log (in Hyper-V related events).
The further errors are related to automatic failover to non-production (without VSS) checkpoints which failed at some point. It looks like problem in this specific "failover" logics in our code which doesn't handle such situations properly. It should be investigated with help from our support team - please submit a support ticket. Remember to capture system report from the Hyper-V host where problematic VM resides.
The workarounds would be either of the following:
- Edit the existing backup plan and enforce crash-consistent snapshot creation by disabling Backup Options->"Volume Shadow Copy (VSS) for Virtual Machines" (set to "No").
- Install Agent for Windows inside the guest OS of the problematic VM. It will appear twice in "Devices" list in Acronis Backup web console: once as VM and one as "VM with agent inside" (you can check the icon tooltip via mouse-over). Next apply backup plan to "VM with agent inside" type of device from the list.
Thank you.
- Log in to post comments