Skip to content

Commit af55e40

Browse files
Merge pull request #309351 from adityabalaji-msft/adityatest
fixing callout on Retention Period for Old Recovery Points
2 parents 36c7cde + c7b16f9 commit af55e40

2 files changed

Lines changed: 4 additions & 1 deletion

File tree

articles/backup/backup-azure-monitor-alerts-notification.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ To configure notifications for Azure Monitor alerts, create an [alert processing
2222

2323
1. Send alerts to the notification channel of your choice using action groups as part of the alert processing rules. Learn [how to create action groups](/azure/azure-monitor/alerts/action-groups#create-an-action-group-in-the-azure-portal).
2424

25+
>[!Note]
26+
>To send notifications for an alert to multiple email addresses, you can select multiple **email** notifications during the action group configuration.
27+
2528
## Suppress notifications during a planned maintenance window
2629

2730
For certain scenarios, you might want to suppress notifications for a particular window of time when backups are going to fail. This is especially important for database backups, where log backups could happen as frequently as every 15 minutes, and you don't want to receive a separate notification every 15 minutes for each failure occurrence. In such a scenario, you can create a second alert processing rule that exists alongside the main alert processing rule used for sending notifications. The second alert processing rule won't be linked to an action group, but is used to specify the time for notification types that should be suppressed.

articles/resiliency/tutorial-reconfigure-backup-alternate-vault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ After the configuration is complete, the new recovery points in the new vault ap
115115

116116
The implications of reconfiguring backup for data sources in an alternate vault incurs the following charges:
117117

118-
- Old recovery points in the previous vault incur storage cost until they're purged as per the retention policy.
118+
- The Azure Backup service forever retains the recovery points that are backed up in the old vault. This recovery point retention in the vault is chargeable. See [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup) for details.
119119
- New recovery points in the new vault also incur storage cost.
120120

121121
## Related content

0 commit comments

Comments
 (0)