Vmware snapshots

A Snapshot is a Snapshot, there is no difference between the Snapshot that you create manually, and the snapshot that Quest vRanger triggers to backup the virtual machine. When vRanger backs up a virtual machine, it invokes a snapshot (creates), so VMware ESX server takes the read lock off the main vmdk file, when the lock is removed off the main vmdk file, vRanger can backup this main vmdk file, whilst it is being backed up, changes made in the virtual machine are written to a delta file (the snapshot), after the backup is completed, vRanger closes/deletes this delta/snapshot by merging it with the main vmdk file.

VMware Snapshots allow you to create snapshots for patching, making small changes, so you can roll them back. Snapshots  are not designed to run ion production for a long time, it is not recommended to run production servers for longer than 2 days ona  snapshot.

Quest vRanger is a backup product that produces a FULL backup of the virtual machine, using the VMware Snapshot functionaility.

let say I have a VM machine that I want to deploy updates or install an application on it.
I will take a snapshot of it using the built-in vmware snapshot function.
Then after the deployment the VMachine , for some reason, crashes and can't come back up. In this case snapshot previously taken by the vmware built-in function will  help or will not?

Yes, this is exactly what VMware Snapshots and Snapshot Manager is for, You take a snapshot before applying changes to virtual machines, e.g. patches, changes etc.

if it doesn't work, you select Revert to Current Snapshot or Go in Snapshot Manager, these diiscards all the changes you've made, and restarts the machine, before the changes, or patches were applied.

If you want to keep the changes you select Delete, and all the changes are merged into the main vmdk disk.

The reason that Quest vRanger restore takes longer to restore, is because it's copying and restoring the entire virtual machine.

Snapshot is quicker for small changes, but be warned do not let them run out of disk space, and only keep them running for 2 days (no more). You should work on having at least 15-20% additional space for snapshots.

So why do companies buy third pary such as Vranger instead of using the built-in snapshit function ?

I also want to know which one is faster in restore operation, Vranger or the Built-in snapshot revert ?

SNAPSHOTS are not a backup.

Comapnies purchase Quest vRanger or Veeam Backup to backup the machine.

Snapshots are not designed for backups.

You should obtain a third party backup product for backing up virtual machines, this is the number one question we get asked on EE, Snapshotting is not a backup product.

Rollback is quicker, after patching, than a complete restore, but Snapshot are not a backup.

If you use the Snapshot function for Backup, you will get into trouble sooner or later with your virtual machines. Snapshots are not designed to run in production for longer than 2 days, because the size of the delta disk expands.

have a read of this VMware KB article

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180

As long as you can save the snapshot as a file, then I think it can be used as a backup.
where is the problem ?

You cannot save the snapshot file. Although it is a file, you cannot copy it, and it's of no use to you without all the other files and main vmdk.

if a VM machine VMDK is 4GB.
The first time you take a snapshot , what will be the size of the snapshot? I guess 4 GB
then you deploy updates , install Apps.
the second time you take a snapshot, the VMDK will be 4.5 GB. what will be the size of the snapshot?
is it going to be 4.5GB or 0.5 GB?

When you first take a snapshot the size of the snapshot is ZERO (0), the Snapshot file grows as the data is written to it.

No more data is written to the main vmdk file. All the changes are written to the snapshot file. So it depends on how many data writes are written by the virtual machine.

On an average monthly patch file session, it could be approx 2GB.

The snapshots grow much larger than, that it's not just what data you are adding to the machine, it's ALL the virtual machine writes are being stored, to merge later.

I can only advise you, that NOT having a third party backup solution and using Snapshots is a bad idea.

Any VMware Expert will state the same.

Just search EE, and see how many questions we get with Snapshots, when they GO WRONG! and then you have to use VMware Converter because the machines runs out of disk space, machines do not start, a virtual machine can only have a maximum of 29 snapshots. They are problematic, and only should be used for short periods. If you delete a large snapshot, it can take hours, crash the machine, corrupt the machine etc

Actually I was not trying to avoid purchasing third pary, but just understanding the difference.
I believe I came up to understand that the Vranger backs up the whole vm machine vmdk file.

so what does the snapshot contains.
As I gave you an example. when a VM machine vmdk is 4 GB, then you take a snapshot and then you deploy your updates and Apps. what is going to be the size of the snapshot ?

and if the VM machine crashes completely, the snapsot would be of any help. if the answers is YES means the snapshot has all files of the vm machine (vmdk).

OR
the other side I have n't understood could be.

VMDK is the initial file when the vm is created and the snapshot is the increment?

I understand you are not trying to get out of purchasing a backup solution, but you need to understand, that it is a dangerous practice to rely on Snapshots for Backup.

I have no idea, what size the snapshot is going to be when you deploy apps.

I tried to give you an example, when you download Security Updates, every month from Microsoft the snapshot size is approx 2GB. (now the updates you download from Microsoft every month are not 2GB), but the snapshot records ALL the block changes needed in the VMDK.

Correct, the Snapshot is the incremental.

Sometimes when machine crashes with snapshots, you cannot merge the snapshot file back into the vmdk, so ALL your changes are lost, back to the point when you created the first snapshot, resulting in a VMware machine that may not start due to disk corruption, or all the changes are lost forever.

Now it makes me think when you first create a VM machine, a VMDK file gets created, but when you add /increase/decrease things like CPU, RAM, disk. would the VMDK changes in size ?
when you install/unistall a new application  or patches would the VMDK file change in size?

Then comes a snapshot. when you take a snapshot. what does that mean ? are you duplicating the image of the VMDK?
 what 's in the snapshot?

Excellent explanation Guys