Oh.... maybe a new records holder.... a 4 years forgotten snapshot... not bad :/
Your VM holds multible snapshots which mean that for a 75GB vDisk you needs up 4 times the space (worst case). Please dont delete anything... the -00000x.vmdk depends on each other. You need to free up some space and deleting (merge together) the snapshots to their current states.
The problem is that for deleting a snapshot you need additional disk space! Also the process of snapshot deletions was changed over the years and your vSphere 5.0 is around 8 years old.
By any change you can add some disk space with NFS and than we can create a copy of the vDisk by using vmkfstools -i Server_01-000004.vmdk /path/new/Server_01.vmdk which merge all files together into a single 75GB vDisk.
Thank you Joerg,
Fells good to be a record holder... Or NOT!
Oh, okay... I was hoping for a quicker solution.
Then I need to order some disks to put into the server and make another array to be used as a new datastore.
It's strange but if I look at the datastore from the Client it says that 33,68 GB is free out of the total capacity of 460,75 GB, however "Last Update" is 14 Mar 2019...
I wonder if I could ge another route and use an external HDD as a temporary storage?
After merging, (and backing up files) delete the old stuff and go back to the RAID Array?
Here is a explanation about vSphere ESXi Snapshots: VMware Knowledge Base
You have 33GB left?.... You have sayed somehting about 75GB vDisk size but for me it looks like a 250GB one. When this is not a Thinprovisioning vDisk its maybe save to click the delete snapshot button within the vSphere Client. But someone with more experience should answered.
You can delete the 2 vmcore files to get some more space back. Also as long as the VM is shutdown there is no swap file created.
Adding a Datastore trough NFS is for me always the easiest thing because no reboot is needed and also no fancy network changes (depends). After the first vmkfstools you have to use this VMDKs in your VM configuration and find out if the VM boots. If so... you clean up the original files.... and run a vmkfstools command again to copy it back. Again.. we are not moving files.. we are create copies for safety reasons.
Ah... Okay, any suggestions of a good unit to use for NFS?
I have never used anything like that except a NAS from Neatgear or two... Have no idea what filesystem they have, though.
Well the required space is said to be 75GB, but I made the vdisk larger since we only where to use the one and only server there.
Acording to Deleting virtual machine snapshots without wasting disk space you dont need extra space as long you vDisk isnt a Thinprovisiong one. So check this out and when its a Lazy or Eager Zerothick one its save to shutdown the VM and press the "Delete All Snaps" button within the Snapthotmanager.
Your Snaps are 40,60 and 100GB so it can take some time. Dont trust the progressbar.... be patient!
If you have found some extra disk space you could try to clone the VM to get rid of the snapshots.
I actually found a Synology NAS-unit that has been decommissioned and was just sitting at the office. It has 2x1TB (mirrored).
So I suspect that I need to Add hardware for the VM in it's properties?
What Disk Provisioning should I use? Thin Provision, is that the best? The old datastore is probably Thick Lazy Zeroed (chosen by default in the wizard).
Anything else I should think of?
Is the NFS already mounted on the ESX? If not create the Volume/Share on the Synology and set a propper ACL. On a real linux the NFS needs the No_Root_Squash option which is most likely a different term in the Synology Config. Iam pretty sure you can find a guide when use google with "sysnology nfs setup for ESXi".
I dont like the GUI to mount the NFS and preferer the old "esxcfg-nas" and a 2nd. putty for looking into var/log/vmkernel.log or maybe hostd.log. Because when the mount went fail the GUI often dont get a hint whats going wrong.
Let me now when the NFS Datastore is mountet.
1. Create a new VM named "n-central2" without a vDisk and choose Datastore "SynologyNFS"
2. Type the following
vmkfstools -i N-Central-000004.vmdk ../../SynologyNFS/n-central2/n-central2.vmdk -d thin
3. After the clone is finished add the existing n-central2.vmdk to the new VM n-central2 together with a LSI Parallel controller
4. Start the VM and open the console to see if the VM is booting fine
If the VM boots we have create a working VM and merge all snapshot together into one.
5. Delete the original N-Central VM
- In your Screenshots the VM is named N-Central but in our beginning Posts its named Server_01
- i prefer lower case for Datastore and VM names with no space and fancy special chars so we dont need quoting the file names on command line
If you open a 2nd putty you can use
to watch disk speeds durin cloning. The "u" will shown the NFS mount.
Or you could just clone the original VM to a new VM that you store on the new NFS datastore. Then shutdown the original VM and start de cloned VM to see if everything is working like it should. When you're happy you can delete the original VM and move the cloned VM to the correct datastore. When you're all done you can dismount the NFS datastore. Personally, I think this is easier than typing commands in a putty session...