Dell EqualLogic PS6210XS EqualLogic Group Manager Administrator s Guide PS Ser - Page 34

Volume Attributes, Callout, Description, NOTE: The system permanently deletes volumes after 7 days

Page 34 highlights

Callout 7 8 9 10 Description Space received from PS Series arrays to allocate data as needed through various structures (volumes, snapshots, thin provisioning, replicas, containers, SMB/NFS, quotas, and local users and groups). Volumes Storage allocated by a PS Series group as addressable iSCSI targets. Collection A set of volumes. Snapshots A point-in-time copy of data on a volume. Snapshots can be taken on a single volume or on a collection. Thin-provisioned volume With thin provisioning, a minimal amount of space (10 percent by default) is reserved on a volume and then allocated when the space is needed. For each volume, the group generates an iSCSI target name, which you cannot modify. An iSCSI target name includes a prefix, a string, and the volume name. Initiators use the target name to connect to a volume. For example: iqn.2001-05.com.equallogic:7-8b0900-6d0000000-001ebbc5d80sf0k0-db3 In this example: prefix is string is volume name is iqn.2001-05.com.equallogic 7-8b0900-6d0000000-001ebbc5d80sf0k0 db3 Each volume appears on the network as an iSCSI target. Hosts with iSCSI initiators use the volume's target name to connect to the volume. Each iSCSI volume supports a set of features and capabilities: • Snapshots - To protect volume data from mistakes, viruses, or database corruption, you can use snapshots. • Replication - To protect against disasters, you can replicate volume data from one group to another. • Thin Provisioning - To manage storage capacity utilization on demand, you can use thin provisioning. • Clones - To create a master or boot image, full system backup, or transfer a system to another person, you can use cloning. • Volume Unmap (block reclaim) - To recover space previously allocated to volumes, you can unmap them. • Volume Undelete - To restore mistakenly deleted volumes, you might be able to use volume undelete. NOTE: The system permanently deletes volumes after 7 days, and sometimes sooner if the space is needed. • Volume Folders - To organize volumes into folders for quick visual reference, you can use volume folders. Using folders has no effect on the contents of the volumes. • Control Access to iSCSI Initiators - To protect your volumes from unauthorized and uncoordinated access by iSCSI initiators, you can use access control policies. • Control Access to Hosts (servers) - To prevent inadvertent corruption of the volume caused by multiple hosts writing to it in an uncoordinated manner, enable multihost access to a volume. Volume Attributes You set some attributes when you create a volume; other attributes use default values. In most cases, you can modify all the volume attributes. Template volumes and thin clones have some restrictions. 34 Architecture Fundamentals

  • 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
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355

Callout
Description
Space received from PS Series arrays to allocate data as needed through various structures (volumes,
snapshots, thin provisioning, replicas, containers, SMB/NFS, quotas, and local users and groups).
7
Volumes
Storage allocated by a PS Series group as addressable iSCSI targets.
8
Collection
A set of volumes.
9
Snapshots
A point-in-time copy of data on a volume. Snapshots can be taken on a single volume or on a collection.
10
Thin-provisioned volume
With thin provisioning, a minimal amount of space (10 percent by default) is reserved on a volume and then
allocated when the space is needed.
For each volume, the group generates an iSCSI target name, which you cannot modify. An iSCSI target name includes a
prefix,
a
string, and the volume name. Initiators use the target name to connect to a volume. For example:
iqn.2001-05.com.equallogic:7-8b0900-6d0000000-001ebbc5d80sf0k0-db3
In this example:
prefix
is
iqn.2001-05.com.equallogic
string is
7-8b0900-6d0000000-001ebbc5d80sf0k0
volume name is
db3
Each volume appears on the network as an iSCSI target. Hosts with iSCSI initiators use the volume's target name to connect to the
volume.
Each iSCSI volume supports a set of features and capabilities:
Snapshots – To protect volume data from mistakes, viruses, or database corruption, you can use snapshots.
Replication – To protect against disasters, you can replicate volume data from one group to another.
Thin Provisioning – To manage storage capacity utilization on demand, you can use thin provisioning.
Clones – To create a master or boot image, full system backup, or transfer a system to another person, you can use cloning.
Volume Unmap (block reclaim) – To recover space previously allocated to volumes, you can unmap them.
Volume Undelete – To restore mistakenly deleted volumes, you might be able to use volume undelete.
NOTE: The system permanently deletes volumes after 7 days, and sometimes sooner if the space is needed.
Volume Folders – To organize volumes into folders for quick visual reference, you can use volume folders. Using folders has no
effect
on the contents of the volumes.
Control Access to iSCSI Initiators – To protect your volumes from unauthorized and uncoordinated access by iSCSI initiators, you
can use access control policies.
Control Access to Hosts (servers) – To prevent inadvertent corruption of the volume caused by multiple hosts writing to it in an
uncoordinated manner, enable multihost access to a volume.
Volume Attributes
You set some attributes when you create a volume; other attributes use default values. In most cases, you can modify all the volume
attributes. Template volumes and thin clones have some restrictions.
34
Architecture Fundamentals