Skip to content

Commit 9a13cd0

Browse files
authored
Merge pull request #187689 from v-amallick/Feb-7-2022-Alert
Alert doc updates
2 parents bfc17b3 + dc44d62 commit 9a13cd0

File tree

2 files changed

+12
-3
lines changed

2 files changed

+12
-3
lines changed

articles/backup/backup-azure-arm-restore-vms.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,11 @@ Azure Backup provides several ways to restore a VM.
2323
**Replace existing** | You can restore a disk, and use it to replace a disk on the existing VM.<br/><br/> The current VM must exist. If it's been deleted, this option can't be used.<br/><br/> Azure Backup takes a snapshot of the existing VM before replacing the disk, and stores it in the staging location you specify. Existing disks connected to the VM are replaced with the selected restore point.<br/><br/> The snapshot is copied to the vault, and retained in accordance with the retention policy. <br/><br/> After the replace disk operation, the original disk is retained in the resource group. You can choose to manually delete the original disks if they aren't needed. <br/><br/>Replace existing is supported for unencrypted managed VMs, including VMs [created using custom images](https://azure.microsoft.com/resources/videos/create-a-custom-virtual-machine-image-in-azure-resource-manager-with-powershell/). It's unsupported for classic VMs, unmanaged VMs, and [generalized VMs](../virtual-machines/windows/upload-generalized-managed.md).<br/><br/> If the restore point has more or less disks than the current VM, then the number of disks in the restore point will only reflect the VM configuration.<br><br> Replace existing is also supported for VMs with linked resources, like [user-assigned managed-identity](../active-directory/managed-identities-azure-resources/overview.md) or [Key Vault](../key-vault/general/overview.md).
2424
**Cross Region (secondary region)** | Cross Region restore can be used to restore Azure VMs in the secondary region, which is an [Azure paired region](../availability-zones/cross-region-replication-azure.md).<br><br> You can restore all the Azure VMs for the selected recovery point if the backup is done in the secondary region.<br><br> During the backup, snapshots aren't replicated to the secondary region. Only the data stored in the vault is replicated. So secondary region restores are only [vault tier](about-azure-vm-restore.md#concepts) restores. The restore time for the secondary region will be almost the same as the vault tier restore time for the primary region. <br><br> This feature is available for the options below:<br> <li> [Create a VM](#create-a-vm) <br> <li> [Restore Disks](#restore-disks) <br><br> We don't currently support the [Replace existing disks](#replace-existing-disks) option.<br><br> Permissions<br> The restore operation on secondary region can be performed by Backup Admins and App admins.
2525

26-
> [!NOTE]
27-
> You can also recover specific files and folders on an Azure VM. [Learn more](backup-azure-restore-files-from-vm.md).
26+
>[!Tip]
27+
>To receive alerts/notifications when a restore operation fails, use [Azure Monitor alerts for Azure Backup](backup-azure-monitoring-built-in-monitor.md#azure-monitor-alerts-for-azure-backup-preview). This helps you to monitor such failures and take necessary actions to remediate the issues.
28+
29+
>[!NOTE]
30+
>You can also recover specific files and folders on an Azure VM. [Learn more](backup-azure-restore-files-from-vm.md).
2831
2932
## Storage accounts
3033

articles/backup/backup-azure-security-feature-cloud.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,11 @@
22
title: Soft delete for Azure Backup
33
description: Learn how to use security features in Azure Backup to make backups more secure.
44
ms.topic: conceptual
5-
ms.date: 04/30/2020
5+
ms.date: 02/07/2022
66
ms.custom: devx-track-azurepowershell
7+
author: v-amallick
8+
ms.service: backup
9+
ms.author: v-amallick
710
---
811
# Soft delete for Azure Backup
912

@@ -28,6 +31,9 @@ To disable soft delete on a vault, you must have the Backup Contributor role for
2831

2932
It's important to remember that once soft delete is disabled, the feature is disabled for all the types of workloads. For example, it's not possible to disable soft delete only for SQL server or SAP HANA DBs while keeping it enabled for virtual machines in the same vault. You can create separate vaults for granular control.
3033

34+
>[!Tip]
35+
>To receive alerts/notifications when a user in the organization disables soft-delete for a vault, use [Azure Monitor alerts for Azure Backup](backup-azure-monitoring-built-in-monitor.md#azure-monitor-alerts-for-azure-backup-preview). As the disable of soft-delete is a potential destructive operation, we recommend you to use alert system for this scenario to monitor all such operations and take actions on any unintended operations.
36+
3137
### Disabling soft delete using Azure portal
3238

3339
To disable soft delete, follow these steps:

0 commit comments

Comments
 (0)