Dell PowerVault MD3200 CLI Guide - Page 84

recopy virtualDiskCopy, You are planning to use the data on the target virtual disk to copy back

Page 84 highlights

• Before the virtual disk copy begins • While the virtual disk copy has a status of In Progress • After the virtual disk copy has completed re-creating a virtual disk copy using the recopy virtualDiskCopy command When you create a virtual disk copy pair and after the original virtual disk copy has completed, the target virtual disk is automatically defined as readonly to the hosts. The read-only status of the target virtual disk ensures that the copied data on the target virtual disk is not corrupted by additional writes to the target virtual disk after the virtual disk copy is created. Maintain the read-only status when the following conditions apply: • You are using the target virtual disk for backup purposes • You are copying data from one disk group to a larger disk group for greater accessibility • You are planning to use the data on the target virtual disk to copy back to the source virtual disk in case of a disabled or failed snapshot virtual disk At other times you might want to write additional data to the target virtual disk. You can use the set virtualDiskCopy command to reset the read/write permission for the target virtual disk. NOTE: If you enabled host writes to the target virtual disk, read and write requests are rejected while the virtual disk copy has a status of In Progress, Pending, or Failed. The following syntax is the general form of the command: set virtualDiskCopy target [targetName] [source [sourceName]] copyPriority=(highest | high | medium | low | lowest) targetReadOnlyEnabled=(TRUE | FALSE) NOTE: Use one or both of the parameters as needed to help define your configuration. It is not necessary to use either parameter. The following example shows how to change parameters using the set virtualDiskCopy command: client>smcli 123.45.67.89 -c "set virtualDiskcopy target [\"Obi_1\"] copyPriority=highest targetreadonlyenabled=false;" 84 Using the Virtual Disk Copy Feature

  • 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

84
Using the Virtual Disk Copy Feature
Before the virtual disk copy begins
While the virtual disk copy has a status of In Progress
After the virtual disk copy has completed re-creating a virtual disk copy
using the
recopy virtualDiskCopy
command
When you create a virtual disk copy pair and after the original virtual disk
copy has completed, the target virtual disk is automatically defined as read-
only to the hosts. The read-only status of the target virtual disk ensures that
the copied data on the target virtual disk is not corrupted by additional writes
to the target virtual disk after the virtual disk copy is created. Maintain the
read-only status when the following conditions apply:
You are using the target virtual disk for backup purposes
You are copying data from one disk group to a larger disk group for greater
accessibility
You are planning to use the data on the target virtual disk to copy back to
the source virtual disk in case of a disabled or failed snapshot virtual disk
At other times you might want to write additional data to the target virtual
disk. You can use the
set virtualDiskCopy
command to reset the read/write
permission for the target virtual disk.
NOTE:
If you enabled host writes to the target virtual disk, read and write requests are
rejected while the virtual disk copy has a status of In Progress, Pending, or Failed.
The following syntax is the general form of the command:
set virtualDiskCopy target [
targetName
] [source
[
sourceName
]] copyPriority=(highest | high |
medium | low | lowest) targetReadOnlyEnabled=(TRUE
| FALSE)
NOTE:
Use one or both of the parameters as needed to help define your
configuration. It is not necessary to use either parameter.
The following example shows how to change parameters using the
set
virtualDiskCopy
command:
client>smcli 123.45.67.89 -c "set virtualDiskcopy
target [\"Obi_1\"] copyPriority=highest
targetreadonlyenabled=false;"