Scaling App Volumes Manager

To scale App Volumes Manager, you can install an additional App Volumes Manager component on multiple servers and point them to a shared SQL database.

Multiple App Volumes Manager instances can be load balanced by a hardware load balancer. Alternatively, you can configure the App Volumes agent to communicate with multiple App Volumes Manager servers.

Procedure

1. To install additional App Volumes Manager instances, follow standard installation procedures and point a new instance to the existing SQL database.

   Important: In the installation wizard, ensure that you have deselected the Create a new database or overwrite the existing database check box.

   Install App Volumes Manager

2. Register App Volumes Manager server.

   For detailed information, see the Register App Volumes Manager Server section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.

3. Depending on whether you use the load balancer or configure App Volumes agent, perform the following steps:

   Option	Procedure
   Use a load balancer	Add the additional App Volumes Manager instances to the load balancer.
   Configure App Volumes agent	Modify the registry key HKLM\SYSTEM\CurrentControlSet\Services\svservice\Parameters as follows: Add ManagerN as the string value. N ranges between 0 to 9 Add FQDN of the App Volumes Manager and port as value data. By default, the port number is 443. For example: To add data for an additional App Volumes Manager instance whose IP address is 192.168.127.53 and port 443, perform the following: Open regedit.exe. Access the registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svservice\Parameters. Right click on the registry key and select New > String Value. Add the value as Manager2. Double-click Manager2 and add the data as 192.168.127.53:443. Click OK. Restart the virtual machine on which you have installed the App Volumes agent.