Just wanted to update you guys. I worked with Veeam support to get this resolved without having to add additional local storage.
The Veeam backup Server is a VM on the same ESXi host and backs up the other VMs. Veeam creates a new Disk for the VM during backup (hot add). This Disk was still attached to the VM, which was locking the file and preventing consolidation.
Once we removed the 2nd Disk, we were able to consolidate the snapshots (which took 2 hours).
All the .vmdk files have been removed, except for the one created on the 13th?
Anyone know why this one still exists?
