Press CTRL+K to open search

Perform failover of your enterprise ePO - On-prem server (example)

  • Published on Sep 7, 2026
  • 2 minute(s) read
Prev Next

This example task shows how to use the Disaster Recovery Snapshot for recovery if the primary ePO - On-prem server fails.

  • If the ePO - On-prem server is damaged, you must restore the SQL database from the backup before performing the failover process.

  • You must have a Snapshot and backup of the database on your SQL Server.

  1. From the EPO-DC1 ePO - On-prem server, stop these services:

    1. Click Start → Run, type services.msc, and click OK.

    2. Right-click each of the following services and select Stop:

      • Trellix ePolicy Orchestrator - On-premises Application Server

      • Trellix ePolicy Orchestrator - On-premises Event Parser

      • Trellix ePolicy Orchestrator - On-premises Server

    3. Double-click each of the following services and change the Startup type to Disabled:

      • Trellix ePolicy Orchestrator - On-premises Application Server

      • Trellix ePolicy Orchestrator - On-premises Event Parser

      • Trellix ePolicy Orchestrator - On-premises Server

  2. Using Windows Services on all Agent Handlers, stop the Event Parser and Apache services. Make sure the Agent Handlers in DC1 aren't active.

  3. On the SQL Server "Virtual-SQL-name," disable Always On Group.

  4. On the DNS server, identify the physical node hosting the ePO - On-prem SQL database. The recovery installation must point to the physical SQL Server (SQL-DC1 or SQL-DC2) during recovery installation, and then change the name to "Virtual-SQL-name" after recovery installation.

  5. On the restore server, ePO - On-prem Server-DC2, confirm ePO - On-prem isn't installed. Delete ePO - On-prem if it is installed.

  6. On the restore server, follow the steps to install ePO - On-prem:

    1. When prompted, click Restore ePO from an existing database Snapshot.

    2. Point to the ePO - On-prem database on SQL-DC1 or SQL-DC2 using a Windows or Active Directory account with local administrator permissions on the ePO - On-prem server.

    3. Use the same drive and directory location used for the ePO - On-prem software on EPO-DC1.

    4. Point ePO - On-prem to the SQL-DC1 or SQL-DC2, the physical node hosting the ePO - On-prem database.

    5. Use Windows Active Directory or Server Administration account credentials to access to the ePO - On-prem database.

    6. Confirm the port information is correct. For detailed port requirements, see Port configuration from failed to restored Trellix ePO server.

    7. Provide the ePO - On-prem administrator account and password.

    8. Provide the Keystore Password. Recovery takes about 15 minutes, depending on the performance of the ePO - On-prem server and SQL Server.

    9. Install ePO - On-prem hotfixes in sequential order.

  7. Change the CNAME record in the DNS for epo.customer.net to point to EPO-DC2 in DC2.

  8. On the SQL Server "Virtual-SQL-name," enable Always On Group.

  9. Reconfigure ePO - On-prem to use the shared SQL resource “Virtual-SQL-name.”

    Note

    All Agent Handlers are configured to use epo.customer.net and to find the restored ePO - On-premserver based on the CNAME. For steps on how to set up the published DNS name, see Configure Agent Handlers list.

  10. Browse to https://epo.customer.net:8443/core/config and change the host name of the SQL Server to “Virtual-SQL-name.”

  11. Make sure ePO - On-prem is uninstalled on EPO-DC1.

    Follow these steps when reverting ePO - On-prem back from DC2 to DC1.

Related articles