7.0

3 In the Initiate reclamation when unused space on VM exceeds text box, type the minimum amount of
unused disk space, in gigabytes, that must accumulate on a linked-clone OS disk before ESXi starts
reclaiming space on that disk.
For example: 2 GB.
The default value is 1 GB.
What to do next
You can configure blackout days and times during which disk space reclamation and regeneration for View
Storage Accelerator do not take place. See “Set Storage Accelerator and Space Reclamation Blackout Times
for View Composer Linked Clones,” on page 254.
In View Administrator, you can select Catalog > Desktop Pools and select a machine to display the last time
space reclamation occurred and the last amount of space reclaimed on the machine.
Using VAAI Storage for View Composer Linked Clones
If your deployment includes NAS devices that support the vStorage APIs for Array Integration (VAAI), you
can enable the View Composer Array Integration (VCAI) feature on View Composer linked-clone desktop
pools. This feature uses native NFS snapshot technology to clone virtual machines.
NOTE In Horizon 7.0, instant clones do not support VAAI.
With this technology, the NFS disk array clones the virtual machine files without having the ESXi host read
and write the data. This operation might reduce the time and network load when virtual machines are
cloned.
Apply these guidelines for using native NFS snapshot technology:
n
You can use this feature only if you configure desktop pools or automated farms on datastores that
reside on NAS devices that support native cloning operations through VAAI.
n
You can use View Composer features to manage linked clones that are created by native NFS snapshot
technology. For example, you can refresh, recompose, rebalance, create persistent disks, and run
QuickPrep customization scripts on these clones.
n
You cannot use this feature if you store replicas and OS disks on separate datastores.
n
This feature is supported on vSphere 5.0 and later.
n
If you edit a pool and select or deselect the native NFS cloning feature, existing virtual machines are not
affected.
To change existing virtual machines from native NFS clones to traditional redo log clones, you must
deselect the native NFS cloning feature and recompose the pool to a new base image. To change the
cloning method for all virtual machines in a pool and use a different datastore, you must select the new
datastore, deselect the native NFS cloning feature, rebalance the pool to the new datastore, and
recompose the pool to a new base image.
Similarly, to change virtual machines from traditional redo log clones to native NFS clones, you must
select a NAS datastore that supports VAAI, select the native NFS cloning feature, rebalance the pool to
the NAS datastore, and recompose the pool. For more information, see
http://kb.vmware.com/kb/2088995.
n
On an ESXi cluster, to configure native cloning on a selected NFS datastore in View Administrator, you
might have to install vendor-specific NAS plug-ins that support native cloning operations on VAAI on
all ESXi hosts in the cluster. See your storage vendor documentation for guidance on configuration
requirements.
Chapter 16 Reducing and Managing Storage Requirements
VMware, Inc. 253