Skip to content

Commit e3f42fe

Browse files
committed
new consideration for ANF backup
1 parent 379aace commit e3f42fe

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-netapp-files/backup-requirements-considerations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: conceptual
15-
ms.date: 05/23/2022
15+
ms.date: 08/15/2022
1616
ms.author: anfdocs
1717
---
1818
# Requirements and considerations for Azure NetApp Files backup
@@ -28,6 +28,8 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
2828

2929
* There can be a delay of up to 5 minutes in displaying a backup after the backup is actually completed.
3030

31+
* For large volumes (greater than 10 TB), it can take multiple hours to transfer all the data from the backup media.
32+
3133
* Currently, the Azure NetApp Files backup feature supports backing up the daily, weekly, and monthly local snapshots created by the associated snapshot policy to the Azure storage. Hourly backups are not currently supported.
3234

3335
* Azure NetApp Files backup uses the [Zone-Redundant storage](../storage/common/storage-redundancy.md#redundancy-in-the-primary-region) (ZRS) account that replicates the data synchronously across three Azure availability zones in the region, except for the regions listed below where only [Locally Redundant Storage](../storage/common/storage-redundancy.md#redundancy-in-the-primary-region) (LRS) storage is supported:

0 commit comments

Comments
 (0)