Merge pull request #98337 from vrvkrajesh/master

Added hyper link

Author: ttorble

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

@@ -9,64 +9,6 @@ ms.date: 10/07/2019
 
 This article describes how to manage files and folders that are backed up with the Microsoft Azure Recovery Services Agent.
 
-## Create a backup policy
-
-The backup policy specifies when to take snapshots of the data to create recovery points and how long to retain recovery points. You configure the backup policy using the MARS agent.
-
-Create a policy as follows:
-
-1. After downloading and registering the MARS agent, launch the agent console. You can find it by searching your machine for **Microsoft Azure Backup**.  
-2. In **Actions**, click **Schedule Backup**.
-
-    ![Schedule a Windows Server backup](./media/backup-configure-vault/schedule-first-backup.png)
-3. In the Schedule Backup Wizard >  **Getting started**, click **Next**.
-4. In **Select Items to Back up**, click **Add Items**.
-
-    ![Select Items to Back up](./media/backup-azure-manage-mars/select-item-to-backup.png)
-
-5. In **Select Items**, select what you want to back up and click **OK**.
-
-    ![Selected Items to Back up](./media/backup-azure-manage-mars/selected-items-to-backup.png)
-
-6. In **Select Items to Back up** page, click **Next**.
-7. In **Specify Back up Schedule** page, specify when you want to take daily or weekly backups. Then click **Next**.
-
-    - A recovery point is created when a backup is taken.
-    - The number of recovery points created in your environment is dependent upon your backup schedule.
-
-8. You can schedule daily backups, up to three times a day. For example, the screenshot shows two daily backups, one at midnight and one at 6:00 PM.
-
-    ![Daily schedule](./media/backup-configure-vault/day-schedule.png)
-
-9. You can run weekly backups too. For example, the screenshot shows backups taken every alternate Sunday & Wednesday at 9:30 AM and 1:00 AM.
-
-    ![Weekly schedule](./media/backup-configure-vault/week-schedule.png)
-
-10. On the **Select Retention Policy** page, specify how you store historical copies of your data. Then click **Next**.
-
-    - Retention settings specify which recovery points should be stored, and how long they should be stored for.
-    - For example, when you set a daily retention setting, you indicate that at the time specified for the daily retention, the latest recovery point will be retained for the specified number of days. Or, as another example, you could specify a monthly retention policy to indicate that the recovery point created on the 30th of every month should be stored for 12 months.
-    - Daily and weekly recovery point retention usually coincides with the backup schedule. Meaning that when the backup is triggered according to schedule, the recovery point created by the backup is stored for the duration indicated in the daily or weekly retention policy.
-    - As an example, in the following screenshot:
-            - Daily backups at midnight and 6:00 PM are kept for seven days.
-            - Backups taken on a Saturday at midnight and 6:00 PM are kept for four weeks.
-            - Backups taken on Saturday on the last week of the month at midnight and 6:00 PM are kept for 12 months.
-            - Backups taken on a Saturday in the last week of March are kept for 10 years.
-
-    ![Retention example](./media/backup-configure-vault/retention-example.png)
-
-11. In **Choose Initial Backup Type** decide if you want to take the initial backup over the network or use offline backup (for more information on offline backup refer, see this [article](backup-azure-backup-import-export.md)). To take the initial backup over the network, select **Automatically over the network** and click **Next**.
-
-    ![initial Backup Type](./media/backup-azure-manage-mars/choose-initial-backup-type.png)
-
-12. In **Confirmation**, review the information, and then click **Finish**.
-    ![Confirm Backup Type](./media/backup-azure-manage-mars/confirm-backup-type.png)
-
-13. After the wizard finishes creating the backup schedule, click **Close**.
-  ![Confirm Modify Backup Process](./media/backup-azure-manage-mars/confirm-modify-backup-process.png)
-
-You must create a policy on each machine where the agent is installed.
-
 ## Modify a backup policy
 
 When you modify backup policy, you can add new items, remove existing items from backup, or exclude files from being backed up using  Exclusion Settings.
@@ -78,7 +20,7 @@ When you modify backup policy, you can add new items, remove existing items from
   - Reselecting these items, leads to a first full-backup and new policy changes are not applied to old backups.
   - Unselecting entire volume retains past backup without any scope for modifying retention policy.
 - **Exclusion Settings** use this option to exclude specific items from being backed up.
-  
+
 ### Add new items to existing policy
 
 1. In **Actions**, click **Schedule Backup**.

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

@@ -23,6 +23,7 @@ The Azure VM agent might be stopped, outdated, in an inconsistent state, or not
 - **Open Azure Portal > VM > Settings > Properties blade** > ensure VM **Status** is **Running** and **Agent status** is **Ready**. If the VM agent is stopped or is in an inconsistent state, restart the agent<br>
   - For Windows VMs follow these [steps](#the-agent-installed-in-the-vm-but-unresponsive-for-windows-vms) to restart the Guest Agent.<br>
   - For Linux VMs follow these [steps](#the-agent-installed-in-the-vm-is-out-of-date-for-linux-vms) to restart the Guest Agent.
+- **Open  Azure Portal > VM > Settings > Extensions** > Ensure all extensions are in **provisioning succeeded** state. If not, follow these [steps](https://docs.microsoft.com/azure/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout#usererrorvmprovisioningstatefailed---the-vm-is-in-failed-provisioning-state) to resolve the issue.
 
 ## GuestAgentSnapshotTaskStatusError - Could not communicate with the VM agent for snapshot status
 
@@ -48,8 +49,8 @@ After you register and schedule a VM for the Azure Backup service, Backup initia
 
 This error occurs when one of the extension failures puts the VM into provisioning failed state.<br>**Open  Azure Portal > VM > Settings > Extensions > Extensions status** and check if all extensions are in **provisioning succeeded** state.
 
-- If VMSnapshot extension is in failed state then right click on the failed extension and remove it. Trigger an adhoc-backup, this is will reinstall the extensions and run the backup job.  <br>
-- If any other extension is in failed state then it can interfere with the backup. Ensure those extension issues are resolved and retry the backup operation.  
+- If VMSnapshot extension is in a failed state, then right-click on the failed extension and remove it. Trigger an on-demand backup, this will reinstall the extensions and run the backup job.  <br>
+- If any other extension is in a failed state, then it can interfere with the backup. Ensure those extension issues are resolved and retry the backup operation.  
 
 ## UserErrorRpCollectionLimitReached - The Restore Point collection max limit has reached
 
@@ -224,7 +225,7 @@ To uninstall the extension:
 1. In the [Azure portal](https://portal.azure.com/), go to the VM that is experiencing backup failure.
 2. Select **Settings**.
 3. Select **Extensions**.
-4. Select **Vmsnapshot Extension**.
+4. Select **Snapshot Extension**.
 5. Select **Uninstall**.
 
 For Linux VM, If the VMSnapshot extension does not show in the Azure portal, [update the Azure Linux Agent](../virtual-machines/linux/update-agent.md), and then run the backup.

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

@@ -179,7 +179,6 @@ This will ensure the snapshots are taken through host instead of Guest. Retry th
 | Error details | Workaround |
 | ------ | --- |
 | **Error code**: 320001, ResourceNotFound <br/> **Error message**: Could not perform the operation as VM no longer exists. <br/> <br/> **Error code**: 400094, BCMV2VMNotFound <br/> **Error message**: The virtual machine doesn't exist <br/> <br/>  An Azure virtual machine wasn't found.  |This error happens when the primary VM is deleted, but the backup policy still looks for a VM to back up. To fix this error, take the following steps: <ol><li> Re-create the virtual machine with the same name and same resource group name, **cloud service name**,<br>**or**</li><li> Stop protecting the virtual machine with or without deleting the backup data. For more information, see [Stop protecting virtual machines](backup-azure-manage-vms.md#stop-protecting-a-vm).</li></ol>|
-| **Error code**: UserErrorVmProvisioningStateFailed<br/> **Error message**: The VM is in failed provisioning state: <br>Restart the VM and make sure the VM is running or shut down. | This error occurs when one of the extension failures puts the VM into failed provisioning state. Go to the extensions list, check if there's a failed extension, remove it, and try restarting the virtual machine. If all extensions are in running state, check if the VM Agent service is running. If not, restart the VM Agent service. |
 |**Error code**: UserErrorBCMPremiumStorageQuotaError<br/> **Error message**: Could not copy the snapshot of the virtual machine, due to insufficient free space in the storage account | For premium VMs on VM backup stack V1, we copy the snapshot to the storage account. This step makes sure that backup management traffic, which works on the snapshot, doesn't limit the number of IOPS available to the application using premium disks. <br><br>We recommend that you allocate only 50 percent, 17.5 TB, of the total storage account space. Then the Azure Backup service can copy the snapshot to the storage account and transfer data from this copied location in the storage account to the vault. |
 | **Error code**: 380008, AzureVmOffline <br/> **Error message**: Failed to install Microsoft Recovery Services extension as virtual machine  is not running | The VM Agent is a prerequisite for the Azure Recovery Services extension. Install the Azure Virtual Machine Agent and restart the registration operation. <br> <ol> <li>Check if the VM Agent is installed correctly. <li>Make sure that the flag on the VM config is set correctly.</ol> Read more about installing the VM Agent and how to validate the VM Agent installation. |
 | **Error code**: ExtensionSnapshotBitlockerError <br/> **Error message**: The snapshot operation failed with the Volume Shadow Copy Service (VSS) operation error **This drive is locked by BitLocker Drive Encryption. You must unlock this drive from the Control Panel.** |Turn off BitLocker for all drives on the VM and check if the VSS issue is resolved. |