330
Chapter 4 Performing CCI Operations
(1) Command specification
CCI operates the volume migration by specifying to the horcm*.conf as same SI and TC,
because the volume migration using CCI is necessary to be defined the mapping for the
target volume.
MU# (of SMPL as SI) which is not used as SI is used for the operation for CC.
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 will be 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 group by describing to the horcm*.conf,
however LU(LDEV) which was mapped to SVOL after command execution does not
maintain the consistency as the group. In other words, the user must consider the
volume mapped to SVOL after execution as the discarded volume.
When HORCM demon is KILLed or the host has crash during group operation, the group
aborted 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 CC command
to the un-executed LU, by the user issues an identical command 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, the user need to execute the command of the volume migration in the
environment for SI having HORCC_MRCF environment variable. An example is shown
below.
PVOL
S/P
VOL
SVOL
oradb
oradb1
1
2
0
0
1
2
It is possible to specify
MU#1 or MU#2 for CC.
It is possible to specify
MU#2 for CC.
0
(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.
Содержание TAGMASTORE MK-90RD011-25
Страница 2: ......
Страница 8: ...viii Preface ...
Страница 18: ...xviii Contents ...
Страница 180: ...162 Chapter 3 Preparing for CCI Operations ...
Страница 250: ...232 Chapter 4 Performing CCI Operations Vol Type logical unit LU type e g OPEN V OPEN 9 ...
Страница 370: ...352 Chapter 5 Troubleshooting ...
Страница 388: ...370 Acronyms and Abbreviations ...