sara2000
asked on
delta.vmdk vs flat.vmdk
I heard that delta vmdk can not grow more than flat.vmdk.
I have a vm with snapshot and noticed the delata .vmdk is bigger than flat vmdk.
Can this delta.vmdk grow more than flat.vmdk?
I have a vm with snapshot and noticed the delata .vmdk is bigger than flat vmdk.
Can this delta.vmdk grow more than flat.vmdk?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, Andrew, I may have to deal with when it explodes. I am banging my head. Will I be able to delete the snapshot if the server stopped working?.
Like with every snapshot issue, each snapshot issue is different, you will be able to discard the snapshot, but what use is a server, if it's been rolled back two months ?
As for tying to commit the snapshot, it will take many hours, to recover the server, I would recommend a V2V using VMware Converter.
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 6.1
HOW TO: FAQ VMware P2V Troubleshooting
that way, you'll end of with a new server, without any snapshot attached, but a little bit of work, to re-add networking.
As for tying to commit the snapshot, it will take many hours, to recover the server, I would recommend a V2V using VMware Converter.
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 6.1
HOW TO: FAQ VMware P2V Troubleshooting
that way, you'll end of with a new server, without any snapshot attached, but a little bit of work, to re-add networking.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If I understood correctly, cloning (V2V) will bring the VM to the latest snapshot level, not the base disk level?
yes thats true
Not really-ish, depends what you mean...., a V2V does not even detect a snapshot, it will just create a CLONED COPY. V2V runs in the VM at the OS level, and just clones the disk out.
and a V2V is not really a CLONE, all it does is copy all files and folders to a new virtual machine disk.....and then convert, inject drivers.
It is not a CLONE, if you compare the Before and After they would be very different, and you've got to add all the Network Config....
the result is you get a copied conversion clone, effectively a new VM. A new VMDK.
What you get is what the CURRENT STATE is, in a new VMDK.
and a V2V is not really a CLONE, all it does is copy all files and folders to a new virtual machine disk.....and then convert, inject drivers.
It is not a CLONE, if you compare the Before and After they would be very different, and you've got to add all the Network Config....
the result is you get a copied conversion clone, effectively a new VM. A new VMDK.
What you get is what the CURRENT STATE is, in a new VMDK.
ASKER
We can only remove the snapshot in the maintenance window. I check the delta.vmdk everyday and it is growing, 10GB more than the flat.vmdk. Will the delta.vmdk grow forever or stop soon?
It is a Linux appliance and the software license is based on mac address. I am not sure V2V is a good option.
I think right now, only option left to delete the snapshot when it breaks or before.
It is a Linux appliance and the software license is based on mac address. I am not sure V2V is a good option.
I think right now, only option left to delete the snapshot when it breaks or before.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's unusual because the snapshot cannot normally be larger than it's parent, that's the theory.
It depends by how much 100GBs, or just a few because the metadata could take it over.
There have been occasions when we've seen this, and there have been issues with the snapshot, the same is true for the number of max snapshots = 32
but we've seen many more snapshots in use than this... and then machines have failed!