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

2. SupportedAsynchronousActions[] - Enumeration indicating what operations are
executed as asynchronous jobs, supported values are:
a. Local Replica Attachment – physical copy creation is asynchronous (Attachment
means attaching a replica to an existing volume).
b. Local Replica Modification – resync physical copy is also asynchronous.
3. SupportedSynchronousActions[] - Enumeration indicating what operations are executed
the without creation of a job, supported values are:
• Local Replica Creation – virtual copy creation is synchronous.
4. SupportedSpecializedElements[] - Enumeration indicating which specialized storage
element types are supported by this instance of StorageReplicationCapabilities. Example
values are “Delta Pool”, “Delta Snapshot”, “Full Snapshots”. This affects the value of
IntendedUsage property of StorageSetting, e.g., if “Delta Snapshot” is defined
here, then this indicates to a CIM client that a StorageSetting can be created with
IntendedUsage set to “Delta Snapshot”, which limits the StorageSetting to only
delta snapshot creation. However, for the Inform OS, StorageSetting cannot be specified
for the replica volume during a physical or virtual copy creation, which means only a value
of “Not Specialized” (0) is supported for StorageSetting. IntendedUsage. In other
words, we cannot specialize a StorageSetting to only be used as a goal for creating
replica volumes since that is not supported (StorageSetting can only be used as a goal
in a base volume creation). Thus, we cannot specify “Full Snapshot” nor “Delta
Snapshot” here. Value can only contain the following:
• Delta Pool – StoragePool corresponding to the SA/SD spaces of a volume, valid
only for virtual copy. This indicates to the CIM client that a specialized pool exists from
which to allocate a delta snapshot replica. Since our provider does not support StoragePool
creation, a client cannot set StorageSetting.IntendedUsage to “Delta Pool”
either.
5. InitialReplicationState – initial state of the replica after it is first created, supported
values are:
a. Initialized – Resynchronization or copy task is queued but the copy engine has not
started. This is the initial state for a physical copy.
b. Idle - an UnSyncAssoc replica is ready to be managed. This is the initial state for a
virtual copy.
6. SupportedModifyOperations[] - Enumeration indicating which
TPD_StorageConfigurationService.ModifySynchronization() Operation are
supported by this instance of StorageReplicationCapabilities. Valid values are
outlined in section, ModifySynchronization().
7. ReplicaHostAccessibility - Indicates host access restrictions for replicas with these
capabilities. Valid values are:
a. Not accessible – this applies to physical copy volumes, which cannot be exported.
If a physical copy is promoted to a base volume, then this restriction is lifted.
b. No restrictions – any host may access; this applies to virtual copy volumes.
8. HostAccessibleState[] - lists the replica synchronization states in which the provider
allows host access to replicas. For physical copy, this is an empty array, as hosts are never
allowed to access it. For virtual copy volumes, there are no restrictions whatsoever, so this
array contains all the valid states that a virtual copy can have:
a. Restore In Progress – a virtual copy promotion is ongoing.
b. Idle – normal state.
9. PersistentReplicasSupported - True indicates replicas can persist during power off
or system reset.
Copy Services Subprofile 53