Skip to content

Latest commit

 

History

History
46 lines (33 loc) · 2.65 KB

File metadata and controls

46 lines (33 loc) · 2.65 KB
title Outdated Backup | Microsoft Docs
ms.custom
ms.date 03/01/2017
ms.prod sql
ms.prod_service database-engine
ms.reviewer
ms.technology security
ms.topic conceptual
helpviewer_keywords
Best Practices [Database Engine]
ms.assetid 307a4ad0-675a-4f97-9a3c-cedd61bdfae5
author VanMSFT
ms.author vanto

Outdated Backup

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] 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.

Best Practices Recommendations

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.

Note

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

For More Information

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)

See Also

Monitor and Enforce Best Practices by Using Policy-Based Management