Skip to content

Commit 788cc89

Browse files
committed
updated content
1 parent 933881e commit 788cc89

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,10 @@ There are two ways to delete a VM's backup data:
161161
162162
### Backup item where primary data source no longer exists
163163

164-
If a resource configured with Azure backup is deleted or moved without stopping protection, scheduled backups continue (while failing) even though the resource no longer exists. Backup jobs are not shown for this kind of protected item after the resource ceases to exist. Failed backup jobs appear and backup pre-check shows as ‘critical’ only when an ad-hoc backup is triggered on these resources. These backup items remain active in the system adhering to the backup and retention policy set by the user. The expired recovery points are cleaned according to the set retention policy. The last recovery point is retained forever and the customer is charged according to the backup pricing applicable.
164+
- 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).
165+
- 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.
165168

166169

167170
## Next steps

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,9 +116,9 @@ Undelete followed by resume operation will protect the resource again. Resume op
116116

117117
Recovery Services vault cannot be deleted if there are backup items in soft-deleted state in the vault. The soft-deleted items are permanently deleted after 14 days of delete operation. You can delete the vault only after all the soft deleted items have been purged.
118118

119-
#### How can I delete the data earlier than the 14 days soft-delete period after deletion?
119+
#### Can I delete the data earlier than the 14 days soft-delete period after deletion?
120120

121-
There is no way to purge the data before 14 days of soft delete period. It is a security feature enabled to protect the data from malicious admins and safeguard the user from not losing the data as soon as the deletion is done. Users should wait for 14 days for the data to be purged before performing any other action on the VM. There is no overhead for this additional retention as it comes at no cost to the customer.
121+
No. You cannot force delete the soft-deleted items, they are automatically deleted after 14 days. This security feature is enabled to safeguard the backed-up data from accidental or malicious deletes. You should wait for 14 day before performing any other action on the VM. Soft-deleted items will not be charged. If you need re-protecting the VMs marked for soft-delete within 14 days to a new vault then contact Microsoft support.
122122

123123
#### Can soft delete operations be performed in PowerShell or CLI?
124124

0 commit comments

Comments
 (0)