VMware 4817V62 Administration Guide - Page 202

Relationship Between Snapshots, Snapshots and Other Activity in the Virtual Machine

Page 202 highlights

vSphere Basic System Administration Because you cannot revert to a snapshot with dynamic disks, quiesced snapshots are not used when backing up dynamic disks. Backup solutions, like VMware Data Recovery, use the snapshot mechanism to freeze the state of a virtual machine. However, the Data Recovery backup method has additional capabilities that mitigate the limitations of snapshots. Multiple snapshots refers to the ability to create more than one snapshot of the same virtual machine. Multiple snapshots are not simply a way of saving your virtual machines. With multiple snapshots, you can save many positions to accommodate many kinds of work processes. When taking a snapshot, the state of the virtual disk at the time the snapshot is taken will be preserved. When this occurs, the guest cannot write to the vmdk file. The delta disk is an additional vmdk file to which the guest is allowed to write. The delta disk represents the difference between the current state of the virtual disk and the state that existed at the time the previous snapshot was taken. If more than one snapshot exists, delta disks can represent the difference (or delta) between each snapshot. For example, a snapshot can be taken, and then the guest could write to every single block of the virtual disk, causing the delta disk to grow as large as the entire virtual disk. When a snapshot is deleted, the changes between snapshots and previous disk states are merged, and all the data from the delta disk that contains the information about the deleted snapshot is written to the parent disk and merges with the base disk only when you choose to do so. This can involve a large amount of disk input and output. This may reduce the virtual machine performance until consolidation is complete. The amount of time it takes to commit or delete snapshots depends on how much data the guest operating system has written to the virtual disks since the last snapshot was taken. The required time is directly proportional to the amount of data (committed or deleted) and the amount of RAM allocated to the virtual machine. For additional information about snapshot behavior, see the Knowledge Base article at http://kb.vmware.com/kb/1015180. Relationship Between Snapshots The relationship between snapshots is like that of a parent to a child. In the linear process, each snapshot has one parent and one child, except for the last snapshot, which has no children. The snapshots taken form a tree. Each time you revert and take another, a branch (child) is formed. In the process tree, each snapshot has one parent, but one snapshot may have more than one child. Many snapshots have no children. You can revert to a parent or a child. Snapshots and Other Activity in the Virtual Machine When you take a snapshot, be aware of other activity going on in the virtual machine and the likely effect of reverting to that snapshot. In general, it is best to take a snapshot when no applications in the virtual machine are communicating with other computers. The potential for problems is greatest if the virtual machine is communicating with another computer, especially in a production environment. For example, if you take a snapshot while the virtual machine is downloading a file from a server on the network, the virtual machine continues downloading the file, communicating its progress to the server. If you revert to the snapshot, communications between the virtual machine and the server are confused and the file transfer fails. 202 VMware, Inc.

  • 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

Because you cannot revert to a snapshot with dynamic disks, quiesced snapshots are not used when backing
up dynamic disks.
Backup solutions, like VMware Data Recovery, use the snapshot mechanism to freeze the state of a virtual
machine. However, the Data Recovery backup method has additional capabilities that mitigate the limitations
of snapshots.
Multiple snapshots refers to the ability to create more than one snapshot of the same virtual machine.
Multiple snapshots are not simply a way of saving your virtual machines. With multiple snapshots, you can
save many positions to accommodate many kinds of work processes.
When taking a snapshot, the state of the virtual disk at the time the snapshot is taken will be preserved. When
this occurs, the guest cannot write to the
vmdk
file. The delta disk is an additional
vmdk
file to which the guest
is allowed to write. The delta disk represents the difference between the current state of the virtual disk and
the state that existed at the time the previous snapshot was taken. If more than one snapshot exists, delta disks
can represent the difference (or delta) between each snapshot. For example, a snapshot can be taken, and then
the guest could write to every single block of the virtual disk, causing the delta disk to grow as large as the
entire virtual disk.
When a snapshot is deleted, the changes between snapshots and previous disk states are merged, and all the
data from the delta disk that contains the information about the deleted snapshot is written to the parent disk
and merges with the base disk only when you choose to do so. This can involve a large amount of disk input
and output. This may reduce the virtual machine performance until consolidation is complete.
The amount of time it takes to commit or delete snapshots depends on how much data the guest operating
system has written to the virtual disks since the last snapshot was taken. The required time is directly
proportional to the amount of data (committed or deleted) and the amount of RAM allocated to the virtual
machine.
For additional information about snapshot behavior, see the Knowledge Base article at
.
Relationship Between Snapshots
The relationship between snapshots is like that of a parent to a child. In the linear process, each snapshot has
one parent and one child, except for the last snapshot, which has no children.
The snapshots taken form a tree. Each time you revert and take another, a branch (child) is formed.
In the process tree, each snapshot has one parent, but one snapshot may have more than one child. Many
snapshots have no children.
You can revert to a parent or a child.
Snapshots and Other Activity in the Virtual Machine
When you take a snapshot, be aware of other activity going on in the virtual machine and the likely effect of
reverting to that snapshot.
In general, it is best to take a snapshot when no applications in the virtual machine are communicating with
other computers. The potential for problems is greatest if the virtual machine is communicating with another
computer, especially in a production environment.
For example, if you take a snapshot while the virtual machine is downloading a file from a server on the
network, the virtual machine continues downloading the file, communicating its progress to the server. If you
revert to the snapshot, communications between the virtual machine and the server are confused and the file
transfer fails.
vSphere Basic System Administration
202
VMware, Inc.