CRR Region and Backup Alerts

Author: David Curwin

articles/backup/backup-azure-monitoring-built-in-monitor.md

@@ -22,17 +22,17 @@ Jobs from the following Azure Backup solutions are shown here:
 
 - Azure VM backup
 - Azure File backup
-- Azure workload backup such as SQL
+- Azure workload backup such as SQL and SAP HANA
 - Azure Backup agent (MAB)
 
 Jobs from System Center Data Protection Manager (SC-DPM), Microsoft Azure Backup Server (MABS) are NOT displayed.
 
 > [!NOTE]
-> Azure workloads such as SQL backups within Azure VMs have huge number of backup jobs. For example, log backups can run for every 15 minutes. Hence, for such DB workloads, only user triggered operations are displayed. Scheduled backup operations are NOT displayed.
+> Azure workloads such as SQL and SAP HANA backups within Azure VMs have huge number of backup jobs. For example, log backups can run for every 15 minutes. Hence, for such DB workloads, only user triggered operations are displayed. Scheduled backup operations are NOT displayed.
 
 ## Backup Alerts in Recovery Services vault
 
-Alerts are primarily scenarios where users are notified so that they can take relevant action. The **Backup Alerts** section shows alerts generated by Azure Backup service. These alerts are defined by the service and user cannot custom create any alerts.
+Alerts are primarily scenarios where users are notified so that they can take relevant action. The **Backup Alerts** section shows alerts generated by Azure Backup service. These alerts are defined by the service and user can't custom create any alerts.
 
 ### Alert scenarios
 
@@ -42,26 +42,31 @@ The following scenarios are defined by service as alertable scenarios.
 - Backup succeeded with warnings for Azure Backup Agent (MAB)
 - Stop protection with retain data/Stop protection with delete data
 
-### Exceptions when an alert is not raised
-
-There are few exceptions when an alert is not raised on a failure, they are:
-
-- User explicitly canceled the running job
-- The job fails because another backup job is in progress (nothing to act on here since we just have to wait for the previous job to finish)
-- The VM backup job fails because the backed-up Azure VM no longer exists
-
-The above exceptions are designed from the understanding that the result of these operations (primarily user triggered) shows up immediately on portal/PS/CLI clients. Hence, the user is immediately aware and doesn't need a notification.
-
 ### Alerts from the following Azure Backup solutions are shown here
 
 - Azure VM backups
 - Azure File backups
-- Azure workload backups such as SQL
+- Azure workload backups such as SQL, SAP HANA
 - Azure Backup agent (MAB)
 
 > [!NOTE]
 > Alerts from System Center Data Protection Manager (SC-DPM), Microsoft Azure Backup Server (MABS) are NOT displayed here.
 
+### Consolidated Alerts
+
+For Azure workload backup solutions such as SQL and SAP HANA, log backups can be generated very frequently (up to every 15 minutes according to the policy). So it's also possible that the log backup failures are also very frequent (up to every 15 minutes). In this scenario, the end user will be overwhelmed if an alert is raised for each failure occurrence. So an alert is sent for the first occurrence and if the subsequent failures are because of the same root cause, then further alerts are not generated. The first alert is updated with the failure count. But if the alert is inactivated by the user, the next occurrence will trigger another alert and this will be treated as the first alert for that occurrence. This is how Azure Backup performs alert consolidation for SQL and SAP HANA backups.
+
+### Exceptions when an alert is not raised
+
+There are few exceptions when an alert isn't raised on a failure. They are:
+
+- User explicitly canceled the running job
+- The job fails because another backup job is in progress (nothing to act on here since we just have to wait for the previous job to finish)
+- The VM backup job fails because the backed-up Azure VM no longer exists
+- [Consolidated Alerts](#consolidated-alerts)
+
+The above exceptions are designed from the understanding that the result of these operations (primarily user triggered) shows up immediately on portal/PS/CLI clients. So the user is immediately aware and doesn't need a notification.
+
 ### Alert types
 
 Based on alert severity, alerts can be defined in three types:
@@ -79,9 +84,6 @@ Once an alert is raised, users are notified. Azure Backup provides an inbuilt no
 
 ![RS Vault inbuilt email notification](media/backup-azure-monitoring-laworkspace/rs-vault-inbuiltnotification.png)
 
-> [!NOTE]
-> The alerts for SQL backups will be consolidated and the email is sent only for the first occurrence. But if the alert is inactivated by the user, the next occurrence will trigger another email.
-
 When notification is configured, you will receive a welcome or introductory email. This confirms that Azure Backup can send emails to these addresses when an alert is raised.<br>
 
 If the frequency was set to an hourly digest and an alert was raised and resolved within an hour, it will not be a part of the upcoming hourly digest.

articles/backup/backup-create-rs-vault.md

@@ -88,10 +88,14 @@ For this process, there are pricing implications as it is at the storage level.
 >    - West US 2
 >    - South Central US
 >    - East US
+>    - East US 2
+>    - North Central US
 >    - Canada Central
 >    - Canada East
 >    - Australia East
 >    - Australia Southeast
+>    - Central India
+>    - South India
 >    - Japan East
 >    - Japan West
 >    - Southeast Asia