beautypg.com

Displaying clpr information, Migrating parity groups in a clpr, Displaying parity group information – HP XP7 Storage User Manual

Page 136: Moving parity groups, Checking result of clpr transfer, Performance control operations

background image

Displaying CLPR information

The raidcom get clpr command lists and displays the status of the CLPRs in the storage system. If
no CLPRs have been created, CLPR0 is displayed as entire cache. Display example:

# raidcom get clpr
CLPR CLPR_NAME TC_CAP(MB) TU_CAP(MB) WP_CAP(MB) SF_CAP(MB) U(%) W(%)S(%)
000 Oracle_DB 40000 20000 4000 0 50 30 0
001 Oracle_DB_PROD 20000 10000 2000 0 50 10 0
003 Oracle_DB_BACK 10000 5000 500 0 50 5 0

Migrating parity groups in a CLPR

This section explains operations from checking the parity group information to moving the parity
group.

Displaying parity group information

The raidcom check the status, display the information about the parity group. The following shows
the display example of parity groups.

# raidcom get parity_grp
T GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPE
R 32-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 32-17 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 33-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 33-17 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC

Moving parity groups

If you change the allocation of parity groups, parity groups are moved from another CLPR. In this
case, plural parity groups which configure the distributed parity group have to be allocated the
same CLPR. Parity groups including LDEVs where cache area of Cache Residency is defined cannot
be moved to another CLPR. For the restrictions on the CLPR's transfer, see HP XP7 Cache Partition
User Guide
. The following shows examples of parity groups transfer in CLPR.

Move the parity group 32-17 to the CLPR number 1.

# raidcom modify clpr –clpr 1 –parity_grp_id 32-17

Checking result of CLPR transfer

By displaying the information about parity groups, check the result of CLPR transfer. The following
shows an example of parity group list.

# raidcom get parity_grp
T GROUP Num_LDEV U(%) AV_CAP(GB) R_LVL R_TYPE SL CL DRIVE_TYPE
R 32-16 4 45 140000 RAID1 2D+2D 0 0 DKS2C-K072FC
R 32-17 4 45 140000 RAID1 2D+2D 0 1 DKS2C-K072FC
R 33-16 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC
R 33-17 4 45 140000 RAID1 2D+2D 0 3 DKS2C-K072FC

Performance Control operations

Performance Control enables you to prioritize host I/O operations to provide high-speed processing
for specified hosts. The host is identified by WWN of host bus adapter. Performance Control has
two settings: prioritized and non-prioritized. Set the prioritized option for hosts that require
high-speed processing, and the non-prioritized option for the other hosts.

The upper limit of the non-prioritized WWN is set to each port to which the non-prioritized WWN
belongs and is applied only to the port. If the threshold is set to the port to which the prioritized
WWN belongs, the threshold overwrites the thresholds of all the ports in the storage system to
which the prioritized WWN belongs as well. For more details about the upper limit and the
threshold, see

“Setting the priority on host bus adapter” (page 139)

.

136

Provisioning operations with RAID Manager

This manual is related to the following products: