Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr

Author: DennisLee-DennisLee

articles/backup/media/sap-hana-db-about/backup-architecture.png

@@ -0,0 +1,54 @@
+---
+title: About SAP HANA database backup in Azure VMs
+description: In this article, learn about backing up SAP HANA databases that are running on Azure virtual machines.
+ms.topic: conceptual
+ms.date: 12/11/2019
+---
+
+# About SAP HANA database backup in Azure VMs
+
+SAP HANA databases are mission critical workloads that require a low recovery point objective (RPO) and a fast recovery time objective (RTO). You can now [back up SAP HANA databases running on Azure VMs](https://docs.microsoft.com/azure/backup/tutorial-backup-sap-hana-db) using [Azure Backup](https://docs.microsoft.com/azure/backup/backup-overview).
+
+Azure Backup is [Backint certified](https://www.sap.com/dmc/exp/2013_09_adpd/enEN/#/d/solutions?id=8f3fd455-a2d7-4086-aa28-51d8870acaa5) by SAP, to provide native backup support by leveraging SAP HANA’s native APIs. This offering from Azure Backup aligns with Azure Backup’s mantra of **zero-infrastructure** backups, eliminating the need to deploy and manage backup infrastructure. You can now seamlessly back up and restore SAP HANA databases running on Azure VMs ([M series VMs](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory#m-series) also supported now!) and leverage enterprise management capabilities that Azure Backup provides.
+
+## Added value
+
+Using Azure Backup to back up and restore SAP HANA databases, gives the following advantages:
+
+* **15-minute Recovery Point Objective (RPO)**: Recovery of critical data of up to 15 minutes is now possible.
+* **One-click, point-in-time restores**: Restore of production data to alternate HANA servers is made easy. Chaining of backups and catalogs to perform restores is all managed by Azure behind the scenes.
+* **Long-term retention**: For rigorous compliance and audit needs. Retain your backups for years, based on the retention duration, beyond which the recovery points will be pruned automatically by the built-in lifecycle management capability.
+* **Backup Management from Azure**: Use Azure Backup’s management and monitoring capabilities for improved management experience. Azure CLI is also supported.
+
+To view the backup and restore scenarios that we support today, refer to the [SAP HANA scenario support matrix](https://docs.microsoft.com/azure/backup/sap-hana-backup-support-matrix#scenario-support).
+
+## Backup architecture
+
+![Backup architecture diagram](./media/sap-hana-db-about/backup-architecture.png)
+
+* The backup process begins by [creating a Recovery services vault](https://docs.microsoft.com/azure/backup/tutorial-backup-sap-hana-db#create-a-recovery-service-vault) in Azure. This vault will be used to store the backups and recovery points created over time.
+* The Azure VM running SAP HANA server is registered with the vault, and the databases to be backed-up are [discovered](https://docs.microsoft.com/azure/backup/tutorial-backup-sap-hana-db#discover-the-databases). To enable the Azure Backup service to discover databases, a [preregistration script](https://aka.ms/scriptforpermsonhana) must be run on the HANA server as a root user.
+* This script creates **AZUREWLBACKUPHANAUSER** DB user and a corresponding key with the same name in **hdbuserstore**. Refer to the [setting up permissions section](https://docs.microsoft.com/azure/backup/tutorial-backup-sap-hana-db#setting-up-permissions) to understand more about what the script does.
+* Azure Backup Service now installs the **Azure Backup Plugin for HANA** on the registered SAP HANA server.
+* The **AZUREWLBACKUPHANAUSER** DB user created by the preregistration script is used by the **Azure Backup Plugin for HANA** to perform all backup and restore operations. If you attempt to configure backup for SAP HANA DBs without running this script, you might receive the following error: **UserErrorHanaScriptNotRun**.
+* To [configure backup](https://docs.microsoft.com/azure/backup/tutorial-backup-sap-hana-db#configure-backup) on the databases that are discovered, choose the required backup policy and enable backups.
+
+* Once the backup is configured, Azure Backup service sets up the following Backint parameters at the DATABASE level on the protected SAP HANA server:
+  * [catalog_backup_using_backint:true]
+  * [enable_accumulated_catalog_backup:false]
+  * [parallel_data_backup_backint_channels:1]
+  * [log_backup_timeout_s:900)]
+  * [backint_response_timeout:7200]
+
+>[!NOTE]
+>Ensure that these parameters are *not* present at HOST level. Host-level parameters will override these parameters and might cause unexpected behavior.
+>
+
+* The **Azure Backup Plugin for HANA** maintains all the backup schedules and policy details. It triggers the scheduled backups and communicates with the **HANA Backup Engine** through the Backint APIs.
+* The **HANA Backup Engine** returns a Backint stream with the data to be backed up.
+* All the scheduled backups and on-demand backups (triggered from the Azure portal) that are either full or differential are initiated by the **Azure Backup Plugin for HANA**. However, log backups are managed and triggered by **HANA Backup Engine** itself.
+
+## Next steps
+
+* Learn how to [restore an SAP HANA database running on an Azure VM](https://docs.microsoft.com/azure/backup/sap-hana-db-restore)
+* Learn how to [manage SAP HANA databases that are backed up using Azure Backup](https://docs.microsoft.com/azure/backup/sap-hana-db-manage)

articles/backup/media/sap-hana-db-manage/backup-items.png

@@ -17,7 +17,7 @@ Azure Backup shows all manually triggered jobs in the **Backup jobs** section on
 
 ![Backup jobs section](./media/sap-hana-db-manage/backup-jobs.png)
 
-The jobs you see in this portal include database discovery and registering, and backup and restore operations. Scheduled jobs, including log backups are not shown in this section. Manually triggered backups from the SAP HANA native clients (Studio/ Cockpit/ DBA Cockpit) also do not show up here.
+The jobs you see in this portal include database discovery and registering, and backup and restore operations. Scheduled jobs, including log backups aren't shown in this section. Manually triggered backups from the SAP HANA native clients (Studio/ Cockpit/ DBA Cockpit) also don't show up here.
 
 ![Backup jobs list](./media/sap-hana-db-manage/backup-jobs-list.png)
 
@@ -70,25 +70,38 @@ If you want to take a local backup (using HANA Studio / Cockpit) of a database t
 3. To do this, double-click **systemdb** > **Configuration** > **Select Database** > **Filter (Log)**.
 4. Set **enable_auto_log_backup** to **No**.
 5. Set **log_backup_using_backint** to **False**.
-6. Take an ad hoc full backup of the database.
+6. Take an on-demand full backup of the database.
 7. Wait for the full backup and catalog backup to finish.
 8. Revert the previous settings back to those for Azure:
    * Set **enable_auto_log_backup** to **Yes**.
    * Set **log_backup_using_backint** to **True**.
 
-### Edit underlying policy
+### Change policy
 
-Modify policy to change backup frequency or retention range:
+You can change the underlying policy for an SAP HANA backup item.
 
-* In the vault dashboard, go to **Manage** > **Backup Policies**
+* In the vault dashboard, go to **Backup items**:
 
-  ![Backup policies in the vault dashboard](./media/sap-hana-db-manage/backup-policies-dashboard.png)
+  ![Select backup items](./media/sap-hana-db-manage/backup-items.png)
 
-* Choose the policy you want to edit:
+* Choose **SAP HANA in Azure VM**
 
-  ![List of backup policies](./media/sap-hana-db-manage/backup-policies-list.png)
+  ![Choose SAP HANA in Azure VM](./media/sap-hana-db-manage/sap-hana-in-azure-vm.png)
 
-  ![Backup policy details](./media/sap-hana-db-manage/backup-policy-details.png)
+* Choose the backup item whose underlying policy you want to change
+* Click on the existing Backup policy
+
+  ![Select existing backup policy](./media/sap-hana-db-manage/existing-backup-policy.png)
+
+* Change the policy, choosing from the list. [Create a new backup policy](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database#create-a-backup-policy) if needed.
+
+  ![Choose policy from drop-down list](./media/sap-hana-db-manage/choose-backup-policy.png)
+
+* Save the changes
+
+  ![Save the changes](./media/sap-hana-db-manage/save-changes.png)
+
+* Policy modification will impact all the associated Backup Items and trigger corresponding **configure protection** jobs.
 
 >[!NOTE]
 > Any change in the retention period will be applied retrospectively to all the older recovery points besides the new ones.
@@ -170,4 +183,3 @@ Unregister an SAP HANA instance after you disable protection but before you dele
 ## Next steps
 
 * Learn how to [troubleshoot common issues when backing up SAP HANA databases.](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot)
-

articles/backup/media/sap-hana-db-manage/choose-backup-policy.png

@@ -244,6 +244,8 @@
       href: manage-monitor-sql-database-backup.md
   - name: SAP HANA databases on Azure VMs
     items:
+    - name: About SAP HANA Backup on Azure VMs  
+      href: sap-hana-db-about.md
     - name: Back up SAP HANA databases on Azure VMs
       href: backup-azure-sap-hana-database.md
     - name: Restore SAP HANA databases in Azure VMs

articles/backup/media/sap-hana-db-manage/existing-backup-policy.png

@@ -49,7 +49,7 @@ The messages can come from any data source supported by [IoT Hub message routing
 
 You can add enrichments to messages that are going to the built-in endpoint of an IoT Hub, or messages that are being routed to custom endpoints such as Azure Blob storage, a Service Bus queue, or a Service Bus topic.
 
-You can add enrichments to messages that are being published to Event Grid by selecting the endpoint as Event Grid. We create a default route in IoT Hub to device telemetry, based on your Event Grid subscription. This single route can handle all of your Event Grid subscriptions. You can configure enrichments for the event grid ent[point after you have created the event grid subscription to device telemetry. For more information, see [Iot Hub and Event Grid](iot-hub-event-grid.md).
+You can add enrichments to messages that are being published to Event Grid by selecting the endpoint as Event Grid. We create a default route in IoT Hub to device telemetry, based on your Event Grid subscription. This single route can handle all of your Event Grid subscriptions. You can configure enrichments for the event grid endpoint after you have created the event grid subscription to device telemetry. For more information, see [Iot Hub and Event Grid](iot-hub-event-grid.md).
 
 Enrichments are applied per endpoint. If you specify five enrichments to be stamped for a specific endpoint, all messages going to that endpoint are stamped with the same five enrichments.