You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -185,7 +185,7 @@ Restoring individual files or folders inside the machine from the recovery point
185
185
186
186
## Job
187
187
188
-
A backup-related task that is created by a user or the Azure Backup service. Jobs can be either scheduled or on-demand (ad-hoc). There are different types of jobs - backup, restore, configure protection, and so on. [Learn more about jobs](backup-azure-monitoring-built-in-monitor.md#backup-jobs-in-backup-center).
188
+
A backup-related task that is created by a user or the Azure Backup service. Jobs can be either scheduled or on-demand (ad-hoc). There are different types of jobs - backup, restore, configure protection, and so on. [Learn more about jobs](backup-azure-monitoring-built-in-monitor.md#backup-jobs).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-diagnostic-events.md
+5-26Lines changed: 5 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Use diagnostics settings for Recovery Services vaults and Backup vault in Azure Backup
2
+
title: Diagnostic Events for Azure Backup users
3
3
description: This article describes how to use the old and new diagnostics events for Azure Backup.
4
4
ms,service: backup
5
5
ms.topic: how-to
6
-
ms.date: 04/30/2024
6
+
ms.date: 12/30/2024
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-abhmallick
9
9
ms.custom: engagement-fy2
10
10
---
11
11
12
-
# Use diagnostics settings for Recovery Services vaults and Backup vaults
12
+
# Diagnostic Events for Azure Backup users
13
13
14
14
This article describes how to use diagnostics settings for Recovery Services vaults and Backup vaults for Azure Backup.
15
15
@@ -136,28 +136,7 @@ You might choose to have separate diagnostics settings for *Azure Backup Report*
136
136
> [!NOTE]
137
137
> The toggle for **Azure diagnostics** or **Resource specific** appears only if the user selects **Send to Log Analytics**. To send data to a storage account or an event hub, a user selects the required destination and selects the check boxes for any of the desired events, without any additional inputs. Again, we recommend that you don't choose the legacy event Azure Backup Reporting Data going forward.
138
138
139
-
140
-
141
-
## Send Azure Site Recovery events to Log Analytics
142
-
143
-
Azure Backup and Azure Site Recovery events are sent from the same Recovery Services vault. Azure Site Recovery offers two resource-specific tables - *Azure Site Recovery Jobs* and *Azure Site Recovery Replicated Items Details*. Users must choose resource specific for the two tables mentioned. Choosing the resource-specific mode for Azure Site Recovery events for any other table for site recovery prevents the required data from being sent to the Log Analytics workspace. Azure Site Recovery Jobs is available as both resource specific and legacy table.
> When you create a Log Analytics workspace, it does not matter if the Recovery Services vault is located in a different region.
149
-
150
-
151
-
To summarize:
152
-
153
-
* If you already have Log Analytics diagnostics set up with Azure Diagnostics and have written custom queries on top of it, keep that setting *intact* until you migrate your queries to use data from the new events.
154
-
* If you also want to onboard onto new tables, as we recommend, create a **new** diagnostics setting, select **Resource specific**, and select the six new events.
155
-
* If you're currently sending Azure Site Recovery events to Log Analytics, *do not* choose the resource-specific mode for these events. Otherwise, data for these events won't flow into your Log Analytics workspace. Instead, create an additional diagnostic setting, select **Azure diagnostics**, and select the relevant Azure Site Recovery events.
156
-
157
-
The following image shows an example of a user who has three diagnostics settings for a vault. The first setting, named **Setting1**, sends data from an Azure Backup Reporting Data event to a Log Analytics workspace in Azure diagnostics mode. The second setting, named **Setting2**, sends data from the six new Azure Backup events to a Log Analytics workspace in the resource-specific mode. The third setting, named **Setting3**, sends data from the Azure Site Recovery events to a Log Analytics workspace in Azure diagnostics mode.
[Learn the Log Analytics data model for the diagnostics events](./backup-azure-reports-data-model.md)
141
+
- [Learn the Log Analytics data model for the diagnostics events](./backup-azure-reports-data-model.md).
142
+
- [Learn how to send Azure Site Recovery events to Log Analytics](../site-recovery/report-site-recovery.md#send-azure-site-recovery-events-to-log-analytics).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-diagnostics-mode-data-model.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Azure Monitor logs data model
2
+
title: Data Model for Legacy diagnostic events
3
3
description: In this article, learn about the Azure Monitor Log Analytics data model details for Azure Backup data.
4
4
ms.topic: how-to
5
-
ms.date: 06/29/2024
5
+
ms.date: 12/30/2024
6
6
ms.service: azure-backup
7
7
ms.custom: engagement-fy24
8
8
author: AbhishekMallick-MS
9
9
ms.author: v-abhmallick
10
10
---
11
11
12
-
# Log Analytics data model for Azure Backup data
12
+
# Data Model for Legacy diagnostic events
13
13
14
14
This article describes the Log Analytics data model for Azure Backup that's added to the Azure Diagnostics table (if your vaults are configured with diagnostics settings to send data to a Log Analytics workspace in Azure Diagnostics mode). You can use this data model to write queries on Log Analytics data to create custom alerts or reporting dashboards.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-files-faq.yml
+11-1Lines changed: 11 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
metadata:
3
3
title: Back up Azure Files FAQ
4
4
description: In this article, discover answers to common questions about how to protect your Azure file shares with the Azure Backup service.
5
-
ms.date: 11/28/2024
5
+
ms.date: 12/11/2024
6
6
ms.topic: faq
7
7
ms.service: azure-backup
8
8
author: AbhishekMallick-MS
@@ -277,6 +277,16 @@ sections:
277
277
- If daily retention is extended, the expiration date of the existing daily recovery points is updated according to the daily retention value configured in the new policy.
278
278
- If daily retention is reduced, the existing daily recovery points and snapshots are marked for deletion in the next cleanup run job according to the daily retention value configured in the new policy, and then deleted.
279
279
280
+
- question: |
281
+
Why the expiry time for latest recovery points doesn't appear in the Azure portal?
282
+
answer: |
283
+
Expiry Time of recovery points are updated when Garbage Collector (GC) runs, which is every 24 hours. After you update the backup policy, it can take up to 24 hours to show the updates in the Expiry Time, if there're no delays in GC jobs.
284
+
285
+
- question: |
286
+
How is the expiry date shown when both snapshot and vaulted backups are configured?
287
+
answer: |
288
+
When both snapshot and vaulted backups are configured, the expiry date initially reflects the retention period of the snapshot backup. After the snapshot backup expires, the expiry date will update to reflect the retention period of the vaulted backup.
[!INCLUDE [Classic alerts deprecation for Azure Backup.](../../includes/backup-azure-classic-alerts-deprecation.md)]
46
+
45
47
The Monitoring section shows the results of predefined **Backup Alerts** and **Backup Jobs** queries. The Monitoring tiles provide up-to-date information about:
46
48
47
49
* Critical and Warning alerts for Backup jobs (in the last 24 hours)
@@ -53,11 +55,14 @@ The Usage tiles provide:
53
55
* The number of Backup items configured for the vault.
54
56
* The Azure storage (separated by LRS and GRS) consumed by the vault.
55
57
56
-
Select the tiles (except Backup Storage) to open the associated menu. In the image above, the Backup Alerts tile shows three Critical alerts. Selecting the Critical alerts row in the Backup Alerts tile, opens the Backup Alerts filtered for Critical alerts.
58
+
Select the tiles (except Backup Storage) to open the associated menu. In the image above, the Backup Alerts tile shows three Critical alerts. Select the Critical alerts row in the Backup Alerts tile to open the Backup Alerts filtered for Critical alerts.
57
59
58
60
59
61
60
-
The Backup Alerts menu, in the image above, is filtered by: Status is Active, Severity is Critical, and time is the previous 24 hours.
62
+
You can see the details of classic alerts by selecting the **Backup Alerts** tile.
63
+
64
+
>[!Important]
65
+
>Classic alerts for Azure Backup will be deprecated on 31 March 2026. We recommend you to [migrate to Azure Monitor Alerts](backup-azure-monitoring-alerts.md#migrate-from-classic-alerts-to-built-in-azure-monitor-alerts) for a seamless experience. View **Azure Monitor alerts** on the **Alerts** blade in the Recovery Services Vault.
61
66
62
67
### Backup Pre-Check Status
63
68
@@ -85,80 +90,8 @@ The Backup Alerts report lists the alerts for the vault.
The Backup Alerts list displays the selected information for the filtered alerts. In the Backup Alerts menu, you can filter for Critical or Warning alerts.
91
-
92
-
| Alert Level | Events that generate alerts |
93
-
| ----------- | ----------- |
94
-
| Critical | You receive critical alerts when: Backup jobs fail, recovery jobs fail, and when you stop protection on a server, but retain the data.|
95
-
| Warning | You receive warning alerts when: Backup jobs complete with warnings. For example, when fewer than 100 files aren't backed up because of corruption issues, or when greater than 1,000,000 files are successfully backed up). |
96
-
| Informational | currently, no informational alerts are in use. |
97
-
98
-
### Viewing alert details
99
-
100
-
The Backup Alerts report tracks eight details about each alert. Use the **Choose columns** button to edit the details in the report.
2. Edit the Severity, Status, Start time, or End time, and select **Done** to save your changes.
148
-
149
-
## Configuring notifications for alerts
150
-
151
-
Configure notifications to generate emails when a Warning or Critical alert occurs. You can send email alerts each hour, or when a particular alert occurs.
By default, Email notifications are **On**. Select **Off** to stop the email notifications.
156
-
157
-
On the **Notify** control, choose **Per Alert** if don't want grouping or don't have many items that could generate alerts. Every alert results in one notification (the default setting), and a resolution email is sent immediately.
158
-
159
-
If you select **Hourly Digest**, an email is sent to the recipients explaining the unresolved alerts generated in the last hour. A resolution email is sent out at the end of the hour.
160
-
161
-
Choose the alert severity (Critical or Warning) used to generate email. Currently there are no Information alerts.
93
+
>[!Important]
94
+
>Backup Alerts (Classic) will be deprecated by 31st March, 2026. Migrate to Azure Monitor alerts for a seamless experience. View **Azure Monitor Alerts** on the **Alerts** tab.
162
95
163
96
## Manage Backup items
164
97
@@ -170,11 +103,11 @@ The list of Backup Items, organized by Backup Management Type, opens.
170
103
171
104
172
105
173
-
To explore a specific type of protected instance, select the item in the Backup Management Type column. For example, in the above image, there are two Azure virtual machines protected in this vault. Selecting**Azure Virtual Machine**, opens the list of protected virtual machines in this vault.
106
+
To explore a specific type of protected instance, select the item in the Backup Management Type column. For example, in the above image, there are two Azure virtual machines protected in this vault. Select**Azure Virtual Machine** to open the list of protected virtual machines in this vault.
174
107
175
108
176
109
177
-
The list of virtual machines has helpful data: the associated Resource Group, previous [Backup Pre-Check](#backup-pre-check-status), Last Backup Status, and date of the most recent Restore Point. The ellipsis, in the last column, opens the menu to trigger common tasks. The helpful data provided in columns, is different for each backup type.
110
+
The list of virtual machines has helpful data: the associated Resource Group, previous [Backup Pre-Check](#backup-pre-check-status), Last Backup Status, and date of the most recent Restore Point. The ellipsis, in the last column, opens the menu to trigger common tasks. The helpful data provided in columns is different for each backup type.
178
111
179
112
180
113
@@ -266,22 +199,8 @@ The Backup Storage tile in the dashboard shows the storage consumed in Azure. St
266
199
* Cloud LRS storage usage associated with the vault
267
200
* Cloud GRS storage usage associated with the vault
268
201
269
-
## Troubleshooting monitoring issues
270
-
271
-
**Issue:** Jobs and/or alerts from the Azure Backup agent don't appear in the portal.
272
-
273
-
**Troubleshooting steps:** The process, ```OBRecoveryServicesManagementAgent```, sends the job and alert data to the Azure Backup service. Occasionally this process can become stuck or shutdown.
274
-
275
-
1. To verify the process isn't running, open **Task Manager**, and check ```OBRecoveryServicesManagementAgent``` is running.
276
-
277
-
2. If the process isn't running, open **Control Panel**, and browse the list of services. Start or restart **Microsoft Azure Recovery Services Management Agent**.
0 commit comments