virtual machine delta (snapshot) files not cleaned up after backup
ABR11 Virtual edtion (17347 and prior) do not always clean up the snapshot delta files after backing up a VM. I continually get stray delta files:
-rw------- 1 root root 209M May 3 08:05 /volumes/vmStor6/Khan/Khan-000001-delta.vmdk
-rw------- 1 root root 1.2G May 3 08:05 /volumes/vmStor1/Tuvok/Tuvok-000001-delta.vmdk
This, even though the backup of those machines returned successful with no errors.
the REAL problem comes if we cannot commit those deltas in vSphere. If that doesn't work for whatever reason, we are left with creating a clone of the VM and that just isn't viable. Can't be doing this on production servers.
so WHY are these files still around? WHY can't we commit them? WHY does this happen? It's not consistent at all.
PLEASE FIX THESE BUGS!
Hello Carl Constantine,
If you are getting these stray files with build 17437, as a workaround you can: 1) Find the Acronis Virtual Appliance that has more than 2 disks (while no backup is running!). 2) Reboot the VA. It will release the disks and commit the delta files. At least, you will be able to commit them.
If the problem persists, I think it's better to open a support case or attach the following info here:
1) the screeshot of the VA configuration (number of disks)
2) the problem VM configuration (number of disks, OS version)
3) the screenshot of the datastore folder where the VA and the VM are located.
Looking through the forum, other people have the EXACT SAME PROBLEM and some of them have already raised it to support. There has to be a better answer than "reboot the Virtual appliance" it shouldn't be doing it in the first place.
Sorry to bump this up but is there a latest patch that address this by any chance? 