Dell PowerVault MD3200 Owner's Manual - Page 137

About the Simple Path, Preparing Host Servers to Create the Snapshot Using the Simple Path

Page 137 highlights

About the Simple Path Using the simple path, you can specify: • Snapshot Virtual Disk Name-A user-specified name that helps you associate the snapshot virtual disk to its corresponding snapshot repository virtual disk and source virtual disk. • Snapshot Repository Virtual Disk Name-A user-specified name that helps you associate the snapshot repository virtual disk to its corresponding snapshot virtual disk and source virtual disk. • Snapshot Repository Virtual Disk Capacity-The snapshot repository virtual disk capacity is expressed as a percentage of the source virtual disk capacity. The maximum percentage allowed is 120 percent. Using the simple path, the following defaults are used for the other parameters of a snapshot virtual disk: • Capacity Allocation-The snapshot repository virtual disk is created using free capacity on the same disk group where the source virtual disk resides. • Host-to-Virtual Disk Mapping-The default setting is Map now. • Percent Full-When the snapshot repository virtual disk reaches the specified repository full percentage level, the event is logged in the Major Event Log (MEL). The default snapshot repository full percentage level is 50 percent of the source virtual disk. • Snapshot Repository Virtual Disk Full Conditions-When the snapshot repository virtual disk becomes full, you are given a choice of failing write activity to the source virtual disk or failing the snapshot virtual disk. Preparing Host Servers to Create the Snapshot Using the Simple Path NOTE: Before using the Snapshot Virtual Disks Premium Feature in a Microsoft® Windows® clustered configuration, you must first map the snapshot virtual disk to the cluster node that owns the source virtual disk. This ensures that the cluster nodes correctly recognize the snapshot virtual disk. NOTE: Mapping the snapshot virtual disk to the node that does not own the source virtual disk before the Snapshot enabling process is completed can result in the operating system mis-identifying the snapshot virtual disk. This, in turn, can result in data loss on the source virtual disk or an inaccessible snapshot. Configuration: Premium Feature-Snapshot Virtual Disks 137

  • 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

Configuration: Premium Feature—Snapshot Virtual Disks
137
About the Simple Path
Using the simple path, you can specify:
Snapshot Virtual Disk Name—A user-specified name that helps you
associate the snapshot virtual disk to its corresponding snapshot repository
virtual disk and source virtual disk.
Snapshot Repository Virtual Disk Name—A user-specified name that
helps you associate the snapshot repository virtual disk to its corresponding
snapshot virtual disk and source virtual disk.
Snapshot Repository Virtual Disk Capacity—The snapshot repository
virtual disk capacity is expressed as a percentage of the source virtual disk
capacity. The maximum percentage allowed is 120 percent.
Using the simple path, the following defaults are used for the other
parameters of a snapshot virtual disk:
Capacity Allocation—The snapshot repository virtual disk is created using
free capacity on the same disk group where the source virtual disk resides.
Host-to-Virtual Disk Mapping—The default setting is
Map now
.
Percent Full—When the snapshot repository virtual disk reaches the
specified repository full percentage level, the event is logged in the Major
Event Log (MEL). The default snapshot repository full percentage level is
50 percent of the source virtual disk.
Snapshot Repository Virtual Disk Full Conditions—When the snapshot
repository virtual disk becomes full, you are given a choice of failing write
activity to the source virtual disk or failing the snapshot virtual disk.
Preparing Host Servers to Create the Snapshot Using the Simple Path
NOTE:
Before using the Snapshot Virtual Disks Premium Feature in a Microsoft®
Windows® clustered configuration, you must first map the snapshot virtual disk to
the cluster node that owns the source virtual disk. This ensures that the cluster
nodes correctly recognize the snapshot virtual disk.
NOTE:
Mapping the snapshot virtual disk to the node that does not own the source
virtual disk before the Snapshot enabling process is completed can result in the
operating system mis-identifying the snapshot virtual disk. This, in turn, can result in
data loss on the source virtual disk or an inaccessible snapshot.