Subscribe

When thin provisioning can apply to snapmirror destination

Thin provisioning feature is one of good solutions from NetApp. This Feature can save alot for companies who match to use it.

I hope this feature can use for snapmirror destination also, so we are not only save on primary storage but we can save on backup storage (dest. snapmirror) also.

Is it possible to make this happen?

Re: When thin provisioning can apply to snapmirror destination

Not sure what you are asking.

We have an active site were the space guaranty is set to volume on each Flexvol. At the standby site (and snapmirror target) we have this set to NONE. When you look at the aggregate in the standby site the aggregate is only 13% used. However if all the services were moved from the live site to standby, things could be a little ‘tight’.

Hope this helps

Re: When thin provisioning can apply to snapmirror destination

Up until recently (DOT 7.3) snapmirror destinations had their guarantee set to none, thereby making them thin provisioned. If you want to take space savings @ both primary and secondary to a new level using deduplication, make sure you follow the volume size constraints of the smaller of the 2 systems ( ex. if replicating from a FAS3040 to a 2050, don't let your volumes get above 1TB on the 3040 or your mirrors will fail ).