Documentor and SEO updates to snapshot article.

Author: roygara

articles/storage/elastic-san/elastic-san-snapshots.md

@@ -1,51 +1,51 @@
 ---
 title: Backup Azure Elastic SAN volumes 
-description: Learn about snapshots for Azure Elastic SAN, including how to create and use them.
+description: Learn about snapshots for Azure Elastic SAN, including their best uses, how to create them, and how to use them to create new volumes or export to a managed disk.
 author: roygara
 ms.service: azure-elastic-san-storage
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ms.topic: concept-article
-ms.date: 12/12/2024
+ms.date: 01/08/2026
 ms.author: rogarana
 # Customer intent: "As a cloud administrator, I want to create and manage snapshots of Azure Elastic SAN volumes, so that I can efficiently back up data and restore volumes as needed for development and testing without incurring extra costs."
 ---
 
 # Snapshot Azure Elastic SAN volumes
 
-Azure Elastic SAN volume snapshots are incremental point-in-time backups of your volumes. The first snapshot you take occupies no space, and every subsequent snapshot consists only of the changes to the Elastic SAN volume since the last snapshot. This is different from a managed disk snapshot, wherein the first snapshot you take will be a full copy of the managed disk and each subsequent snapshot will consist of only the changes to the disk since the last snapshot. Snapshots of your volumes don't have any separate billing, but they reside in your elastic SAN and consume the SAN's capacity. Snapshots can't be used to change the state of an existing volume, you can only use them to either deploy a new volume or export the data to a managed disk snapshot.
+Azure Elastic SAN volume snapshots are incremental point-in-time backups of your volumes. The first snapshot you take doesn't occupy any space, and every subsequent snapshot consists only of the changes to the Elastic SAN volume since the last snapshot. This approach is different from a managed disk snapshot. The first snapshot you take for a managed disk is a full copy of the managed disk and each subsequent snapshot consists of only the changes to the disk since the last snapshot. Snapshots of your Elastic SAN volumes don't incur any separate billing. However, they reside in your Elastic SAN and consume the SAN's capacity. You can't use snapshots to change the state of an existing volume. You can only use them to either deploy a new volume or export the data to a managed disk snapshot.
 
-You can take up to 200 snapshots per volume at a rate of seven snapshots every five minutes. Snapshots persist until either the volume itself is deleted or the snapshots are deleted. Snapshots don't persist after the volume is deleted. If you need your data to persist after deleting a volume, [export your volume's snapshot to a managed disk snapshot](#export-volume-snapshot). You can only export your volume snapshots to the same region via Elastic SAN, and the redundancy type of the snapshot (LRS vs ZRS) is dependent on the redundancy type of the SAN.
+You can take up to 200 snapshots per volume at a rate of seven snapshots every five minutes. Snapshots persist until either the volume itself is deleted or the snapshots are deleted. Snapshots don't persist after the volume is deleted. If you need your data to persist after deleting a volume, [export your volume's snapshot to a managed disk snapshot](#export-volume-snapshot). You can only export your volume snapshots to the same region via Elastic SAN. The redundancy type of the snapshot (LRS or ZRS) is determined by the redundancy type of the SAN.
 
 
 ## General guidance
 
-You should use Elastic SAN volume snapshots when you want to restore volumes quickly, like when you have dev/test workloads. Volumes created from volume snapshots are available instantly for use, while the rehydration happens in the background. Volume snapshots shouldn't be considered when hardening your backups.
+Use Elastic SAN volume snapshots when you want to restore volumes quickly, like when you have dev/test workloads. Volumes created from volume snapshots are available instantly for use, while the rehydration happens in the background. Don't consider volume snapshots when hardening your backups.
 
-You should use managed disk snapshots when you either want to create a managed disk from your Elastic SAN volume, or if you want to keep a long term backup of your Elastic SAN volumes. Managed disk snapshots are useful when you require durable checkpoints or version control for your Elastic SAN volumes, and you don't need to restore a volume backup instantly. Volumes created from managed disk snapshots are available instantly, but it takes time for the rehydration to happen in the background, and you may experience slightly degraded performance. Volumes can be created from volume snapshots or disk snapshots that were taken from a different volume group in the same SAN or even from within a different SAN as long as they are in the same region. You cannot create a volume from a managed disk snapshot in a different region. 
+Use managed disk snapshots when you either want to create a managed disk from your Elastic SAN volume or if you want to keep a long term backup of your Elastic SAN volumes. Managed disk snapshots are useful when you require durable checkpoints or version control for your Elastic SAN volumes, and you don't need to restore a volume backup instantly. Volumes created from managed disk snapshots are available instantly, but it takes time for the rehydration to happen in the background, and you might experience slightly degraded performance. You can create volumes from volume snapshots or disk snapshots that were taken from a different volume group in the same SAN or even from within a different SAN as long as they are in the same region. You can't create a volume from a managed disk snapshot in a different region.  
 
 ### Take a stable snapshot
 
-You can take a snapshot anytime, but if you’re taking snapshots while the VM is running, keep these things in mind:
+You can take a snapshot anytime. However, if you take snapshots while the VM is running, keep these things in mind:
 
-When the VM is running, data is still being streamed to the volumes. As a result, snapshots of a running VM might contain partial operations that were in flight.
-If there are several volumes attached to a VM, snapshots of different volumes might occur at different times.
-In the described scenario, snapshots weren't coordinated. This lack of coordination is a problem for striped volumes whose files might be corrupted if changes were being made during a backup. So the backup process must implement the following steps:
+When the VM is running, data is still streaming to the volumes. As a result, snapshots of a running VM might contain partial operations that are in flight.
+If several volumes are attached to a VM, snapshots of different volumes might occur at different times.
+In the described scenario, snapshots aren't coordinated. This lack of coordination is a problem for striped volumes whose files might be corrupted if changes were being made during a backup. So the backup process must implement the following steps:
 
 - Freeze all the volumes.
 - Flush all the pending writes.
 - Create an incremental snapshot for each volume.
 
-Some Windows applications, like SQL Server, provide a coordinated backup mechanism through a volume shadow service to create application-consistent backups. On Linux, you can use a tool like fsfreeze to coordinate disks (this tool provides file-consistent backups, not application-consistent snapshots).
+Some Windows applications, like SQL Server, provide a coordinated backup mechanism through a volume shadow service to create application-consistent backups. On Linux, you can use a tool like fsfreeze to coordinate disks. This tool provides file-consistent backups, not application-consistent snapshots.
 
 ## Create a volume snapshot
 
-You can create snapshots of your volumes snapshots using the Azure portal, the Azure PowerShell module, or the Azure CLI.
+You can create snapshots of your volumes using the Azure portal, the Azure PowerShell module, or the Azure CLI.
 
 # [Portal](#tab/azure-portal)
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-1. Navigate to your elastic SAN, select volume snapshots.
-1. Select create a snapshot, then fill in the fields.
+1. Navigate to your elastic SAN and select **Volume snapshots**.
+1. Select **Create a snapshot**, and then fill in the fields.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -72,13 +72,13 @@ az elastic-san volume snapshot create -g "resourceGroupName" -e "san_name" -v "v
 
 ## Create a volume from a volume snapshot
 
-You can use snapshots of elastic SAN volumes to create new volumes using the Azure portal, the Azure PowerShell module, or the Azure CLI. You can't use snapshots to change the state of existing volumes.
+You can use snapshots of elastic SAN volumes to create new volumes by using the Azure portal, the Azure PowerShell module, or the Azure CLI. You can't use snapshots to change the state of existing volumes.
 
 # [Portal](#tab/azure-portal)
 
 1. Navigate to your elastic SAN and select **Volumes**.
-1. Select **+ Create volume** and fill out the details.
-1. For **Source type** select **Volume snapshot** and fill out the details, specifying the snapshot you want to use.
+1. Select **+ Create volume** and enter the details.
+1. For **Source type**, select **Volume snapshot** and fill out the details, specifying the snapshot you want to use.
 1. Select **Create**.
 
 # [PowerShell](#tab/azure-powershell)
@@ -98,13 +98,13 @@ az elastic-san volume create -g "resourceGroupName" -e "san_name" -v "vg_name" -
 
 ## Create a volume from a managed disk snapshot
 
-You can use snapshots of managed disks to create new elastic SAN volumes using the Azure portal, the Azure PowerShell module, or the Azure CLI.
+You can use snapshots of managed disks to create new elastic SAN volumes by using the Azure portal, the Azure PowerShell module, or the Azure CLI.
 
 # [Portal](#tab/azure-portal)
 
 1. Navigate to your elastic SAN and select **Volumes**.
-1. Select **+ Create volume** and fill out the details.
-1. For **Source type** select **Disk snapshot** and fill out the details, specifying the snapshot you want to use.
+1. Select **+ Create volume** and enter the details.
+1. For **Source type**, select **Disk snapshot** and enter the details, specifying the snapshot you want to use.
 1. Select **Create**.
 
 # [PowerShell](#tab/azure-powershell)
@@ -128,20 +128,20 @@ You can use the Azure portal, Azure PowerShell module, or Azure CLI to delete in
 # [Portal](#tab/azure-portal)
 
 1. Navigate to your elastic SAN and select **Volume snapshots**.
-1. Select a volume group, then select the snapshot you'd like to delete.
-1. Select delete.
+1. Select a volume group, then select the snapshot you want to delete.
+1. Select **Delete**.
 
 # [PowerShell](#tab/azure-powershell)
 
-The following script deletes an individual snapshot. Replace the values, then run the command.
+The following script deletes an individual snapshot. Replace the values, and then run the command.
 
 ```azurepowershell
 # remove a snapshot
 Remove-AzElasticSanVolumeSnapshot -ResourceGroupName $rgname -ElasticSanName $esname -VolumeGroupName $vgname -Name $snapshotname1
 ```
 
 # [Azure CLI](#tab/azure-cli)
-The following command deletes an individual snapshot. Replace the values, then run the command.
+The following command deletes an individual snapshot. Replace the values, and then run the command.
 
 ```azurecli
 az elastic-san volume snapshot delete -g "resourceGroupName" -e "san_name" -v "vg_name" -n "snapshot_name"
@@ -150,21 +150,21 @@ az elastic-san volume snapshot delete -g "resourceGroupName" -e "san_name" -v "v
 
 ## Export volume snapshot
 
-Elastic SAN volume snapshots are automatically deleted when the volume is deleted. For your snapshot's data to persist beyond deletion, export them to managed disk snapshots. Exporting a volume snapshot to a managed disk snapshot takes time, how much time it takes depend on the size of the snapshot. You can check how much is left before completion by checking the `CompletionPercentage` property of the managed disk snapshot.
+Elastic SAN volume snapshots are automatically deleted when you delete the volume. To make your snapshot data persist beyond deletion, export the snapshots to managed disk snapshots. Exporting a volume snapshot to a managed disk snapshot takes time. How much time it takes depends on the size of the snapshot. You can check how much is left before completion by checking the `CompletionPercentage` property of the managed disk snapshot.
 
 ### Billing implications
 
-Elastic SAN snapshots don't have any extra billing associated with them, they only consume your elastic SAN's capacity. Once you export an elastic SAN snapshot to a managed disk snapshot, the managed disk snapshot begins to incur billing charges.
+Elastic SAN snapshots don't have any extra billing associated with them. They only consume your elastic SAN's capacity. Once you export an elastic SAN snapshot to a managed disk snapshot, the managed disk snapshot begins to incur billing charges.
 
 # [Portal](#tab/azure-portal)
 
 1. Navigate to your elastic SAN and select **Volume snapshots**.
-1. Select a volume group, then select the snapshot you'd like to export.
-1. Select Export and fill out the details, then select **Export**.
+1. Select a volume group, and then select the snapshot you want to export.
+1. Select **Export**, enter the details, and then select **Export**.
 
 # [PowerShell](#tab/azure-powershell)
 
-Replace the variables in the following script, then run it:
+Replace the variables in the following script, and then run it.
 
 ```azurepowershell
 $elasticSanName = <nameHere>
@@ -183,7 +183,7 @@ New-AzSnapshot -ResourceGroupName $rgName -SnapshotName $newSnapName -Snapshot $
 
 # [Azure CLI](#tab/azure-cli)
 
-Replace the variables in the following script, then run it:
+Replace the variables in the following script, and then run it.
 
 ```azurecli
 region=<yourRegion>