3.1

VMware, Inc. 119
Chapter 6 View Composer
Storageovercommitlevelscanbevariedbetweendifferenttypesofdatatstoresinorder
toaddressthedifferentlevelsofthroughputoneachdatastore(forexample,NAS
versusSAN).Wherethroughputisrelativelyslow,theovercommitlevelcanbesettoa
lowerleveltoensurethatasmallernumberofclones
arecreatedonthedatastore.
Conversely,ahigherlevelofovercommitcouldbeappliedtodatastoresthatexhibita
greaterrateofdatatransfer.
Storageovercommitonlyappliestodeltadisks.Itdoesnotapplytouserdisksor
standard(non‐linked)clones.
Desktop Recomposition
InFigure 6‐2adesktopcloneislinkedtoreplica1,whichitselfisacopyofParent VM 1.
Arecompositionactionisinitiatedwhentheadministratorselectsadifferentsnapshot
inthesameParentVMordifferentParentVM(asinthisexample).Ineithercaseanew
replicaisprovisioned.
Figure 6-2. Desktop Recomposition
Replica2isanexactcopyofParentVM2.Whentherecompositionactioniscomplete
thedesktopwillbeanchoredtoreplica2andtheoperatingsystemdatamodified
accordingly.Theoperatingsystemdataofarecomposeddesktopisreducedinsizeafter
recomposition,howevertheuserdatais
unaffectedbythisevent.
base image + snapshot
bloated
OS data disk
refreshed
OS data disk
user data disk
user data disk
replica 2—
new base image
after recomposition
replica 1
parent VM 1
base image + snapshot
parent VM 2
recompose