Skip to content

Commit 256f73a

Browse files
author
AbhishekMallick01
committed
Addressed EEE doc ask #30547304
1 parent aea0cea commit 256f73a

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/backup/backup-instant-restore-capability.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Instant Restore Capability
33
description: Azure Instant Restore Capability and FAQs for VM backup stack, Resource Manager deployment model
44
ms.topic: overview
5-
ms.date: 05/19/2025
5+
ms.date: 06/16/2025
66
author: jyothisuri
77
ms.author: jsuri
88
---
@@ -141,4 +141,8 @@ Yes it's safe, and there's absolutely no impact in data transfer speed.
141141

142142
### Why does a 12-month backup retention policy retain data for 372 days instead of 365?
143143

144-
The retention period for monthly backups is calculated considering **31 days** for each month. When you multiply 31 days by 12 months, the total retention duration becomes **372 days**. This approach ensures consistent retention across all months, regardless of their actual number of days.
144+
The retention period for monthly backups is calculated considering **31 days** for each month. When you multiply 31 days by 12 months, the total retention duration becomes **372 days**. This approach ensures consistent retention across all months, regardless of their actual number of days.
145+
146+
### Is there a charge for retaining additional Restore Points beyond expiry for the garbage collection cycle?
147+
148+
Yes, this incurs extra charges, as pricing depends on policy duration and unpruned recovery points, which should be considered when estimating backup costs.

0 commit comments

Comments
 (0)