Other scenarios for implementing PI AF high availability

In addition to the recommended approach for PI AF high availability (see Recommended approach for PI AF high availability), there are other possible scenarios, all based on different combinations of Microsoft high availability technologies and load balancers.

Note: This document assumes familiarity with the configuration and operation of network load balancers, failover clusters, and the cluster administration tools provided with the Windows operation system. For an overview of Microsoft high availability solutions, see the Microsoft article Business continuity and database recovery - SQL Server.

Here are some of the most common configurations:

• High availability using Clustered SQL Servers and a network load balancer:

  • Deploy the PI AF application service on multiple computers and the PI AF SQL database on another set of two or more computers. We recommend that the PI AF application service be configured to run under a domain account.

  • Configure the PI AF SQL database computers as a Clustered SQL Server.

  • Point all instances of the PI AF application service toward the Clustered SQL Server.

  • Deploy a network load balancer between the PI AF client and the PI AF application service.

  • Install the PI AF client on separate computers. Direct the PI AF clients toward the network load balancer.

• High availability using only Windows Failover Clusters:

  • Deploy the PI AF application service on multiple computers and the PI AF SQL database on another set of two or more computers. We recommend that the PI AF application service be configured to run under a domain account.

  • Set up a Windows Failover Cluster for all instances of the PI AF application service and another Windows Failover Cluster for the clustered SQL Servers. Then, create a SQL Server Cluster to host the PI AF SQL database.

  • Install the PI AF client on separate computers. Direct the PI AF clients toward the name of the Windows Failover Cluster used for the PI AF application service.

• High availability using Windows Failover Clusters and a Microsoft Always On availability group but no load balancer:

  • Deploy the PI AF application service on multiple computers and the PI AF SQL database on another set of two or more computers. The PI AF application service should be configured to run under a domain account.

  • Configure all instances of the PI AF application service as a Windows Failover Group.

  • Configure the PI AF SQL databases as a Microsoft Always On availability group.

  • Install the PI AF client on separate computers. Direct the PI AF clients toward the PI AF application Service configured as a Windows Failover Cluster.

• High availability using SQL Server mirroring: and an optional load balancer:

  • Deploy the PI AF application service and the PI AF SQL database on separate computers.

  • Set up the PI AF SQL database on a mirrored SQL Server.

  • Install the PI AF client on a different computer. Optionally, deploy a network load balancer between the PI AF client and the PI AF application service.

    Database mirroring: Database mirroring for the PI AF SQL Server database is still documented and supported in current PI Server releases. However, Microsoft has deprecated the SQL Server mirroring feature and plans to remove it in a future version. We do not recommend mirroring for new deployments. Use SQL Server Always On availability groups (or Basic availability groups with SQL Server Standard Edition) for high availability instead. If you currently rely on mirroring, plan a migration to availability groups during your next upgrade or maintenance window. See Microsoft’s guidance for prerequisites, restrictions, and recommendations for database mirroring.