Citrix Provisioning

Provisioning Server failover

December 28, 2018

Contributed by:

By default, all Provisioning Servers within a site that can access a vDisk can provide that vDisk to target devices. Multiple Provisioning Servers can access the same physical files on shared storage. This allows a target device to establish a connection on an alternate Provisioning Server if the connection to the active Provisioning Server is interrupted for any reason. A target device does not experience any disruption in service or loss of data when failover occurs.

Note: For implementations that use vDisk replication, if a server failover occurs, only those servers with access to an identical replicated vDisk can provide that vDisk to target devices. For example, if a vDisk is replicated across three servers hard drives and then one of the vDisks is updated, that vDisk is no longer identical. It is not considered if a server failover occurs. Even if the same exact update is made to two of the vDisks, the timestamps on each differs, therefore the vDisks are no longer identical.

Note: Provisioning Services does not support the high availability of vDisks on local storage that is in Private Image mode or that are currently in maintenance (read/write enabled).

If load balancing is enabled for the vDisk and a server providing that vDisk should fail, Provisioning Services automatically balances the target device load between the remaining servers. If the load balancing option is not enabled, a single server is assigned to provide the vDisk to target devices, therefore failover fails.

Note: For information on configuring Provisioning Services to automatically balance the target device load between servers, refer to Balancing the Target Device Load on Provisioning Servers.

Highly Available Implementation

The Provisioning Server that a target device accesses to login does not necessarily become the Provisioning Server that accesses the vDisk on behalf of the target device. In addition, once connected, if one or more Provisioning Servers can access the vDisk for this target device, the server that is least busy is selected.

To purposely force all target devices to connect to a different Provisioning Server, while avoiding having targets timeout and attempt to reconnect to the current server, stop the Stream Service on that server. Upon shutdown, the Stream Service notifies each target device to relogin to another server.

Testing target device Failover

To ensure that devices can failover successfully, complete the following:

Double-click the vDisk status icon on the target device and then note the IP address of the connected Provisioning Server.
Right-click the connected Provisioning Server in the Console. Select Stream Services, then select Stop.
Confirm that the IP address of the connected Provisioning Server changes to that of an alternate Provisioning Server in the vDisk status dialog on the target device.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Provisioning Server failover

December 28, 2018

Contributed by:

December 28, 2018

Contributed by:

Provisioning Server failover

Testing target device Failover

In this article