Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mwahl-gov-app-file

Author: markwahl-msft

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -79,7 +79,7 @@ You need a Windows or Linux machine that can access both your vCenter Server ins
 
 8. Under **Region**, select an Azure location where the resource metadata will be stored. Currently, supported regions are **East US**, **West Europe**, **Australia East** and **Canada Central**.
 
-9. Provide a name for **Custom location**. This is the name that you'll see when you deploy VMs. Name it for the datacenter or the physical location of your datacenter. For example: **contoso-nyc-dc**.
+9. Provide a name for **Custom location**. You'll see this name when you deploy VMs. Name it for the datacenter or the physical location of your datacenter. For example: **contoso-nyc-dc**.
 
 10. Leave **Use the same subscription and resource group as your resource bridge** selected.
 
@@ -145,11 +145,35 @@ A typical onboarding that uses the script takes 30 to 60 minutes. During the pro
 | **Data store** | Select the name of the datastore to be used for the Azure Arc resource bridge VM. |
 | **Folder** | Select the name of the vSphere VM and the template folder where the Azure Arc resource bridge's VM will be deployed. |
 | **VM template Name** | Provide a name for the VM template that will be created in your vCenter Server instance based on the downloaded OVA file. For example: **arc-appliance-template**. |
-| **Control Plane IP** address | Provide a static IP address that's outside the DHCP range but still available on the network. Ensure that this IP address isn't assigned to any other machine on the network. Azure Arc resource bridge (preview) runs a Kubernetes cluster, and its control plane requires a static IP address. Control Plane IP must have internet access. |
+| **Control Plane IP address** | Provide a static IP address that is outside the DHCP scope for virtual machines but in the same subnet. Ensure that this IP address isn't assigned to any other machine on the network. Azure Arc resource bridge (preview) runs a Kubernetes cluster, and its control plane requires a static IP address. Control Plane IP must have internet access. |
 | **Appliance proxy settings** | Enter **y** if there's a proxy in your appliance network. Otherwise, enter **n**. </br> You need to populate the following boxes when you have a proxy set up: </br> 1. **Http**: Address of the HTTP proxy server. </br> 2. **Https**: Address of the HTTPS proxy server. </br> 3. **NoProxy**: Addresses to be excluded from the proxy. </br> 4. **CertificateFilePath**: For SSL-based proxies, the path to the certificate to be used.
 
 After the command finishes running, your setup is complete. You can now use the capabilities of Azure Arc-enabled VMware vSphere.
 
+> [!IMPORTANT]
+> After the successful installation of Azure Arc resource bridge, it is recommended to retain a copy of the resource bridge config .yaml files and the kubeconfig file safe and secure in a place that facilitates easy retrieval. These files may be needed later to run a few commands to perform management operations on the resource bridge.
+
+## Recovering from failed deployments
+
+If the Azure Arc resource bridge deployment fails, consult the [Azure Arc resource bridge troubleshooting document](../resource-bridge/troubleshoot-resource-bridge.md). While there can be many reasons why the Azure Arc resource bridge deployment fails, one of them is KVA timeout error. For more information about the KVA timeout error and how to troubleshoot it, see [KVA timeout error](../resource-bridge/troubleshoot-resource-bridge.md#kva-timeout-error).
+
+To clean up the installation and retry the deployment, use the following commands.
+
+### Retry command - Windows
+
+Run the command with ```-Force``` to clean up the installation and onboard again.
+
+```powershell-interactive
+./resource-bridge-onboarding-script.ps1 -Force
+```
+
+### Retry command - Linux
+
+Run the command with ```--force``` to clean up the installation and onboard again.
+```bash
+bash resource-bridge-onboarding-script.sh --force
+```    
+
 ## Next steps
 
 - [Browse and enable VMware vCenter resources in Azure](browse-and-enable-vcenter-resources-in-azure.md)

articles/azure-netapp-files/azacsnap-cmd-ref-configure.md

@@ -105,7 +105,7 @@ When you add an *SAP HANA database* to the configuration, the following values a
 
 [Azure Backup](../backup/index.yml) service provides an alternate backup tool for SAP HANA, where database and log backups are streamed into the 
 Azure Backup Service.  Some customers would like to combine the streaming backint-based backups with regular snapshot-based backups.  However, backint-based 
-backups block other methods of backup, such as using a files-based backup or a storage snapshot-based backup (for example, AzAcSnap).  Guidance is provided on the Azure Backup site on how to [Run SAP HANA Studio backup on a database with Azure Backup enabled](../backup/backup-azure-sap-hana-database.md#run-sap-hana-studio-backup-on-a-database-with-azure-backup-enabled). 
+backups block other methods of backup, such as using a files-based backup or a storage snapshot-based backup (for example, AzAcSnap).  Guidance is provided on the Azure Backup site on how to [Run SAP HANA native clients backup on a database with Azure Backup enabled](../backup/backup-azure-sap-hana-database.md#run-sap-hana-native-clients-backup-on-a-database-with-azure-backup). 
 
 The process described in the Azure Backup documentation has been implemented with AzAcSnap to automatically do the following steps:
 

articles/backup/backup-azure-sap-hana-database.md

@@ -1,26 +1,18 @@
 ---
 title: Back up an SAP HANA database to Azure with Azure Backup 
 description: In this article, learn how to back up an SAP HANA database to Azure virtual machines with the Azure Backup service.
-ms.topic: conceptual
-ms.date: 08/09/2022
+ms.topic: how-to
+ms.date: 12/23/2022
 author: v-amallick
 ms.service: backup
 ms.author: v-amallick
 ---
 
 # Back up SAP HANA databases in Azure VMs
 
-SAP HANA databases are critical workloads that require a low recovery-point objective (RPO) and long-term retention. You can back up SAP HANA databases running on Azure virtual machines (VMs) by using [Azure Backup](backup-overview.md).
-
-This article shows how to back up SAP HANA databases that are running on Azure VMs to an Azure Backup Recovery Services vault.
+This article describes how to back up SAP HANA databases that are running on Azure VMs to an Azure Backup Recovery Services vault.
 
-In this article, you'll learn how to:
-> [!div class="checklist"]
->
-> * Create and configure a vault
-> * Discover databases
-> * Configure backups
-> * Run an on-demand backup job
+SAP HANA databases are critical workloads that require a low recovery-point objective (RPO) and long-term retention. You can back up SAP HANA databases running on Azure virtual machines (VMs) by using [Azure Backup](backup-overview.md).
 
 >[!NOTE]
 >See the [SAP HANA backup support matrix](sap-hana-backup-support-matrix.md) to know more about the supported configurations and scenarios.
@@ -51,7 +43,7 @@ More details around using these options are shared below:
 Private endpoints allow you to connect securely from servers inside a virtual network to your Recovery Services vault. The private endpoint uses an IP from the VNET address space for your vault. The network traffic between your resources inside the virtual network and the vault travels over your virtual network and a private link on the Microsoft backbone network. This eliminates exposure from the public internet. Read more on private endpoints for Azure Backup [here](./private-endpoints.md).
 
 > [!NOTE]
-> Private endpoints are supported for Azure Backup and Azure storage. Azure AD has support private end-points in private preview. Until they are generally available, Azure backup supports setting up proxy for AAD so that no outbound connectivity is required for HANA VMs. Refer to the [proxy support section](#use-an-http-proxy-server-to-route-traffic) for more details.
+> Private endpoints are supported for Azure Backup and Azure storage. Azure AD has support private end-points in private preview. Until they are generally available, Azure backup supports setting up proxy for Azure AD so that no outbound connectivity is required for HANA VMs. For more information, see the [proxy support section](#use-an-http-proxy-server-to-route-traffic).
 
 #### NSG tags
 
@@ -90,11 +82,11 @@ You can also use the following FQDNs to allow access to the required services fr
 > [!NOTE]
 > Currently, we only support HTTP Proxy for Azure Active Directory (Azure AD) traffic for SAP HANA. If you need to remove outbound connectivity requirements (for Azure Backup and Azure Storage traffic) for database backups via Azure Backup in HANA VMs, use other options, such as private endpoints.
 
-##### Using an HTTP proxy server for AAD traffic
+##### Using an HTTP proxy server for Azure AD traffic
 
 1. Go to the "opt/msawb/bin" folder
 2. Create a new JSON file named "ExtensionSettingsOverrides.json"
-3. Add a key-value pairs to the JSON file as follows:
+3. Add a key-value pair to the JSON file as follows:
 
     ```json
     {
@@ -112,7 +104,7 @@ You can also use the following FQDNs to allow access to the required services fr
     chown root:msawb ExtensionSettingsOverrides.json
     ```
 
-5. No restart of any service is required. The Azure Backup service will attempt to route the AAD traffic via the proxy server mentioned in the JSON file.
+5. No restart of any service is required. The Azure Backup service will attempt to route the Azure AD traffic via the proxy server mentioned in the JSON file.
 
 [!INCLUDE [How to create a Recovery Services vault](../../includes/backup-create-rs-vault.md)]
 
@@ -124,11 +116,11 @@ At the Recovery Services vault, you can enable Cross Region Restore. You must tu
 
 ## Discover the databases
 
-1. In the Azure portal, go to **Backup center** and click **+Backup**.
+1. In the Azure portal, go to **Backup center** and select **+Backup**.
 
    :::image type="content" source="./media/backup-azure-sap-hana-database/backup-center-configure-inline.png" alt-text="Screenshot showing to start checking for SAP HANA databases." lightbox="./media/backup-azure-sap-hana-database/backup-center-configure-expanded.png":::
 
-1. Select **SAP HANA in Azure VM** as the datasource type, select a Recovery Services vault to use for backup, and then click **Continue**.
+1. Select **SAP HANA in Azure VM** as the datasource type, select a Recovery Services vault to use for backup, and then select **Continue**.
 
    :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-vault.png" alt-text="Screenshot showing to select an SAP HANA database in Azure VM.":::
 
@@ -233,36 +225,11 @@ Specify the policy settings as follows:
 
 ## Run an on-demand backup
 
-Backups run in accordance with the policy schedule. You can run a backup on-demand as follows:
-
-1. In the vault menu, select **Backup items**.
-1. In **Backup Items**,  select the VM running the SAP HANA database, and then select **Backup now**.
-1. In **Backup Now**, choose the type of backup you want to perform. Then select **OK**.
-
-   The retention period of this backup is determined by the type of on-demand backup you have run.
-
-   - *On-demand full backups* are retained for a minimum of *45 days* and a maximum of *99 years*.
-   - *On-demand differential backups* are retained as per the *log retention set in the policy*.
-   - *On-demand incremental backups* aren't currently supported.
-
-1. Monitor the portal notifications. You can monitor the job progress in the vault dashboard > **Backup Jobs** > **In progress**. Depending on the size of your database, creating the initial backup may take a while.
-
-## Run SAP HANA Studio backup on a database with Azure Backup enabled
+Backups run in accordance with the policy schedule. Learn how to [run an on-demand backup](sap-hana-database-manage.md#run-on-demand-backups).
 
-If you want to take a local backup (using HANA Studio) of a database that's being backed up with Azure Backup, do the following:
+## Run SAP HANA native clients backup on a database with Azure Backup
 
-1. Wait for any full or log backups for the database to finish. Check the status in SAP HANA Studio / Cockpit.
-1. Disable log backups, and set the backup catalog to the file system for relevant database.
-1. To do this, double-click **systemdb** > **Configuration** > **Select Database** > **Filter (Log)**.
-1. Set **enable_auto_log_backup** to **No**.
-1. Set **log_backup_using_backint** to **False**.
-1. Set **catalog_backup_using_backint** to **False**.
-1. Take an on-demand full backup of the database.
-1. Wait for the full backup and catalog backup to finish.
-1. Revert the previous settings back to those for Azure:
-    * Set **enable_auto_log_backup** to **Yes**.
-    * Set **log_backup_using_backint** to **True**.
-    * Set **catalog_backup_using_backint** to **True**.
+You can run an on-demand backup using SAP HANA native clients to local file-system instead of Backint. Learn more how to [manage operations using SAP native clients](sap-hana-database-manage.md#manage-operations-using-sap-hana-native-clients).
 
 ## Next steps
 

articles/backup/sap-hana-database-manage.md

@@ -2,7 +2,7 @@
 title: Manage backed up SAP HANA databases on Azure VMs
 description: In this article, you'll learn common tasks for managing and monitoring SAP HANA databases that are running on Azure virtual machines.
 ms.topic: how-to
-ms.date: 12/21/2022
+ms.date: 12/23/2022
 author: v-amallick
 ms.service: backup
 ms.custom: ignite-2022
@@ -42,7 +42,8 @@ To run on-demand backups, follow these steps:
 
 1. Monitor the Azure portal notifications. To do so, on the Recovery Services vault dashboard, select **Backup Jobs**, and then select **In progress**. 
 
-   Depending on the size of your database, creating the initial backup might take a while.
+   >[!Note]
+   >Based on the size of your database, creating the initial backup might take a while.
 
 ## Monitor manual backup jobs
 
@@ -273,4 +274,4 @@ The Azure Backup service currently doesn't modify the HANA backup catalog as per
 
 ## Next steps
 
-[Troubleshoot common issues with SAP HANA database backups](./backup-azure-sap-hana-database-troubleshoot.md)
+- [Troubleshoot common issues with SAP HANA database backups](./backup-azure-sap-hana-database-troubleshoot.md)

articles/backup/sap-hana-database-with-hana-system-replication-backup.md

@@ -1,8 +1,8 @@
 ---
 title: Back up SAP HANA System Replication databases on Azure VMs (preview)    
 description: In this article, discover how to back up SAP HANA databases with HANA System Replication enabled.
-ms.topic: conceptual
-ms.date: 10/05/2022
+ms.topic: how-to
+ms.date: 12/23/2022
 author: v-amallick
 ms.service: backup
 ms.custom: ignite-2022
@@ -13,17 +13,6 @@ ms.author: v-amallick
 
 SAP HANA databases are critical workloads that require a low recovery-point objective (RPO) and long-term retention. This article describes how you can back up SAP HANA databases that are running on Azure virtual machines (VMs) to an Azure Backup Recovery Services vault by using [Azure Backup](backup-overview.md).
 
-In this article, you'll learn how to:
-
->[!div class="checklist"]
->- Create and configure a Recovery Services vault
->- Create a policy
->- Discover databases
->- Run the preregistration script
->- Configure backups
->- Run an on-demand backup
->- Run an SAP HANA Studio backup
-
 >[!Note]
 > For more information about the supported configurations and scenarios, see [SAP HANA backup support matrix](sap-hana-backup-support-matrix.md).
 
@@ -87,7 +76,7 @@ When a failover occurs, the users are replicated to the new primary, but *hdbuse
 
    `-bk CUSTOM_BACKUP_KEY_NAME` or `-backup-key CUSTOM_BACKUP_KEY_NAME`
 
-   If the password of this custom backup key expires, it could lead to backup and restore failures.
+   If the password of this custom backup key expires, it could lead to the backup and restore operations failure.
 
 1. Create the same customer backup user (with the same password) and key (in *hdbuserstore*) on both VMs/nodes.
 
@@ -212,41 +201,11 @@ To configure the policy settings, follow these steps:
 
 ## Run an on-demand backup
 
-The backup operations run in accordance with the policy schedule. You can also run an on-demand backup by doing the following:
-
-1. On the vault menu, select **Backup items**.
-
-1. On the **Backup items** pane, select **VM running the SAP HANA database**, and then select **Backup now**.
-
-1. On the **Backup now** pane, choose the **Type of backup** you want to perform, and then select **OK**. 
-
-   This backup will be retained for 45 days.
-
-To monitor the portal notifications and the job progress on the vault dashboard, select  **Backup Jobs** > **In progress**.
-
->[!Note]
->The time it takes to create the initial backup depends on the size of your database.
-
-## Run an SAP HANA Studio backup on a database with Azure Backup enabled
-
-To take a local backup, by using HANA Studio, of a database that's backed up with Azure Backup, do the following:
-
-1. After the full or log backups of the database are complete, check the status in the SAP HANA cockpit.
-
-1. Disable the log backups, and then set the backup catalog to the file system for the relevant database. To do so:
-
-   a. Double-click **systemdb**, and then select **Configuration** > **Database** > **Filter (Log)**.  
-   b. Set **enable_auto_log_backup** to **No**.  
-   c. Set **log_backup_using_backint** to **False**.  
-   d. Set **catalog_backup_using_backint** to **False**.
-
-1. Run an on-demand full backup of the database.
+Backups run in accordance with the policy schedule. Learn how to [run an on-demand backup](sap-hana-database-manage.md#run-on-demand-backups).
 
-1. After the full and catalog backups are complete, change the settings to point to Azure by doing the following:
+## Run SAP HANA native clients backup on a database with Azure Backup
 
-   a. Set **enable_auto_log_backup** to **Yes**.  
-   b. Set **log_backup_using_backint** to **True**.  
-   c. Set **catalog_backup_using_backint** to **True**.  
+You can run an on-demand backup using SAP HANA native clients to local file-system instead of Backint. Learn more how to [manage operations using SAP native clients](sap-hana-database-manage.md#manage-operations-using-sap-hana-native-clients).
 
 ## Next steps
 

articles/hdinsight/hbase/apache-hbase-migrate-new-version-new-storage-account.md

@@ -4,7 +4,7 @@ description: Learn how to migrate an Apache HBase cluster in Azure HDInsight to
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive
-ms.date: 05/06/2021
+ms.date: 12/23/2022
 ---
 
 # Migrate Apache HBase to a new version and storage account
@@ -270,4 +270,4 @@ To learn more about [Apache HBase](https://hbase.apache.org/) and upgrading HDIn
 - [Upgrade an HDInsight cluster to a newer version](../hdinsight-upgrade-cluster.md)
 - [Monitor and manage Azure HDInsight using the Apache Ambari Web UI](../hdinsight-hadoop-manage-ambari.md)
 - [Azure HDInsight versions](../hdinsight-component-versioning.md)
-- [Optimize Apache HBase](../optimize-hbase-ambari.md)
+- [Optimize Apache HBase](../optimize-hbase-ambari.md)

articles/hdinsight/hdinsight-create-non-interactive-authentication-dotnet-applications.md

@@ -4,7 +4,7 @@ description: Learn how to create non-interactive authentication Microsoft .NET a
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: "hdinsightactive, devx-track-csharp"
-ms.date: 12/23/2019
+ms.date: 12/23/2022
 
 ---
 

articles/hdinsight/hdinsight-hadoop-development-using-azure-resource-manager.md

@@ -4,7 +4,7 @@ description: How to migrate to Azure Resource Manager development tools for HDIn
 ms.service: hdinsight
 ms.custom: hdinsightactive, devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 02/21/2018
+ms.date: 12/23/2022
 ---
 # Migrating to Azure Resource Manager-based development tools for HDInsight clusters
 

articles/hdinsight/hdinsight-operationalize-data-pipeline.md

@@ -4,7 +4,7 @@ description: Set up and run an example data pipeline that is triggered by new da
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive
-ms.date: 12/25/2019
+ms.date: 12/23/2022
 ---
 
 # Operationalize a data analytics pipeline