[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 373
  • Last Modified:

snap shot space

I have seen many storage devices require 25% or somekind of % space for snapshot.
i am wondering how it is possible when i create 10GB VD and he snapshot space only 2.5GB.
is not it suppose to be 1:1ratio?
0
pdsmicro
Asked:
pdsmicro
1 Solution
 
nobusCommented:
what exactly do you you mean with snapshot space??
can you explain what this is about??
0
 
Gerald ConnollyCommented:
A Clone would be 1:1 space but a Snapshot only holds the blocks changed, thats why they normally only take up a small proportion of the volume they are a snapshot of. An old rule of thumb is that 80% of writes goto 20% of the disk.

Snapshots can either be Copy-on-write  or Redirect-on-write, COW means the original data is stored in the snapshot, ROW means the new data is stored in the snapshot
0
 
Paul SolovyovskySenior IT AdvisorCommented:
It depends on the hardware/software. Are you talking about consumer or enterprise grade storage?  What exactly are you looking to accomplish and does it involve specific application or just file server data?
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
pdsmicroAuthor Commented:
This is an enterprise storage devices.
I read dell equalllogic tech notes and it says that we allocate 25% of volume space for snapshot.
NetApp says % for snapshoto.
Jetstore says 2:1 for snap shot.

When we create 1TB space for volume the we give 25GB for snapshot.
how that 1TB data is being converted to 250GB?
0
 
Gerald ConnollyCommented:
Its about layers of virtualisation. When you create a volume (say a E: drive) on a LUN of a RAIDset, you are creating a virtual disk whose virtual blocks are mapped onto the Physical Spindles used in the volume. These virtual blocks can be visualised as a set of pointers.

When you create a snapshot of a volume, aside from any preallocation of space all that is required is the space required for a copy of the pointers plus any header info required ie a tiny amount of space, probably MBytes worth of space depending on the size of the original volume. No data space needs to be allocated although most implementations will preallocate some space to speed up the process.

So now you have two sets of pointers the Original set (orgset) and the Snapshot set (snpset) both pointing at the original data.

Now when you now try and write to the original Volume it ultimately ends up as a write to a block (or blocks) and before the write happens, space is allocated in the snapshot (either by using some of the pre-allocated space or by grabbing some of the spare space on the RAIDsystem.

In a CoW implementation -   The blocks in question are then copied into the snapshot space and they pointer for the snpset is modified to point to this copied data, the write completes to the original volume, but the original pointer is not changed.

In a RoW implementation - The write completes to the snapshot space and orgset is modified to point to the new space, but the snpset is not changed.

If you only write to 25% of the disk the snapshot space will only be 25% of the size of the original volume, but if you write to 100% of the original volume then the snapshot will take up 100% of the space taken up by the original.
0
 
pdsmicroAuthor Commented:
thank you
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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