HP 3PAR CIM API Programming Reference (OS 3.1.2 MU2) (QL226-97015, June 2013)

[In, REQ] CIM_ManagedElement ref SourceElement,
[In, REQ] CIM_ManagedElement ref TargetElement,
[In, REQ,
Values {"Async", "Sync", "UnSyncAssoc", "UnSyncUnAssoc"},
ValueMap {"2", "3", "4", "5"}]
Uint16 CopyType);
Table 46 Return values for AttachOrModifyReplica()/AttachReplica()
Explanation/NotesValuesValueMap
Success0
For example: the source volume does
not have snapspace, target volume is
incompatible.
Failed4
For example: the wrong CopyType is
specified.
Invalid Parameter5
Target volume is already a physical
copy of another volume.
In Use6
Method parameters checked – job
started
0x1000
The method execution, if successful, always returns 0x1000, which means that job has started. A
client can either monitor Job.OperationalStatus for job completion or wait for the arrival of
modification of OperationalStatus for a ConcreteJob to indicate ‘Complete’ and ‘OK’ or
‘Complete’ and ‘Error’.
If the operation is of CopyType UnSyncAssoc, a resync snapshot of the physical copy is created.
This snapshot has the same characteristics as a regular snapshot.
STATE TRANSITIONS
Table 47 (page 63) shows the values for SyncState and WhenSynced during various stages of
physical copy creation. Internal vvol_t volume state flags (v_overall_state) are mapped to each
SyncState.
Table 47 State Transitions for Physical Copy Creation
WhenSyncedSyncStateOperation
NULLInitialized (2)Copy task queued but copy engine
not yet started
NULLResyncInProgress (5)Copy in progress
Initial copy in progress
Time of when copy is completedFrozen (14)Copy complete
All blocks copied from source to an
UnSyncAssoc replica and the copy
engine is stopped
NULLBroken (12)Copy Failed
The relationship is non-functional due
to errors in the source or the target
RESYNCHRONIZATION
CLI EQUIVALENCE
createvvcopy –r <destvol>
Copy Services Subprofile 63