Skip to content

Commit 66bdf5e

Browse files
committed
updated content
1 parent 788cc89 commit 66bdf5e

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/backup/backup-azure-manage-vms.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,8 +163,7 @@ There are two ways to delete a VM's backup data:
163163

164164
- If Azure VM configured for Azure backup is either deleted or moved without stopping protection, then both scheduled backup job and on demand (ad-hoc) backup jobs will fail with the error UserErrorVmNotFoundV2. The backup pre-check will appear as critical only for failed ad-hoc backup jobs (failed scheduled jobs are not displayed).
165165
- These backup items remain active in the system adhering to the backup and retention policy set by the user. The backed-up data for these Azure VM will be retained as per the retention policy. The expired recovery points (except the last recovery point) are cleaned as per the retention range set in the backup policy.
166-
- User are recommended to delete the backup items where the primary data source no longer exists to avoid any additional cost, if the backup item/data for the delete resources is no longer required.
167-
- The last recovery point is retained forever and the user is charged as per the backup pricing applicable.
166+
- User are recommended to delete the backup items where the primary data source no longer exists to avoid any additional cost, if the backup item/data for the delete resources is no longer required as the last recovery point is retained forever and the user is charged as per the backup pricing applicable.
168167

169168

170169
## Next steps

0 commit comments

Comments
 (0)