So what do I mean by disks needing to be consolidated….. However, since this first issue or two, I have noticed that v Center doesn’t always let you know something is going on, so expecting a Warning is hit an miss.
But who wants to go through and check every VM to see if v Center happens to let you know(and it might not) that there is something going on. So of course, as one might expect, I decided to write a script to let me know if there is an issue.
You will need to edit the Veeam Proxy Servers VM and remove the disks of the VM that needs consolidated from the “Hardware tab”.
Make sure you only remove the disks and not remove and delete them or you will be using Veeam for a restore 🙂 After you remove the disks from the Veeam Proxy, you can once again try to “Consolidate” the VM using the previous steps above.
Then it goes to 60 minutes per Snapshot consolidation cycle.
When the maximum of iterations if reached, the VM is stunned and a synchronous consolidation is forced.
When you do it through the GUI it does throw a warning about logs, but again, I haven’t had an issue, and hopefully I don’t ever have one 🙂 Good Luck, and I hope this helps!
I arrived at work today and noticed 2 VM’s had a warning indicating “Virtual Machine Disk Consolidation is needed”.
If the VM snapshot consolidation doesn’t work well as the incoming data rate is too high, VMware is increasing the asynchronous consolidation run cycle from 5 to 10, 20, 30 and so on until the 9th iterations.
You can check this very easily in the settings of the backup server: All crossed the disks are the remnants of failed backups.
Just delete them to drive consolidation was completed correctly.
I waited till we could get a service window on the VM, performed a shutdown and re-ran the disk consolidation. I then used command vim-cmd vmsvc/getallvms to quickly locate the volume containing the VM: Then checked if there was any locks on the vmdk file: I have highlighted the line showing us there is a RO (Read-Only) lock on the VMDK file.
This is most likely what is causing the disk consolidation to fail.