Citrix Provisioning

Database mirroring

November 19, 2020

Contributed by:

In order to provide a highly available configuration, if you mirror a MS SQL database and the primary version becomes unavailable, Provisioning Services supports the mirrored version. This results in improved overall availability of Provisioning Services.

Database mirroring can be implemented in a new or existing farm and requires the following high-level tasks:

Creating the Provisioning Services MS SQL primary database (created when the Installation Wizard is run on the server) Note: For database mirroring to function, the recovery model must be set to Full.
Identifying the primary database server and instance (identified when the Configuration Wizard is run).
Identifying an existing MS SQL failover database server (identified, not created, when the Configuration Wizard is run).
Configuring mirroring between the primary and failover database servers (configured using MS SQL database server tools)

Citrix recommends that you start the failover server before enabling database mirroring in the farm. For information, see Windows Server Failover Clustering with SQL Server.

Note: The procedures that follow are only intended to call out the steps that are applicable to database mirroring when running the Configuration Wizard.

Note: Run the Configuration Wizard to specify the new failover server so that the status of the Provisioning Service’s farm correctly reports the new settings. After re-running the wizard, some services, including the stream service, restart so that the farm has the new failover server settings specified with the wizard was run.

Enabling Mirroring when Configuring a New Farm

To enable mirroring:

Start the Configuration Wizard on a server that will be in the new farm.
While running the wizard, when the Farm Configuration page displays, select the Create Farm radio button to create a new farm, then click Next.
Type or use the Browse button to identify the primary database server and instance names. Optionally, enter a TCP port number to use to communicate with this database server.
Enable the Specify database mirror failover partner option.
Type or use the Browse button to identify the failover database server and instance names. Optionally, enter a TCP port number to use to communicate with this server.
Click Next. If the failover database has already been configured and it is up and running, Provisioning Services should be able to connect to it. If the failover database server has not yet been created or is not running, an error message may display indicating a failure to connect. In this case, when prompted, click Yes to continue (the failover database can be created and configured after the new farm is created).
On the New Farm page, enter a name for the new database on the primary database server, then complete any additional requested information.
Click Next.
Complete the remaining wizard pages.

Enabling Mirroring Within an Existing Farm

To enable mirroring within an existing farm:

Confirm that the primary and failover database servers are up and running.
Using MS SQL server tools, mirror the Provisioning Services database to a database on the failover database server.
Run the Configuration Wizard on each server.
Identify the farm by choosing either the Farm is already configured or the Join exisiting farm option on the Farm Configuration page.
On the Database Server page, select the primary and failover database servers and instance names, then enable the database mirror failover feature.
Complete the remaining wizard pages.

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

Database mirroring

November 19, 2020

Contributed by:

November 19, 2020

Contributed by:

Database mirroring

Enabling Mirroring when Configuring a New Farm

Enabling Mirroring Within an Existing Farm

In this article