[WORKARROUND] Failed to create a backup. when you have disks attached to the acronis VA
Dear all
i had some issues with my vm, and had my backups failing a few times and now thx to the acronis team we know why!.
this were the error messages i got
Task 'XXX' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09500ab
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d3b2
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f8
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 1080
Module: 1
LineInfo: 145a191bfe9050d1
Fields:
Message: Failed to execute the operation.
--------------------'.
scope/situation:
i had in vcenter no backup tasks running, or active snapshots on vm's but i did had was disks attached to the acronis VM from VM's there were backupped. so i manually removed the disks that were attached to the acronis vm. and then after this my backups started to fail for these vm's
it appears if you do this. then you need to reboot your acronis vm. (refresh of storage inside the vm does not help!!) then the backups will work again
analytics:
the whole reason why a disk stays attached to the VM while there are no active snapshots or tasks is a thing acronis support is working hard on. as this seems a thing happening at the vmware-vcenter side and acronis wants to build in checks but then the exact situation should be clear.
i suspect the reason vcenter on windows on vsphere 5 i really using a lot of memory especially if you have the sql server/vcenter and the new vcenter client on the same server. so for people who have this issue happening a lot i would advise to migrate the sql function off to anotehr server and or disable the new vcenter webclient and see if this decreases the amount of disks staying attached to the vm.
workarround
- remove disks from vm backups on the acronis vm (do not delete vmdk not needed)
- reboot the appliance