Merge pull request #79535 from MicrosoftDocs/master

6/13 AM Publish

Author: huypub

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

@@ -65,6 +65,9 @@ In addition, there are a couple of things that you might need to do in some circ
 
 ![List of backup vaults](./media/backup-azure-arm-vms-prepare/rs-list-of-vaults.png)
 
+> [!NOTE]
+> Azure Backup service creates a separate resource group (other than the VM resource group) to store snapshot, with the naming format **AzureBackupRG_geography_number** (example: AzureBackupRG_northeurope_1). The data in this resource group will be retained for the duration in days as specified in *Retain instant recovery snapshot* section of the Azure Virtual Machine Backup policy.  Applying a lock to this resource group can cause backup failures.
+
 ### Modify storage replication
 
 By default, vaults use [geo-redundant storage (GRS)](https://docs.microsoft.com/azure/storage/common/storage-redundancy-grs).

articles/backup/backup-azure-mars-troubleshoot.md

@@ -36,9 +36,29 @@ We recommend you perform the below validation, before you start troubleshooting
 
 ## Invalid vault credentials provided
 
-| Error details | Possible causes | Recommended actions |
-| ---     | ---     | ---    |
-| **Error** </br> *Invalid vault credentials provided. The file is either corrupted or does not have the latest credentials associated with recovery service. (ID: 34513)* | <ul><li> The vault credentials are invalid (that is, they were downloaded more than 48 hours before the time of registration).<li>MARS Agent is unable to download files to the Windows Temp directory. <li>The vault credentials are on a network location. <li>TLS 1.0 is disabled<li> A configured proxy server is blocking the connection. <br> |  <ul><li>Download the new vault credentials.(**Note**: If multiple vault credential files are downloaded previously, only the latest downloaded file is valid within 48 hours.) <li>Launch **IE** > **Setting** > **Internet options** > **Security** > **Internet**. Next, select **Custom Level**, and scroll until you see the file download section. Then select **Enable**.<li>You might also have to add these sites in IE [trusted sites](https://docs.microsoft.com/azure/backup/backup-configure-vault#verify-internet-access).<li>Change the settings to use a proxy server. Then provide the proxy server details. <li> Match the date and time with your machine.<li>If you get an error stating that file downloads are not allowed, it is likely that there are a large number of files in the C:/Windows/Temp directory.<li>Go to C:/Windows/Temp and check whether there are more than 60,000 or 65,000 files with the .tmp extension. If there are, delete these files.<li>Ensure that you have .NET framework 4.6.2 installed. <li>If you have disabled TLS 1.0 due to PCI compliance, refer to this [troubleshooting page](https://support.microsoft.com/help/4022913). <li>If you have anti-virus software installed on the server, exclude the following files from the anti-virus scan: <ul><li>CBengine.exe<li>CSC.exe, which is related to .NET Framework. There is a CSC.exe for every .NET version that's installed on the server. Exclude CSC.exe files that are tied to all versions of .NET Framework on the affected server. <li>Scratch folder or cache location. <br>*The default location for the scratch folder or the cache location path is C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch*.<br><li>The bin folder C:\Program Files\Microsoft Azure Recovery Services Agent\Bin
+**Error message**: Invalid vault credentials provided. The file is either corrupted or does not have the latest credentials associated with recovery service. (ID: 34513)
+
+| Cause | Recommended Action |
+| ---     | ---    |
+| **The vault credentials are invalid** <br/> <br/> Vault credential files might be corrupt or may have expired (i.e. downloaded more than 48 hours before the time of registration)| Download a new credential from Recovery Services vault from the Azure portal (see *Step 6* under [**Download the MARS agent**](https://docs.microsoft.com/azure/backup/backup-configure-vault#download-the-mars-agent) section) and perform the below: <ul><li> If you have already installed and registered Microsoft Azure Backup Agent, then open the Microsoft Azure Backup Agent MMC console and choose **Register Server** from Action Pane to complete the registration with the newly downloaded credentials <br/> <li> If the new installation failed then try re-installing using the new credentials</ul> **Note**: If multiple vault credential files are downloaded previously, only the latest downloaded file is valid within 48 hours. Hence it is recommended to download fresh new vault credentials file.
+| **Proxy Server/firewall is blocking <br/>or <br/>No Internet connectivity** <br/><br/> If your machine or Proxy Server has limited Internet access then without listing the necessary URLs the registration will fail.| To resolve this issue, perform the below:<br/> <ul><li> Work with your IT team to ensure the system has Internet connectivity<li> If you do not have Proxy server, then ensure the proxy option is unselected when registering the agent, verify proxy settings steps listed [here](#verifying-proxy-settings-for-windows)<li> If you do have a firewall/proxy server then work with your networking team to ensure that below URLs and IP address have access<br/> <br> **URLs**<br> - *www.msftncsi.com* <br>- *.Microsoft.com* <br> - *.WindowsAzure.com* <br>- *.microsoftonline.com* <br>- *.windows.net* <br>**IP address**<br> - *20.190.128.0/18* <br> - *40.126.0.0/18* <br/></ul></ul>Try re-registering after you complete the above troubleshooting steps
+| **Anti-virus software is blocking** | If you have anti-virus software installed on the server, then add necessary exclusion rules for the following files from the anti-virus scan: <br/><ui> <li> *CBengine.exe* <li> *CSC.exe*<li> Scratch folder, the default location is *C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch* <li> Bin folder at *C:\Program Files\Microsoft Azure Recovery Services Agent\Bin*
+
+### Additional recommendations
+- Go to *C:/Windows/Temp* and check whether there are more than 60,000 or 65,000 files with the .tmp extension. If there are, delete these files
+- Ensure the machine’s date and time is matching with local time zone
+- Ensure the [following](backup-configure-vault.md#verify-internet-access) sites are added to IE trusted sites
+
+### Verifying proxy settings for Windows
+
+- Download **psexec** from [here](https://docs.microsoft.com/sysinternals/downloads/psexec)
+- Run this `psexec -i -s "c:\Program Files\Internet Explorer\iexplore.exe"` command from elevated prompt:
+- This will launch *Internet Explorer* window
+- Go to *Tools* -> *Internet Options* -> *Connections* -> *LAN settings*
+- Verify proxy settings for *System* account
+- If no proxy is configured and proxy details are provided, then remove the details
+-	If proxy is configured and proxy details are incorrect, then ensure *Proxy IP* and *port* details are accurate
+- Close *Internet Explorer*
 
 ## Unable to download vault credential file
 
@@ -100,11 +120,11 @@ If scheduled backups don't get triggered automatically, while manual backups wor
 
   `PS C:\WINDOWS\system32> Set-ExecutionPolicy Unrestricted`
 
-- Ensure there are no missing or corrupted **PowerShell** module **MSonlineBackup**. In case there are any missing or corrupt file, to resolve this issue perform the below:
+- Ensure there are no missing or corrupted **PowerShell** module **MSonlineBackup**. In case there is any missing or corrupt file, to resolve this issue perform the below:
 
   - From any machine having MARS agent that is working properly, copy the MSOnlineBackup folder from *(C:\Program Files\Microsoft Azure Recovery Services Agent\bin\Modules)* path.
   - Paste this in problematic machine in the same path *(C:\Program Files\Microsoft Azure Recovery Services Agent\bin\Modules)*.
-  - If **MSOnlineBackup** folder is already exists in the machine, paste or replace the content files inside it.
+  - If **MSOnlineBackup** folder is already existed in the machine, paste or replace the content files inside it.
 
 
 > [!TIP]

articles/backup/backup-azure-vms-first-look-arm.md

@@ -6,7 +6,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: backup
 ms.topic: conceptual
-ms.date: 02/17/2019
+ms.date: 06/13/2019
 ms.author: raynew
 ---
 # Back up an Azure VM from the VM settings
@@ -16,27 +16,27 @@ This article explains how to back up Azure VMs with the [Azure Backup](backup-ov
 - Single Azure VM: The instructions in this article describe how to back up an Azure VM directly from the VM settings.
 - Multiple Azure VMs: You can set up a Recovery Services vault and configure backup for multiple Azure VMs. Follow the instructions in [this article](backup-azure-arm-vms-prepare.md) for this scenario.
 
- 
+
 
 ## Before you start
 
-1. [Learn](backup-architecture.md#how-does-azure-backup-work) how backup works, and [verify](backup-support-matrix.md#azure-vm-backup-support) support requirements. 
+1. [Learn](backup-architecture.md#how-does-azure-backup-work) how backup works, and [verify](backup-support-matrix.md#azure-vm-backup-support) support requirements.
 2. [Get an overview](backup-azure-vms-introduction.md) of Azure VM backup.
 
 ### Azure VM agent installation
 
-In order to back up Azure VMs, Azure Backup installs an extension on the VM agent running on the machine. If your VM was created from an Azure marketplace image, the agent will be running. In some cases, for example if you create a custom VM, or you migrate a machine from on-premises. you might need to install the agent manually. 
+In order to back up Azure VMs, Azure Backup installs an extension on the VM agent running on the machine. If your VM was created from an Azure marketplace image, the agent will be running. In some cases, for example if you create a custom VM, or you migrate a machine from on-premises. you might need to install the agent manually.
 
-- If you do need to install the VM agent manually, follow the instructions for [Windows](https://docs.microsoft.com/azure/virtual-machines/extensions/agent-windows) or [Linux](https://docs.microsoft.com/azure/virtual-machines/extensions/agent-linux) VMs. 
+- If you do need to install the VM agent manually, follow the instructions for [Windows](https://docs.microsoft.com/azure/virtual-machines/extensions/agent-windows) or [Linux](https://docs.microsoft.com/azure/virtual-machines/extensions/agent-linux) VMs.
 - After the agent is installed, when you enable backup, Azure Backup installs the backup extension to the agent. It updates and patches the extension without user intervention.
 
 ## Back up from Azure VM settings
 
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-2. Click **All services** and in the Filter, type **Virtual machines**, and then click **Virtual machines**. 
+2. Click **All services** and in the Filter, type **Virtual machines**, and then click **Virtual machines**.
 3. From the list of VMs select the VM you want to back up.
-4. On the VM menu, click **Backup**. 
+4. On the VM menu, click **Backup**.
 5. In **Recovery Services vault**, do the following:
    - If you already have a vault, click **Select existing**, and select a vault.
    - If you don't have a vault, click **Create new**. Specify a name for the vault. It's created in the same region and resource group as the VM. You can't modify these settings when you enable backup directly from the VM settings.
@@ -51,7 +51,7 @@ In order to back up Azure VMs, Azure Backup installs an extension on the VM agen
 
    ![Select backup policy](./media/backup-azure-vms-first-look-arm/set-backup-policy.png)
 
-7. Click **Enable Backup**. This associates the backup policy with the VM. 
+7. Click **Enable Backup**. This associates the backup policy with the VM.
 
     ![Enable Backup button](./media/backup-azure-vms-first-look-arm/vm-management-menu-enable-backup-button.png)
 
@@ -63,23 +63,20 @@ In order to back up Azure VMs, Azure Backup installs an extension on the VM agen
 10. After enabling backup, an initial backup runs. You can start the initial backup immediately, or wait until it starts in accordance with the backup schedule.
     - Until the initial backup completes, the **Last backup status** shows as **Warning (Initial backup pending)**.
     - To see when the next scheduled backup will run, click the backup policy name.
-    
-   
 
-> [!NOTE]
-> Azure Backup creates a separate resource group (other than the VM resource group) to store restore points, with the naming format **AzureBackupRG_geography_number** (example:
-AzureBackupRG_northeurope_1). You shouldn't lock this resource group.
 
+> [!NOTE]
+> Azure Backup service creates a separate resource group (other than the VM resource group) to store snapshot, with the naming format **AzureBackupRG_geography_number** (example: AzureBackupRG_northeurope_1). The data in this resource group will be retained for the duration in days as specified in “Retain instant recovery snapshot” section of the Azure Virtual Machine Backup policy. Applying a lock to this resource group can cause backup failures.
 
 
-## Run a backup immediately 
+## Run a backup immediately
 
 1. To run a backup immediately, in the VM menu, click **Backup** > **Backup now**.
 
     ![Run backup](./media/backup-azure-vms-first-look-arm/backup-now-update.png)
 
 2. In **Backup Now** use the calendar control to select until when the recovery point will be retained >  and **OK**.
-  
+
     ![Backup retention day](./media/backup-azure-vms-first-look-arm/backup-now-blade-calendar.png)
 
 3. Portal notifications let you know the backup job has been triggered. To monitor backup progress, click **View all jobs**.
@@ -95,4 +92,3 @@ Follow the instructions in this article to enable backup for Azure VMs by settin
 
 - If you have difficulties with any of the procedures in this article, consult the [troubleshooting guide](backup-azure-vms-troubleshoot.md).
 - [Learn about](backup-azure-manage-vms.md) managing your backups.
-

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

@@ -5,7 +5,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: backup
 ms.topic: conceptual
-ms.date: 03/22/2019
+ms.date: 06/13/2019
 ms.author: raynew
 ---
 
@@ -22,7 +22,7 @@ This article details how to enable backup when you create a virtual machine (VM)
 ## Sign in to Azure
 
 If you aren't already signed in to your account, sign in to the [Azure portal](https://portal.azure.com).
- 
+
 ## Create a VM with Backup configured
 
 1. In Azure portal, click **Create a resource**.
@@ -36,40 +36,44 @@ If you aren't already signed in to your account, sign in to the [Azure portal](h
 6. Accept the suggested vault name or specify your own.
 7. Specify or create a resource group in which the vault will be located. The resource group vault can be different from the VM resource group.
 
-    ![Enable backup for a VM](./media/backup-during-vm-creation/enable-backup.png) 
+    ![Enable backup for a VM](./media/backup-during-vm-creation/enable-backup.png)
 
 8. Accept the default backup policy, or modify the settings.
-    - A backup policy specifies how frequently to take backup snapshots of the VM, and how long to keep those backup copies. 
+    - A backup policy specifies how frequently to take backup snapshots of the VM, and how long to keep those backup copies.
     - The default policy backs up the VM once a day.
     - You can customize your own backup policy for an Azure VM to take backups daily or weekly.
     - [Learn more](backup-azure-vms-introduction.md#backup-and-restore-considerations) about backup considerations for Azure VMs.
     - [Learn more](backup-instant-restore-capability.md) about the instant restore functionality.
 
-      ![Default backup policy](./media/backup-during-vm-creation/daily-policy.png) 
+      ![Default backup policy](./media/backup-during-vm-creation/daily-policy.png)
+
+
+> [!NOTE]
+> Azure Backup service creates a separate resource group (other than the VM resource group) to store snapshot, with the naming format **AzureBackupRG_geography_number** (example: AzureBackupRG_northeurope_1). The data in this resource group will be retained for the duration in days as specified in *Retain instant recovery snapshot* section of the Azure Virtual Machine Backup policy.  Applying a lock to this resource group can cause backup failures.
 
 
-## Start a backup after creating the VM 
+## Start a backup after creating the VM
 
-Your VM backup will run in accordance with your backup policy. However, we recommend that you run an initial backup. 
+Your VM backup will run in accordance with your backup policy. However, we recommend that you run an initial backup.
 
 After the VM is created, do the following:
 
 1. In the VM properties, click **Backup**. The VM status is Initial Backup Pending until the initial backup runs
 2. Click **Back up now** to run an on-demand backup.
 
-    ![Run an on-demand backup](./media/backup-during-vm-creation/run-backup.png) 
+    ![Run an on-demand backup](./media/backup-during-vm-creation/run-backup.png)
 
 ## Use a Resource Manager template to deploy a protected VM
 
 The previous steps explain how to use the Azure portal to create a virtual machine and protect it in a Recovery Services vault. To quickly deploy one or more VMs and protect them in a Recovery Services vault, see the template [Deploy a Windows VM and enable backup](https://azure.microsoft.com/resources/templates/101-recovery-services-create-vm-and-configure-backup/).
 
 
 
-## Next steps 
+## Next steps
 
 Now that you've protected your VM, learn how to manage and restore them.
 
-- [Manage and monitor VMs](backup-azure-manage-vms.md) 
-- [Restore VM](backup-azure-arm-restore-vms.md) 
+- [Manage and monitor VMs](backup-azure-manage-vms.md)
+- [Restore VM](backup-azure-arm-restore-vms.md)
 
 If you encounter any issues, [review](backup-azure-vms-troubleshoot.md) the troubleshooting guide.