Merge pull request #263738 from roygara/perfUpdate

Updating headers.

Author: prmerger-automator[bot]

articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md

@@ -1,7 +1,6 @@
 ---
 title: Create managed disk from snapshot (Linux) - CLI sample
 description: Azure CLI Script Sample - restore a disk from a snapshot and learn about the performance impact of restoring managed disk snapshots
-services: virtual-machines-linux
 documentationcenter: storage
 author: ramankumarlive
 manager: kavithag
@@ -11,7 +10,7 @@ ms.devlang: azurecli
 ms.topic: sample
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
-ms.date: 11/17/2023
+ms.date: 01/19/2024
 ms.author: ramankum
 ms.custom: mvc, devx-track-azurecli
 ---
@@ -79,9 +78,9 @@ diskEncryptionSetId=$(az disk-encryption-set show --name $diskEncryptionSetName
 az disk create -g $resourceGroupName -n $diskName --source $snapshotId --disk-encryption-set $diskEncryptionSetID --location eastus2euap
 ```
 
-## Check disk status
+## Performance impact - background copy process
 
-When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you will experience performance impact (4k disks experience read impact, 512e experience both read and write impact). For Ultra Disks and Premium SSD v2, you can check the status of the background copy process with the following commands:
+When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you'll experience performance impact (4k disks experience read impact, 512e experience both read and write impact). For Ultra Disks and Premium SSD v2, you can check the status of the background copy process with the following commands:
 
 > [!IMPORTANT]
 > You can't use the following sections to get the status of the background copy process for disk types other than Ultra Disk or Premium SSD v2. Other disk types will always report 100%.

articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md

@@ -11,7 +11,7 @@ ms.topic: sample
 ms.tgt_pltfrm: vm-windows
 ms.custom: devx-track-azurepowershell
 ms.workload: infrastructure
-ms.date: 11/17/2023
+ms.date: 01/19/2024
 ms.author: ramankum
 ---
 
@@ -27,9 +27,9 @@ This script creates a managed disk from a snapshot. Use it to restore a virtual
 
 [!code-powershell[main](../../../powershell_scripts/virtual-machine/create-managed-disk-from-snapshot/create-managed-disk-from-snapshot.ps1 "Create managed disk from snapshot")]
 
-## Check disk status
+## Performance impact - background copy process
 
-When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you will experience performance impact (4k disks experience read impact, 512e experience both read and write impact). For Ultra Disks and Premium SSD v2, you can check the status of the background copy process with the [Azure CLI](create-managed-disk-from-snapshot.md#check-disk-status). This isn't currently supported with the Azure PowerShell module.
+When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you'll experience performance impact (4k disks experience read impact, 512e experience both read and write impact). For Ultra Disks and Premium SSD v2, you can check the status of the background copy process with the [Azure CLI](create-managed-disk-from-snapshot.md#performance-impact---background-copy-process). This isn't currently supported with the Azure PowerShell module.
 
 > [!IMPORTANT]
 > You can't use the following sections to get the status of the background copy process for disk types other than Ultra Disk or Premium SSD v2. Other disk types will always report 100%.

includes/virtual-machines-disks-incremental-snapshots-restrictions.md

@@ -5,7 +5,7 @@
  author: roygara
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 11/17/2023
+ ms.date: 01/19/2024
  ms.author: rogarana
  ms.custom: include file
 ---
@@ -17,7 +17,7 @@
 - Up to seven incremental snapshots per disk can be created every five minutes.
 - A total of 500 incremental snapshots can be created for a single disk. The 500 quota limit is not over the lifetime of a disk, but at any given point in time. You can always delete older snapshots of a disk to make room for newer snapshots.
 - You can't get the changes between snapshots taken before and after you changed the size of the parent disk across 4-TB boundary. For example, You took an incremental snapshot `snapshot-a` when the size of a disk was 2 TB. Now you increased the size of the disk to 6 TB and then took another incremental snapshot `snapshot-b`. You can't get the changes between `snapshot-a` and `snapshot-b`. You have to download the full copy of `snapshot-b` created after the resize. Subsequently, you can get the changes between `snapshot-b` and snapshots created after `snapshot-b`.
-- When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you'll experience [performance impact](../articles/virtual-machines/premium-storage-performance.md#latency). You can use CompletionPercent property to [check the status of the background copy](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#check-disk-status) for Ultra Disks and Premium SSD v2 disks.
+- When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you'll experience [performance impact](../articles/virtual-machines/premium-storage-performance.md#latency). You can use CompletionPercent property to [check the status of the background copy](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#performance-impact---background-copy-process) for Ultra Disks and Premium SSD v2 disks.
 
 ### Incremental snapshots of Premium SSD v2 and Ultra Disks
 
@@ -28,7 +28,7 @@ Incremental snapshots of Premium SSD v2 and Ultra Disks have the following extra
 - When an incremental snapshot of either a Premium SSD v2 or an Ultra Disk is created, a background copy process for that disk is started. While a background copy is ongoing, you can have up to three total snapshots pending. The process must complete before any more snapshots of that disk can be created.
 - Incremental snapshots of a Premium SSD v2 or an Ultra disk can't be used immediately after they're created. The background copy must complete before you can create a disk from the snapshot. See [Check snapshot status](#check-snapshot-status) for details.
 - Taking increment snapshots of a Premium SSD v2 or an Ultra disk while the CompletionPercent property of the disk hasn't reached 100 isn't supported.
-- When you attach a Premium SSD v2 or Ultra disk created from snapshot to a running Virtual Machine while CompletionPercnet property hasn't reached 100, the disk suffers performance impact. Specifically, if the disk has a 4k sector size, it may experience slower read. If the disk has a 512e sector size, it may experience slower read and write. To track the progress of this background copy process, see the the check disk status section of either the Azure [PowerShell sample](../articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md#check-disk-status) or the [Azure CLI sample](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#check-disk-status).
+- When you attach a Premium SSD v2 or Ultra disk created from snapshot to a running Virtual Machine while CompletionPercent property hasn't reached 100, the disk suffers performance impact. Specifically, if the disk has a 4k sector size, it may experience slower read. If the disk has a 512e sector size, it may experience slower read and write. To track the progress of this background copy process, see the the check disk status section of either the Azure [PowerShell sample](../articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md#performance-impact---background-copy-process) or the [Azure CLI](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#performance-impact---background-copy-process).
 
 > [!NOTE]
 > Normally, when you take an incremental snapshot, and there aren't any changes, the size of that snapshot is 0 MiB. Currently, empty snapshots of disks with a 4096 logical sector size instead have a size of 6 MiB, when they'd normally be 0 MiB.