This problem is almost always exactly what it says - disk space.This problem is almost always exactly what it says - disk space.
- That's what I used to think until I experienced the problem, and even thought afterward that somehow it was still the problem. At length, I learned not so, and the op is coming to the same conclusion as others have.
- GhettoVCB is not the root cause of the problem. It simply uses standard components of ESXi to perform the backup/clone. The same problem occurs when running vkmfstools manually. The biggest thing to watch out for with GhettoVCB is it will rotate out your good backups, and replacing them with failed backups. I wrote that to the author a while back. The change log shows the latest is 1/13/13, and I've downloaded since then, so that problem still exists. The other problem is you need to run vkmfstools manually to determine the actual error as the script does not return that. Perhaps it cannot. It is evident that the op also discovered that which is why his output is not from GhettoVCB.
- For me, these are thin to thin backups. Even if they were to grow to their actual size on the destination, there would still be 20 times the disk space necessary to contain the backups. If I erase all of the backups, it will still return the same error until I make a new VHD, which is also what the op is figuring out. It's as though the space is not returned on the VHD when backups are rotated. However, the ESXi and the host operating system both indicate plenty of disk space.
- I don't see any quiesce errors in his output.
- What I find useful from your post is you are doing it successfully, and running 5.x. My question to you is, Which VM hardware version are you running?
Thanks for your input!