MOVEit Transfer supports running in a tiered architecture, commonly called a web farm. In this architecture, the application nodes are generally separated from the support nodes, such as database and filesystem servers, and any number of application nodes can be present in the farm. Additional nodes can be easily added if necessary, and if any one application node fails, the others continue to run, providing resilient access to the application. A load balancer provides access to the application nodes, and directs requests to each node, skipping any nodes that are not operational.
Note: You can find Web Farm installation instructions for MOVEit Transfer in the MOVEit Transfer Installation and Upgrade Guide.

Components

A MOVEit Transfer web farm requires the following components:

  • One or more MOVEit Transfer servers to act as application nodes.
  • A database server or cluster, accessible from the application nodes (Microsoft SQL Server is recommended as the database platform. See the Release Notes for supported versions).
  • A fileserver or cluster, accessible from the application nodes using Microsoft File Sharing.
  • A network load balancer to provide a single access point for external connections to access the application nodes.

Application Nodes

Each application node is a server containing a licensed copy of the MOVEit Transfer software. Each node is automatically assigned a node number when it is added to the farm, starting with node 1 when the farm is created. The nodes run independently of each other, having only minimal contact through node status and auditing records in the database that are constantly updated while each node is active. However, each node accesses the same database and filesystem as all the others.

SFTP Server Host Key

SFTP Server Host Keys are configured at the primary node (at installation or after installation using the MOVEit Transfer Config Utility) and the system automatically synchronizes the primary node's server host key with all other web farm nodes.

Database Server

The database server should be a separate server from the application nodes and, in the most secure architectures, on a separate network from the application nodes with access controlled by a firewall. For increased reliability, a database cluster may be used, as long as the cluster is available to the application nodes using a single IP address.

Fileserver

The fileserver should be a separate server from the application nodes and, in the most secure architectures, on a separate firewalled network from the application nodes. For smaller farms, the fileserver and database server may be the same system, though for maximum performance and reliability, they should be separate. Using a fileserver cluster increases reliability of the farm, as long as the cluster is available to the application nodes via a single IP address.

Load Balancer

The load balancer provides a single access point for external connections to access the application nodes. It should be capable of monitoring the health and connectivity of the application nodes, so that when one fails, it is removed from the load balancer's list of servers to forward connections to.

Note: If you use FTP or FTPS (FTP over TLS/SSL), once a session has been established, your load balancer should be able to forward subsequent traffic from a client to the original application mode ('sticky sessions'). This is not needed for SFTP or HTTP.

MOVEit Transfer web farms can be used with hardware load balancers from companies like Cisco and F5, or the Windows Network Load Balancing service from Microsoft.