Database backup is not current

REASON

Disaster recovery is deeply embedded into the design of SQL Server, and as such, it is important to carefully understand and manage your database backup policies. SQL Server databases must be backed up using the built-in BACKUP command, either natively within SQL Server or through the use of a SQL-specific, third-party tool. If no backup is done on a particular database, it is impossible to recover in case of corruption, system failure, or accidental data deletion. Regular filesystem backups are not a substitute for database backups.

RESOLUTION

Refer to the Microsoft Technet article Backup (Transact-SQL) for an overview of backup operations in SQL Server. All databases include a configured recovery model, which dictates the type of backup and restore operations that are available. In all cases, perform a full backup of any database that has never experienced a backup. In the simple recovery model, perform regular, full backups on an ongoing basis while using the full or bulk-logged recovery model. In addition, add regular log and differential backups to the full backup schedule.

Update Health Check

The Database backup is not current health check alerts you when the indicated database does not have a current backup file. Currently, this alert is displayed when the database backup meets either one of the following conditions:

1. No differential backup in 7 days or more (Warning Alert)
2. No full backup in 7 days or more (Critical Alert)

You can select a different periods of time for each alert. After making any change, alerts are not displayed until the new thresholds met or exceed the selected value. IDERA SQL Inventory Manager does not display this alert for excluded databases. 

To configure this health check, in the Administration view, click Manage Health Checks, and then click Configure next to Database backup is not current.

Excluded Databases

To exclude databases from this alert select one or more databases from the databases list and click Exclude. To reduce the number of listed databases type either a tag name, database name, or instance name on the Filter By field or select one from the drop-down list.

Save