HP P6000 Replication Solutions Manager User Guide (T3680-96089, October 2012)

Mirrorclone states
The following mirrorclone states are reported by the replication manager.
RemarksMirrorclone replication state
There is no replication activity between the mirrorclone virtual disk and its
source virtual disk. At the instant of the fracture, data on the mirrorclone is
identical to its source.
After a fracture, data on the two disks may no longer be identical due to
host I/O to the source or the mirrorclone.
fractured
In response to a replication command, data is being copied from the
mirrorclone virtual disk to its original source virtual disk. Data on the original
source is not yet identical to its mirrorclone.
restore in progress
The source virtual disk and its mirrorclone are synchronized. Data on the
mirrorclone is identical to its source. Any changes to data on the source
virtual disk are automatically copied to its mirrorclone.
synchronized or normalized
In response to a replication command, data is being copied from the source
virtual disk to its mirrorclone virtual disk. Data on the mirrorclone is not yet
identical to its source.
sync in progress
Normalization
Snapclone normalization (unsharing)
Snapclone normalization is a local replication background process in which a storage system
copies the data from the initial snapshot to an independent virtual disk. Snapclone normalization
is also called unsharing.
Some actions should not be performed during snapclone normalization. When creating jobs, use
wait commands to ensure that normalization is completed. See the
WaitStorageVolumeNormalization, WaitStorageVolumesNormalization, and
WaitVolumeGroupNormalization job commands. For more information on jobs, see the HP P6000
Replication Solutions Manager Job Command Reference.
Remote copy normalization
Remote copy normalization is a remote replication background process in which two storage
systems ensure that the data on the source and destination virtual disks in a DR group are identical.
Some actions should not be performed during remote copy normalization. When creating jobs,
use wait commands to ensure that normalization is completed. See the WaitDrGroupNormalization
job command.
Preferred controller
Preferred controller specifies which controller manages and presents the virtual disk. The primary
purpose is for load balancing. Although set by a storage administrator, the controller software can
override the setting when required. Values are:
• No preference. Presentation of the virtual disk is completely controlled by the controller software.
• Path A - Failover only. Controller A presents the virtual disk to hosts when both controllers are
simultaneously started.
• Path A - Failover/failback. Controller A presents the virtual disk to hosts, but if controller A
fails, control of the virtual disk is transferred to controller B, then transferred back to controller
A when it is available again.
Virtual disk concepts 267