Merge pull request #298251 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 4/15

Author: ttorble

articles/azure-vmware/ecosystem-external-storage-solutions.md

@@ -1,4 +1,4 @@
---- 
+---
 title: External storage solutions overview
 description: Learn about external storage solutions for Azure VMware Solution private cloud.
 ms.topic: how-to
@@ -7,8 +7,8 @@ ms.author: dsoderholm
 ms.service: azure-vmware
 ms.date: 12/09/2024
 ms.custom: engagement-fy23
---- 
-
+---
+ 
 # External storage solutions
 
 Azure VMware Solution is a Hyperconverged Infrastructure (HCI) service that offers VMware vSAN as the primary storage option. VMware vSAN provides high-performance NVMe storage for virtual machines. However, it has a limited capacity. The exact amount of storage available in vSAN depends on several factors, including the number and type of nodes in the cluster type; the RAID and FTT (Failures To Tolerate) settings; and the deduplication and compression performance of a particular workload. 
@@ -40,6 +40,7 @@ When you combine Azure VMware Solution with an external storage service, remembe
 |[Azure NetApp Files](./attach-azure-netapp-files-to-azure-vmware-solution-hosts.md)|NetApp bare-metal hardware with all-flash performance|Azure native|File|NFS|[What is Azure NetApp Files?](../azure-netapp-files/azure-netapp-files-introduction.md)|
 |[Azure Elastic SAN](./configure-azure-elastic-san.md)|Provides a familiar SAN resource hierarchy and industry-standard iSCSI block interface|Azure native|Block|iSCSI|[Introduction to Azure Elastic SAN](../storage/elastic-san/elastic-san-introduction.md)|
 |[Pure Cloud Block Store](./configure-pure-cloud-block-store.md)|Enterprise-grade performance and reliability using Pure Storage technology in Azure|Partner|Block|iSCSI|[Pure Cloud Block Store on Azure](https://support.purestorage.com/bundle/m_cbs_for_azure/page/Pure_Cloud_Block_Store/topics/concept/c_introduction_121.html)|
+|[Azure Native Pure Storage Cloud](./configure-azure-native-pure-storage-cloud.md)|Enterprise-grade performance and reliability using Pure Storage technology in Azure with Azure Native experience|Azure native experience|Block|iSCSI|[Pure Storage Cloud on Azure](https://support.purestorage.com/bundle/m_azure_native_pure_storage_cloud/page/Production/Pure_Cloud_Block_Store/Azure_Native_Pure_Storage_Cloud/topics/c_azure_native_pure_storage_cloud.html)|
 
 ### Azure storage solutions
 
@@ -63,4 +64,6 @@ Providing the same consistent external block storage architecture in the cloud i
 
 - Learn about [Azure NetApp Files](./attach-azure-netapp-files-to-azure-vmware-solution-hosts.md)
 - Learn about [Azure Elastic SAN](./configure-azure-elastic-san.md)
-- Learn about [Pure Cloud Block Store](./configure-pure-cloud-block-store.md)
+- Learn about [Pure Cloud Block Store](./configure-pure-cloud-block-store.md)
+- Learn about [Azure Native Pure Storage Cloud](./configure-azure-native-pure-storage-cloud.md)
+

articles/backup/backup-azure-linux-app-consistent.md

@@ -1,21 +1,21 @@
 ---
-title: Application-consistent backups of Linux VMs using Azure Backup
-description: Create application-consistent backups of your Linux virtual machines to Azure. This article explains configuring the script framework to back up Azure-deployed Linux VMs. This article also includes troubleshooting information.
+title: Configure application-consistent backup for Azure Linux VMs using Azure Backup
+description: Learn how to create application-consistent backups for Azure-deployed Linux VMs using Azure Backup.
 ms.service: azure-backup
 ms.topic: how-to
 ms.custom: linux-related-content, engagement-fy24
-ms.date: 04/23/2024
+ms.date: 04/15/2025
 author: jyothisuri
 ms.author: jsuri
 ---
 
-# Application-consistent backup of Azure Linux VMs using Azure Backup
+# Configure application-consistent backup for Azure Linux VMs using Azure Backup
 
-This article describes how to create application-consistent backups of your Linux Virtual Machines to Azure by using Azure Backup. In this article, you'll configure the script framework to back up Azure-deployed Linux VMs. This article also provides the troubleshooting information.
+This article describes how to create application-consistent backups for Azure-deployed Linux VMs using Azure Backup. It covers configuring the script framework and troubleshooting.
 
-When you take backup snapshots of VMs, application consistency means your applications start when the VMs boot after being restored. As you can imagine, application consistency is extremely important. To ensure your Linux VMs are application consistent, you can use the Linux prescript and post-script framework to take application-consistent backups. The prescript and post-script framework supports Azure Resource Manager-deployed Linux virtual machines. Scripts for application consistency don't support Service Manager-deployed virtual machines or Windows virtual machines.
+When Azure Backup takes snapshot of a VM, application consistency ensures that applications start correctly after VM restoration. To achieve this, use the Linux prescript and post-script framework, which supports Azure Resource Manager-deployed Linux VMs. However, these scripts don't work for Service Manager-deployed or Windows VMs.
 
-## How the framework works
+## How the framework works?
 
 The framework provides an option to run custom prescripts and post-scripts while you're taking VM snapshots. Prescripts run just before you take the VM snapshot, and post-scripts run immediately after you take the VM snapshot. Prescripts and post-scripts provide the flexibility to control your application and environment, while you're taking VM snapshots.
 
@@ -31,16 +31,16 @@ To configure Prescript and post-script, follow these steps:
 
 3. Copy the prescript and post-script for your application on all VMs you plan to back up. You can copy the scripts to any location on the VM. Be sure to update the full path of the script files in the **VMSnapshotScriptPluginConfig.json** file.
 
-4. Ensure the following permissions for these files:
+4. To use the following files, ensure that you have the corresponding permissions:
 
-   - **VMSnapshotScriptPluginConfig.json**: Permission “600.” For example, only “root” user should have “read” and “write” permissions to this file, and no user should have “execute” permissions.
+   - **VMSnapshotScriptPluginConfig.json**: Permission **600**. For example, only **root** user should have **read** and **write** permissions to this file, and no user should have **execute** permissions.
 
-   - **Pre-script file**: Permission “700.”  For example, only “root” user should have “read”, “write”, and “execute” permissions to this file. The file is expected to be a shell script but theoretically this script can internally spawn or refer to other scripts like a Python script.
+   - **Pre-script file**: Permission **700**.  For example, only **root** user should have **read**, **write**, and **execute** permissions to this file. The file is expected to be a shell script but theoretically this script can internally spawn or refer to other scripts like a Python script.
 
-   - **Post-script** Permission “700.” For example, only “root” user should have “read”, “write”, and “execute” permissions to this file. The file is expected to be a shell script but theoretically this script can internally spawn or refer to other scripts like a Python script.
+   - **Post-script** Permission **700**. For example, only **root** user should have **read**, **write**, and **execute** permissions to this file. The file is expected to be a shell script but theoretically this script can internally spawn or refer to other scripts like a Python script.
 
    > [!IMPORTANT]
-   > The framework gives users a lot of power. Secure the framework, and ensure only “root” user has access to critical JSON and script files.
+   > The framework gives users numerous power. Secure the framework, and ensure only **root** user has access to critical JSON and script files.
    > If the requirements aren't met, the script won't run, which results in a file system crash and inconsistent backup.
    >
 
@@ -59,7 +59,7 @@ To configure Prescript and post-script, follow these steps:
 
     - **postScriptNoOfRetries**:  Set the number of times the post-script should be retried if there's any error before terminating. Zero means only one try and no retry if there's a failure.
 
-    - **timeoutInSeconds**: Specify individual timeouts for the prescript and the post-script (maximum value can be 1800).
+    - **timeoutInSeconds**: Specify individual time-outs for the prescript and the post-script (maximum value can be 1800).
 
     - **continueBackupOnFailure**: Set this value to **true** if you want Azure Backup to fall back to a file system consistent/crash consistent backup if prescript or post-script fails. Setting this to **false** fails the backup if there's a script failure (except when you have a single-disk VM that falls back to crash-consistent backup regardless of this setting). When the **continueBackupOnFailure** value is set to false, if the backup fails the backup operation will be attempted again based on a retry logic in service (for the stipulated number of attempts).
 
@@ -69,7 +69,7 @@ To configure Prescript and post-script, follow these steps:
 
 6. The script framework is now configured. If the VM backup is already configured, the next backup invokes the scripts and triggers application-consistent backup. If the VM backup isn't configured, configure it by using [Back up Azure virtual machines to Recovery Services vaults.](./backup-azure-vms-first-look-arm.md)
 
-## Troubleshooting
+## Troubleshoot Azure Linux VM application-consistent backup errors  
 
 Make sure you add appropriate logging while writing your prescript and post-script, and review your script logs to fix any script issues. If you still have problems running scripts, refer to the following table for more information.
 
@@ -79,12 +79,12 @@ Make sure you add appropriate logging while writing your prescript and post-scri
 |Post-ScriptExecutionFailed |The post-script returned an error that might impact application state. |Look at the failure logs for your script to fix the issue and check the application state. |
 | Pre-ScriptNotFound |The prescript wasn't found at the location that's specified in the **VMSnapshotScriptPluginConfig.json** config file. |Make sure that prescript is present at the path that's specified in the config file to ensure application-consistent backup.|
 | Post-ScriptNotFound |The post-script wasn't found at the location that's specified in the **VMSnapshotScriptPluginConfig.json** config file. |Make sure that post-script is present at the path that's specified in the config file to ensure application-consistent backup.|
-| IncorrectPluginhostFile |The **Pluginhost** file, which comes with the VmSnapshotLinux extension, is corrupted, so prescript and post-script can't run and the backup won't be application-consistent.| Uninstall the **VmSnapshotLinux** extension, and it will automatically be reinstalled with the next backup to fix the problem. |
+| IncorrectPluginhostFile |The `Pluginhost` file, which comes with the VmSnapshotLinux extension, is corrupted, so prescript and post-script can't run and the backup won't be application-consistent.| Uninstall the **VmSnapshotLinux** extension, and it will automatically be reinstalled with the next backup to fix the problem. |
 | IncorrectJSONConfigFile | The **VMSnapshotScriptPluginConfig.json** file is incorrect, so prescript and post-script can't run and the backup won't be application-consistent. | Download the copy from [GitHub](https://github.com/MicrosoftAzureBackup/VMSnapshotPluginConfig) and configure it again. |
-| InsufficientPermissionforPre-Script | For running scripts, "root" user should be the owner of the file and the file should have “700” permissions (that is, only "owner" should have “read”, “write”, and “execute” permissions). | Make sure “root” user is the “owner” of the script file and that only "owner" has “read”, “write” and “execute” permissions. |
-| InsufficientPermissionforPost-Script | For running scripts, root user should be the owner of the file and the file should have “700” permissions (that is, only "owner" should have “read”, “write”, and “execute” permissions). | Make sure “root” user is the “owner” of the script file and that only "owner" has “read”, “write” and “execute” permissions. |
-| Pre-ScriptTimeout | The execution of the application-consistent backup pre-script timed-out. | Check the script and increase the timeout in the **VMSnapshotScriptPluginConfig.json** file that's located at **/etc/azure**. |
-| Post-ScriptTimeout | The execution of the application-consistent backup post-scripts timed out. | Check the script and increase the timeout in the **VMSnapshotScriptPluginConfig.json** file that's located at **/etc/azure**. |
+| InsufficientPermissionforPre-Script | For running scripts, **root** user should be the owner of the file and the file should have **700** permissions (that is, only **owner** should have **read**, **write**, and **execute** permissions). | Make sure **root** user is the **owner** of the script file and that only **owner** has **read**, **write** and **execute** permissions. |
+| InsufficientPermissionforPost-Script | For running scripts, root user should be the owner of the file and the file should have **700** permissions (that is, only **owner** should have **read**, **write**, and **execute** permissions). | Make sure **root** user is the **owner** of the script file and that only **owner** has **read**, **write** and **execute** permissions. |
+| Pre-ScriptTimeout | The execution of the application-consistent backup pre-script timed-out. | Check the script and increase the time-out in the **VMSnapshotScriptPluginConfig.json** file that's located at **/etc/azure**. |
+| Post-ScriptTimeout | The execution of the application-consistent backup post-scripts timed out. | Check the script and increase the time-out in the **VMSnapshotScriptPluginConfig.json** file that's located at **/etc/azure**. |
 
 ## Next steps
 

articles/backup/backup-azure-reserved-pricing-optimize-cost.md

@@ -3,17 +3,15 @@ title: Optimize costs for Azure Backup Storage with reserved capacity
 description: This article explains about how to optimize costs for Azure Backup Storage with reserved capacity.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 04/16/2024
+ms.date: 04/15/2025
 ms.custom: engagement-fy24
 author: jyothisuri
 ms.author: jsuri
 ---
 
 # Optimize costs for Azure Backup Storage with reserved capacity
 
-You can save money on backup storage costs for the vault-standard tier using Azure Backup Storage reserved capacity. Azure Backup Storage reserved capacity offers you a discount on capacity for backup data stored for the vault-standard tier when you commit to a reservation for either one year or three years. A reservation provides a fixed amount of backup storage capacity for the term of the reservation.
-
-Azure Backup Storage reserved capacity can significantly reduce your capacity costs for Azure Backup data. The cost savings achieved depend on the duration of your reservation, the total capacity you choose to reserve, and the vault tier, and type of redundancy you've chosen for your vault. Reserved capacity provides a billing discount and doesn't affect the state of your Azure Backup Storage resources.
+Azure Backup Storage reserved capacity allows cost savings for the vault-standard tier by providing discounts on backup storage when committing to a one- or three-year reservation. A reservation provides a fixed amount of backup storage capacity for the term of the reservation. The savings depend on the reservation term, total reserved capacity, vault tier, and chosen redundancy type. Reserved capacity reduces costs without impacting Azure Backup Storage resources.
 
 For information about Azure Backup pricing, see [Azure Backup pricing page](https://azure.microsoft.com/pricing/details/backup/).
 

articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md

@@ -1,16 +1,16 @@
 ---
-title: Troubleshoot Agent and extension issues
+title: Troubleshoot Azure Backup failures caused by agent or extension issues
 description: Symptoms, causes, and resolutions of Azure Backup failures related to agent, extension, and disks.
 ms.topic: troubleshooting
-ms.date: 04/08/2024
+ms.date: 04/15/2025
 ms.service: azure-backup
 ms.custom: engagement-fy24
 ms.reviewer: sooryar
 author: jyothisuri
 ms.author: jsuri
 ---
 
-# Troubleshoot Azure Backup failure: Issues with the agent or extension
+# Troubleshoot Azure Backup failures caused by agent or extension issues
 
 This article provides troubleshooting steps that can help you resolve Azure Backup errors related to communication with the VM agent and extension.