000001.vmdk file, but NO snapshot

[ken43]

I am trying to understand why one of my virtual machines has a 000001.vmdk file, but that server does not have a current snapshot (and I can't remember it ever having one since I've been managing it over the last 3 years). I am attempting to free up some space on my storage where this virtual machine resides, and am curious what the files are. I have a 50GB flat.vmdk file, a 50GB 000001.vmdk file, and a 7GB 000002.vmdk file. The actual volume these files represent is a 50GB volume. Thanks for the help.

[a_p_]

Sometimes you don't see the snapshots in the snapshot manager, although they exist, because the snapshot manager relies on the vmsd file which sometimes does not contain the correct data.

Please post a list of the files in the VM's folder (showing name, size and time stamps), the free disk space and the VMware product and version you are using. Also attach the VM's vmx file. Then I can tell you how to remove the snapshots.

André

[continuum]

IMHO the safest way to get erid of the snapshot is vmkfstools

you would check if the 000001.vmdk is the one referen ced in the vmx - if yes a comand like

vmkfstools -i blabla-0000001.vmdk consolidated.vmdk

would merge the snapshot to the basedisk.

If the VMFS - volume where the VM lives now is full - put consolidated.vmdk to a second datastore.

I think that is a safe approach as you do not change the VM as it is now until you was able to verify the consolidated.vmdk with a testrun.

If you use a target on a different datastore this will also work if none of the regular methods would work because you are running out of space ....

_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

My host software is VMware ServerVersion 2.0.1, Build 156745. free disk space is 79.8GB on a 475GB volume. vmx and file sizes attached/included. Thanks for the help

[continuum]

oops - on VMserver the story is different.

Please post a filelist that displays full filenames - also include the content of the directory F:\BCNServer2 - it may have further files we need to include in the analysis




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

here is the file list with complete file names (sorry for the previous pic that cut off the extensions). this screen shot is all of the data in the F:\bcnserver2\ location. thanks for the help.

[continuum]

Hmm - I need the embedded vmdk-desriptors - please read http://sanbarrow.com/vmdk-howtos.html#editvmdk

On next post then add all the small vmdk-files you have now plus the embedded description for the 000001.vmdk and the 000002.vmdk




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

here are the vmdk descriptors for 01 and 02, plus a small production vmdk file; thanks again:

[continuum]

weird - very weird

the file Windows Server 2003 Standard Edition BCNServer2-admindata-000002.vmdk is not a snapshot - it is a standalone disk.

Can you explain how this VM was created - or do you have any info on the history of this VM ?




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

weird - very weird

the file Windows Server 2003 Standard Edition BCNServer2-admindata-000002.vmdk is not a snapshot - it is a standalone disk.

Can you explain how this VM was created - or do you have any info on the history of this VM ?<br><br><br><br><br>_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

-

---

Sorry, I was not around when the VM was created, and we don't have documentation detailed enough to describe the creation process. I just know that there hasn't been a snapshot since I've had it for the last 18 months.

[a_p_]

I just know that there hasn't been a snapshot since I've had it for the last 18 months.

That's probably what you think by looking at the GUI. However continuum is correct, your admindata has a snapshot 000001 running since more than 3 years. That's probably why the size of the snapshot is close to the size of the base disk.

To make sure the 000002 file is obsolete, please post the latest vmware.log file or take a look at it to see whether or not the 000002 file is mentioned in it.

I'm not familiar enough with VMware Server to tell you how to remove the snapshot. I think there might be a tool like "vdiskmanager" to either consolidate the snapshot or - to be save - create a clone of the admindata disk. I'm sure continuum can help you with this.

André

[continuum]

yep - we need more info to find out whats up with that 000002.vmdk - logs or the vmx would help

to consolidate snapshots in VMserver vmware-vdiskmanager is to be used like

vmware-vdiskmanager -r vmdk-with-snapshots.vmdk -t 0 consolidated.vmdk

watch out - many vdiskmanager versions of VMserver are buggy and can't work with snapshots !!!!!!




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

here is the vmx file. can you tell me what logs you are looking for, and where to find them? here is a screen shot of various logs for this VM, but not sure if this is what you want. I am attaching the 2 most recently accessed logs from this location. thanks

[continuum]

can I see the vmware-2.log as well

from what I see I would think that the 000002.vmdk is not needed .... just want to confirm




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

from my perspective, no snapshots are necessary on this machine. I'm just looking for ways to free up space. Thanks

[ken43]

here is the vmware-2 log file

[continuum]

run

vmware-vdiskmanager -r "F:\BCNServer2\Windows Server 2003 Standard Edition BCNServer2-admindata-000001.vmdk"  -t 0 "F:\BCNServer2\admindata.vmdk"

if that works with your vdiskmanager version - unsure as so many buggy versions exist that can't do that - you can test the consolidated vmdk and later delete the 00000*.vmdks

Your vmdks don't performm well - are you sure you shrink your growing vmdks often enough ?

the buggy versions will claim "can't work on partial chains"




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

Before I run the command you provided, can you please explain exactly what it will do? I don't follow your suggestion to 'test the consolidated vmdk and later delete the 00000*.vmdks'. Would you please expand on this process--exactly what steps do I take after before/after running this command, and how do I 'test' the consolidated vmdk. Again, I really appreciate you taking so much time to evaluate my problem and educate me on VMwre.

As for shrinking my growing vmdks, no, I don't do this--didn't know I needed to. I am far from a VMware expert, but I thought when I inherited this config that my servers had fixed size disks.

[continuum]

sorry for late reply ...

the command I suggested will operate on the one vmdk that has the snapshot.

It creates a new vmdk where the old basedisk and the snapshot are merged into a new one without snapshots.

It is a good idea to test this new vmdk before you delete the two old files.

So you would then edit the VM and remove the old vmdk with 000001.vmdk in the name.

Then you would add another disk by selecting "use existing vmdk" - now you select the newly created consolidated.vmdk

Boot the VM once and check if it looks as expected.

If yes - you then can delete the two no longer used vmdks from your physical disks.

lets check this now - I will answer your other questions later

Ulli




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[ken43]

I've reviewed the Virtual Disk Manager User’s Guide so I can understand what we are going to do, and it all makes sense. I do want to clarify a couple of points. The guide warns about backing up the data before using disk manager; is the 000001.vmdk the only file I need to backup? The guide doesn't specify that the VM needs to be shut down during the new disk creation, but it seems to make sense that it does. If so, can you estimate how long it will take to perform this process so I can plan ahead with users, etc.. Obviously the VM has to be shut down to switch disks; is there anything I need to be careful of if the VM doesn't boot as expected after the new disk is installed? Finally, I have 79GB free on the host F drive, where this VM resides; I assume that is enough free space to perform this operation? Thanks for the handholding