About configuration for EMC_CLARiiON_SnapView_Snapshot
You must configure a reserved LUN pool for each storage processor that owns a source LUN for which you want to create a SnapView snapshot. (Starting at FLARE version x.24, one combined reserved LUN pool exists for both storage processors.) The reserved LUN pool stores the portions of the client's data that incoming write requests change while the snapshot is active.
Note the following before you configure a reserved LUN pool.
The reserved LUN pool must contain at least one LUN for each source LUN that is the subject of (participates in) the snapshot. Any available LUN can be added to the reserved LUN pool if the LUN is owned by the storage processor that owns the source LUN.
LUNs in the reserved LUN pool are private LUNs, which cannot belong to a storage group. The storage processor manages its reserved LUN pool and automatically assigns one or more private LUNs to a source LUN. This assignment is based on how much snapshot activity takes place in the source LUN. This activity can result from one busy snapshot or multiple snapshots.
While the snapshot is active, client write activity on the source consumes more space in the reserved LUN pool. Adding more LUNs to the reserved LUN pool increases the size of the reserved LUN pool. The storage processor automatically uses a LUN if one is needed.
All snapshots share the reserved LUN pool. If two snapshots are active on two different source LUNs, the reserved LUN pool must contain at least two private LUNs. If both snapshots are of the same source LUN, the snapshots share the same private LUN (or LUNs) in the reserved LUN pool.
More Information