HP 3PAR StoreServ 7200 2-node HP 3PAR CIM API Programming Reference (OS 3.1.2 - Page 133
TPD_RemoteReplicationGroup, TPD_RemoteGroupSynchronized
View all HP 3PAR StoreServ 7200 2-node manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 133 highlights
SyncedElement. Similar to remote StorageVolume, this ReplicationEntity cannot be retrieved via EnumerateInstances/EnumerateInstanceNames.GetInstance. ReplicationEntity cannot be discovered via EnumerateInstances, EnumerateInstanceNames nor GetInstance. It will appear as an instance as a result of an Associators request, and will have the following value: Table 111 Relevant Properties of TPD_ReplicationEntity Property InstanceID Type Persistent EntityID OtherTypeDescription Description HP_3PAR: StorageVolume (4) Always FALSE, which means that ReplicationEntity will disappear if link is back up and copy is successful. Remote volume name NULL Since there is no full-blown support for ReplicationEntity, in the replication service capabilities the SupportedFeatures property will still include "Requires full discovery of target ComputerSystem" which indicates that the service does not support undiscovered resources. TPD_RemoteReplicationGroup This corresponds to the remote replication group, sub-classed from CIM_ReplicationGroup. Table 112 Relevant Properties of TPD_RemoteReplicationGroup Property InstanceID ElementName Persistent DeleteOnEmptyElement DeleteOnUnassociated Description HP_3PAR: Name of the rcopy group Always TRUE. If true, group will be deleted when the last element is removed. This is always FALSE since an rcopy group can be empty. If true, group will be deleted when the group is no longer associated with another group. This is always FALSE. TPD_RemoteGroupSynchronized This is the synchronization association between the remote copy group pairs, sub-classed from CIM_GroupSynchronized. The RemoteReplicationGroup of the peer system cannot be retrieved via EnumerateInstances, EnumerateInstanceNames or GetInstance. The object path of the RemoteReplicationGroup of the peer system will not have a valid hostname, as neither the hostname nor IP address of the peer system is known to the local provider; instead, target name of the peer system will be used. Target name is an arbitrary name given to the peer system when a user creates a remote copy target. Consult Remote Copy User s Guide for details. Table 113 Relevant Properties of RemoteGroupSynchronized Property SystemElement SyncedElement Description Source RemoteReplicationGroup (rm_natural is TRUE); the „natural source group will remain as the SystemElement even after a fail over. Target RemoteReplicationGroup (rm_natural is FALSE); the „natural target group will remain as the SyncedElement even after a fail over. Replication Services Profile 133