Create a Snapshot of your current ePO - On-prem server and make sure the server task is finished before starting the restore process.
ePO - On-prem server
Primary ePO - On-prem server — Used for day-to-day activities. The ePO - On-prem snapshots of the SQL database are completed automatically or initiated manually just after updates occur.
Note
By default, server tasks automate snapshots every night.
Restore ePO - On-prem server — This server is running with only the SQL database installed. This is where you copy the Disaster Recovery snapshot and SQL database backups from the primary ePO - On-prem server.
Note
After a primary ePO - On-prem server failure, reinstall the ePO - On-prem software using the restore option during the ePO - On-prem setup process.
Shared resource — The DNS server configured with an availability name (for example, epo.customer.net) uses CNAME to point to the primary ePO - On-prem server, and is configured to point to the restore ePO - On-prem server after a failure.
SQL database servers
Primary SQL database — Used for day-to-day activities. Use either a Microsoft SQL Server Management Studio or the BACKUP (Transact-SQL) command-line process to copy the Disaster Recovery Snapshots and database backups daily to the Restore SQL database.
Restore SQL database — Used for running and receiving the Disaster Recovery Snapshots and database backups daily from the Primary SQL database.
Trellix ePO console — Depending on the DNS server configuration, the console is connected to either the primary or restore ePO - On-prem server. The console is used to manage systems, run the SQL backups, and install the ePO - On-prem software.
