This is a theoretical understanding than a problem question. How is it possible that when I am doing full backups that the snapshots are so small?
For instance, my VMDK is about 40GB but the snapshot vmdk is only like 17MB?
-
- Enthusiast
- Posts: 26
- Liked: never
- Joined: Sep 04, 2010 11:06 pm
- Full Name: Richard Yamauchi
- Contact:
-
- VP, Product Management
- Posts: 6031
- Liked: 2856 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Question: What is this Snapshot Space Sorcery?
A "snapshot" in the VMware world is actually an incredibly simple concept. When you take a snapshot VMware stops writing changes to the original VMDK, and starts writing change blocks to the snapshot.vmdk. As you continue to make changes to the disks in the VM the snapshot.vmdk will grow to contain those changes. If you "delete" the snapshot, the changes a read from the snapshot VMDK and written to the "real" vmdk. If you revert a snapshot you basically just throw the snapshot.vmdk away.
There's plenty of information about VMware snapshots on the internet if you want to know more.
There's plenty of information about VMware snapshots on the internet if you want to know more.
-
- Enthusiast
- Posts: 26
- Liked: never
- Joined: Sep 04, 2010 11:06 pm
- Full Name: Richard Yamauchi
- Contact:
Re: Question: What is this Snapshot Space Sorcery?
Oh, that's right. I think I should have known that. This also explains why it often takes longer to "delete" the snapshot than to create one.
Then, this is not sorcery, it is enlightenment.
Then, this is not sorcery, it is enlightenment.
Who is online
Users browsing this forum: Google [Bot], Janne.Haatainen, sapsam, srlarsen and 135 guests