Controlling auto lun, Specifications for auto lun – HP XP P9500 Storage User Manual

Page 142

Advertising
background image

NOTE:

Pairsplit (“simplex -S”) of a Snapshot volume is returned without verification of the state transition
that waits until SMPL state. In a SMPL state, note that the volume that was an S-VOL becomes
R/W disabled and data is discarded.

In the “PSUE” state, Snapshot does not manage differential data between the primary volume
and secondary volume.

Controlling Auto LUN

Auto LUN, including external volumes, must be controlled using CLI in a Data Lifecycle Management
(DLCM) solution. It is possible to support volume migration (Auto LUN function) and the external
connection by operating the current Business Copy and VDEV mapping of the external connection.

Also, it is important to consider the support of Auto LUN on the compatibility based on the current
CLI interface, because RAID Manager is supporting Business Copy and the external connection.
For this purpose, RAID Manager makes the CLI interface that works by minimum compatible of the
application by specifying the COPY mode for Auto LUN to the CLI of RAID Manager.

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 59 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 P-VOL. A target volume for the migration is
defined as S-VOL. In other words, an original volume is 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.

142

Data replication operations with RAID Manager

Advertising
This manual is related to the following products: