linked clones

Contributor(s): Julia Anderson

A linked clone is a copy of a virtual machine (VM) that shares virtual disks with its parent VM. The term is most often associated with VMware.

In a virtual desktop infrastructure (VDI), a linked clone contains all the files available on a parent VM at the time of a snapshot. Although the linked clone must always have access to the parent VM or it will shut down, changes to the parent VM's virtual disks do not affect the linked clone -- or vice versa. Instead, to preserve disk capacity, changes are stored in a delta disk on a per-VM basis.

If an administrator wants to update a parent's VM and have those changes reflected on the children, the administrators needs to perform a recompose. Desktop recomposition simultaneously updates all the linked clone desktops anchored to a parent virtual machine so the linked clones point to the right base disk. The net effect is all the changes accrued in the delta disk are lost, and users get a brand new virtual desktop. To do this, however, end users have to log off their desktops and then log back on when the new desktop is ready. 

For linked clones to be possible, administrators must install the VMware View Composer Service on their vCenter servers.

See also: thin provisioning, differencing disks

This was last updated in October 2013

Continue Reading About linked clones

Dig Deeper on VMware management tools

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

Whenever a snapshot is taken the parent disk gets into "Read Only" mode and any changes are made to the delta disk. So if we are able to make changes on the parent machines disk files, does that mean the parent machine is also working on a snapshot? So basically when we create a linked clone, a new snapshot is taken from the base disk and the linked clone works on that and the parent is working on the snapshot taken earlier of the base disk?