The Disaster Recovery Snapshot Server task allows you to save your files in an encrypted format and save the Snapshot to the database.
Disaster Recovery Snapshot contents
The files are saved in an encrypted format in the database when the Disaster Recovery Snapshot Server task runs.
The extensions are processed one at a time. Extensions can specify additional files to be stored in the snapshot: when each extension is processed, the snapshot task asks each extension what other files are required, and if any are defined it stores them in the snapshot.
Core ePO - On-prem configuration files | <ePO Install path>\Server\Keystore\ <ePO Install path>\Server\conf\ |
Installed extensions | <ePO Install path>\Server\extensions\installed\ |
The Disaster Recovery Snapshot records include the paths configured for your registered executables. The registered executable files are not stored in the Snapshot, and you must replace the executable files when you restore your ePO - On-prem environment. After you restore the ePO - On-prem environment, any registered executables with broken paths appear in red on the Registered Executables page.
Note
Test your registered executable paths after you restore your ePO - On-prem server. Some registered executable paths might not appear in red, but still fail because of dependency issues related to the registered executables.
Disaster Recovery Snapshot Server task
Use the Disaster Recovery Snapshot Server task to save the Snapshot to the database. The Snapshot is created when you install ePO - On-prem. The task can be scheduled to run at a specific time, by default it's configured to run every day at 2 a.m. You can also run the task manually from the ePO - On-prem dashboard and the WebAPI interface.
When ePO - On-prem is installed, the Disaster Recovery Snapshot Server task is enabled by default if the database is hosted on a full version of SQL Server. It's disabled by default if the database is hosted on an SQL Express instance, due to the hard-coded database size limit enforced by SQL Express.
ePO - On-prem only saves one Snapshot to the database at a time: each time the task runs, the current Snapshot information is removed, and the new Snapshot information takes its place.