After upgrading to or installing ePO - On-prem 5.10, a new SQL database is created, in addition to the existing ePO - On-prem database, in this format:
ePO_<ePOServerName>_Events
When you configure SQL database backups, you must add the ePO Events database to your current backup plan.
ePO - On-prem stores monthly event data in the ePO Events database, which handles threat information.
SQL server can be recovered in Full and Simple Recovery models. You can select a recovery model for ePO Events or any database attached to the SQL server.
Full recovery model
By default, the ePO Events database is configured to use the Full Recovery Model.
The Full Recovery Model includes the administrative overhead of periodically backing up the Transaction log for your ePO - On-prem database.
If a disaster recovery is needed, the data and events database must be restored to avoid historical data loss.
Warning
The size of the Transaction log continues to grow if you don't perform periodic backups of the Transaction log when the ePO Events database is in Full Recovery mode. The log grows until it consumes all available disk space, so it is important to perform regular Transaction log backups. Full and differential SQL backups do not truncate the Transaction log.
Simple recovery model
Set the Simple Recovery mode, if the regular Transaction log backup is not required.
Simple recovery model performs a full backup of ePO database excluding Transaction logs.
If there is a disaster, you can recover only to the last full backup. All changes that occurred after the last full backup are lost.
The Simple Recovery Model is an acceptable solution for most enterprise customers because the data lost in a disaster is usually event data since the last full backup.