So I have a particularly troubling issue left behind by the old IT department. We're running several snapshots in and no one thought to consolidate them, likely because no one was skilled enough in VMWare to realize they had to do this. So, this is the problem I'm left with:
Assuming the image doesn't load, we have this:
- ->The VM 343.7GB
- --> Snapshot 1 5/14/2018, 150 GB
- ---> Snapshot 2 06/13/2018, 9.03 GB (Snapshot the VM's memory is: NO)
- ----> Snapshot 3 06/13/2018, 31.19 GB
- -----> Snapshot 4 06/14/2018, 386.24 MB
- ------> Snapshot 5 08/27/2018, 45.43 GB
- -------> You are here (yay) 59.5 GB
I did some digging and what looks to be the best fix is to do this:
- Create a backup of the VM files, ideally while it is powered off. Just copying the whole VM to a second location should suffice.
- Delete the snapshots. Ideally during non office hours, the consolidation will take time. A lot of time. It will go faster when the VM is turned off.
- Check if the VM is intact, if not, restore the backup. Source: VMWare old snapshot consolidation
My question to you is:
These snapshots have been running for quite some time, the oldest since 2018. Based on what I'm reading, it's likely to cause some degradation if not completely corrupt the VM at this point.
- Is it worth my time to attempt the above fix?
- If not, am I better off backing up the databases stored on the server and reverting the server?
If I understand correctly, reverting returns it to the state before the snapshots occurred, discarding the changes made in the snapshot. Whereas deleting the snapshots consolidates all of the changes made into one. (Weird terminology VMWare)
Also, this is a thin-provisioned server. Running out of disk space is what made me discover this issue, and I've got about 4GB left at this point.