However the consolidate operation may fail again, if the issue which caused the snapshot deletion operation to fail disk consolidation previously has not been cleared.It has been a good 6 months or more since I've last seen this issue, but today I found a VM with this issue in another customers environment.What happens if you include optimized and proxy media?These files can be massive (and take a long time to render), which will significantly slow down your upload process and the post-production process in general.This is what had happened: But this did not clear the locked file error as shown below: "Unable to access file since it is locked" Keen to locate the problem I SSH'd to the ESXi server and checked the Even with the VM still powered off, I could see it was having a problem locking one of the VMDKs when tying to run the Snapshot - I could see a single entry for "RO Owner" which had the lock and the MAC address ending in "69a0".This is the ESXi server which has the lock on the VMDK file. You’ll want to create a new, ‘Master’ _Serato_ folder to which all info from the other libraries will be copied.

Note: The consolidate option allows you to consolidate the delta disks to the base disk when there are no snapshots shown in the Snapshot Manager.

This is because it simplifies our ability to archive projects, or allows us to optimize existing projects for better playback.

Project consolidation is the easiest way to gather all our project assets into one location for archiving or long-term storage.

It does not fix the underlying issue that may have caused the issue initially.

After deleting snapshots on a VM either by deleting an individual snapshot or selecting "Delete All" snapshots, you may see the following warning for the VM, stating that disk consolidation is needed.