--- title: "Set recovery model in SQL server" slug: "set-recovery-model-in-sql-server" tags: ["Install and Get Started", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T08:10:37Z published: 2026-09-07T08:10:37Z canonical: "docs.trellix.com/set-recovery-model-in-sql-server" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Set recovery model in SQL server 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__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] > 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.