[RESOLVED] Failed Backup does not remove snapshots
Hi All,
I am having a problem where cancelled or failed backups do not clean up snapshots. When backing up a file server (with approx 1.5TB of data) to a network share. The backup starts, and even transfers a large amount of data (approx 1.2 - 1.3 TB) but eventually cancels itself after about 20 hours. I am currently running Acronis vmProtect 7.0 (build 7.0.5173).
This is fine as once the initial backup is successful - the incremental backups work within an hour. However the problem I have had is that the cancelled (or failed) tasks are not cleaning up after themselves and so are leaving behind snapshots. As you can imagine this starts to fill up my SAN rather quickly.
What is the best way to get the acronis appliance to clean up these failed snapshots? Do I need to go into vCenter and manually remove the added hard drives (to the acronis appliance) and then remove the snapshot (on my file server)?
Any advice would be very much appreciated.
Cheers,
Iain
I have a similar problem backing up a large VM (about 1.5TB) to a network share. I have plenty of free space and the backup job completes, but it completes with a warning and the snapshots of the virtual disks are not consolidated successfully. This appears to be because some process has a lock on the snapshot file. After each backup, I get a warning message in the vsphere client telling me the disks need to be consolidated. If I restart the ESXi management agents, create a new snapshot and then delete all snapshots, the consolidation warning message goes away. However there are some orphaned files from the VMP7 snapshot that I must delete manually each time I do this.
I have been totally unsuccessful in communicating this to level 1 support. So I am waiting for VMP8 to see if that resolves anything.
Hello Jim,
Thank you for your posting in our forum.
I informed the support professional about your post and forwarded your comment to our management team.
If you want to participate in vmProtect 8 Beta program, you can follow this link.
If there is anything else, we can do for you, please let me know.
Thank you.
Peter,
at this point I will just wait for the official release. I found another thread that seems to detail the issues with large VMs, refused connection warnings and locked snapshots (http://forum.acronis.com/forum/30925). This seems to have been a known issue since April that has been under investigation. Yet level 1 support does not appear to have been aware of it. I think some of the hours I spent in chat sessions could have been avoided if level 1 support had been better informed.
Jim
Hello Jim,
Thank you for your reply.
I apologize for the problems. I have forwarded your message to our management team.
If there is anything else, we can do for you, please let me know.
Thank you.
To the op,
I had this problem in vmProtect 6 and 7. Support was able to give me an updated build of vmProtect7 that seemed to fix the problem.
Also with my experience in testing vmProtect 8... I have not had this problem since. I would look into an upgrade if I were you. Yes it was a major problem for us in earlier builds. We even had to do a Virtual 2 Virtual migration, as one of our VM's had over 56 snapshots. VMWare consolidation only can do up to 32... not to mention the time and disk space requirements for that consolidation. VMWare doesn't support more because it can get into an issue where it takes so long and uses so much space you can actually corrupt the VM totally.
Good luck and I hope an updated version will fix your issue like it did for me.
Hello KJSTech,
Thank you for your reply.
I apologize for the problems. I have forwarded your message to our management team.
If there is anything else, we can do for you, please let me know.
Thank you.
Peter,
VMP8 appears to have resolved this problem for me. Thanks.
Jim
Hello Everyone,
I want to inform you, that we have released Acronis vmProtect 8. If you have a valid support subscription, you can upgrade your Acronis vmProtect 7 serial numbers in your account.
Please upgrade your installation. If you then receive any problem, please contact support or open a new thread. You can find your support options in our Customer Handbook.
As your issue is now resolved, I lock this thread.
If there is anything else, we can do for you, please let me know.
Thank you.