7.0

3 To move existing View Composer desktop pools from another type of datastore to a Virtual SAN
datastore, in View Administrator, edit the pool to deselect the old datastore and select the Virtual SAN
datastore instead, and use the Rebalance command. This operation is not possible for automated farms
because you cannot rebalance an automated farm .
4 (Optional) Use vCenter Server to modify the parameters of the storage policy profiles, which include
things like the number of failures to tolerate and the amount of SSD read cache to reserve.
The names of the policies are OS_DISK (for operating system files), PERSISTENT_DISK (for user data
files), REPLICA_DISK (for replicas), and VM_HOME (for virtual machine files such as .vmx and .vmsn
files). Changes to the policy are propagated to newly created virtual machines and to all existing virtual
machines in the desktop pool or the automated farm.
5 Use vCenter Server to monitor the Virtual SAN cluster and the disks that participate in the datastore.
For more information, see the vSphere Storage document and the vSphere Monitoring and Performance
documentation. For vSphere 6 or later, see the Administering VMware Virtual SAN document.
6 (Optional) For View Composer linked-clone desktop pools, use the Refresh and Recompose commands
as you normally would. For automated farms, only the Recompose command is supported, regardless
of the type of datastore.
Requirements and Limitations
The Virtual SAN feature has the following limitations when used in a View deployment:
n
This release does not support using the View space-efficient disk format feature, which reclaims disk
space by wiping and shrinking disks.
n
Virtual SAN does not support the View Composer Array Integration (VAAI) feature because Virtual
SAN does not use NAS devices.
n
Virtual SAN datastores are not compatible with Virtual Volumes datastores for this release.
NOTE Virtual SAN is compatible with the View Storage Accelerator feature. Virtual SAN provides a
caching layer on SSD disks, and the View Storage Accelerator feature provides a content-based cache that
reduces IOPS and improves performance during boot storms.
The Virtual SAN feature has the following requirements:
n
vSphere 5.5 Update 1 or a later release.
n
Appropriate hardware. For example, VMware recommends a 10GB NIC and at least one SSD and one
HDD for each capacity-contributing node. For specifics, see the VMware Compatibility Guide.
n
A cluster of at least three ESXi hosts. You need enough ESXi hosts to accommodate your setup. For
more information, see the vSphere Configuration Maximums document, available from
https://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html.
n
SSD capacity that is at least 10 percent of HDD capacity.
n
Enough HDDs to accommodate your setup. Do not exceed more than 75% utilization on a magnetic
disk.
For more information about Virtual SAN requirements, see "Working with Virtual SAN" in the vSphere 5.5
Update 1 Storage document. For vSphere 6 or later, see the Administering VMware Virtual SAN document. For
guidance on sizing and designing the key components of View virtual desktop infrastructures for VMware
Virtual SAN, see the white paper at
http://www.vmware.com/files/pdf/products/vsan/VMW-TMD-Virt-SAN-Dsn-Szing-Guid-Horizon-
View.pdf.
Setting Up Desktop and Application Pools in View
236 VMware, Inc.