Skip to content

Commit 7b4df6f

Browse files
Merge pull request #78667 from ThalathBhagya/master
Added Ad hoc backup retention
2 parents 506823e + bce193a commit 7b4df6f

File tree

4 files changed

+18
-10
lines changed

4 files changed

+18
-10
lines changed

articles/backup/backup-azure-monitoring-use-azuremonitor.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: shivamg
77
keywords: Log Analytics; Azure Backup; Alerts; Diagnostic Settings; Action groups
88
ms.service: backup
99
ms.topic: conceptual
10-
ms.date: 02/26/2019
10+
ms.date: 06/04/2019
1111
ms.author: pullabhk
1212
ms.assetid: 01169af5-7eb0-4cb0-bbdb-c58ac71bf48b
1313
---
@@ -41,7 +41,7 @@ You can select an LA workspace from another subscription as the target. *By sele
4141
4242
### Deploying solution to Log Analytics workspace
4343

44-
Once the data is inside LA workspace, [deploy a github template](https://azure.microsoft.com/resources/templates/101-backup-oms-monitoring/) onto LA to visualize the data. Make sure you give the same resource group, workspace name, and workspace location to properly identify the workspace and then install this template on it.
44+
Once the data is inside LA workspace, [deploy a GitHub template](https://azure.microsoft.com/resources/templates/101-backup-oms-monitoring/) onto LA to visualize the data. Make sure you give the same resource group, workspace name, and workspace location to properly identify the workspace and then install this template on it.
4545

4646
### View Azure Backup data using Log Analytics (LA)
4747

@@ -237,13 +237,13 @@ Apply the filters shown in the following picture to verify whether you are recei
237237

238238
![Activity logs for Azure VM backups](media/backup-azure-monitoring-laworkspace/activitylogs-azurebackup-vmbackups.png)
239239

240-
You can click the “JSON” segment to get more details and view it by copy-pasting it onto a text editor. It should display the vault details and the item that triggered the activity log that is, the backup item.
240+
Click on the operation name it will display the operation and relevant details.
241241

242-
Then click “Add activity log alert” to generate alerts for all such logs.
242+
![New alert rule](media/backup-azure-monitoring-laworkspace/new-alert-rule.png)
243243

244-
You can click on "Add Activity log alert" shown above and it will open the alert creation screen that is similar to alert creation screen [as described above](#create-alerts-using-log-analytics).
244+
Click **New alert rule** to open the **Create rule** screen, here you can create alert using steps described in this [article](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log).
245245

246-
Here the resource is the RS vault itself and hence you need to repeat the same action for all the vaults in which you want notification via activity logs. The condition will not have any threshold, period, frequency since this is an event-based alert. As soon as the relevant activity log is generated, the alert is fired.
246+
Here the resource is the Recovery Service vault itself and hence you need to repeat the same action for all the vaults in which you want notification via activity logs. The condition will not have any threshold, period, frequency since this is an event-based alert. As soon as the relevant activity log is generated, the alert is fired.
247247

248248
## Recommendation
249249

articles/backup/backup-configure-vault.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: rayne-wiselman
66
manager: carmonm
77
ms.service: backup
88
ms.topic: conceptual
9-
ms.date: 03/13/2019
9+
ms.date: 06/04/2019
1010
ms.author: raynew
1111
---
1212

@@ -66,7 +66,7 @@ If your machine has limited internet access, ensure that firewall settings on th
6666

6767
A Recovery Services vault stores all the backups and recovery points you create over time, and contains the backup policy applied to backed up machines. Create a vault as follows:
6868

69-
1. Sign in to the [Azure Portal](https://portal.azure.com/) using your Azure subscription.
69+
1. Sign in to the [Azure portal](https://portal.azure.com/) using your Azure subscription.
7070
2. In search, type **Recovery Services** and click **Recovery Services vaults**.
7171

7272
![Create Recovery Services Vault step 1](./media/backup-try-azure-backup-in-10-mins/open-rs-vault-list.png)
@@ -160,7 +160,7 @@ Download the MARS agent for installation on machines you want to back up.
160160
- Save the encryption passphrase in a secure location.
161161
- If you lose or forget the passphrase, Microsoft can't help recover the backup data. Save the file in a secure location. You need it to restore a backup.
162162

163-
7. click **Finish**. The agent is now installed and your machine is registered to the vault. You're ready to configure and schedule your backup.
163+
7. Click **Finish**. The agent is now installed and your machine is registered to the vault. You're ready to configure and schedule your backup.
164164

165165
## Create a backup policy
166166

@@ -249,6 +249,14 @@ Enable network throttling as follows:
249249

250250
After the initial backup is completed, the **Job completed** status appears in the Backup console.
251251

252+
## Ad hoc backup policy retention behavior
253+
254+
| Backup Policy for Scheduled Backup | Ad hoc Backup Retention
255+
| -- | --
256+
| Daily | **Default Retention**: Equivalent to the “retention in days for daily backups.” <br/><br/> **Exception**: If a daily scheduled backup is set for long-term retentions (Weeks, Months, Years) fails, then an ad hoc backup triggered right after this failed scheduled backup is considered for long-term retention. Otherwise, the next successful scheduled backup is considered for long-term retention.<br/><br/> **Example**: If all the (Weekly/Monthly/Yearly) retention backups are in failed state and you triggers a ad hoc backup then it will follow the Yearly retention period.
257+
| Weekly | **Default Retention** : 1 day. <br/> Ad hoc Backups taken for a data source with weekly Backup policy are deleted the very next day, even if they are the most recent Backups for the data source. <br/><br/> **Exception**: If a weekly scheduled backup is set for long-term retentions (Weeks, Months, Years) fails, then an ad hoc backup triggered right after this failed scheduled backup will be considered for long-term retention. Otherwise, the next successful scheduled backup is considered for long-term retention. <br/><br/> **Example**: If both the (Weekly/Monthly) retention backups are in failed state and you triggers a ad hoc backup then it will follow the Monthly retention period.
258+
259+
252260
## Next steps
253261

254-
[Learn how to](backup-azure-restore-windows-server.md) restore files.
262+
[Learn how to restore files](backup-azure-restore-windows-server.md).
-21.7 KB
Loading
111 KB
Loading

0 commit comments

Comments
 (0)