Looking for thoughts on this … please read carefully. I have a single VM. That VM has the following (4) hard drives attached.. 1. Drive 1 (40GB) on Datastore1 2. Drive 2 (400GB) on Datastore2 3. Drive 3 (500GB) on Datastore3 4. Drive 4 (800GB) on Datastore4 The .VMX file is also on Datastore1. We had been using VEEAM for backups of the VM, but there was a problem with VEEAM, and it basically started creating snapshots of the VM for each nights backup, but never getting rid of those snapshots. So now, there are (55) orphaned snapshot files all on Datastore1. In total, the (55) snapshot files take up about 550GB of disk space… of that, about 45 snapshot files take up LESS than a couple MB in size, the remaining ten snapshot files range from 2GB in size to 200GB in size. The VM is currently writing all data to the snapshot files NOT to the original .VMDK files. When looking at the VM in the vSphere client, it shows NO snapshots, so I need to perform a consolidation. My question is, with 55 snapshots, and those being about 550GB in total size (all being on Datastore1 since that's where the .VMX file is), and Datastore1 having 153GB of free space right now, will I be able to consolidate snapshots on the VM properly? I realize this could take several hours, and might be better to perform when the VM is turned off… Host is currently running on vSphere 5.5, however, this problem was occurring for several weeks now when the host was on 4.1. The problem with the snapshots wasn't noticed until after the upgrade. Thoughts?
↧