Migrating to a load balanced configuration

This guide is provided as a general overview on the requirements of a load balanced setup and the processes involved in migration to a load balanced deployment. Your setup may differ from our example, but the way the components interact and their settings are the same.

The recommended configuration is to split all of the parts of the Files Advanced Server onto separate machines behind load balancers. The File Repository and File Store can reside on the same machine.

Before migrating the production server, we strongly recommend that these steps be performed in a test environment. The test deployment should have the same architecture as the production servers, along with a couple of test user desktop and mobile clients to ensure compatibility in your environment.

This guide uses an example setup of Files Advanced running in a standard deployment, with every component is installed on the same machine.

Note: In our example, we will keep the original Files Advanced Tomcat service running and connect it to the new configuration. This is not mandatory.

Before proceeding with any changes to your deployment, read our Backup & Recovery articles.

In this section

System Requirements

Migrating the PostgreSQL server

Files Advanced Server Configurations

FileStore and File Repository migration

Migrating Your Gateway Server

Log Management and Purging

Loadbalancer-specific settings

Cleanup of the original server(s)