Planning for Fault Tolerance

The goal of a fault-tolerant environment is to ensure that if a hardware component fails, FME Server remains online.

The fault tolerant architecture is comprised of redundant FME Servers spread across separate servers.

A third-party load balancer is required, which directs incoming traffic to one of the redundant web components.

Organizations are expected to maintain the FME Server Database and FME Server System Share (a file system for hosting Repositories and Resources) on their own fault-tolerant servers. This ensures the fault-tolerant FME Server has reliable access to workspaces, repositories, resources, and other items.

WARNING: We recommend installing all FME Servers on systems that are synchronized to the same time zone. If time zones differ across FME Servers, unexpected issues may arise, including:
Improper timing of Schedule Initiated triggers.
Inconsistent or misleading timestamps in log files (accessed from Resources).

Note: In a fault tolerant installation of FME Server, the Automations triggers UDP Message Received and Email Received (SMTP) (and corresponding Notification Service UDP Publisher and SMTP Publisher) are not supported. To receive email messages, consider the Email Received (IMAP) trigger instead.

To Install a Fault Tolerant System

Proceed to Installing a Scalable, Fault-Tolerant FME Server.