Merge pull request #179133 from v-amallick/Nov-9-2021-VMupdates

VM updates

Author: PMEds28

articles/backup/backup-azure-arm-restore-vms.md

@@ -3,7 +3,10 @@ title: Restore VMs by using the Azure portal
 description: Restore an Azure virtual machine from a recovery point by using the Azure portal, including the Cross Region Restore feature.
 ms.reviewer: geg
 ms.topic: conceptual
-ms.date: 09/27/2021
+ms.date: 11/09/2021
+author: v-amallick
+ms.service: backup
+ms.author: v-amallick
 ---
 # How to restore Azure VM data in Azure portal
 
@@ -157,7 +160,7 @@ If CRR is enabled, you can view the backup items in the secondary region.
 1. Select **Secondary Region** to view the items in the secondary region.
 
 >[!NOTE]
->Only Backup Management Types supporting the CRR feature will be shown in the list. Currently, only support for restoring secondary region data to a secondary region is allowed.<br></br>CRR for Azure VMs is supported for Azure Managed VMs (including encrypted Azure VMs).
+>Only Backup Management Types supporting the CRR feature will be shown in the list. Currently, only support for restoring secondary region data to a secondary region is allowed.<br></br>CRR for Azure VMs is supported for Azure Managed VMs (including encrypted Azure VMs). See the [management types that support Cross Region Restore](/azure/backup/backup-support-matrix#cross-region-restore).
 
 ![Virtual machines in secondary region](./media/backup-azure-arm-restore-vms/secbackedupitem.png)
 

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

@@ -2,8 +2,10 @@
 title: Troubleshoot Agent and extension issues
 description: Symptoms, causes, and resolutions of Azure Backup failures related to agent, extension, and disks.
 ms.topic: troubleshooting
-ms.date: 05/25/2021
+ms.date: 11/10/2021
 ms.service: backup
+author: v-amallick
+ms.author: v-amallick
 ---
 
 # Troubleshoot Azure Backup failure: Issues with the agent or extension
@@ -126,6 +128,9 @@ To resolve this issue, remove the lock on the resource group of the VM, and retr
 
 For a backup operation to succeed on encrypted VMs, it must have permissions to access the key vault. Permissions can be set through the [Azure portal](./backup-azure-vms-encryption.md) or through [PowerShell](./backup-azure-vms-automation.md#enable-protection).
 
+>[!Note]
+>If the required permissions to access the key vault have already been set, retry the operation after a little while.
+
 ## <a name="ExtensionSnapshotFailedNoNetwork-snapshot-operation-failed-due-to-no-network-connectivity-on-the-virtual-machine"></a>ExtensionSnapshotFailedNoNetwork - Snapshot operation failed due to no network connectivity on the virtual machine
 
 **Error code**: ExtensionSnapshotFailedNoNetwork<br>

articles/backup/backup-azure-vm-backup-faq.yml

@@ -4,7 +4,9 @@ metadata:
   description: In this article, discover answers to common questions about backing up Azure VMs with the Azure Backup service.
   ms.topic: article
   ms.service: backup
-  ms.date: 08/19/2021
+  ms.date: 11/09/2021
+  author: v-amallick
+  ms.author: v-amallick
 
 title: Frequently asked questions-Back up Azure VMs
 summary: |
@@ -79,7 +81,7 @@ sections:
           Yes, Azure Backup supports [standard SSD managed disks](../virtual-machines/disks-types.md#standard-ssds).
 
       - question: Can we back up a VM with a Write Accelerator (WA)-enabled disk?
-        answer: Snapshots can be taken on only data disks which are WA enabled and not OS disks. So only data disks which are WA enabled can be protected.
+        answer: Snapshots can be taken on only data disks that are WA enabled and not OS disks. So, only data disks that are WA enabled can be protected.
 
       - question: I have a VM with Write Accelerator (WA) disks and SAP HANA installed. How do I back up?
         answer: |
@@ -112,7 +114,7 @@ sections:
         answer: All the VM configurations required to perform the restore operations are stored in the VM backup. That includes the encryption copies of the VM encrypted keys, which are accessible to you on restore. The encryption copies can only be decrypted using the key vault. Temporary disks and memory state aren't captured in the snapshot.
 
       - question: Can we back up tags from Azure VM? If so, how many tags?
-        answer: Azure B0ackup can back up and restore tags, except NICs and IPs. Azure Backup honors the subscription limitations of Azure Resource Group and restores up to 50 tags.<br><br>For detailed information, see [Subscription limits](../azure-resource-manager/management/azure-subscription-service-limits.md#subscription-limits).
+        answer: Azure Backup can back up and restore tags, except NICs and IPs. Azure Backup honors the subscription limitations of Azure Resource Group and restores up to 50 tags.<br><br>For detailed information, see [Subscription limits](../azure-resource-manager/management/azure-subscription-service-limits.md#subscription-limits).
 
       - question: Can I take on-demand (ad-hoc) backup without scheduling backup for an Azure VM?
         answer: |
@@ -264,6 +266,12 @@ sections:
         answer: |
           **RPO**: The minimum RPO is 1 day or 24 hours.  <br><br>  **RTO**: The snapshots are stored in the storage account. So, the restore from the instant restore tier is instantaneous. This data is then transferred to the Recovery Services vault that is maintained by the Azure Backup service and will take a couple of hours for transfer and restore.
 
+      - question: Why does the error VMMarketplaceInvalidInputmessage appear?
+        answer: |
+          This error appears when you try to start a VM after creating an Azure VM from a non-Marketplace image or swap the OS disk of a VM with a non-Marketplace image, and then the VM deployment fails. To resolve this issue, remove the plan information from the VM.
+
+
+
 
 
       

articles/backup/backup-during-vm-creation.md

@@ -2,7 +2,10 @@
 title: Enable backup when you create an Azure VM
 description: Describes how to enable backup when you create an Azure VM with Azure Backup.
 ms.topic: conceptual
-ms.date: 06/03/2021
+ms.date: 11/09/2021
+author: v-amallick
+ms.service: backup
+ms.author: v-amallick
 ---
 
 # Enable backup when you create an Azure VM
@@ -25,6 +28,9 @@ If you aren't already signed in to your account, sign in to the [Azure portal](h
 
 2. In Azure Marketplace, select **Compute**, and then select a VM image.
 
+   >[!Note]
+   >To create a VM from a non-Marketplace image or swap the OS disk of a VM with a non-Marketplace image, remove the plan information from the VM. This helps in seamless VM restore.
+
 3. Set up the VM in accordance with the [Windows](../virtual-machines/windows/quick-create-portal.md) or [Linux](../virtual-machines/linux/quick-create-portal.md) instructions.
 
 4. On the **Management** tab, in **Enable backup**, select **On**.
@@ -44,7 +50,7 @@ If you aren't already signed in to your account, sign in to the [Azure portal](h
       ![Default backup policy](./media/backup-during-vm-creation/daily-policy.png)
 
 >[!NOTE]
->[SSE and PMK are the default encryption methods](backup-encryption.md) for Azure VMs. Azure Backup supports backup and restore of these Azure VMs.
+> [SSE and PMK are the default encryption methods](backup-encryption.md) for Azure VMs. Azure Backup supports backup and restore of these Azure VMs.
 
 ## Azure Backup resource group for Virtual Machines
 

articles/backup/selective-disk-backup-restore.md

@@ -2,8 +2,11 @@
 title: Selective disk backup and restore for Azure virtual machines
 description: In this article, learn about selective disk backup and restore using the Azure virtual machine backup solution.
 ms.topic: conceptual
-ms.date: 05/13/2021
-ms.custom: references_regions , devx-track-azurecli, devx-track-azurepowershell
+ms.date: 11/10/2021
+ms.custom: references_regions , devx-track-azurecli, devx-track-azurepowershell3
+author: v-amallick
+ms.service: backup
+ms.author: v-amallick
 ---
 
 # Selective disk backup and restore for Azure virtual machines
@@ -181,9 +184,9 @@ Each recovery point has the information of the included and excluded disks:
 ### Remove disk exclusion settings and get protected item with Azure CLI
 
 ```azurecli
-az backup protection update-for-vm --vault-name {vaultname} --resource-group {resourcegroup} -c {vmname} -i {vmname} --backup-management-type AzureIaasVM --disk-list-setting resetexclusionsettings
+az backup protection update-for-vm --vault-name {vaultname} --resource-group {resourcegroup} -c {vmname} -i {vmname} --disk-list-setting resetexclusionsettings
 
-az backup item show -c {vmname} -n {vmname} --vault-name {vaultname} --resource-group {resourcegroup} --backup-management-type AzureIaasVM
+az backup item show -c {vmname} -n {vmname} --vault-name {vaultname} --resource-group {resourcegroup}
 ```
 
 When you execute these commands, you'll see `"diskExclusionProperties": null`.

articles/virtual-machines/how-to-enable-write-accelerator.md

@@ -6,7 +6,7 @@ manager: markkie
 ms.service: virtual-machines
 ms.topic: how-to
 ms.workload: infrastructure
-ms.date: 2/20/2019
+ms.date: 11/10/2021
 ms.author: raiye
 ms.subservice: disks 
 ms.custom: devx-track-azurepowershell
@@ -40,7 +40,7 @@ Enabling Write Accelerator for OS disks should not be necessary for SAP-related
 When using Write Accelerator for an Azure disk/VHD, these restrictions apply:
 
 - The Premium disk caching must be set to 'None' or 'Read Only'. All other caching modes are not supported.
-- Snapshot are not currently supported for Write Accelerator-enabled disks. During backup, the Azure Backup service automatically excludes Write Accelerator-enabled disks attached to the VM.
+- Snapshots are currently supported for only Write Accelerator-enabled data disks, and not the OS disk. During backup, the Azure Backup service automatically backs up and protects Write Accelerator-enabled data disks attached to the VM.
 - Only smaller I/O sizes (<=512 KiB) are taking the accelerated path. In workload situations where data is getting bulk loaded or where the transaction log buffers of the different DBMS are filled to a larger degree before getting persisted to the storage, chances are that the I/O written to disk is not taking the accelerated path.
 
 There are limits of Azure Premium Storage VHDs per VM that can be supported by Write Accelerator. The current limits are: