Dell PowerVault MD3260i CLI Guide - Page 48

Creating The Initial Snapshot Virtual Disk, See step 1 through step 4 in the preceding

Page 48 highlights

NOTE: Verify that the virtual disk has a status of Optimal or Disabled by clicking the Summary tab and then clicking the Disk Groups & Virtual Disks link. 4. Follow any additional instructions for your operating system. Failure to follow these additional instructions can create unusable snapshot virtual disks. NOTE: If your operating system requires additional instructions, you can find those instructions in your operating system documentation. If you want to use a snapshot regularly, such as for backups, use the Disable Snapshot and Re-create Snapshot options to reuse the snapshot. Disabling and re-creating snapshots preserves the existing virtual disk-to-host mappings to the snapshot virtual disk. After your server has been prepared, see Creating The Initial Snapshot Virtual Disk. Creating The Initial Snapshot Virtual Disk After first preparing the host server(s) as specified in the preceding procedure, use the following examples to make a virtual disk snapshot. The following syntax is the general form of the command to create a snapshot virtual disk: create snapshotVirtualDisk sourceVirtualDisk= "sourceVirtualDiskName" [repositoryRAIDLevel=(0 | 1 | 5) (repositoryPhysicalDisks= (enclosureID0,slotID0 ... enclosureIDn,slotIDn) userLabel="snapshotVirtualDiskName" warningThresholdPercent=percentValue repositoryPercentOfSource=percentValue repositoryUserLabel="repositoryName" repositoryFullPolicy=(failSourceWrites | failSnapShot)] [enclosureLossProtect=(TRUE | FALSE)]enableSchedule=(TRUE | FALSE) | schedule= (immediate | snapshotSchedule)] NOTE: Use one or all of the optional parameters as needed to help define your configuration. You do not, however, need to use any optional parameters. See step 1 through step 4 in the preceding section, Preparing Host Servers To Create An Initial Snapshot Virtual Disk. The following example shows a command in which users assign the physical disks: client>smcli 123.45.67.89 -c "create snapshotVirtualDisk sourceVirtualDisk= \"Mars_Spirit_4\" repositoryRAIDLevel=5 repositoryPhysicalDisks=(1,1 1,2 1,3 1,4 1,5);" The command in this example creates a new snapshot of the source virtual disk Mars_Spirit_4. The snapshot repository virtual disk consists of five physical disks that form a new disk group. The new disk group has a RAID level of 5. This command also takes a snapshot of the source virtual disk, starting the copy-on-write operation. See step 1 through step 4 in the preceding section, Preparing Host Servers To Create An Initial Snapshot Virtual Disk. The following example is the script file version of the command: create snapshotVirtualDisk sourceVirtualDisk= "Mars_Spirit_4" repositoryRAIDLevel=5 repositoryPhysicalDisks=(1,1 1,2 1,3 1,4 1,5); A minimal version of this command might look like the following example: client>smcli 123.45.67.89 -c "create snapshotVirtualDisk sourceVirtualDisk= \"Mars_Spirit_4\";" 48

  • 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

NOTE:
Verify that the virtual disk has a status of Optimal or Disabled by clicking the Summary tab and then
clicking the Disk Groups & Virtual Disks link.
4.
Follow any additional instructions for your operating system. Failure to follow these additional instructions can
create unusable snapshot virtual disks.
NOTE:
If your operating system requires additional instructions, you can find those instructions in your
operating system documentation.
If you want to use a snapshot regularly, such as for backups, use the Disable Snapshot and Re-create Snapshot options
to reuse the snapshot. Disabling and re-creating snapshots preserves the existing virtual disk-to-host mappings to the
snapshot virtual disk.
After your server has been prepared, see Creating The Initial Snapshot Virtual Disk.
Creating The Initial Snapshot Virtual Disk
After first preparing the host server(s) as specified in the preceding procedure, use the following examples to make a
virtual disk snapshot.
The following syntax is the general form of the command to create a snapshot virtual disk:
create snapshotVirtualDisk sourceVirtualDisk=
"
sourceVirtualDiskName
" [repositoryRAIDLevel=(0 |
1 | 5) (repositoryPhysicalDisks=
(
enclosureID0,slotID0 ... enclosureIDn,slotIDn
)
userLabel="
snapshotVirtualDiskName
"
warningThresholdPercent=
percentValue
repositoryPercentOfSource=
percentValue
repositoryUserLabel="
repositoryName
"
repositoryFullPolicy=(failSourceWrites |
failSnapShot)] [enclosureLossProtect=(TRUE |
FALSE)]enableSchedule=(TRUE | FALSE) | schedule=
(immediate | snapshotSchedule)]
NOTE:
Use one or all of the optional parameters as needed to help define your configuration. You do not, however,
need to use any optional parameters.
See step 1 through step 4 in the preceding section, Preparing Host Servers To Create An Initial Snapshot Virtual Disk.
The following example shows a command in which users assign the physical disks:
client>smcli 123.45.67.89 -c "create
snapshotVirtualDisk sourceVirtualDisk=
\"Mars_Spirit_4\" repositoryRAIDLevel=5
repositoryPhysicalDisks=(1,1 1,2 1,3 1,4 1,5);"
The command in this example creates a new snapshot of the source virtual disk
Mars_Spirit_4
. The snapshot repository
virtual disk consists of five physical disks that form a new disk group. The new disk group has a RAID level of 5. This
command also takes a snapshot of the source virtual disk, starting the copy-on-write operation.
See step 1 through step 4 in the preceding section, Preparing Host Servers To Create An Initial Snapshot Virtual Disk.
The following example is the script file version of the command:
create snapshotVirtualDisk sourceVirtualDisk=
"Mars_Spirit_4" repositoryRAIDLevel=5
repositoryPhysicalDisks=(1,1 1,2 1,3 1,4 1,5);
A minimal version of this command might look like the following example:
client>smcli 123.45.67.89 -c "create
snapshotVirtualDisk sourceVirtualDisk=
\"Mars_Spirit_4\";"
48