VMWare Vsphere datastore and VM hard drive usage question

I have a Vsphere 4.1 server that currently hosts 2 VM's.  The hard drives are 10-15k rpm Raid-10 fashion and I have about 600gb of total storage on one datastore.

Currently the datastore has been running low and I'm kind of curious as to why because I have VM-1 provisioned with 2 drives (50GB and 225GB respectively) and VM-2 provisioned with 1 drive (150GB)

Total its about 425GB of provisioned space.  I am however concerened that the datastore only shows 4gb of available now.

Under further scruitiny, I looked at the datastore folders and noticed some redundancy to the VMDK files for each VM.

What I think happened was that I replicated from a physical to this Vsphere server and it did a few passes to keep the 2 boxes current until I was able to power down the phsical and power up the VM's.  

Attached are the screenshots of the VMDK files for each VM below:

phxex
phxsql
My question is, is it possible to delete one of the redundant files or are they both necessary for the VM's to boot properly?  For instance there is a C.vmdk and D.vmdk for the phxex01 server.  There is also a C-000002.vmdk and a D-000002.vmdk.

How can I tell which ones are active, and or is there a way to combine the two safely?

Thanks.
jhuntinAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The reason for the lack of datastore store space, is your Virtual Machine is cirrently running on a Snapshot. You must not delete them, you must merge them correctly.


A snapshot is NOT a backup of a VM; that is a gross misconception.  

A snap shot is a way to preserve a point in time when the VM was running OK before making changes. A snapshot is NOT a way to get a static copy of a VM before making changes.  When you take a snapshot of a VM what happens is that a delta file gets created and the original VMDK file gets converted to a Read-Only file.  There is an active link between the original VMDK file and the new delta file.  Anything that gets written to the VM actually gets written to the delta file.   The correct way to use a snapshot is when you want to make some change to a VM like adding a new app or a patch; something that might damage the guest OS. After you apply the patch or make the change and it’s stable, you should really go into snapshot manager and delete the snapshot which will commit the changes to the original VM, delete the snap, and make the VMDK file RW. The official stance is that you really shouldn’t have more than one snap at a time and that you should not leave them out there for long periods of time. Adding more snaps and leaving them there a long time degrades the performance of the VM.  If the patch or whatever goes badly or for some reason you need to get back to the original unmodified VM, that’s possible as well.  

I highly recommend reading these 2 articles on VMware Virtual Machine Snapshots:

Understanding Snapshots - http://kb.vmware.com/kb/1015180
Snaphot Best Practices - http://kb.vmware.com/kb/1025279

Also check out the following Snapshot Articles by Eric Siebert

Pt.1- http://is.gd/Lajg4p
Pt.2- http://is.gd/NdKQWC
Pt.3- http://is.gd/tp2vEK

Check Snapshot Manager, for a Snapshot Entry. Shutdown the Virtual Machines, and DELETE the Snapshot, this will merge the snapshot into the parent disk.

Be Patient, this can take several minutes, to hours or days to complete. (it may stick at 95%, JUST BE PATIENT) It will complete.
0
jhuntinAuthor Commented:
So this is the snapshot manager for PHXSQL.

snapshot
Are you saying shut down PHXSQL, and delete the non-bootable snapshot and then restart the VM?

Thanks for your help!
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, Shutdown the VM. (it's quicker)

either DELETE ALL, or DELETE BOOTABLE and DELETE NON-BOOTABLE, this will merge the changes.

and then restart the VM.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jhuntinAuthor Commented:
This wont obviously delete the VM's hard drive(s)? Just want to be certain. Thanks again!
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
no, it will remove the snapshots and merge with the parent disk.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.