5.2

n
You can rebalance selected linked clones or all clones in a pool.
n
You can rebalance a desktop pool on demand or as a scheduled event.
You can schedule only one rebalance operation at a time for a given set of linked clones. If you start a
rebalance operation immediately, the operation overwrites any previously scheduled task.
You can schedule multiple rebalance operations if they affect different linked clones.
Before you schedule a new rebalance operation, you must cancel any previously scheduled task.
n
You can only rebalance desktops in the Available, Error, or Customizing state with no schedules or
pending cancellations.
n
As a best practice, do not mix linked-clone virtual machines with other types of virtual machines on the
same datastore. This way View Composer can rebalance all the virtual machines on the datastore.
n
If
you edit a pool and change the host or cluster and the datastores on which linked clones are stored, you
can only rebalance the linked clones if the newly selected host or cluster has full access to both the original
and the new datastores. All hosts in the new cluster must have access to the original and new datastores.
For example, you might create a linked-clone pool on a standalone host and select a local datastore to store
the clones. If you edit the pool and select a cluster and a shared datastore, a rebalance operation will fail
because the hosts in the cluster cannot access the original, local datastore.
n
You can set a minimum number of ready, provisioned desktops that remain available for users to connect
to during the rebalance operation. See “Keeping Linked-Clone Desktops Provisioned and Ready During
View Composer Operations,” on page 117.
Migrate Linked-Clone Desktops to Another Datastore
To migrate linked-clone virtual machines from one set of datastores to another, use the rebalance operation.
When you use rebalance, View Composer manages the movement of the linked clones between datastores.
View Composer ensures that the linked clones' access to the replica is maintained during and after the rebalance
operation. If necessary, View Composer creates an instance of the replica on the destination datastore.
NOTE Do not use vSphere Client or vCenter Server to migrate or manage linked clone virtual machines. Do
not use Storage vMotion to migrate linked-clone virtual machines to other datastores.
Prerequisites
Familiarize
yourself with the rebalance operation. See “Rebalance Linked-Clone Desktops,” on page 257 and
“Rebalancing Linked Clones Among Logical Drives,” on page 258.
Procedure
1 In View Administrator, select the linked-clone pool you want to migrate and click Edit.
2 In the vCenter Settings tab, scroll down to Datastores and click Browse.
3 On the Select Linked Clone Datastores page, deselect the datastores that currently store the linked clones,
select the destination datastores, and click OK.
4 In the Edit pool name window, click OK.
5 On the pool name page, click View Composer > Rebalance.
6 Follow the wizard instructions to rebalance the linked-clone desktops.
The linked-clone desktops are refreshed and migrated to the destination datastores.
Chapter 10 Managing Linked-Clone Desktops
VMware, Inc. 259