Skip to content

Commit 74bbe41

Browse files
committed
ANF-35819
1 parent db2841a commit 74bbe41

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

articles/azure-netapp-files/dynamic-change-volume-service-level.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ The capacity pool that you want to move the volume to must already exist. The ca
2020

2121
* This functionality is supported within the same NetApp account. You can't move the volume to a capacity pool in a different NetApp Account.
2222

23-
* After the volume is moved to another capacity pool, you'll no longer have access to the previous volume activity logs and volume metrics. The volume will start with new activity logs and metrics under the new capacity pool.
23+
* After the volume is moved to another capacity pool, you'll no longer have access to the previous volume activity logs and volume metrics. The volume starts with new activity logs and metrics under the new capacity pool.
2424

25-
* If you move a volume to a capacity pool of a higher service level (for example, moving from *Standard* to *Premium* or *Ultra* service level), you must wait at least seven days before you can move that volume *again* to a capacity pool of a lower service level (for example, moving from *Ultra* to *Premium* or *Standard*). You can always change to higher service level without wait time.
25+
* If you move a volume to a capacity pool of a higher service level (for example, moving from *Standard* to *Premium* or *Ultra* service level), you must wait at least 24 hours before you can move that volume *again* to a capacity pool of a lower service level (for example, moving from *Ultra* to *Premium* or *Standard*). You can always change to higher service level without wait time.
2626

2727
* If the target capacity pool is of the *manual* QoS type, the volume's throughput isn't changed with the volume move. You can [modify the allotted throughput](manage-manual-qos-capacity-pool.md#modify-the-allotted-throughput-of-a-manual-qos-volume) subsequently in the target manual capacity pool.
2828

articles/azure-netapp-files/whats-new.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,10 @@ ms.author: anfdocs
1414

1515
Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
1616

17+
* [Dynamic service level change enhancement:](dynamic-change-volume-service-level.md) shortened wait time for changing to lower service levels
18+
19+
To address rapidly changing performance requirements, Azure NetApp Files allows [dynamic service level changes of volume](dynamic-change-volume-service-level.md)s. The wait time for moving Azure NetApp Files volumes to a lower service level (after first moving service levels upwards) is now 24 hours--an improvement from the original seven days--enabling you to more actively benefit from this cost optimization capability.
20+
1721
## April 2024
1822

1923
* [Application volume group for Oracle](application-volume-group-oracle-introduction.md) (Preview)

0 commit comments

Comments
 (0)