Specifications for auto lun – HP XP7 Storage User Manual

Page 170

Advertising
background image

Specifications for Auto LUN

RAID Manager must be mapped to the port for pooling of RAID in order to control the volume of
the external connection. Therefore, the external volume needs to be mapped previously to the RAID
port without connecting to the host. Following is an execution example of the volume migration
executed for LDEV#18.

Figure 57 Auto LUN configurations

(1) Command specification

RAID Manager operates the volume migration by specifying to the horcm*.conf as same BC and
Cnt Ac-S, because the volume migration using RAID Manager is necessary to be defined the
mapping for the target volume.

MU# (of SMPL as BC) that is not used because BC is used for Auto LUN operation.

An original volume for the migration is defined as PVOL. A target volume for the migration is
defined as SVOL. In other words, an original volume is migrated from PVOL to SVOL, and the
mapping between LDEV and VDEV is swapped after copied.

(2) Mapping specification

The mapping between LUN and LDEV is maintained for the replying of SCSI-Inquiry in order to
make recognize as identical LUN through the host after mapping changes.

The way to know whether the mapping is changed or not is possible to use "-fe" option of
pairdisplay

and/or raidscan command that shows the connection for the external volumes.

Also LU of the external connection and LU of RAID Group intermingle on the port for pooling, but
can confirm this with the above option of the raidscan command.

(3) Group operation

It is possible to execute the Auto LUN as a group by describing it to the horcm*.conf, however
LU(LDEV), which was mapped to SVOL after command execution, does not maintain the consistency
of the group. In other words, you must consider the volume mapped to the SVOL after execution
as the discarded volume.

When HORCM demon is KILLed or the host has crash during group operation, the group aborting
the execution of the command has LUN mixed with the external connection and RAID Group as
the group. In this case, RAID Manager skips the executed LU and issues the CC (Auto LUN) command
to the un-executed LU, and an identical command is executed once again.

(4) Using MU#

RAID Manager manages the status of Cnt Ac-S/BC using MU#, so RAID Manager uses the empty
MU# that is managed for BC. Therefore, execute the command of the volume migration in the
environment for BC having HORCC_MRCF environment variable. An example is shown below.

170

Data replication operations with RAID Manager

Advertising
This manual is related to the following products: