A Backup Alarm becomes active when Spotlight on SQL Server detects that the backup on the SQL Server database has never taken place or has not taken place in the designated time frame.
| Alarm | Description |
|---|---|
|
Backup - Days Since Last Full Backup |
The Full Backup Alarm is enabled by default. A high alarm is raised if a full backup on this database has never taken place or has not taken place in the last three days. |
|
Backup - Hours Since Last Differential Backup |
Differential backups are important for mission-critical databases. The Differential Backup alarm is disabled by default. When enabled, a high alarm is raised if a differential backup on this database has never taken place or has not taken place in the last 24 hours. |
|
Backup - Minutes Since Last Log Backup |
Log backups are useful in keeping transaction logs in reasonable size. The Log Backup alarm is disabled by default. When enabled, a high alarm is raised if a log backup on this database has never taken place or has not taken place in the last 120 minutes. |
Tip: By default the alarm is cleared once the time frame since the last backup has come down below the threshold. To maintain the alarmed status until the alarm is acknowledged, enable Alarm requires acknowledgement in the Configure Alarms dialog.
When this alarm is current, you should:
Tips:
You can configure different alarm severities for specific databases. See "Configure Keyed Alarms" (page 1) for more information.
There is an example to exclude certain databases from this alarm. See Configure an Alarm to Ignore Certain Values (page 1).
