Skip to content

Commit b5ffebc

Browse files
Disk backup overview updates
1 parent 9982fd4 commit b5ffebc

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/backup/disk-backup-overview.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Overview of Azure Disk Backup
33
description: Learn about the Azure Disk backup solution.
44
ms.topic: conceptual
5-
ms.date: 07/21/2023
5+
ms.date: 08/17/2023
66
ms.service: backup
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
@@ -84,6 +84,15 @@ The snapshots created by Azure Backup are stored in the resource group within yo
8484

8585
The number of recovery points is determined by the Backup policy used to configure backups of the disk backup instances. Older block blobs are deleted according to the garbage collection process as the corresponding older recovery points are pruned.
8686

87+
## Why do I see more snapshots than my retention policy?
88+
89+
If a retention policy is set as *1*, you can find two snapshots. This configuration ensures that at least one latest recovery point is always present in the vault, if all subsequent backups fail due to any issue. This causes the presence of two snapshots.
90+
91+
So, if the policy is for *n* snapshots, you can find *n+1* snapshots at times. Further, you can even find *n+1+2* snapshots if there is a delay in deletion of recovery points whose retention period is over (garbage collection). This can happen at rare times when:
92+
93+
- You clean up snapshots, which are past retentions.
94+
- The garbage collector (GC) in the backend is under heavy load.
95+
8796
## Next steps
8897

8998
[Azure Disk Backup support matrix](disk-backup-support-matrix.md)

0 commit comments

Comments
 (0)