It is also worth noting the different ways the RLP is used by SnapView Snapshots and MV/Async.
Snapshots perform copy on first write to the RLP as writes are made on the source lun. If writes are received by the snapshot, it writes to the RLP whatever was written on the source lun blocks as well as whatever that host has written to the snapshot (physically requiring twice the space of that write).
MV/A incremental requires RLP luns on both the primary and secondary arrays. On the primary array, it assigns a RLP lun to each mirror relationship. It contains bitmaps to track changes required during the next synchronization. It will also hold data when new writes are coming in during a sync - on the secondary array, the RLP lun stores the data present on the secondary lun before the sync in order to maintain a ¿gold copy¿ (to go back to if the session fails midway through).
I hope that helps to clarify what RRR already answered.
brendm
2 Intern
•
313 Posts
298
0
Posted April 27th, 2009 11:00
Snapshots perform copy on first write to the RLP as writes are made on the source lun. If writes are received by the snapshot, it writes to the RLP whatever was written on the source lun blocks as well as whatever that host has written to the snapshot (physically requiring twice the space of that write).
MV/A incremental requires RLP luns on both the primary and secondary arrays. On the primary array, it assigns a RLP lun to each mirror relationship. It contains bitmaps to track changes required during the next synchronization. It will also hold data when new writes are coming in during a sync - on the secondary array, the RLP lun stores the data present on the secondary lun before the sync in order to maintain a ¿gold copy¿ (to go back to if the session fails midway through).
I hope that helps to clarify what RRR already answered.