Skip to content

Commit 8117793

Browse files
authored
Update configure-reports.md
1 parent 5e504f8 commit 8117793

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/backup/configure-reports.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Today, Azure Backup provides a reporting solution that uses [Azure Monitor logs]
1616

1717
## Supported scenarios
1818

19-
* Backup reports are supported for Azure VMs, SQL in Azure VMs, SAP HANA/ASE in Azure VMs, Microsoft Azure Recovery Services (MARS) agent, Microsoft Azure Backup Server (MABS), and System Center DPM.
19+
* Backup reports are supported for Azure VMs, SQL in Azure VMs, SAP HANA/ASE in Azure VMs, Microsoft Azure Recovery Services (MARS) agent, Microsoft Azure Backup Server (MABS), and System Center Data Protection Manager (DPM).
2020
* For DPM workloads, Backup reports are supported for DPM Version 5.1.363.0 and above and Agent Version 2.0.9127.0 and above.
2121
* For MABS workloads, Backup reports are supported for MABS Version 13.0.415.0 and above and Agent Version 2.0.9170.0 and above.
2222
* Backup reports can be viewed across all backup items, vaults, subscriptions, and regions as long as their data is being sent to a Log Analytics workspace that the user has access to. To view reports for a set of vaults, you only need to have reader access to the Log Analytics workspace to which the vaults are sending their data. You don't need to have access to the individual vaults.
@@ -27,15 +27,15 @@ Today, Azure Backup provides a reporting solution that uses [Azure Monitor logs]
2727

2828
Follow these steps to start using the reports.
2929

30-
#### 1. Create a Log Analytics workspace or use an existing one.
30+
#### 1. Create a Log Analytics workspace or use an existing one
3131

3232
Set up one or more Log Analytics workspaces to store your Backup reporting data. The location and subscription where this Log Analytics workspace can be created is independent of the location and subscription where your vaults exist.
3333

3434
To set up a Log Analytics workspace, see [Create a Log Analytics workspace in the Azure portal](https://docs.microsoft.com/azure/azure-monitor/learn/quick-create-workspace).
3535

3636
By default, the data in a Log Analytics workspace is retained for 30 days. To see data for a longer time horizon, change the retention period of the Log Analytics workspace. To change the retention period, see [Manage usage and costs with Azure Monitor logs](https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage).
3737

38-
#### 2. Configure diagnostics settings for your vaults.
38+
#### 2. Configure diagnostics settings for your vaults
3939

4040
Azure Resource Manager resources, such as Recovery Services vaults, record information about scheduled operations and user-triggered operations as diagnostics data.
4141

@@ -48,7 +48,7 @@ Azure Backup also provides a built-in Azure policy, which automates the configur
4848
> [!NOTE]
4949
> After you configure diagnostics, it might take up to 24 hours for the initial data push to complete. After data starts flowing into the Log Analytics workspace, you might not see data in the reports immediately because data for the current partial day isn't shown in the reports. For more information, see [Conventions used in Backup reports](https://docs.microsoft.com/azure/backup/configure-reports#conventions-used-in-backup-reports). We recommend that you start viewing the reports two days after you configure your vaults to send data to Log Analytics.
5050
51-
#### 3. View reports in the Azure portal.
51+
#### 3. View reports in the Azure portal
5252

5353
After you've configured your vaults to send data to Log Analytics, view your Backup reports by going to any vault's pane and selecting **Backup Reports**.
5454

@@ -122,4 +122,4 @@ The widgets in the Backup report are powered by Kusto queries, which run on the
122122
* In addition, the V1 schema of sending diagnostics data to a storage account or a Log Analytics workspace is also on a deprecation path. If you've written any custom queries or automations based on the V1 schema, you're advised to update these queries to use the currently supported V2 schema.
123123

124124
## Next steps
125-
[Learn more about monitoring and reporting with Azure Backup](https://docs.microsoft.com/azure/backup/backup-azure-monitor-alert-faq)
125+
[Learn more about monitoring and reporting with Azure Backup](https://docs.microsoft.com/azure/backup/backup-azure-monitor-alert-faq)

0 commit comments

Comments
 (0)