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

StorageReplicationCapabilities, CREATION, CLI EQUIVALENCE, SMI-S METHOD, SourceElement, TargetElement

Page 62 highlights

StorageReplicationCapabilities The ability to create a physical copy is described by the following instance of TPD_StorageReplicationCapabilities (see Section (page 52)): • UnSyncUnAssoc - describes the capability of our provider to create an independent clone of a volume CREATION CLI EQUIVALENCE createvvcopy -p createvvcopy -p -s SMI-S METHOD A physical copy can be created by a CIM client using the TPD_StorageConfigurationService.AttachOrModifyReplica() method. uint32 AttachOrModifyReplica( [Out] CIM_ConcreteJob ref Job, [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, [In, EmbeddedInstance ( "CIM_SettingData" )] String Goal, [In] CIM_NetworkPipe ref ReplicationPipe); • Job: A Job is created as a side-effect of the execution of the method, and a reference to that Job is returned through this parameter. • SourceElement: Reference to the base StorageVolume to copy from. • TargetElement: Reference to the base StorageVolume to copy to. • CopyType: Can only be "UnsyncAssoc" (4) or "UnsyncUnAssoc" (5) • UnsyncAssoc: Creates an unsynchronized physical copy that is associated to the source StorageVolume. This creates a snapshot volume as a side-effect. This is equivalent to the CLI command "createvvcopy -p -s ". • UnsyncUnAssoc: Creates an unsynchronized physical copy of the source StorageVolume and does not maintain the source association after completing the copy operation. This is equivalent to the CLI command "createvvcopy -p ", i.e., without the -s option. • Goal: The StorageSetting properties to be created or modified for the target StorageVolume. We does not support changing the volume characteristics during createvvcopy, so this can only be NULL. A Non-NULL value is ignored. • ReplicationPipe: The NetworkPipe element that scopes the remote mirror pair. This is only for remote copy, which is not supported in Phase I, so this can only be NULL. SMI-S also specifies that providers have to accept the AttachReplica() method, which is defined in an earlier version of the copy services subprofile, for backward compatibility. AttachReplica is similar to AttachOrModifyReplica with the omission of the Goal and ReplicationPipe parameters. uint32 AttachReplica( [Out] CIM_ConcreteJob ref Job, 62 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

StorageReplicationCapabilities
The ability to create a physical copy is described by the following instance of
TPD_StorageReplicationCapabilities
(see
Section (page 52)
):
UnSyncUnAssoc - describes the capability of our provider to create an independent clone of
a volume
CREATION
CLI EQUIVALENCE
createvvcopy
p <parvol> <destvol>
createvvcopy
p <parvol> -s <destvol>
SMI-S METHOD
A physical copy can be created by a CIM client using the
TPD_StorageConfigurationService.AttachOrModifyReplica() method.
uint32 AttachOrModifyReplica(
[Out] CIM_ConcreteJob ref Job,
[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,
[In, EmbeddedInstance ( "CIM_SettingData" )]
String Goal,
[In] CIM_NetworkPipe ref ReplicationPipe);
Job
: A Job is created as a side-effect of the execution of the method, and a reference to that
Job is returned through this parameter.
SourceElement
: Reference to the base
StorageVolume
to copy from.
TargetElement
: Reference to the base
StorageVolume
to copy to.
CopyType
: Can only be “
UnsyncAssoc
(4)
or “
UnsyncUnAssoc
(5)
UnsyncAssoc
: Creates an unsynchronized physical copy that is associated to the source
StorageVolume
. This creates a snapshot volume as a side-effect. This is equivalent to the
CLI command “
createvvcopy
p <parvol> -s <destvol>
”.
UnsyncUnAssoc
: Creates an unsynchronized physical copy of the source
StorageVolume
and does not maintain the source association after completing the copy operation. This is
equivalent to the CLI command “
createvvcopy
p <parvol> <destvol>
”, i.e., without
the
s
option.
Goal
: The
StorageSetting
properties to be created or modified for the target
StorageVolume
. We does not support changing the volume characteristics during
createvvcopy
, so this can only be NULL. A Non-NULL value is ignored.
ReplicationPipe
: The
NetworkPipe
element that scopes the remote mirror pair. This is only
for remote copy, which is not supported in Phase I, so this can only be NULL.
SMI-S also specifies that providers have to accept the
AttachReplica()
method, which is
defined in an earlier version of the copy services subprofile, for backward compatibility.
AttachReplica
is similar to
AttachOrModifyReplica
with the omission of the
Goal
and
ReplicationPipe
parameters.
uint32 AttachReplica(
[Out] CIM_ConcreteJob ref Job,
62
CIM API SMI-S Support