• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2413
  • Last Modified:

VMWARE working directory options


I have a question regarding the working directory in VMWARE.  Here is the background:

I have a Windows 2003 server hosting a virtual SBS 2003 and another virtual instance of 2003.  I allocated all disk space to both virtual machines when I created then (as opposed to the 2GB option).  I originally set both machines working directory to use partitions that I created specifically for these machines (c: - host partition, f: - SBS partition, g: - 2003 partion).  Both f: and g: (after allocating all disk space to the virtual machine ((the *-flat. vmdk)) have only 4 GB free space on each.  A couple of weeks ago I ran out of space on the f: drive while attempting to make a snapshot:


To deal with this I changed the working directory of the virtual server (as I mistakenly thought this would only affect where the snapshot is kept).  After a short period of time I noticed that the new location is being filled up with vmdk files (*-000001.vmdk, *-000002.vmdk, etc).  The new folder (on the c: drive) is filling up so I wanted to get some feedback on the best course of action.

Based on other questions being asked in the VMWARE area I understand that *-000001.vmdk files are the files that are currently being used.  So if I understand correctly what happened was that by redirecting my working directory I also redirected the original vmdk file which then incremented itself based on the work I was doing in the virtual machine.  I would like to go back to using the original f: drive as the working partition (and the original vmdk file) BUT have the snapshot stored elsewhere (I don't have the room for it in the f; drive).  The separtaion of these two does not seem possible (at least in the free version).   My two questions are:

1) Can you change the working directory back to use the original vmdk file?
2) what is the purpose of the *flat.vmdk file?   This is the biggest file in the f: and g: drive, yet both virtual  machines also create vmdk files as well.  I thought that by alocating space when i create the file that will be all the space I would need.

Any input would be appreciated.



PS I found this article :  http://www.vmwarez.com/2006/11/beware-long-snapshot.html   Is this a contirbutor?
1 Solution
GVC_AdminAuthor Commented:

The latest update is that link at the bottom of the question has pointed me in the right direction.  It appears that if you leave a snapshot on the system (at least in the free version) it will be incremented continuously based on changes until you run out of room.  The theory goes that once you delete these snapshots, the *.000001.vmdk files will also be removed and you will go back to your original .vmdk file, which is a pointer to the *-flat.vmdk virtual disk (if I am wrong please let me know).  My issue it appears is that since I let the snapshots get so big the vm server is timing out when it tries to clear out the incremented vmdk files.  

Anyways, if anyone has any thoughts I would be happy to hear them.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now