Storage management logical partitions (s, Storage management logical partitions (slprs), Table 2 – HP 200 Storage Virtualization System User Manual

Page 13

Advertising
background image

Table 2 Capacity for data in a hard disk drive associated with a CLPR and standard

cache capacity

Capacity for data in

CLPR

to 0.7TB to 2.6TB to 8.5TB to 14.4TB to 20.3TB 20.3TB or

more

Standard cache

capacity

4GB

8GB

12GB

16GB

20GB

24GB

NOTE:

To calculate the capacity for data in a hard disk drive associated with a CLPR, add the following

formulas:
Number of parity groups: capacity of one disk x 3 x (3D+1P)
Number of parity groups: capacity of one disk x 6 x (6D+2P)
Number of parity groups: capacity of one disk x 7 x (7D+1P)
Number of parity groups: capacity of one disk x 2 x (2D+2D)

NOTE:

To add cache memories to the local array, install them with Standard Cache Access Model or High

Performance Cache Access Model mode. If the local array has additional printed circuit boards

(PCBs), you must use the High Performance Cache Access Model mode. For more information about

additional cache memories, contact your HP account support representative.

Restriction on CLPR and CU group
You cannot allocate parity groups belonging to different CU groups to a CLPR other than CLPR0.

For more information about CU groups, see the HP StorageWorks XP Remote Web Console user

guide for XP12000/XP10000/SVS200.

Storage management logical partitions (SLPRs)

An array can be shared with multiple organizations, for example, enterprises and departments within

an enterprise. Therefore, multiple administrators who belong to different organizations might manage

one array. This creates the potential for an administrator who belongs in one organization to destroy

other organizations' volumes. Furthermore, it can complicate and increase the difficulty of managing the

array because of an incorrect operation by an administrator and its influence on other organizations.

The storage management logical partition function in XP Disk/Cache Partition allocates all of an array's

resources (that is, ports and CLPRs) to multiple virtual arrays. Each virtual array can be accessed by only

its administrator. Therefore, this prevents the risk that an administrator will destroy another organization's

volumes or leak another organization's data.
In a non-partitioned environment, a full array is considered one single partition SLPR0. After the array is

partitioned, SLPR0 becomes the unpartitioned portion of the array. Similarly, CLPR0 contains all parity

groups (PGs) and cache in the non-partitioned environment. After the array is partitioned, CLPR0 contains

the remaining PGs and cache that are not allocated to other CLPRs.

Figure 2

shows an example of when one array is partitioned into two virtual arrays. Each virtual array is

allocated to two enterprises respectively. In this case, enterprise A's array administrator can manage

enterprise A's virtual array, but cannot manage one of enterprise B's arrays. Similarly, enterprise B's array

administrator can manage enterprise B's virtual array, but cannot manage one of enterprise A's arrays.

IMPORTANT:

Disk/cache partitioning for the SVS200 is limited to one SLPR and four CLPRs.

HP StorageWorks

13

Advertising