Planning for High Availability with App-V 5.0
Microsoft Application Virtualization 5.0 (App-V 5.0) system configurations can take advantage of options that maintain a high level of available service.
Use the information in the following sections to help you understand the options to deploy App-V 5.0 in a highly available configuration.
Support for Microsoft SQL Server clustering
You can run the App-V Management database and Reporting database on computers that are running Microsoft SQL Server clusters. However, you must install the databases using scripts.
For instructions, see How to Deploy the App-V Databases by Using SQL Scripts.
Support for IIS Network Load Balancing
You can use Internet Information Services (IIS) Network Load Balancing to configure a highly available environment for computers running the App-V 5.x Management, Publishing, and Reporting services which are deployed through IIS.
Review the following for more information about configuring IIS and Network Load Balancing for computers running Windows Server operating systems:
Provides information about configuring Internet Information Services (IIS) 7.0.
Achieving High Availability and Scalability - ARR and NLB (https://go.microsoft.com/fwlink/?LinkId=316369)
Configuring Microsoft Windows Server
Network Load Balancing (https://go.microsoft.com/fwlink/?LinkId=316370).
This information also applies to IIS Network Load Balancing (NLB) clusters in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.
Note The IIS Network Load Balancing functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details are changed in Windows Server 2012. For information on new ways to do tasks, see Common Management Tasks and Navigation in Windows Server 2012 R2 Preview and Windows Server 2012 (https://go.microsoft.com/fwlink/?LinkId=316371).
Support for clustered file servers when running (SCS) mode
Running App-V 5.0 in Share Content Store (SCS) mode with clustered file servers is supported.
The following steps can be used to enable this configuration:
Configure App-V 5.0 to run in client SCS mode. For more information about configuring App-V 5.0 SCS mode, see How to Install the App-V 5.0 Client for Shared Content Store Mode.
Configure the file server cluster configured in both the Microsoft Server 2012 scale out mode and pre 2012 mode with a virtual SAN.
The following steps can be used to validate the configuration:
Add a package on the publishing server. For more information about adding a package, see How to Add or Upgrade Packages by Using the Management Console.
Perform a publishing refresh on the computer running the App-V 5.0 client and open an application.
Switch cluster nodes mid-publishing refresh and mid-streaming to ensure fail-over works correctly.
Review the following for more information about configuring Windows Server Failover clusters:
Checklist: Create a Clustered File Server (https://go.microsoft.com/fwlink/?LinkId=316372).
Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster (https://go.microsoft.com/fwlink/?LinkId=316373).
Support for Microsoft SQL Server Mirroring
Using Microsoft SQL Server mirroring, where the App-V 5.0 management server database is mirrored utilizing two SQL Server instances, for App-V 5.0 management server databases is supported.
Review the following for more information about configuring Microsoft SQL Server Mirroring:
How to: Prepare a Mirror Database for Mirroring (Transact-SQL) (https://go.microsoft.com/fwlink/?LinkId=316375)
Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio) (https://go.microsoft.com/fwlink/?LinkId=316377)
The following steps can be used to validate the configuration:
Initiate a Microsoft SQL Server Mirroring session.
Select Failover to designate a new master Microsoft SQL Server instance.
Verify that the App-V 5.0 management server continues to function as expected after the failover.
The connection string on the management server can be modified to include failover partner = <server2>. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V 5.0 client is doing a fresh connection (say after reboot).
Use the following steps to modify the connection string to include failover partner = <server2>:
Important This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
Login to the management server and open regedit.
Navigate to HKEY_LOCAL_MACHINE \ Software \ Microsoft \ AppV \ Server \ ManagementService.
Modify the MANAGEMENT_SQL_CONNECTION_STRING value with the failover partner = <server2>.
Restart management service using the IIS console.
Note Database Mirroring is on the list of Deprecated Database Engine Features for Microsoft SQL Server 2012 due to the AlwaysOn feature available with Microsoft SQL Server 2012.
Click any of the following links for more information:
How to: Prepare a Mirror Database for Mirroring (Transact-SQL) (https://go.microsoft.com/fwlink/?LinkId=394235).
How to: Configure a Database Mirroring Session (SQL Server Management Studio) (https://go.microsoft.com/fwlink/?LinkId=394236).
Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio) (https://go.microsoft.com/fwlink/?LinkId=394237).
Deprecated Database Engine Features in SQL Server 2012 (https://go.microsoft.com/fwlink/?LinkId=394238).
Support for Microsoft SQL Server Always On configuration
The App-V 5.0 management server database supports deployments to computers running Microsoft SQL Server with the Always On configuration.