Disaster Recovery helps you quickly recover and reinstall your ePO - On-prem software.
To recover your ePO - On-prem environment, you must have a backup of the data that is unique to your environment and a mechanism for restoring ePO - On-prem using this backup. The data that makes your ePO - On-prem environment unique consists of two things: the ePO - On-prem database, and sections of the ePO - On-prem server file system. For example, the extensions that you checked in and the configuration files that control ePO - On-prem.
A ePO - On-prem database backup containing a valid Disaster Recovery Snapshot allows you to restore:
ePO - On-prem to your current ePO - On-prem server, which allows you to recover from. For example, a failed ePO - On-prem software upgrade.
ePO - On-prem to new server hardware with the original server name and IP address. For example, in the case of catastrophic hardware failure.
ePO - On-prem server hardware with a new server name, which allows you to move your ePO - On-prem server from one domain to another.
For security, the files stored in the Snapshot are encrypted using the Keystore Encryption Passphrase. Keep a record of this passphrase; you need it to decrypt the Disaster Recovery Snapshot records and Trellix can't recover it.
Important considerations
For a successful disaster recovery, the database and the snapshot it contains must be in sync. For example, if you took a Disaster Recovery Snapshot a week ago, two days ago you checked in a new extension, and last night you backed up the ePO - On-prem database without taking a new snapshot, the database and snapshot are not in sync and it is unlikely you will be able to successfully restore from that database. The Server Snapshot dashboard monitor can be used to tell you if your snapshot is up to date.
To prepare for disaster recovery, save the files to the Snapshot in the database, and then perform a full backup of the ePO - On-prem database.