High Availability Environment

EPM supports high availability for both the Web Server and the Database Server.

IIS high availability

Perform the following during installation:


The domain name must be the same for all Servers.

  1. Set the Load Balancer Server with the FQDN and IP to be used by the Agents. This is the FQDN that will identify the EPM Server.

  2. On each extra Server:

    1. Create a host file entry directing the Server's IP to the Load Balancer Server's IP.

    2. Install EPM on the Server, using the Load Balancer Server as the FQDN.

    3. Specify the Data File Location on all Servers to point to the same location, which is accessible by the application pool user on each Server.

    4. When the installation is complete, remove the host file entry and test that it installed successfully.

    5. Stop all IIS Application Pools, EPM Server Helper service, and EPM Server Background Worker service.

  3. Verify that all host file entries have been removed.

  4. Start all application pools and services on all IIS machines.

  5. Confirm that everything works from the Load Balancer Server.

Test the health of each Server in the IIS array

Run the https:// SYSTEM_URL/EPM/API/Server/Version API on the Server. The output must contain the word Version. You can also test the HTTP response code on each Server for the value 200.

SQL high availability

For instructions on SQL high availability, see High Availability Solutions (SQL Server).

  • SQL database recovery mode for transaction logs is set by default to Simple mode. Changing the recovery mode to Full Recovery mode has significant performance and operational impact on server performance and database size.
  • When you copy the database to a new instance, you perform a EPM database restore. After the restore, you must revive all Store Procedures on the new instance. For details, see Database Maintenance.