Horizon 6.0 introduced some new default storage policies for Virtual SAN. These policies are not automatically applied to existing virtual machine desktops created on Virtual SAN by View 5.3.1 (or 5.3.x maintenance releases) after the desktop pool is upgraded.
About this task
In addition, when you upgrade from View 5.3.1, the Use VMware Virtual SAN pool setting will not automatically be enabled, even if the pool is on a Virtual SAN datastore. You have the following upgrade options:
If you continue to use VMware vSphere 5.5 Update 1, after upgrading, continue to use the default storage policies that were used with View 5.3.1. If you choose this option, edit the pool settings so that Use VMware Virtual SAN is enabled.
Use the procedure described in this topic so that the desktop pool uses the new default storage policies. This procedure involves rebalancing the desktop pool to a non-Virtual SAN datastore and then upgrading and rebalancing back to the Virtual SAN datastore.
The tasks outlined in this procedure describe upgrading from a View 5.3.1 desktop pool using a Virtual SAN datastore on a VMware vSphere 5.5 Update 1 cluster. Upgrading from Virtual SAN datastore on a VMware vSphere 5.5 or earlier cluster (a Tech Preview feature) is not supported.
Also, because this procedure involves recomposing the desktop pool, any changes that end users have made to the operating system disk will be lost.
Verify that all virtual machines in the pool are VMware vSphere 5.5 Update 1 or later virtual machines. VMware recommends that you upgrade to VMware vSphere 6.0 or later because the Virtual SAN feature available with vSphere 6.0 and later releases contains many performance improvements over the feature that was available with vSphere 5.5 Update 1. With vSphere 6.0 this feature also has broader HCL (hardware compatibility) support.
For information about upgrades, see Upgrade ESXi Hosts and Their Virtual Machines and see the VMware vSphere Upgrade Guide. For information about Virtual SAN requirements and upgrades, see the Administering VMware Virtual SAN document.
In vCenter Server, verify that the following privileges are added to the Composer role:
Profile-Driven Storage: All Folder: Create Folder & Delete Folder Host: Configuration: Advanced settings
- Edit the pool settings of the desktop pool to change the datastore from a Virtual SAN datastore to a non-Virtual SAN datastore, and use the Rebalance command.
For instructions on editing server settings and using the Rebalance command, click the Help button in View Administrator.
- Upgrade the desktop pool to the latest version, as described in Upgrade View Composer Desktop Pools.
This process includes installing the latest version of View Agent on the parent virtual machine and taking a snapshot.
- Recompose the pool on the non-Virtual SAN datastore using the snapshot of the parent virtual machine you just created.
For instructions on recomposing pools, click the Help button in View Administrator.
- Edit the pool settings of the newly upgraded desktop pool to change the datastore from a non-Virtual SAN datastore to a Virtual SAN datastore, and use the Rebalance command.
What to do next
If you upgraded your virtual machines to VMware vSphere 6.0, to upgrade to using Virtual SAN 2 rather than Virtual SAN 1, see Upgrade from Virtual SAN Disk Format Version 1.