HP 3PAR StoreServ 7450 4-node HP 3PAR CIM API Programming Reference (OS 3.1.2 - Page 110

Consistency, Sequential Consistency. For us this can only be Sequential Consistency.

Page 110 highlights

• Consistency: This parameter overrides the default group consistency. For example, "No Consistency", "Sequential Consistency". For us this can only be "Sequential Consistency". • ReplicationSettingData: NULL • Job: For physical copy of vv sets, InFormOS actually spawns one task for each of the vv pair in the set and not one task for the whole set. However, this job parameter can only contain reference to one job, so as a compromise, only the job of the first vv pair copy will be returned. • Synchronization: Refers to the created association between the source element (or source replication group) and the target replication group. InFormOS does not have the capability to keep track of which vv set is synchronized with which other vv set; only individual sync-ed vv pair is known. Therefore, as a compromise, only the StorageSynchronized association of the first vv pair in the vv set will be returned. • TargetSettingGoal: NULL • TargetPool: NULL • WaitForCopyState Table 94 Parameter Matrix for CreateGroupReplica What to Create: Physical copy Sync Type: Mode: Clone Clone Synchronous (default) Asynchronous) Virtual copy (snapshot Synchronous volume) snapshots of remote copy volumes, on both primary and secondary arrays Snapshot Snapshot Optional (can only be Synchronous) Optional (can only be Synchronous) RelationshipName: SourceGroup: NULL NULL Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory TPD_ReplicationGroup TPD_ReplicationGroup TPD_ReplicationGroup TPD_RemoteReplicationGroup TargetGroup: Output Job? WaitForCopyState: Mandatory Mandatory NULL NULL Y Y N N Optional (only valid option is Synchronized) - independent clones will be created that detach automatically Optional (only valid option is Inactive) - the clones will retain association with the parent If non-NULL, then only If non-NULL, then only 'Synchronized' is 'Synchronized' is supported supported TPD_CreateGroupReplica Due to the inadequacies of the SMI-S defined CreateGroupReplica in supporting vv set replication and consistent volume list replication, a couple of proprietary methods are defined. uint32 ReplicationService.TPD_CreateGroupReplica( [IN] string RelationshipName, [IN, Required] uint16 SyncType, [IN] uint16 Mode, [IN] SNIA_ReplicationGroup REF SourceGroup, [IN] SNIA_ReplicationGroup REF TargetGroup, [OUT] TargetElements [OUT] CIM_ConcreteJob REF Jobs[], [OUT] CIM_Synchronized REF Synchronizations[]); 110 CIM API SMI-S Support

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309

Consistency: This parameter overrides the default group consistency. For example, "No
Consistency", "Sequential Consistency". For us this can only be "Sequential Consistency".
ReplicationSettingData
: NULL
Job
: For physical copy of vv sets, InFormOS actually spawns one task for each of the vv pair
in the set and not one task for the whole set. However, this job parameter can only contain
reference to one job, so as a compromise, only the job of the first vv pair copy will be returned.
Synchronization
: Refers to the created association between the source element (or source
replication group) and the target replication group. InFormOS does not have the capability
to keep track of which vv set is synchronized with which other vv set; only individual sync-ed
vv pair is known. Therefore, as a compromise, only the StorageSynchronized association of
the first vv pair in the vv set will be returned.
TargetSettingGoal
: NULL
TargetPool
: NULL
WaitForCopyState
Table 94 Parameter Matrix for CreateGroupReplica
Synchronous
snapshots of remote
Virtual copy (snapshot
volume)
Physical copy
What to Create:
copy volumes, on both
primary and
secondary arrays
Snapshot
Snapshot
Clone
Clone
Sync Type:
Optional
Optional
Asynchronous)
Synchronous (default)
Mode:
(can only be
Synchronous)
(can only be
Synchronous)
Mandatory
Mandatory
NULL
NULL
RelationshipName:
Mandatory
Mandatory
Mandatory
Mandatory
SourceGroup:
TPD_RemoteReplicationGroup
TPD_ReplicationGroup
TPD_ReplicationGroup
TPD_ReplicationGroup
NULL
NULL
Mandatory
Mandatory
TargetGroup:
N
N
Y
Y
Output Job?
If non-NULL, then only
'Synchronized' is
supported
If non-NULL, then only
'Synchronized' is
supported
Optional (only valid
option is Inactive) –
the clones will retain
Optional (only valid
option is
Synchronized) –
WaitForCopyState:
association with the
parent
independent clones
will be created that
detach automatically
TPD_CreateGroupReplica
Due to the inadequacies of the SMI-S defined CreateGroupReplica in supporting vv set replication
and consistent volume list replication, a couple of proprietary methods are defined.
uint32 ReplicationService.TPD_CreateGroupReplica(
[IN]
string RelationshipName,
[IN, Required]
uint16 SyncType,
[IN]
uint16 Mode,
[IN]
SNIA_ReplicationGroup REF SourceGroup,
[IN]
SNIA_ReplicationGroup REF TargetGroup,
[OUT]
TargetElements
[OUT]
CIM_ConcreteJob REF Jobs[],
[OUT]
CIM_Synchronized REF Synchronizations[]);
110
CIM API SMI-S Support