Products documentation

• When a disaster strikes SQL Server databases, a efficient working backup is essential in order to recover from most disasters
• Backup will also help to protect against database upgrades that go bad, table corruption, and other system problems.
• Monitoring database backup execution results becomes then crucial in order to guarantee Database Administrators that a full database recovery is possible, database damages etc..

Monitor features include :

• Monitoring of every SQL Server database backup tpe (Full, Differential, Transaction log …)
• It is able to alert if time elapsed from last backup (of any type) has reached a given threshold expressed in number of days, hours, or minutes
• It is capable to retrieve duration time of a given backup and to alert in case a threshold is reached
• It will also send an alert in case a backup size overreached a threshold set by the user
• The monitor can be configurated so to trigger an alert if the database has been damaged

Surveillance table:

• This is a table of rules that you can use to configure and customize the configuration.
• Each line of the table will define a rule of monitoring. You can combine multiple rules to cover different cases.
• Within a rule, you can configure the last database backup type you want to monitor, the elapsed time from last backup that you can express in days, hours or minutes, the duration time in seconds of last backup
• You can also seta severity level alert if the database is detected as damaged

Backup type
Select the specific backup type you want to monitor or select “All” to monitor any kind of backup that has been made of the database

Elapsed time from last backup:
Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:1 W2M:2 M2C:3 (Green To Warning, Warning To Major, etc…), expressed in days, hours or minutes An alarm of the corresponding severity will be sent if time eapsed from last backup is over threshold. Set 0 in the field if unused

Duration time in seconds:
Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:60 W2M:120 M2C:180 (Green To Warning, Warning To Major, etc…), expressed in seconds An alarm of the corresponding severity will be sent if backup time duration is over threshold. Set 0 in the field if unused

Backup size in MB:
Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:512 W2M:1024 M2C:2048 (Green To Warning, Warning To Major, etc…), expressed in MB An alarm of the corresponding severity will be sent if backup size is over threshold. Notice that values retrieved will be rounded Set 0 in the field if unused

Damaged DB:
Set a alert severity level if the database has been detected as damaged and you want to be notified. Set it to “DISABLED” to deactivate the alert

Effect : For this rule, only Full database backup type will be monitored (Backup Type set to : “Full”).

A WARNING alarm is sent if elapsed time time from last Full database backup is 1 day (see Unit field) or more, a MAJOR alarm if 3 days (see Unit field) or more.

A WARNING alarm is sent if backup duration time was 60 seconds or more, a MAJOR alarm if 180 seconds or more. A WARNING alarm is sent if backup size is 1024 MB or more, a MAJOR alarm if 4096 MB or more.

A CRITICAL alarm will be sent if the database has been detected as damaged.