Table of Contents
Advertisement
Controlling Volume Migration
Volume Migration, including external volumes, must be controlled using CLI in
a Data Lifecycle Management (DLCM) solution. It is possible to support
volume migration (Volume Migration function) and the external connection by
operating the current ShadowImage and VDEV mapping of the external
connection.
Also, it is important to consider the support of Volume Migration on the
compatibility based on the current CLI interface, because CCI is supporting
ShadowImage and the external connection. For this purpose, CCI makes the
CLI interface that works by minimum compatible of the application by
specifying the COPY mode for Volume Migration to the CLI of CCI.
Specifications for Volume Migration
CCI 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.
(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) that is not used because SI is used for Volume Migration
operation.
An original volume for the migration is defined as P-VOL. A target volume for
the migration is defined as S-VOL. In other words, an original volume is
Figure 6-14 Volume Migration configurations
Data replication operations with CCI
Command Control Interface User and Reference Guide
6-37
- Quick Links:
- Overview
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
