When a large number of users store and read files at the same time, the intense input/output processing can affect performance on the data-va virtual machine. You can add additional data-va virtual machines to balance the load.

Important

It is recommended that each data-va virtual machine serve no more than 1,000 users.

User accounts are provisioned to a specific data-va virtual machine that handles their file activity. The account’s class of service (COS) determines the data-va virtual machine where the account is provisioned. If the host pool in the COS specifies only one data-va virtual machine, users entitled to that COS are provisioned on that data-va virtual machine. If the host pool in the COS specifies multiple data-va virtual machines, users are randomly provisioned to any of the data-va virtual machines in the list.

When you add a new data-va virtual machine, the new data-va virtual machine automatically becomes available from the default COS host pool. The host pool for other classes of service that are created displays the new data-va virtual machine, but it is not enabled in that COS. To use a new data-va virtual machine in the other classes of service, the administrator must modify the COS and enable the data-va virtual machine.

When you add an additional virtual machine for either the data-va or connector-va virtual machines, you must use a base snapshot. A base snapshot is taken automatically after deployment.

Important

The first data-va virtual machine in the Horizon Workspace configuration is the master node. This node contains the metadata for the data-va virtual machine user accounts. If you create additional data-va virtual machines, these data-va virtual machines are file stores only. When the master node is down, users cannot log in to their accounts.

You can configure the host pool in the COS to use specific data-va virtual machines. In this way, you can manage where accounts are provisioned. For example, you add a second data-va virtual machine because disk space on the first data-va virtual machine is low. You do not want the first data-va virtual machine to be provisioned with any more new accounts once you have added the second node. From the Horizon Workspace Administrator Web interface, edit each COS to select the new data-va virtual machine in the Host Pool and deselect the other data-va virtual machine.

When a user signs into access their Horizon Folder, the gateway-va virtual machine routes the request to the data-va virtual machine where they are provisioned. When a data-va virtual machine is down, users receive a 502 error. The user’s authentication request is denied. In addition, when the data-va virtual machine is down, files shared from accounts on that machine cannot be accessed.

To maximize performance for Horizon Files service, you can add a new data-va virtual machine.

External guest users are given a COS called guest that is not visible from the Horizon Workspace Administrator Web interface. This COS determines the data-va virtual machine that guest users are provisioned on.

To add storage or perform other maintenance on a specific data-va virtual machine, you can shut down the machine temporarily. No new accounts are provisioned on the data-va virtual machine while it is down.

When you finish with the maintenance on the data-va virtual machine, you can add it back to the rotation.

When a data-va virtual machine is damaged and no longer operational, you can move the users provisioned to that virtual machine to another data-va virtual machine before removing the data-va virtual machine.

Horizon Files provides a script that allows you to integrate with VMware High Availability (HA) Application Monitoring. This script sets up a heartbeat based on the status of the Horizon Files processes including the store and directory processes.