Skip to content

Commit 52b9632

Browse files
removing consideration
1 parent eb99497 commit 52b9632

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

articles/azure-netapp-files/snapshots-restore-new-volume.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 08/28/2025
8+
ms.date: 02/03/2026
99
ms.author: anfdocs
1010
# Customer intent: "As a cloud administrator, I want to restore a volume from a snapshot so that I can recover data to a specific point in time and maintain system integrity."
1111
---
@@ -16,8 +16,6 @@ ms.author: anfdocs
1616

1717
## Considerations
1818

19-
* Currently, you can [restore a snapshot only to a new volume](snapshots-introduction.md#restoring-cloning-an-online-snapshot-to-a-new-volume).
20-
2119
* Depending on the size of the selected volume snapshot to restore, the operation may take minutes to hours to complete.
2220

2321
* To avoid extensive restore times, only perform one "restore snapshot to new volume" operation at a time. For this reason, chained restore operations, such as restoring a snapshot to a new volume while the originating volume itself is being restored from a snapshot, should be avoided as well. Alternatively, consider using [cross-zone replication within the same zone](cross-zone-region-replication-configure.md) to create an independent volume copy.

0 commit comments

Comments
 (0)