Hitachi VSP F1500 User And Reference Manual page 262

migrated from P-VOL to S-VOL, 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 Volume Migration as a group by describing it to
the horcm*.conf, however LU(LDEV), which was mapped to S-VOL after
command execution, does not maintain the consistency of the group. In other
words, you must consider the volume mapped to the S-VOL 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, CCI skips the
executed LU and issues the CC (Volume Migration) command to the un-
executed LU, and an identical command is executed once again.
(4) Using MU#
CCI manages the status of TC/SI using MU#, so CCI uses the empty MU#
that is managed for SI. Therefore, execute the command of the volume
migration in the environment for SI having HORCC_MRCF environment
variable. An example is shown below.
(5) HORCM instance
It is possible to describe the original and target volume for the volume
migration to MU# as another group in horcm*.conf for HORCM instance of SI
and /or TC. Also, it is possible to define the original and target volume for the
volume migration in the horcm*.conf as HORCM instance independent from
SI/TC.
6-38
Data replication operations with CCI
Command Control Interface User and Reference Guide