Physical Server VMFS datastore running out of disk space due to snapshot ?
Hi All,
I've got one physical server that is running out of disk space with just a few MBs of disk space left, it is consumed by open VMware snapshot that was forgotten for few days.
So how to make sure the VM in this ESXi can commit the snapshot and not corrupted ?
Thanks.
I've got one physical server that is running out of disk space with just a few MBs of disk space left, it is consumed by open VMware snapshot that was forgotten for few days.
So how to make sure the VM in this ESXi can commit the snapshot and not corrupted ?
Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When you turn OFF the VM, it will remove the VSWAP file, so hopefully you will have some space.
Otherwise you would not be able to power on the VM.
otherwise you will have to run off existing VMs, to obtain some space.
Otherwise you would not be able to power on the VM.
otherwise you will have to run off existing VMs, to obtain some space.
ASKER
Andrew, so in this case if I provision another ESXi with larger VMFS data store, can I manually move / migrate the whole VM directory and then commit the snapshot from there ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The vswp file is quite small it's just 1 GB, since the VM is old Windows Server 2003 that was still used as file server.
The previous technician who left the company forgot to close the snapshot.
So why migrating the whole directory with offline svMotion to another larger VMFS data store is risky ?
The previous technician who left the company forgot to close the snapshot.
So why migrating the whole directory with offline svMotion to another larger VMFS data store is risky ?
can corrupt snapshot.
ASKER
But in this case, the free disk space is almost 0 bytes.
Can I still do the snapshot ?