From Navisphere Manager help guide:  "SnapView, incremental SAN Copy, and MirrorView/Asynchronous share the LUN  resources of the reserved LUN pool. For example, if you are running an  incremental SAN Copy session on one LUN and a SnapView session on another LUN,  the reserved LUN pool must contain at least two LUNs - one for each source  LUN. If both sessions are running on the same source LUN, the  sessions will share a reserved LUN."  For your 1st question, if the sessions are running on same source LUN, snapview will share the same RLP as that of the MV/A.  I am not sure about your 2nd question. In simple terms terms - when data is written on the source LUN, the original data on the source is moved to the RLP and the pointers are updated - COFW (copy on first write procedure). Any subsequent changes to those blocks have no affect.  Regards,
Hi guys, I have a question regarding the Reserved LUN Pool when using snapview and mirrorview/A. I have 8 luns being replicated using mirrorview/A. At present i have 8 private LUNS in the RLP. If i start using snapview will the same 8 luns, would i have to double the amount to accomodate 8 when using snapview? I dont think i have to, but just want to double check.The second question i have is regards to the writable space when using a snap. Is the data that is written when you are working from a snap help in the RLP? Any help would be appreciated Thanks Douglas
RLP with Mirrorview/A & Snapview