VMware View Manager 4.5 Admin Manual page 87

To arrive at a recommendation for storing replicas on a separate datastore, View Manager allows space for
two replicas on the datastore. The same value is calculated for minimum and maximum usage.
For details, see "Sizing Formulas for Linked-Clone Pools,"
Sizing Guidelines and Storage Overcommit
After you estimate storage requirements, select datastores, and deploy the pool, View Manager provisions
linked-clone virtual machines on different datastores based on the free space and the existing clones on each
datastore.
Based on the storage-overcommit option that you select on the Select Datastores page in the Add Pool wizard,
View Manager stops provisioning new clones and reserves free space for the existing clones. This behavior
ensures that a growth buffer exists for each desktop on the datastore.
If you select an aggressive storage-overcommit level, the estimated storage requirements might exceed the
capacity shown in the Selected Free Space column. The storage-overcommit level affects how many virtual
machines that View Manager actually creates on a datastore.
For details, see "Set the Storage Overcommit Level for Linked-Clone Desktops,"
Sizing Formulas for Linked-Clone Pools
Storage-sizing formulas can help you estimate the size of linked-clone disks relative to the free space on the
datastores that you select for OS disks, View Composer persistent disks, and replicas.
Storage Sizing Formulas
Table 5-8 shows the formulas that calculate the estimated sizes of linked-clone disks when you create a pool
and as the linked-clone desktops grow over time. These formulas include the space for replica disks that are
stored with the clones on the datastore.
If you edit an existing pool or store replicas on a separate datastore, View Manager uses a different sizing
formula. See "Sizing Formulas for Creating Linked Clones When You Edit a Pool or Store Replicas on a Separate
Datastore," on page 88.
Table 5-8. Storage Sizing Formulas for Linked-Clone Disks on Selected Datastores
Data Type
OS disks
Persistent disks
Example of a Storage Sizing Estimate
In this example, the parent virtual machine is configured with 1GB of memory. The parent virtual machine's
disk size is 10GB. A linked-clone pool is created with 10 desktops. Persistent disks are configured as 2048MB
in size.
The OS disks are configured on a datastore that currently has 184.23GB of available space. The persistent disks
are configured on a different datastore with 28.56GB of available space.
Table 5-9 shows how the sizing formulas calculate estimated storage requirements for the sample linked-clone
pool.
VMware, Inc.
Selected Free Space Min Recommended
(GB) (GB)
Free space on the Number of VMs * (2 *
selected datastores memory of VM) + (2 *
replica disk)
Free space on the Number of VMs * 20%
selected datastores of persistent disk
Chapter 5 Creating Desktop Pools
on page 87.
on page 89.
50% Utilization (GB)
Number of VMs *
(50% of replica disk +
memory of VM) + (2 *
replica disk)
Number of VMs * 50%
of persistent disk
Max Recommended
(GB)
Number of VMs *
(100% of replica disk +
memory of VM) + (2 *
replica disk)
Number of VMs * 100%
of persistent disk
87