- 6 minutes to read

Managing Monitoring of SQL Backups

Stay in control of your SQL Server database backups with the Nodinite Database Monitoring Agent. Protect against data loss, ensure disaster recovery readiness, and maintain compliance with backup policies.

SQL Backups in a Monitor View, one database waiting for its first backup and one with an outdated backup in Error, then Edit thresholds with the last backup and the timespans, animated walkthrough (7.12)
Animated walkthrough: in the SQL Backups Category, 'ContosoOrdersArchive' is OK while it waits for its first backup, and 'BizTalkMgmtDb' is Error with an outdated backup. Edit thresholds shows the Last backup and the Warning and Error timespans.

Why Monitor SQL Server Backups?

Database backups are your last line of defense against data loss. Outdated or missing backups expose organizations to catastrophic risks:

  • Unrecoverable data loss – Hardware failures, corruption, or ransomware attacks with no recent backup mean permanent data loss
  • Business disruption – Recovery Point Objective (RPO) violations lead to hours or days of lost transactions
  • Compliance failures – Regulatory requirements (SOX, HIPAA, GDPR) mandate regular, tested backups
  • Ransomware vulnerability – Without verified backups, organizations are forced to pay ransoms or lose data
  • Extended downtime – Incomplete or failed backups extend recovery time during incidents

Without proactive monitoring, teams discover backup failures only during disaster recovery—when it's too late.

What Does Nodinite Monitor?

The Database Monitoring Agent actively monitors backups for all databases on your configured SQL Server instances, providing:

✅ Backup age tracking – Alert when backups exceed Warning or Error age thresholds ✅ Missing backup detection – Identify databases that have never been backed up ✅ Multi-instance visibility – Monitor backup status across all SQL Server instances from one dashboard ✅ Customizable thresholds – Set global defaults and override per-database for production vs. test environments ✅ Automated alerts – Get notifications via email, SMS, Teams, or any Alarm Plugins before backups become critically outdated ✅ Remote management – Edit thresholds and investigate issues directly from Nodinite

When to Use SQL Backup Monitoring?

Use this feature when you need to:

  • Ensure disaster recovery readiness – Validate that all production databases have recent backups
  • Meet compliance requirements – Demonstrate backup policies are enforced for regulatory audits
  • Enforce backup SLAs – Alert when backups don't meet RPO commitments (e.g., 24 hours for production)
  • Empower operations teams – Enable non-DBAs to monitor backup health without SQL Server access
  • Track backup coverage – Identify databases missing from backup schedules
  • Support 24/7 operations – Automate alerts for backup failures during off-hours

How It Works

The Database Monitoring Agent actively monitors backups for all databases on your configured SQL Database Instances. Each monitored database appears in Nodinite as a unique Resource, providing real-time state evaluation. You can monitor backup status using Monitor Views and trigger external alerts through any installed Alarm Plugins.

Backup checks for SQL Databases are grouped by the Category SQL Backups.
A Monitor View filtered on the SQL Backups Category with BizTalkMgmtDb in Error and ContosoOrdersArchive OK (7.12)
Here's an example of a Monitor View filtered by the 'SQL Backups' category.

  • Your SQL Backups within the SQL databases(s) are listed in Nodinite as Resources where the name of the SQL Database becomes the Resource name.
graph LR subgraph "Configuration" c["fal:fa-code 1 SQL Database"] --> r[fal:fa-lightbulb 1 Resource] end

This diagram illustrates how each SQL Database is mapped to a monitored Resource in Nodinite for backup tracking.

What are the key features for Monitoring SQL Database Backups?

  • State Evaluation – Instantly monitors and evaluates the backup status of each SQL database
  • Remote Actions – Execute Remote Actions to resolve backup issues directly from Nodinite
  • Automated Alerts – Receive notifications for outdated, missing, or failed backups
  • Customizable Thresholds – Set global or specific backup age thresholds for warnings and errors
  • Centralized Visibility – View all backup states in a single dashboard for rapid response

What is evaluated for SQL Database Backup?

The different possible evaluated states for your SQL Backup are provided in the table below:

State Status Description Actions
🚫 Unavailable Resource not available Evaluation of the 'Last backup' is not possible either due to network or security-related problems Review prerequisites
❌ Error Error state raised The database backup is over (older) than the error threshold value: Outdated backup error: The last full database backup was taken at …
A backup has never been taken and the database is older than the Error timespan: A backup has never been taken. The database was created at '…'		 Edit
⚠️ Warning Warning state raised The database backup is over (older) than the warning threshold value Edit
✅ OK Online The last backup taken is below threshold values
A database that has never been backed up and is younger than the thresholds: Waiting for the first backup for the database created at '…' (UTC)		 Edit

Tip

The System Administrator can override the Monitoring state using the Expected State feature on the Resource within Nodinite.

How do I configure the thresholds for SQL Backups?

Monitoring of SQL Backups is enabled when the checkbox Enable feature Monitoring of SQL backups is checked from within the Remote Configuration dialogue for the Database Monitoring Agent. When checked,
all databases for the SQL instance provided by the ConnectionString are monitored.

There are two different ways to configure thresholds for the category SQL Backup:

Global configuration

In the Remote Configuration, open the SQL Servers tab, expand the SQL Server Instance accordion, and click its Backups tab. The Global sub-tab holds the thresholds for all databases of the instance; the Specific sub-tab holds one entry per database with its own thresholds.
The Backups tab of SQL Server Instance localhost in the Remote Configuration with the global Warning and Error Time Span and the list of specific database backups (7.12)
Here's an example of the Backups tab with global monitoring thresholds for backup related checks.

The expanded specific entry Backup: BizTalkMgmtDb with Database name, Warning Time Span, Error Time Span, and Description (7.12)
A specific entry for one database.

You can then edit the available properties.

  • Enable Monitoring of SQL Backups – When checked, Monitor for SQL Server backups is enabled, otherwise it is not
  • ⚠️ Warning Time Span – The longest allowed timespan for warning on last backup
  • ❌ Error Time Span – The longest allowed timespan for error on last backup
  • Description – user-friendly description for resource

Info

Timespan format is (days.hours.minutes.seconds)

Actions

The Database Monitoring Agent category SQL Backups has one Remote Action in the Control Center part of the Action menu; there is no Details action for a backup Resource:

  • Edit thresholds Action menu of a SQL Backups Resource with only Edit thresholds under Control Center (7.12)
    Here's an example of Remote Actions.

Edit thresholds

The following dialogue is on display after clicking the action button menu item Edit thresholds.
Edit thresholds dialog for BizTalkMgmtDb with Last backup, Description, and the Warning and Error timespan thresholds (7.12)
Here's an example of dialogue changing global thresholds to specific thresholds.

The Default values are set using Remote Configuration. Review the Global configuration section of this document for further details.

Note

Saving specific thresholds keeps the Category SQL Backups; the database gets its own entry on the Specific sub-tab of the Backups tab.

The dialog shows the Server, Database, Application, and the time of the Last backup.

The same properties as described in the Global configuration are available and in addition the following can be managed:

  • Description – Short description for this specific backup check

Save

You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.
Save, Save and close, and Close buttons of the Remote Configuration dialog (7.12)
Here's an example of the Save options.

Note

Depending on the synchronization interval set for the agent, there might be a delay before the Web Client reflects upon the change. You can force the agent to synchronize the Configuration for all Nodinite Monitoring Agents.

Save and close, save, and close the dialogue.

Close, closes the dialogue without saving any changes.

Next Steps

Add or manage Monitor View

Secure Custom Database Scripts and Actions
Database Monitoring Agent
Monitoring Agents
Monitor Views
Resources
SQL Categories