Outdated Backup


Applies To: SQL Server 2016

This rule checks that a database has recent backups. Scheduling regular backups is important for protecting your databases against data loss from many different failures. The appropriate frequency for backing up data depends on the recovery model of the database, on business requirements about potential data loss, and on how frequently the database is updated. In a frequently updated database, the work-loss exposure increases fairly quickly between backups.

We recommend that you perform backups frequently enough to protect databases against data loss.

The simple recovery model and full recovery model both require data backups. For either recovery model, you can supplement your full backups with differential backups to efficiently reduce the risk of data loss.

For a database that uses the full recovery model, we recommend that you take frequent log backups. For a production database that contains very important data, log backups would typically be taken every one to fifteen minutes.

System_CAPS_ICON_note.jpg Note

The recommended method for scheduling backups is a database maintenance plan.

Back Up and Restore of System Databases (SQL Server)

Recovery Models (SQL Server)

Create a Differential Database Backup (SQL Server)

Create a Full Database Backup (SQL Server)

Maintenance Plans

Transaction Log Backups (SQL Server)

Monitor and Enforce Best Practices by Using Policy-Based Management

Community Additions