HP StorageWorks XP Remote Web Console Software - Manual (Page 20)

Creation of a LUSE volume
• Adding or changing the definition of the CLPR requires several hours or more.
• The mainframe volumes must be allocated to SLPR0. All operations of the mainframe volumes can
be performed by the storage administrators, not the storage partition administrators.
• The target ports must be allocated to the SLPRs other than SLPR0.
• We do not recommend that the following operations with CLPRs are performed.
Creation of a LUSE volume that extends over multiple CLPRs
Note: If this operation is forcibly performed, the volumes belonging to the CLPRs which LUSE is set
to cannot be used as the Continuous Access or the TrueCopy for Mainframe pair volume.
Business Copy Quick Restore operation that affects multiple CLPRs
Manual Migration of Auto LUN that affects multiple CLPRs
• If the operations of HP StorageWorks XP Continuous Access Asynchronous or TrueCopy
Asynchronous for Mainframe are performed, and the volumes which are extended over multiple
CLPRs are allocated to the same consistency group, a pair cannot be created.
• If the operations of Continuous Access Asynchronous or TrueCopy Asynchronous for Mainframe
are performed, only Continuous Access Asynchronous pairs or TrueCopy Asynchronous for
Mainframe pairs that belong to the same CLPR can be allocated to one consistency group. The
parity groups allocated to the CLPR that these Continuous Access Asynchronous pairs or TrueCopy
Asynchronous for Mainframe pairs belong to cannot migrate to another CLPR.
• The parity group that contains the LDEVs to which the Cache Residency cache extents is defined
cannot migrate to another CLPR.
• Continuous Access Journal data volumes and journal volumes do not need to belong to the
same CLPR.
• When the CU numbers are allocated to the SLPR:
Before a customized volume (CV) is created, the storage administrator must allocate the CU
numbers to the SLPR. These allocated CU numbers are necessary only for defining the CU
number that will be allocated to the LDEV when the storage partition administrator will create a
customized volume.
Figure 4 on page 21 shows an example of the Manual Migration of the volumes using the Auto
LUN function. This example indicates that the volume LDKC00:CU01:LDEV05 migrates from
SLPR1 to SLPR2, and the volume LDKC00:CU02:LDEV10 migrates from SLPR2 to SLPR1.
CU01 is allocated to SLPR1. The volume LDKC00:CU01:LDEV05 belonged to CU01 before
Manual Migration was performed. However, after Manual Migration is performed, the volume
LDKC00:CU02:LDEV10 will be allocated to CU01 in SLPR1. Therefore, the CU number will not
correspond with the volume number in SLPR1.
By the same token, the CU number will not correspond with the volume number in SLPR2 after
Manual Migration is performed. Even if the CU number does not correspond with the volume
number in the SLPR, an error does not occur. Since such a discrepancy, however, will make
the administration of subsystem difficult, the special attentions are required when a storage
administrator forcibly performs the Manual Migration function of Auto LUN between the different
SLPRs.
For further information on the customized volume, see the HP StorageWorks XP24000 Virtual
LVI/LUN (VLL) and Volume Shredder User’s Guide. For further information on Manual Migration
of Auto LUN, see the HP StorageWorks XP24000 Auto LUN Software User's Guide.
20 Preparing for Disk/Cache Partition Operations