Backup it by copying all its files to external storage (configured in ESXi or using scp).The 4th way helped me in worst cases and it's most complicated way. the last resort: copy vmdk files to external storage and use vmware-vdiskmanager from VMWare Workstation.login using SSH to ESXi and use vmkfstools to consolidate disks, to make them thin (if you clone a snapshot of disk, you will get a freshly consolidated disk, but you need space).
#Disk space required for vmware on mac how to
How to consolidate snapshots in vSphere 5.x/6.x (2003638) - basic howto.Note: Deleting data at the guest OS level will likely only make the snapshot files bigger, as it makes the snapshots more different to the previous snapshot than before. Try the "Delete All" button in the snapshot manager instead of consolidate.Note that since the machine is not running you can use a few different methods of moving the VM.
If all else fails, move the VM to a datastore with enough space, then see if you can get rid of the snapshots.What Dmitry Zayats suggests about extending the datastore to make it bigger or moving other VMs off that datastore.You may find that shutting down some VMs will free up some space taken by the *.vswp files, while they are shut down.I see that you have over 2GB in logs in that one folder alone. Free up some space and try again, perhaps enough for the consolidate to work by.While I've not run in to that particular problem before you might try
0 kommentar(er)
