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

Space Considerations for Template Volumes and Thin Clones

Page 161 highlights

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. • Volume reserve decreases to the amount of in-use space (or the minimum volume reserve, whichever is greater), and free volume reserve becomes unreserved space. • Snapshot reserve is adjusted, based on the new volume reserve. If necessary to preserve existing snapshots, the snapshot reserve percentage is increased. When you create a thin clone volume, it has the same reported size and contents as the template volume. If you mount the thin clone, you can see the data that the thin clone shares with the template volume. The group allocates only the minimum volume reserve when you first create a thin clone. The group allocates additional space if you specify snapshot reserve for the thin clone. As with a standard, thin-provisioned volume, as you write to a thin clone, the group allocates more space and increases the volume reserve as needed. In the Volume Status window for a thin clone volume, the Volume Space table shows the space utilization for the thin clone, including the in-use space, which is the portion of volume reserve that is storing data unique to the thin clone. When you first create a thin clone, it has zero in-use space. Also in the Volume Status window for a thin clone volume, the Shared Space table (appears only for thin clones) shows the amount of space that is shared with the template volume and the unshared (in-use) space. As you write to the thin clone, unshared (in-use) space increases. In some cases, when you write to a thin clone, shared space can decrease (for example, if you are overwriting shared data). Free space in the Shared Space table shows the amount of unwritten thin clone space (that is, the reported volume size minus the combined shared space and unshared space). This space represents the amount of data you can write to the thin clone before you need to increase its size. This value is the same as the value for "unreserved" space in the Volume Space table in the Volume Status window for the template volume. About Volumes 161

  • 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
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498
  • 499
  • 500
  • 501
  • 502
  • 503
  • 504
  • 505
  • 506
  • 507
  • 508
  • 509
  • 510
  • 511
  • 512
  • 513
  • 514
  • 515
  • 516
  • 517
  • 518
  • 519
  • 520
  • 521
  • 522
  • 523
  • 524
  • 525
  • 526
  • 527
  • 528
  • 529
  • 530
  • 531
  • 532
  • 533
  • 534
  • 535
  • 536
  • 537
  • 538
  • 539
  • 540
  • 541
  • 542
  • 543
  • 544
  • 545
  • 546
  • 547
  • 548
  • 549
  • 550
  • 551
  • 552
  • 553
  • 554
  • 555
  • 556
  • 557
  • 558
  • 559
  • 560
  • 561
  • 562
  • 563
  • 564
  • 565
  • 566
  • 567
  • 568
  • 569
  • 570
  • 571
  • 572
  • 573
  • 574
  • 575
  • 576
  • 577
  • 578
  • 579
  • 580
  • 581
  • 582
  • 583

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.
Volume reserve decreases to the amount of in-use space (or the minimum volume reserve, whichever is greater), and free
volume reserve becomes unreserved space.
Snapshot reserve is adjusted, based on the new volume reserve. If necessary to preserve existing snapshots, the snapshot
reserve percentage is increased.
When you create a thin clone volume, it has the same reported size and contents as the template volume. If you mount the thin
clone, you can see the data that the thin clone shares with the template volume.
The group allocates only the minimum volume reserve when you
first
create a thin clone. The group allocates additional space if you
specify snapshot reserve for the thin clone. As with a standard, thin-provisioned volume, as you write to a thin clone, the group
allocates more space and increases the volume reserve as needed.
In the Volume Status window for a thin clone volume, the Volume Space table shows the space utilization for the thin clone,
including the in-use space, which is the portion of volume reserve that is storing data unique to the thin clone. When you
first
create
a thin clone, it has zero in-use space.
Also in the Volume Status window for a thin clone volume, the Shared Space table (appears only for thin clones) shows the amount
of space that is shared with the template volume and the unshared (in-use) space. As you write to the thin clone, unshared (in-use)
space increases. In some cases, when you write to a thin clone, shared space can decrease (for example, if you are overwriting
shared data).
Free space in the Shared Space table shows the amount of unwritten thin clone space (that is, the reported volume size minus the
combined shared space and unshared space). This space represents the amount of data you can write to the thin clone before you
need to increase its size. This value is the same as the value for “unreserved” space in the Volume Space table in the Volume Status
window for the template volume.
About Volumes
161