• Status: Solved
  • Priority: High
  • Security: Public
  • Views: 101
  • Last Modified:

Cant consolidate snapshots due to insufficient Disk Space!

Cant consolidate snapshots due to insufficient Disk Space!

Vcenter 5.5

I ran a comvault backup on a 11TB vmdk and did not realize i did not have enough space and comvault forced the snapshot anyway and now my 11TB Datastore dedicated just for that vmdk doubled in provisioned size to 22TB!  
Insufficient Disk Space
I have tried the steps in Hancock's link here https://www.experts-exchange.com/questions/28704560/Insufficient-disk-space-while-tring-to-consolidate-disks.html

With no luck :(  

The VM is powered off and i tried migrating it to a 12TB lun and it took almost 24 hours and got to 93% and then the task in vcenter just disappeard! no error or message!

Im guessing the 12TB lun was not big enough, but then why would Vcenter allow me to even start the Storage migration task?

anyway, I really need help on this one i am trying to avoid having to increase the 12TB lun to 23TB just to migrate the vmdk

Also what ever will be the fastest solution would be ideal.  I am worried i might of corrupted the data too :(

please help

Thanks
0
JB Blanco
Asked:
JB Blanco
  • 36
  • 26
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you do not have enough space to consolidate you can get into issues.

Can you send me a screenshot of the VM folder files ?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
VM Datastore with the .vmx file (main VM Files)

Af5K
Independent Datastore with the .VMDK files

cs500
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
is the VM actually writing to those snapshot disk, because they do not look very large....
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
JB BlancoSr Systems EngineerAuthor Commented:
Good question, all i know is that the datastore shows 22TB provisioned when the VMDK should only be 11TB in size.  I see what your saying on the second screenshot, i am not sure why they look so small.  Did you look at both screenshots?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
just so you know, i could care less about the snapshot or the changes.. I just want to get this VM backup in the state it was before the snapshot occured.  IF i could delete all the snapshots without it breaking the parent disk then i would.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
screenshots of VMs disk please...so I can advise accordingly....
0
 
JB BlancoSr Systems EngineerAuthor Commented:
The second screen shot is the Datastore that holds the Disk that is in question that the snapshot was done on.  its hardisk#2 on the edit VM settings properties

what other VMs disk screenshot do you need?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would like to see what actual filenames are in the Disk setting Properties, so I can provide a solution.

It's difficult enough we do not have remote access trying to provide a working solution and fix...

and you previously tried the creating a snapshot and waiting 120 seconds, and deleting ALL ? and did not work.... what did it do, create a new snapshot, so increased the number of snapshots or did it give an error.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
It wont let me even create a snapshot  - same message insufficient disk space :(

I am more than happy to have you teamviewer me for remote access.  Just let me know.

Here is what i think you are asking for.  You need to guide me where you want me to go so i can get you the correct screenshot.  

asdfasdf
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Or is it this?
sdfsadf
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I am more than happy to have you teamviewer me for remote access.  Just let me know.

I'm afraid EE states that all communication must be via the forum, and no remote access is allowed, as it is seen unfair to other Experts that want to help!

Okay something is very wrong with your VM. There are two methods we can try to fix this by creating a new VM (clone) and destroying the old VM after testing the new CLONE.

So do you have vCenter Server ?

and do you have enough storage space to create a new "working copy" of this VM ?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
did you see the size of the disk?  its showing 4tb because of the first message DiskCapControlVaule out of range

The other disk Hardisk#3 is a 15TB datastore VMDK connected to that VM.  How would i be able to clone this VM with all of those DISKS???

and if i am going to do that, then is that faster and more efficent then me just adding and additional 12TB to CS500-DEV-SQLBACKUP-e datastore to make it a total of 24TB and do the storage migration of the .VMDK???

I am trying to avoid this because one, it will require more storage and two, the time it would take to do the storage vmotion of the .VMDK will take forever.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
and if i am going to do that, then is that faster and more efficent then me just adding and additional 12TB to CS500-DEV-SQLBACKUP-e datastore to make it a total of 24TB and do the storage migration of the .VMDK???

Sorry, i mean adding 12 more TB of lun space to the Datastore i tried migrating the .VMDK to earlier that failed at 93%
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We are not migrating....

are these values correct ?

the disk2 is 4GB ?

The only method to fix this issue is

1. CLONE to a new VM, the new VM will be a VM without any snapshots.

or

2. VMware Converter, and create a V2V to a new datastore, resulting VM, without snapshots.

or

3. Escalate to VMware Support they can do a webex, and do probably 1 or 2 above...

or

4. DELETE VM, and Restore from Baxckup if needed.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
are these values correct ?

the disk2 is 4GB ?

The disk#2 is showing 4TB because there is an error. When i click on the disk in VM edit settings,
fasdf
This the error i get and then it will show only 4TB which is not true.,  it should show 11TB but the disk is over filled due to the snapshot hence why in the first screenshot in my original thread it shows 22tb provisioned size

We are not migrating....
I know we are not migrating!

1. CLONE to a new VM, the new VM will be a VM without any snapshots.

or

2. VMware Converter, and create a V2V to a new datastore, resulting VM, without snapshots.
Again, I will need LOTS of storage space on my SAN for both procedures am i right??  This VM has 2 Independent DAtastores just for its VMDKS.  One called CS500-DEV-SQLBACKUP-e wich holds 11TB vmdk, and another called CS500-MIA1DAS01-Archive which holds a 15TB vmdk!

So if i clone or v2v whichever you prefer will it just clone the VM itself and not include the VMDK's?  or will it include them as well which in that case of course i dont have storage for that.  

Again, wont migrating this one VMDK that has balooned to 22TB to a larger datastore resolve the problem? and wont that be quicker than what your suggesting?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
CLONE or V2V is a data copy, so slow....

CLONE-ing or V2V will just copy the data in use and merge the snapshots.

what is a concern is the disk setting error.... which means CLONE will likely barf....

so V2V with VMware Converter, will just copy the data in the OS in use. (so smaller)

Those are your options...

Does the VM power on ?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
CLONE-ing or V2V will just copy the data in use and merge the snapshots.

Can you please answer my question i stated about this process?  will it or will it not also copy the .VMDK's HardDisk#2 and HardDisk#3 along with the VM?  so what, I would need like a 30TB volume of space!!??? are you kidding me?  Am i thinking this the wrong way?  

please explain

and No the VM does not power on
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, VMware Converter, can possibly not be used if the VM cannot be powered.

What disk size have you set the VM disks to ? (excluding snapshot), it will only copy the defined disk size, but something is wrong with your VM, or disks have become corrupted.

Can you use the vSphere Web Client, because using the vSphere Client is NOT Supported with large disk, greater than 2TB/4TB
0
 
JB BlancoSr Systems EngineerAuthor Commented:
I want to make sure you are understanding the situation here.  

Im sorry, i should of mentioned this in my original thread.  The VM cant power on because Vsphere is forcing me to consolidate.  

The main problem with this VM not powering on is because of Hardisk#2  on Datastore "CS500-DEV-SQLBACKUP-e" .  A snapshot was done on that .VMDK which took up double what the Datastore/Lun size is set for which is 11TB.  

Of course the VM wont power on because it keeps complaining that there is not enough space on that Disk for the VM to power on.  But i see a message saying i need to consolidate.  But i cant consolidate, because of Hardisk#2.  

So my objective here is to do something with the VMDK in Harddisk#2.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Here is what happens when i try to power the VM on
adfasdf
Hitting Retry just gives me the same message.

As you can see it is telling me about mia1share03-00002.vmdk which is Hardisk#2 on Datastore CS500-DEV-SQLBACKUP-e
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The VM cant power on because Vsphere is forcing me to consolidate.  

that not really true....the datastore is full it cannot grow the snapshot. Hence power on fail. If you had space on the datastore VM would Power On, but this is dangerous, because as the snapshot grows, VM will fail again.

Get rid of snapshots and merge them. If you can... or they are corrupt.

Can you view the VM properties using Web Client

We could CLONE out the Disk2 to another datastore, but you will need at least the same size as disk 2. e.g. 11TB

The new virtual disk will be 11TB, the snapshot will be merged into the parent on the clone operation.

So CLONE Disk2 on current datastore to new virtual disk on new datastore.

Once this is done, and it's going to take time, then add disk2 on new datastore back to VM, and delete the older disk2 with snapshots.

We will know very quickly if Disk 2 is corrupted.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Do you mean Clone? or Storage Vmotion?
I think you forgot that I already mentioned that i had tried to storage vmotion the VMDK to a new datastore that was 12TB in size.  I created a brand new 12TB LUN to migrate this disk to and it took over 24 hours and stopped at 93% with no error or message! it was strange.  So i imagined it got close to completely migrating the VMDK over and perhaps because of the snap shots maybe it tried to merge them?

Anyway  as i stated earlier, i can add more space on the problem datastore by increasing the LUN Size but i was trying to avoid having to do that.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
what i mean is the Task just literally dissapeard after it got to 93%.  No log or anything saying that it was canceled or nothing
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Yes i can access the VM properties via the web client.  why?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Because the vSphere Client does not supported managing a VM, with disks over 2/4TB.

Do you mean Clone? or Storage Vmotion?
I think you forgot that I already mentioned that i had tried to storage vmotion the VMDK to a new datastore that was 12TB in size.  I created a brand new 12TB LUN to migrate this disk to and it took over 24 hours and stopped at 93% with no error or message! it was strange.  So i imagined it got close to completely migrating the VMDK over and perhaps because of the snap shots maybe it tried to merge them?

Anyway  as i stated earlier, i can add more space on the problem datastore by increasing the LUN Size but i was trying to avoid having to do that.

not doing any of that....

We will use the vmkfstools command at the command line, to create a copy/clone of disk2, to a new datastore.

execute the following command...(at the console or remotely via ssh)

vmkfstools -i <most recent snapshot file name> /vmfs/volumes/<temp folder name>/<newfilename.vmdk>

Open in new window


in the VM Folder you need to type

vmkfstools -i mia1share03-00002-sesparse.vmdk /vmfs/volumes/<temp folder name>/mia1share03.vmdk

Open in new window



the command is case sensitive, you will need to specify new datastore, and create a new folder

this process will take some time to complete, it will merge the snapshot into the parent, and create a new parent virtual machine disk.

if validation FAILS - VM Disk is corrupt, and that can happen if you run out of storage space!
0
 
JB BlancoSr Systems EngineerAuthor Commented:
I was going to try increasing the LUN size of the new datastore i created and try the Storage Vmotion of the Disk to the New datastore again.

Is your method of Cloning a better proceedure than this?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Please follow my instructions, yes my method is better. You need to get rid of your snapshots!

The command posted will confirm if the VM disk is corrupted and broke! and then you'll need recovery or restore!

and that's all disks with SEsparse in them!

Storage vMotion is not going to solve your issue, you'll end up with the same VM with snapshots!
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Ok! i will get right on it!  Thanks,  I'll keep you posted
0
 
JB BlancoSr Systems EngineerAuthor Commented:
But wait!  if i storage vmotion the problem VMDK over to the new datastore, yeah I'll end up with the same VM with snapshots but i should then be able to consolidate right?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
i need to know if your method can be done at anytime and not affect performance with any other VM's on the host i run this command from
0
 
JB BlancoSr Systems EngineerAuthor Commented:

in the VM Folder you need to type

vmkfstools -i mia1share03-00002-sesparse.vmdk /vmfs/volumes/<temp folder name>/mia1share03.vmdk

What do i put for temporary Folder name? why am i creating a temporary folder for?  and you said i will need to specify a new datastore.  Ok will the commandline prompt me to enter the name of the new datastore?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
But wait!  if i storage vmotion the problem VMDK over to the new datastore, yeah I'll end up with the same VM with snapshots but i should then be able to consolidate right?

think about that move, and time....

1. time to migrate........ X hours

2. time to consolidate (merge snapshot!) Y hours

Total Z = X + Y

Any data I/O can/could affect performance of the datastore! I have no idea, what your datastores are made off, and what current VMs are on them, and whether they would be affected.... I would be guessing....

But the host has to read a 11TB file, and merge and write to another datastore!

- ???

CLONE a single VMDK = X Hours!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
the foldername could be anything, temp, or maybe the name of the VM would be a good idea!

the vmdk, needs to be created in a folder - good practice to arrange you VM files!

I'm afraid you will have to supply ALL the correct details, and name of datastore, it will not ask you ....

and make sure this new datastore has enough storage space, maybe the same datastore as you were going to use to MIgrate to.... (what you call Storage vMotion - but that's what we call it when the VM is Powered ON, this VM is off, so cold migration!)
0
 
JB BlancoSr Systems EngineerAuthor Commented:
I'm afraid you will have to supply ALL the correct details, and name of datastore, it will not ask you ....

vmkfstools -i mia1share03-00002-sesparse.vmdk /vmfs/volumes/<temp folder name>/mia1share03.vmdk

Where in this command syntax, do i input the new datastore name???  do i first browse into the datastore in vpshrere and create a new folder?  and then input it in the command?  
Oh and can it be the label of the datastore? or does it have to be the long name?  

I am not a linux guy by no means.   So you have to fully explain these commands and make it dummy proof for me.  Sorry
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
vmkfstools -i mia1share03-00002-sesparse.vmdk /vmfs/volumes/datastore-name/mia1share/mia1share03.vmdk
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you will need to create the folder name on the new datastore, in advance of running the command, and the command needs to be run from the folder with the original vmdk file....

the folder with this file in it

mia1share03-00002-sesparse.vmdk
0
 
JB BlancoSr Systems EngineerAuthor Commented:
In the command you specified above

vmkfstools -i mia1share03-00002-sesparse.vmdk /vmfs/volumes/datastore-name/mia1share/mia1share03.vmdk

Does it matter that i name the .vmdk like that?  shouldn't it be named the same as the original disk which is MIA1SHARE03-000002.vmdk????

or does it not matter?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Ok Hancock,

I get "failed for source disk The file specified is not a virtual disk (15)."

I ran the command from the source datastore folder where that MIA1SHARE03-000002.vmdk file resides
0
 
JB BlancoSr Systems EngineerAuthor Commented:
I think you may have gave me the wrong option on the vmkfstools
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Sorry, Datacentre lost power, and hard lines shutdown....

right commands, and correct file the file you use is the last snapshot...

vmkfstools -i <most recent snapshot file name> /vmfs/volumes/<temp folder name>/<newfilename.vmdk>

as I suspected something wrong with the files!

Possibly Corrupt.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
I dont think it is corrupt.  That error message "failed for source disk The file specified is not a virtual disk (15)." is just telling me that it does not recognize it as a virtual disk.  And in Vcenter Web gui it specifies it as a file not a virtual disk.  

asfasdf

it works if i just use the actual MIA1SHARE03-000002.VMDK instead of the sesparse.vmdk snapshot file.  
Maybe that is the wrong option (-i) for snapshot file
I mean its the disk we are cloning not the file correct?  
When this snapshot was getting created, i did not let it finish.   I stoped/killed the backup that was creating the snapshot immediately after the VM crashed.  It was no more than maybe 1 minute into the snapshot creation phase that i did this

So will specifiying MIA1SHARE03-000002.VMDK as the source be ok to use with this command?

Also How do i Specify THin provision???  i dont want the default Zeroed Thick!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you exclude the snapshot, then what you are left with is not the entire disk!

So you can exclude the snapshot and just clone out the parent disk.

Your virtual machine is virtual disk = parent + snapshot

if the snapshot is corrupted, and you discard it, and just use parent, you will be missing data, in effect rolling back the VM.

the command is thin.
0
 
JB BlancoSr Systems EngineerAuthor Commented:
do i just type the word thin after your command
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
vmkfstools -i <most recent snapshot file name> /vmfs/volumes/<datastore>/<temp folder name>/<newfilename.vmdk> --diskformat thin

syntax is here

https://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vmkfstools.html

you can use his

-e --chainConsistent

to check consisency of chain of snapshot/parent
0
 
JB BlancoSr Systems EngineerAuthor Commented:
trying any of the sesparse.vmdk files fails with "Not a Virtual Disk"  So it wont work, i have no choice but to use the Virtual Disk.  its almost like this command is not meant for Vcenter 5.5 but for older version.,.   perhaps when they were called delta.vmdk instead of sesparse.vmdk

Thats why i was thinking there is another command we should be using for 5.5 that will give us the desired outcome

Any way,

I mentioned i dont care about the snapshots.  I just want things back the way they were before shit hit the fan

So i am running it now on MIA1SHARE03-000002.VMDK Thin provision, I'll let you know the outcome when its done

Thanks for all your help Hancock!

Your the MAN!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
its almost like this command is not meant for Vcenter 5.5 but for older version.,.   perhaps when they were called delta.vmdk instead of sesparse.vmdk

Nothing to do with vCenter Server, it's a host command, and it's broken snapshot! It happens if you create a snapshot with no datastore space!

The snapshot is corrupted it happens.

All you need to do is remove current virtual disk from the VM, do not remove from disk.....

the delete the snapshot (corrupted).

Re-add the disk back to the VM.

There  is nothing to be gained from cloning the disk...at present....

unless you want a thin disk....

No problems
0
 
JB BlancoSr Systems EngineerAuthor Commented:
!!!!!???? what?????

You mean to tell me, thats all i had to do from the beginning?

I know i stated how i dont care about the snapshots and just want this VM backup the way it was before shit hit the fan,

LOL' why did'nt we think of this earlier?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
because you may end up with rubbish and corruption by just discarding snapshot
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Ok but as of now, we know for certain that the snapshots are corrupt right?

So discarding the sanpshots is ok right?  since at this point, there is no way to recover those snapshots.  

your thoughts?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Possible, we do not have access to confirm.

Escalate to see if VMware Support have any ideas confirm corruption

try a CLONE using Web Client, but thats going to need 11TB on a LUN
0
 
JB BlancoSr Systems EngineerAuthor Commented:
I disconnected the vmdk from the VM like you said and deleted the corrupted snapshots

I re-connected the vmdk to the vm and it seems to be stuck at 99%  But it took a little while for it to get to 99%

Is this normal?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Ok it finished just now, but the VM is still saying it needs to consolidate

Should i try to consolidate? or ignore?  i have the option to acknowledge to green
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Ok it finally finished reconfiguring.  I guess it just took a while.

I still see VM needs consolidation.   I did not remove "MIA1SHARE03-000002-ctk.vmdk" File since i am not sure what that file is and the only corrupt snapshot files we identified i already deleted.  

Should this file be removed aswell?  it is about 5gb and there is also one for MIA1SHARE03-000001-ctk.vmdk
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
vSphere is dumb it only gives the Consolidation warning when it detects a 00000x.vmdk file present in the VM folder it has no idea oe intelligence as to whether you need to consolidate

any what are you consolidating you have now dropped the snapshot

htose files are not required change block tracking files there is also a snapshot files called .vmsd and .vmsn
0
 
JB BlancoSr Systems EngineerAuthor Commented:
This is what my datastore looks like now after i removed the two sesparse.vmdk files that we confirmed are corrrupt!
asdfasdf
Should i remove everything that reads 00000x??  

Im confused, which one is the actual VMDK?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
correct those are snapshots we prefer to archive rather than delete
 
.0000x.vmdk are snapshots

the parent has no 00001 or 00002.vmdk

but whatever you need to do
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
before you delete just confirm filenames in disk properties

because this is a 3 virtual disk VM with at least two disk on different datastores with 2 and 4 snapshots
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Hancock, im sorry man, your going to have to be more specific,

Is there anyway we can chat in the Tech Help chat window here that i keep seeing?

when i said i disconnected the vmdk from the VM earlier, the VM properties showed MIA1SHARE03-000002.VMDK as the connected VMDK.  So after i disconnected it, i removed just the sesparse.vmdk files since i thought those were the snapshots.  So instead of reconnecting to MIA1SHARE03-000002.VMDK, i should of reconnected the VM to MIA1SHARE03.VMDK (the Parent)?  

I just want to know is it safe to remove those remaining 0000x.vmdk files and ctk.vmdk files?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
yes those are also snapshots

sorry I dont do EE LIVE

but leave filename.vmdk

but please note this is all fine in theory dropping snapshot files BUT it could leave the remaining parent VMDK OS volume corrupt.....

and out find that out later starting the VM
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Ok!  we did it!!

your the man Hancock!  

Its backup like it never happened lol

This is exactly what i wanted to accomplish.  I never needed these snapshots lol.  Its a shame we just did'nt remove them earlier.

I was under the impression that the disk would not work at all without them or the VM required them to be consolidated or it would not power on.  

Quick question:  I do still see the notification that the VM requires consolidation.  Is there anyway to remove this alert?  is it safe to try running consolidation?
0
 
JB BlancoSr Systems EngineerAuthor Commented:
Disconnecting the vmdk from the VM and Removing the Snapshots manually and then reconnecting the vmdk to the VM
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
snapshot files still present

consolidate what

no snapshots

you can try either will do nothing or give you an error

if VM starts after dropping snapshot files thats lucky!
0
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

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

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