Merge pull request #106292 from dcurwin/mar3-2020

Few fixes

Author: PRMerger6

articles/backup/back-up-hyper-v-virtual-machines-mabs.md

@@ -166,7 +166,7 @@ After you complete the steps in the previous sections, and the MABS Summary Mana
 
 1. Open SQL Server Management Studio and connect to the instance that hosts the MABS database.
 
-2. Run the following query: `select * from tbl_SCH_ScheduleDefinition where JobDefinitionID='9B30D213-B836-4B9E-97C2-DB03C3EB39D7'`. This query returns the **ScheduleID**. Note this ID as you will use it in the next step.
+2. Run the following query: `SELECT SCH.ScheduleId FROM tbl_JM_JobDefinition JD JOIN tbl_SCH_ScheduleDefinition SCH ON JD.JobDefinitionId = SCH.JobDefinitionId WHERE JD.Type = '282faac6-e3cb-4015-8c6d-4276fcca11d4' AND JD.IsDeleted = 0 AND SCH.IsDeleted = 0`. This query returns the **ScheduleID**. Note this ID as you will use it in the next step.
 
 3. In the SQL Server Management Studio, expand **SQL Server Agent**, and then expand **Jobs**. Right-click **ScheduleID** that you noted, and select **Start Job at Step**.
 

articles/backup/backup-azure-backup-faq.md

@@ -118,7 +118,7 @@ BMR/System state |Each individual copy of BMR or system state of the machine bei
 
 ### Is there a limit on the amount of data backed up using a Recovery Services vault?
 
-There is no limit on the amount of data you can back up using a Recovery Services vault.
+There is no limit on the total amount of data you can back up using a Recovery Services vault. The individual data sources (other than Azure VMs), can be a maximum of 54,400 GB in size. For more information about limits, see the [vault limits section in the support matrix](https://docs.microsoft.com/azure/backup/backup-support-matrix#vault-support).
 
 ### Why is the size of the data transferred to the Recovery Services vault smaller than the data selected for backup?
 

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

@@ -38,9 +38,7 @@ After you register and schedule a VM for the Azure Backup service, Backup starts
 
 **Cause 3: [The snapshot status can't be retrieved, or a snapshot can't be taken](#the-snapshot-status-cannot-be-retrieved-or-a-snapshot-cannot-be-taken)**
 
-**Cause 4: [The backup extension fails to update or load](#the-backup-extension-fails-to-update-or-load)**
-
-**Cause 5: [VM-Agent configuration options are not set (for Linux VMs)](#vm-agent-configuration-options-are-not-set-for-linux-vms)**
+**Cause 4: [VM-Agent configuration options are not set (for Linux VMs)](#vm-agent-configuration-options-are-not-set-for-linux-vms)**
 
 ## UserErrorVmProvisioningStateFailed - The VM is in failed provisioning state
 
@@ -84,7 +82,7 @@ For a backup operation to succeed on encrypted VMs, it must have permissions to
 After you register and schedule a VM for the Azure Backup service, Backup starts the job by communicating with the VM backup extension to take a point-in-time snapshot. Any of the following conditions might prevent the snapshot from being triggered. If the snapshot isn't triggered, a backup failure might occur. Complete the following troubleshooting steps in the order listed, and then retry your operation:
 
 **Cause 1: [The snapshot status can't be retrieved, or a snapshot can't be taken](#the-snapshot-status-cannot-be-retrieved-or-a-snapshot-cannot-be-taken)**  
-**Cause 2: [The backup extension fails to update or load](#the-backup-extension-fails-to-update-or-load)**  
+
 
 ## <a name="ExtensionOperationFailed-vmsnapshot-extension-operation-failed"></a>ExtensionOperationFailedForManagedDisks - VMSnapshot extension operation failed
 
@@ -93,9 +91,8 @@ After you register and schedule a VM for the Azure Backup service, Backup starts
 
 After you register and schedule a VM for the Azure Backup service, Backup starts the job by communicating with the VM backup extension to take a point-in-time snapshot. Any of the following conditions might prevent the snapshot from being triggered. If the snapshot isn't triggered, a backup failure might occur. Complete the following troubleshooting steps in the order listed, and then retry your operation:  
 **Cause 1: [The snapshot status can't be retrieved, or a snapshot can't be taken](#the-snapshot-status-cannot-be-retrieved-or-a-snapshot-cannot-be-taken)**  
-**Cause 2: [The backup extension fails to update or load](#the-backup-extension-fails-to-update-or-load)**  
-**Cause 3: [The agent is installed in the VM, but it's unresponsive (for Windows VMs)](#the-agent-installed-in-the-vm-but-unresponsive-for-windows-vms)**  
-**Cause 4: [The agent installed in the VM is out of date (for Linux VMs)](#the-agent-installed-in-the-vm-is-out-of-date-for-linux-vms)**
+**Cause 2: [The agent is installed in the VM, but it's unresponsive (for Windows VMs)](#the-agent-installed-in-the-vm-but-unresponsive-for-windows-vms)**  
+**Cause 3: [The agent installed in the VM is out of date (for Linux VMs)](#the-agent-installed-in-the-vm-is-out-of-date-for-linux-vms)**
 
 ## BackUpOperationFailed / BackUpOperationFailedV2 - Backup fails, with an internal error
 
@@ -106,8 +103,7 @@ After you register and schedule a VM for the Azure Backup service, Backup initia
 **Cause 1: [The agent installed in the VM, but it's unresponsive (for Windows VMs)](#the-agent-installed-in-the-vm-but-unresponsive-for-windows-vms)**  
 **Cause 2: [The agent installed in the VM is out of date (for Linux VMs)](#the-agent-installed-in-the-vm-is-out-of-date-for-linux-vms)**  
 **Cause 3: [The snapshot status can't be retrieved, or a snapshot can't be taken](#the-snapshot-status-cannot-be-retrieved-or-a-snapshot-cannot-be-taken)**  
-**Cause 4: [The backup extension fails to update or load](#the-backup-extension-fails-to-update-or-load)**  
-**Cause 5: Backup service doesn't have permission to delete the old restore points because of a resource group lock** <br>
+**Cause 4: Backup service doesn't have permission to delete the old restore points because of a resource group lock** <br>
 
 ## UserErrorUnsupportedDiskSize - The configured disk size(s) is currently not supported by Azure Backup
 
@@ -208,26 +204,6 @@ The following conditions might cause the snapshot task to fail:
 | The VM status is reported incorrectly because the VM is shut down in Remote Desktop Protocol (RDP). | If you shut down the VM in RDP, check the portal to determine whether the VM status is correct. If it’s not correct, shut down the VM in the portal by using the **Shutdown** option on the VM dashboard. |
 | The VM can't get the host or fabric address from DHCP. | DHCP must be enabled inside the guest for the IaaS VM backup to work. If the VM can't get the host or fabric address from DHCP response 245, it can't download or run any extensions. If you need a static private IP, you should configure it through the **Azure portal** or **PowerShell** and make sure the DHCP option inside the VM is enabled. [Learn more](../virtual-network/virtual-networks-static-private-ip-arm-ps.md#change-the-allocation-method-for-a-private-ip-address-assigned-to-a-network-interface) about setting up a static IP address with PowerShell.
 
-### The backup extension fails to update or load
-
-If extensions can't load, backup fails because a snapshot can't be taken.
-
-#### Solution
-
-Uninstall the extension to force the VMSnapshot extension to reload. The next backup attempt reloads the extension.
-
-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 **Snapshot Extension**.
-5. Select **Uninstall**.
-
-For Linux VM, If the VMSnapshot extension doesn't show in the Azure portal, [update the Azure Linux Agent](../virtual-machines/linux/update-agent.md), and then run the backup.
-
-Completing these steps causes the extension to be reinstalled during the next backup.
-
 ### <a name="remove_lock_from_the_recovery_point_resource_group"></a>Remove lock from the recovery point resource group
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).

articles/backup/backup-support-matrix.md

@@ -27,7 +27,7 @@ The following table describes the features of Recovery Services vaults:
 --- | ---
 **Vaults in subscription** | Up to 500 Recovery Services vaults in a single subscription.
 **Machines in a vault** | Up to 1,000 Azure VMs in a single vault.<br/><br/> Up to 50 MABS servers can be registered in a single vault.
-**Data sources in vault storage** | Maximum 54,400 GB. There's no limit for Azure VM backups.
+**Data sources** | Maximum size of an individual [data source](https://docs.microsoft.com/azure/backup/backup-azure-backup-faq#how-is-the-data-source-size-determined) is 54,400 GB. This limit does not apply to Azure VM backups. No limits apply to the total amount of data you can back up to the vault.
 **Backups to vault** | **Azure VMs:** Once a day.<br/><br/>**Machines protected by DPM/MABS:** Twice a day.<br/><br/> **Machines backed up directly by using the MARS agent:** Three times a day.
 **Backups between vaults** | Backup is within a region.<br/><br/> You need a vault in every Azure region that contains VMs you want to back up. You can't back up to a different region.
 **Move vaults** | You can [move vaults](https://docs.microsoft.com/azure/backup/backup-azure-move-recovery-services-vault) across subscriptions or between resource groups in the same subscription. However, moving vaults across regions isn’t supported.
@@ -151,8 +151,6 @@ Azure Backup has added the Cross Region Restore feature to strengthen data avail
 | SQL /SAP HANA          | No                                                           | N/A               |
 | AFS                    | No                                                           | N/A               |
 
-
-
 ## Next steps
 
 - [Review support matrix](backup-support-matrix-iaas.md) for Azure VM backup.

articles/backup/sap-hana-backup-support-matrix.md

@@ -20,7 +20,7 @@ Azure Backup supports the backup of SAP HANA databases to Azure. This article su
 | **Geos**                   | **GA:**<br> **Americas** – Central US, East US 2, East US, North Central US, South Central US, West US 2, West Central US, West US, Canada Central, Canada East, Brazil South <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India, China East, China North, China East2, China North 2 <br> **Europe** – West Europe, North Europe, France Central, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North <br> **Africa / ME** - South Africa North, South Africa West, UAE North, UAE Central  <BR>  **Azure Government regions** | France South, Germany Central, Germany Northeast, US Gov IOWA |
 | **OS versions**            | SLES 12 with SP2, SP3, or SP4; SLES 15 with SP1                              | RHEL                                                |
 | **HANA versions**          | SDC on HANA 1.x, MDC on HANA 2.x <= SPS04 Rev 46       | -                                                            |
-| **HANA deployments**       | SAP HANA on a single Azure VM -  Scale up only               | Scale-out                                                    |
+| **HANA deployments**       | SAP HANA on a single Azure VM -  Scale up only. <br><br> For high availability deployments, both the nodes on the two different machines are treated as individual nodes with separate data chains.               | Scale-out <br><br> In high availability deployments, backup doesn’t failover to the secondary node automatically. Configuring backup should be done separately for each node.                                           |
 | **HANA Instances**         | A single SAP HANA instance on a  single Azure VM – scale up only | Multiple SAP HANA instances on a  single VM                  |
 | **HANA database types**    | Single Database Container (SDC)  ON 1.x, Multi-Database Container (MDC) on 2.x | MDC in HANA 1.x                                              |
 | **HANA database size**     | 2-TB full backup size as reported by HANA)                   |                                                              |