Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1965

June 24th, 2013 06:00

RLP in VNX?

Hi All,

I used snapview snapshots in emc clariion with Reserved Lun Pools. I want to know does EMC VNX series using reserved lun

pools when taking snapview snapshot? what happen if RLP's space got saturated, whether snapview session continue or not? kindly suggest me on this.

1K Posts

July 1st, 2013 07:00

Main difference:

  • Snapview Snapshot - COFW (copy on first write). Performance concern since the block that is being changed needs to be copied to the RLP first, pointer has to be updated and only then is the new write committed
  • VNX Snapshots - ROW (redirect on write). No performance concern since the new write will be written to a new block (no copy process)

Min/max values are different. Certain restrictions also apply (pool LUNs, traditional LUNs, etc.). Take a look at the white paper Rainer posted.

1K Posts

June 24th, 2013 06:00

Yes, VNX still uses the RLP for Snapview Snapshots. VNX Snapshots don't use the RLP but Snapview Snapshots do.

Snapview Sessions will not continue is the RLP space runs out.

June 24th, 2013 08:00

Ernes Taljic,

can you elaborate difference between snapview snapshot vs snapshot?

8.6K Posts

June 24th, 2013 09:00

See the white paper

http://www.emc.com/collateral/software/white-papers/h10858-vnx-snapshots-wp.pdf

2 Intern

 • 

1.4K Posts

July 10th, 2013 18:00

Hi Dhakshinamoorthy.B


For your questions:

(1) Yes, VNX snapview snapshot still use reserved lun pools when you start a snapshot session on a source lun.

(2) The snapshot session which causes saturation on the reserved lun pool will be stopped. Other sessions will still run until they are also going to be out of reserved lun space.

hope that's helpful!

4.5K Posts

July 17th, 2013 12:00

Extra point about the Reserve LUNs Pool - with raid group LUNs, best practice is to create a raid group(s) that is only for RLP LUNs - no user LUNs. Then you add these LUNs to the Reserve LUN Pool. When you use these RLP LUNs, the RLP LUN will get trespassed to the same SP as the source LUN. With raid group LUNs, there is no issue with trespassing the LUN to a different SP.

With Pools, if you use a Pool for the RLP LUNs, just as with raid group LUNs, you should use a separate Pool for RLP LUNs with no user LUNs in the Pool. As with raid group RLP LUN, when a snap session needs an RLP, the LUN will trespass to the SP that owns the source LUN.  In Pools, it is not good practice to trespass LUNs.

I would recommend that for RLP LUNs, you continue to use the Best Practice for RLP - separate raid groups, no user LUNs, if more than two raid groups, put the LUNs into each Raid Group in alternating number sequence - that way, each new RLP that is assigned is taken from the different raid group (not completely, but mostly).

glen

251 Posts

July 17th, 2013 12:00

And another note try to make sure the RLP luns are all of the same size

Gearoid

4.5K Posts

July 30th, 2013 14:00

Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.

glen

No Events found!

Top