Page History
...
The Days since last backup alert applies to any database at the instance level. This
Note |
---|
The Days since last backup alert is enabled by default. |
To configure thresholds and employ alert filters such as excluding specific databases, follow these steps:
To configure an instance-level alert:
- Right-click a SQL Server SQL Server instance in the Servers tree.
- Select Configure Alerts.
- Select the Days since last backup metric in the Alert Configuration window.
- Click Edit to modify default threshold (number of days).
- Check the boxes next to Informational, Warning, and Critical to include alerts for these states.
- Change the alert thresholds by moving the arrows to the appropriate levels or by double-clicking the value and typing a new threshold level.
- Click Advanced to apply advanced settings such as alert suppression or alert filters (excluding a database from alerts or/and Availability Group Collection).
- Click OK to accept your changes.
Info |
---|
The configuration of the "Days since last backup" alert now has the option to include or exclude Read-Only databases. |
Anchorperdb perdb
Days since last backup per-database
perdb | |
perdb |
...
To configure a per-database alert:
- Right-click a SQL Server SQL Server instance in the Servers tree.
- Select Configure Alerts.
- Select the Days since last backup metric in the Alert Configuration window.
- If the metric features a per-database , on the Configuration tab of the Alert Configuration window, click Add. Use the drop-down list to select the database to which you want to apply these settings.
- Check the boxes next to Informational, Warning, and Critical to include alerts for these states.
- Change the alert thresholds by moving the arrows to the appropriate levels or by double-clicking the value and typing a new threshold level.
- Click Advanced to apply alert suppression.
- Click OK to accept your changes.
Anchoragmetric agmetric
Days since last backup for availability groups
agmetric | |
agmetric |
The Advanced Alert Configuration for this metric includes the following options for Availability Group Collection Options: Anchor agmetrictwo agmetrictwo
- Primary
- Secondary
- Default
- Both
And under the Replica Collections Options
- Monitored Only
- All
Here are some escenarios to understand this metric relates scenarios applied to Availability Groups:
- When primary and (any or all) other secondary servers are being monitored: Primary server
...
- displays the last backup date alert by checking all other secondary servers for the latest backup date of that database. If the latest backup date across that
...
- Availability Groups justifies the alert, it
...
- displays. The secondary monitored databases
...
- also
...
- display the same alert, as the latest backup date for
...
- an Availability Group across all replicas will be the same.
- When only primary replica of a database is being monitored:
...
- In this scenario the alert displays after SQLDM checks the latest backup date across all replicas and if that date justifies
...
- the displayed alert.
- When some secondary replica is being monitored but no primary replica:
...
- In this scenario the alert displays after SQLDM checks the latest backup date across all replicas and if that date justifies
...
- the displayed alert.
Note | ||
---|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Scroll pdf ignore | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
Newtabfooter | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IDERA Website | Products | Purchase | Support | Community | About Us | Resources | Legal