Skip to content

Commit e1bc229

Browse files
author
AbhishekMallick01
committed
Addressed EEE doc ask #27625306
1 parent 59f37d5 commit e1bc229

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/manage-recovery-points.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage recovery points
33
description: Learn how the Azure Backup service manages recovery points for virtual machines
44
ms.topic: how-to
5-
ms.date: 09/11/2024
5+
ms.date: 01/22/2025
66
author: AbhishekMallick-MS
77
ms.author: v-abhmallick
88
---
@@ -96,7 +96,7 @@ There are two ways to stop protecting a VM:
9696

9797
## Impact of deleting a VM without stop protection
9898

99-
Deleting a VM without stop protection has impact on recovery points, and is an undesirable scenario. Ideally backups should be stopped before deleting the virtual machine. Since the resource doesn't exist, the scheduled backups will fail with the [VMNotFoundV2 error](backup-azure-vms-troubleshoot.md#320001-resourcenotfound---could-not-perform-the-operation-as-vm-no-longer-exists--400094-bcmv2vmnotfound---the-virtual-machine-doesnt-exist--an-azure-virtual-machine-wasnt-found). The recovery points will be cleaned periodically according to the retention policy, but the last copy of the virtual machine will remain forever and you'll be billed accordingly. Depending on your scenario, you have the following two options:
99+
Deleting a VM without stop protection has impact on recovery points, and is an undesirable scenario. Ideally backups should be stopped before deleting the virtual machine. Since the resource doesn't exist, no further backups will be triggered and the item will still show as Healthy. If a manual backup is triggered, this will force a check on the VM and the job will fail with the [VMNotFoundV2 error](backup-azure-vms-troubleshoot.md#320001-resourcenotfound---could-not-perform-the-operation-as-vm-no-longer-exists--400094-bcmv2vmnotfound---the-virtual-machine-doesnt-exist--an-azure-virtual-machine-wasnt-found). The recovery points will be cleaned periodically according to the retention policy, but the last copy of the virtual machine will remain forever and you'll be billed accordingly. Depending on your scenario, you have the following two options:
100100

101101
- **Option 1:** Restore the VM using any of the recovery points. If you want to recover the deleted VM, restore using the same name and in the same resource group. If you protect the restored VM to the same vault, then the existing recovery points will automatically get attached.
102102
- **Option 2:** Go to the Recovery Services vault and stop protection with delete data.

0 commit comments

Comments
 (0)