Skip to content

Commit 5ea7bfc

Browse files
committed
acrolinx
1 parent ad1f9b9 commit 5ea7bfc

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.author: anfdocs
1717
---
1818
# Dynamically change the service level of a volume
1919

20-
You can change the service level of an existing volume by moving the volume to another capacity pool in the same NetApp account that uses the [service level](azure-netapp-files-service-levels.md) you want for the volume. This in-place service-level change for the volume does not require that you migrate data. It also does not impact access to the volume.
20+
You can change the service level of an existing volume by moving the volume to another capacity pool in the same NetApp account that uses the [service level](azure-netapp-files-service-levels.md) you want for the volume. This in-place service-level change for the volume does not require that you migrate data. It also does not affect access to the volume.
2121

2222
This functionality enables you to meet your workload needs on demand. You can change an existing volume to use a higher service level for better performance, or to use a lower service level for cost optimization. For example, if the volume is currently in a capacity pool that uses the *Standard* service level and you want the volume to use the *Premium* service level, you can move the volume dynamically to a capacity pool that uses the *Premium* service level.
2323

@@ -27,7 +27,7 @@ The capacity pool that you want to move the volume to must already exist. The ca
2727

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

30-
* After the volume is moved to another capacity pool, you will 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.
30+
* 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.
3131

3232
* 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.
3333

@@ -43,7 +43,7 @@ The capacity pool that you want to move the volume to must already exist. The ca
4343

4444
![Change pool](../media/azure-netapp-files/change-pool.png)
4545

46-
3. Click **OK**.
46+
3. Select **OK**.
4747

4848

4949
## Next steps

0 commit comments

Comments
 (0)