Merge pull request #207746 from b-ahibbard/anf-lagtime-20842

Add lag time statement. New consideration for dynamic vol change

Author: PRMerger12

articles/azure-netapp-files/azure-netapp-files-metrics.md

@@ -12,14 +12,14 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 09/29/2021
+ms.date: 08/11/2022
 ms.author: anfdocs
 ---
 # Metrics for Azure NetApp Files
 
 Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume IOPS, and latency. By analyzing these metrics, you can gain a better understanding on the usage pattern and volume performance of your NetApp accounts.  
 
-You can find metrics for a capacity pool or volume by selecting the **capacity pool** or **volume**.  Then click **Metric** to view the available metrics: 
+You can find metrics for a capacity pool or volume by selecting the **capacity pool** or **volume**. Then select **Metric** to view the available metrics: 
 
 [ ![Snapshot that shows how to navigate to the Metric pull-down.](../media/azure-netapp-files/metrics-navigate-volume.png) ](../media/azure-netapp-files/metrics-navigate-volume.png#lightbox)
 
@@ -78,6 +78,12 @@ You can find metrics for a capacity pool or volume by selecting the **capacity p
 - *Is volume replication transferring*    
     Whether the status of the volume replication is ‘transferring’. 
 
+- *Volume replication lag time* <br>
+    Lag time is the actual amount of time the replication lags behind the source. It indicates the age of the replicated data in the destination volume relative to the source volume.
+
+> [!NOTE]
+> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume will not catch up to the source. To resolve this issue, adjust the replication speed or the replication schedule. 
+
 - *Volume replication last transfer duration*   
     The amount of time in seconds it took for the last transfer to complete. 
 
@@ -111,7 +117,7 @@ You can find metrics for a capacity pool or volume by selecting the **capacity p
     Write throughput in bytes per second.
 
 * *Other throughput*   
-    Other throughput (that is not read or write) in bytes per second.
+    Other throughput (that isn't read or write) in bytes per second.
 
 ## Volume backup metrics  
 
@@ -122,7 +128,7 @@ You can find metrics for a capacity pool or volume by selecting the **capacity p
     Shows whether the last volume backup or restore operation is successfully completed.  `1` is successful. `0` is unsuccessful.
 
 * *Is Volume Backup Suspended*   
-    Shows whether the backup policy is suspended for the volume.  `1` is not suspended. `0` is suspended.
+    Shows whether the backup policy is suspended for the volume.  `1` isn't suspended. `0` is suspended.
 
 * *Volume Backup Bytes*   
     The total bytes backed up for this volume.

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

@@ -12,12 +12,12 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 04/18/2022
+ms.date: 08/11/2022
 ms.author: anfdocs
 ---
 # Dynamically change the service level of a volume
 
-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.  
+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.  
 
 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.  
 
@@ -27,9 +27,11 @@ The capacity pool that you want to move the volume to must already exist. The ca
 
 * This functionality is supported within the same NetApp account. You can't move the volume to a capacity pool in a different NetApp Account.
 
-* 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.
+* 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.
 
 * 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.
+
+* You cannot change the service level for volumes in a cross-region replication relationship. 
 
 ## Move a volume to another capacity pool
 
@@ -41,7 +43,7 @@ The capacity pool that you want to move the volume to must already exist. The ca
 
     ![Change pool](../media/azure-netapp-files/change-pool.png)
 
-3.	Click **OK**.
+3.	Select **OK**.
 
 
 ## Next steps