You are here: Administrator's Guide > Planning an FME Server Installation > System Architectures > Planning for Fault Tolerance > Active-Active Architecture

Active-Active Architecture

The Active-Active failover architecture duplicates complete FME Server installations on separate servers. In other words, all components reside on the same system, and additional systems are configured similarly and provide similar functionality. A third-party load balancer directs incoming traffic to one of the available systems. When requests are directed to any of the systems, they are handled independently and only by one system. This approach works well with a cloud-based computing environment, such as Amazon Web Services, in which machines can be cloned easily to expand capacity.

Installing an Active-Active System:

Installing an Active-Active system involves multiple Express Installations (as many as you plan for your network), which you link together using your third-party load balancer. Follow the Express Installation instructions for either Windows or Linux:

Unsupported Active-Active Configuration

Can multiple FME Server installations point to the same FME Server System Share and/or FME Server Database?

No. Each installation of FME Server must reference a different location for the System Share (which includes Repositories and Resources). Referencing the same location causes FME Job Logs to collide and write together. Likewise, each installation must reference its own FME Server Database. The data tier for FME Server must be separate for each FME Server Core.