5.2

In these cases, View Manager does not include space for replicas when it calculates storage recommendations
for linked-clone disks.
Table 5-10
shows the formulas that calculate the estimated sizes of linked-clone disks when you edit a pool or
store replicas on a separate datastore.
Table 5-10. Storage Sizing Formulas for Linked-Clone Disks When You Edit a Pool or Store Replicas on a
Separate Datastore
Data Type
Selected Free Space
(GB)
Min Recommended
(GB) 50% Utilization (GB)
Max Recommended
(GB)
OS disks Free space on the
selected datastores
Number of VMs * (2 *
memory of VM)
Number of VMs *
(50% of replica disk +
memory of VM)
Number of VMs *
(100% of replica disk +
memory of VM)
Persistent disks Free space on the
selected datastores
Number of VMs * 20%
of persistent disk
Number of VMs * 50%
of persistent disk
Number of VMs * 100%
of persistent disk
Example of a Storage Sizing Estimate When You Edit a Pool or Store Replicas on a Separate Datastore
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-11 shows how the sizing formulas calculate estimated storage requirements for the sample linked-
clone pool.
Table 5-11. Example of a Sizing Estimate for Linked-Clone Disks When You Edit a Pool or Store Replicas on
a Separate Datastore
Data Type
Selected Free Space
(GB)
Min Recommended
(GB) 50% Utilization (GB)
Max Recommended
(GB)
OS disks 184.23 10 * (2*1GB) =
20.00
10 * (50% of 10GB +
1GB) =
60.00
10 * (100% of 10GB +
1GB) =
110.00
Persistent disks 28.56 10 * (20% of 2GB) =
4.00
10 * (50% of 2GB) =
10.00
10 * (100% of 2GB) =
20.00
Set the Storage Overcommit Level for Linked-Clone Desktops
You can control how aggressively View Manager creates linked-clone desktops on a datastore by using the
storage
overcommit feature. This feature lets you create linked clones that have a total logical size larger than
the physical storage limit of the datastore.
This feature works only with linked-clone pools.
The storage overcommit level calculates the amount of storage greater than the physical size of the datastore
that the clones would use if each clone were a full virtual machine. For details, see “Storage Overcommit for
Linked-Clone Desktops,” on page 111.
Procedure
1 In View Administrator, click Inventory > Pools.
VMware Horizon View Administration
110 VMware, Inc.