Perform failover of your small and medium-sized ePO

This example task shows how to use the Disaster Recovery Snapshot in the SQL database 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.
See the Small and medium-sized ePO - On-prem Disaster Recovery network configuration graphic to reference names and connections described in these steps.

From the primary 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
(Optional) If you have remote Agent Handlers, use Windows Services on all Agent Handlers, and stop the Event Parser and Apache services. This step is only required if the primary Agent Handlers aren't used in failover situations.
On the restore server, install ePO - On-prem using the same version as the Snapshot:
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 the 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.
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.
On the DNS server, change the CNAME record in epo.customer.net to point to the restore ePO - On-prem server.
(Optional) If you have remote Agent Handlers, change their configuration to use epo.customer.net and to find the restore ePO - On-prem server based on the CNAME.
Complete the ePO - On-prem software installation process using the documented steps until your new ePO - On-prem server is up and running.
Confirm your managed systems and remote Agent Handlers (if used) can connect to the restore ePO - On-prem server.

Perform failover of your small and medium-sized ePO - On-prem server (example)