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

About Improving Pool Space Utilization (Template Volumes and Thin Clones)

Page 151 highlights

The Pool Space table values change, based on the new volume setting. If the volume change exceeds pool capacity, the free space field displays a negative value. 6. Click OK. About Improving Pool Space Utilization (Template Volumes and Thin Clones) Some computing environments use multiple volumes that contain a large amount of common data. For example, some environments clone a standard volume and create multiple "boot volumes" that administrators use to boot different client computers. Most of the data is common to all the volumes; only a small portion of volume space contains unique data. Because each boot volume consumes pool space for the common data, the group is storing multiple copies of the same data, which is not an efficient utilization of space. To use pool space more efficiently, instead of cloning standard volumes, you can create one volume and populate it with the common data. After you convert the volume to a template volume, you can create multiple thin clone volumes and then write to each thin clone to make it unique. For example, you can add data such as a page file to a thin clone. Because a thin clone shares the common data in the template volume, each thin clone only consumes the space needed to store the differences (or deltas) between the thin clone and the template volume. Initially, a template volume and thin clone are identical in reported size and content. Because the group allocates space to the new thin clone in the same way it allocates space to a new standard, thin-provisioned volume, only the minimum volume reserve is consumed from free pool space. When initiators write data to a thin clone, space is consumed from free volume reserve. As needed, the group allocates additional volume reserve to the thin clone, up to the maximum in-use space setting for the thin clone. You can also modify the thin clone and change the data that the thin clone shares with the template volume. However, the data in the template volume is always preserved because a template volume is read-only. Group Manager tracks the amount of data that is shared between each thin clone and template volume. With a few exceptions, all normal volume operations apply to template volumes and thin clones. Keep in mind: • Thin clones are considered attached to the template volume and cannot exist without the template volume, similar to how snapshots depend on the base volume. • The group always maintains and shows the dependency of a thin clone on a template volume. You can use the GUI to display all volumes in alphabetical order or display thin clones under the template volume on which they depend. • When you replicate a template volume and its attached thin clones, the primary and secondary groups maintain the dependency. For example, you must replicate a template volume before replicating any of its thin clones. On the secondary group, you can display thin clone replica sets under the template replica set on which they depend. • The group maintains and shows the dependency of a thin clone on a template volume (or a thin clone replica set on a template replica set), even if a volume (or replica set) changes state, as occurs during failover and failback operations. For example, if you promote a thin clone replica set to a recovery thin clone, you can still see the dependency of the recovery thin clone on the template replica set. • You cannot delete a template volume, a template replica set, or a recovery template if a thin clone, thin clone replica set, or recovery thin clone depends on it. • You cannot disable replication on a template volume until you disable replication on all its thin clones. Space Considerations for Template Volumes and Thin Clones When you convert a standard volume to a template volume: • Thin provisioning is enabled on the volume, the volume is set offline, and the volume permission is set to read-only. NOTE: If you are using the Group Manager CLI, you must perform these tasks manually before you can convert to a template volume. About Volumes 151

  • 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

The Pool Space table values change, based on the new volume setting. If the volume change exceeds pool capacity, the free
space
field
displays a negative value.
6.
Click
OK
.
About Improving Pool Space Utilization (Template Volumes and Thin
Clones)
Some computing environments use multiple volumes that contain a large amount of common data. For example, some environments
clone a standard volume and create multiple “boot volumes” that administrators use to boot
different
client computers. Most of the
data is common to all the volumes; only a small portion of volume space contains unique data. Because each boot volume consumes
pool space for the common data, the group is storing multiple copies of the same data, which is not an
efficient
utilization of space.
To use pool space more
efficiently,
instead of cloning standard volumes, you can create one volume and populate it with the common
data. After you convert the volume to a template volume, you can create multiple thin clone volumes and then write to each thin
clone to make it unique. For example, you can add data such as a page
file
to a thin clone.
Because a thin clone shares the common data in the template volume, each thin clone only consumes the space needed to store the
differences
(or deltas) between the thin clone and the template volume.
Initially, a template volume and thin clone are identical in reported size and content. Because the group allocates space to the new
thin clone in the same way it allocates space to a new standard, thin-provisioned volume, only the minimum volume reserve is
consumed from free pool space.
When initiators write data to a thin clone, space is consumed from free volume reserve. As needed, the group allocates additional
volume reserve to the thin clone, up to the maximum in-use space setting for the thin clone.
You can also modify the thin clone and change the data that the thin clone shares with the template volume. However, the data in
the template volume is always preserved because a template volume is read-only. Group Manager tracks the amount of data that is
shared between each thin clone and template volume.
With a few exceptions, all normal volume operations apply to template volumes and thin clones.
Keep in mind:
Thin clones are considered attached to the template volume and cannot exist without the template volume, similar to how
snapshots depend on the base volume.
The group always maintains and shows the dependency of a thin clone on a template volume. You can use the GUI to display all
volumes in alphabetical order or display thin clones under the template volume on which they depend.
When you replicate a template volume and its attached thin clones, the primary and secondary groups maintain the dependency.
For example, you must replicate a template volume before replicating any of its thin clones. On the secondary group, you can
display thin clone replica sets under the template replica set on which they depend.
The group maintains and shows the dependency of a thin clone on a template volume (or a thin clone replica set on a template
replica set), even if a volume (or replica set) changes state, as occurs during failover and failback operations. For example, if you
promote a thin clone replica set to a recovery thin clone, you can still see the dependency of the recovery thin clone on the
template replica set.
You cannot delete a template volume, a template replica set, or a recovery template if a thin clone, thin clone replica set, or
recovery thin clone depends on it.
You cannot disable replication on a template volume until you disable replication on all its thin clones.
Space Considerations for Template Volumes and Thin Clones
When you convert a standard volume to a template volume:
Thin provisioning is enabled on the volume, the volume is set
offline,
and the volume permission is set to read-only.
NOTE: If you are using the Group Manager CLI, you must perform these tasks manually before you can convert to a
template volume.
About Volumes
151