It seems that I ran out of space on a virtual partition of my VM. The
VM is a Windows 2003 Standard Edition.
I've deleted some unnecessary stored files from the storage (~2GB) and
Virtual server started to run as normal once again.
But when I check the storage it says there is 2.5GB free space so that means
I'll experience the same issue soon again.
I have experienced the exactly the same issue twice before and when I have
deleted a snapshot from snapshot manager that has solved the problem before,
but now even there is no more snapshot left on the snapshot manager to delete.
If I browse the datastore I can see that (pic1)
So I am assuming that ****.local-000002.vmdk & ****.local_1-000002.vmdk
files are snapshot files.
Being honest I don’t need any snapshot on this server because I am already
using Symantec Backup Exec on this one.
I've read some posts in here and some solutions I've found which are not really suitable
with my situation;
1. Create a new snapshoot and then delete all from snapshot manager, that removes all the
snapshot files
I don’t have no more enough free space for a new snapshoot
2. Move the VM to other host that auto. removes the snapshot files
I do not have any other host in my environment
So how do I delete those files(snapshots) without interrupt anything on the
server, or am I on the wrong way?
Regards,
Serhan
do it then
when done run
vmkfstools -i current-vmdk-with-snapshots.vmdk nfs-storage/consolidated vmdk
do that for every virtual disk used by that VM
when done change the VM so that it uses the new vmdks on NFS instead of the current -00000.vmdks
when the test is successful you can delete the old vmdks and re-import the files from NFS
if unsure post the vmx-file
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
Hi
you can not delete snapshots without free space.
In your environment where adding more storage disks or using a temporary second host to commit the snapshots is impossible the only answer is:
give up some of your VMs and use the free space you get by deleting them to commit your snapshots.
I think you forgot the option to use a non ESX-host temporarily ...
I would rather commit the snapshots using a Windows host or backup one of the rarely used VMs to a Windows host
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
I dont have any other VM on the same storage...
do you have another host that could work as a NFS-server ?
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
No I dont have an other host either. But I can install ESXi4.0 on to one of the work station if I need it.
??? Workstations are not hosts ???
So can you use one of your workstations as an NFS-server ?
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
Sure...
do it then
when done run
vmkfstools -i current-vmdk-with-snapshots.vmdk nfs-storage/consolidated vmdk
do that for every virtual disk used by that VM
when done change the VM so that it uses the new vmdks on NFS instead of the current -00000.vmdks
when the test is successful you can delete the old vmdks and re-import the files from NFS
if unsure post the vmx-file
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
I have installed ESXi 4.0 on to one of the workstation and I have used vm converter to move current wmserver to new host. That removed all snapshot files and I have put vmserver back to orginal host. All ok now.
Many thanks for answers.
Serhan
hehe - you like the complicated approach more than the easy one 😉
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook