HP XP7 Storage - Manual (Page 169)

Table 38 Snapshot Pairing Status (continued)
Secondary Primary Pairing Status P-VOL
Status
R/W enabled R/W enabled The differences of the updated data of the primary and
secondary volume are controlled with copying on write. PSUS
(PFUS)
R/W disable R/W enabled
2
"PSUS" status owing to an internal failure. The differences of
the updated data for the Snapshot volume are not controlled. PSUE
(Error)
Notes:
1. V-VOL unmapped to the SVOL of a Snapshot will reply to a SCSI Inquiry, but Reading and/or Writing is not allowed.
2. Reading and writing are enabled, as long as no failure occurs in the primary volume.
Pair status relationship to Snapshot commands
Table 39 (page 169) applies to a Snapshot context. It explains 1) what a pair status may be prior
to any RAID Manager command execution, 2) what the result would be after giving a RAID Manager
command, and 3) what the pair status may be if the RAID Manager command is Accepted.
Table 39 Pair status relationship to Snapshot commands
Snapshot Command -
pairresync pairsplit paircreate
Resync -S option -C option -E option -split No -split Pair Status
Rejected Acceptable Rejected Rejected Rejected Accepted 2 SMPL 1
Acceptable Accepted 1 Accepted* Rejected Rejected Acceptable COPY 2
RCPY
Acceptable Accepted 1 Accepted* Rejected Accepted*4 Acceptable PAIR 3
Accepted*2 Accepted 1 Accepted* Rejected Acceptable Rejected PSUS
(PFUS) 4
Accepted*2 Accepted 1 Rejected Rejected Rejected Rejected PSUE 5
*A command is accepted and issued. Whether this command is executed or not depends on the microcode version of the RAID
storage system.
NOTE:
•
pairsplit -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 SVOL 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.
Controlling Auto LUN 169