Merge pull request #115649 from dcurwin/saphana-may19-2020

ttorble · web-flow · commit d7cbb044fd35 · 2020-05-20T10:25:41.000+01:00
Updates to SAPHANA troubleshooting
diff --git a/articles/backup/backup-azure-sap-hana-database-troubleshoot.md b/articles/backup/backup-azure-sap-hana-database-troubleshoot.md
@@ -57,19 +57,12 @@ Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [
 | **Possible causes**    | The log backup destination may have been updated from backint to file system or the backint executable may have been changed |
 | **Recommended action** | Trigger a full backup to resolve the issue                   |
 
-### UserErrorIncomaptibleSrcTargetSystsemsForRestore
-
-| Error Message      | <span style="font-weight:normal">The source and target systems for restore are incompatible</span>    |
-| ------------------ | ------------------------------------------------------------ |
-| **Possible causes**    | The target system for restore is incompatible with the source |
-| **Recommended action** | Refer to the SAP Note [1642148](https://launchpad.support.sap.com/#/notes/1642148) to learn about the restore types supported today |
-
 ### UserErrorSDCtoMDCUpgradeDetected
 
 | Error Message      | <span style="font-weight:normal">SDC to MDC upgrade detected</span>                                   |
 | ------------------ | ------------------------------------------------------------ |
 | **Possible causes**    | The SAP HANA instance has been upgraded from SDC to MDC. Backups will fail after the update. |
-| **Recommended action** | Follow the steps listed in the [Upgrading from SAP HANA 1.0 to 2.0 section](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot#upgrading-from-sap-hana-10-to-20) to resolve the issue |
+| **Recommended action** | Follow the steps listed in the [SDC to MDC upgrade](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot#sdc-to-mdc-upgrade-with-a-change-in-sid) to resolve the issue |
 
 ### UserErrorInvalidBackintConfiguration
 
@@ -83,7 +76,7 @@ Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [
 |Error Message  |The source and target systems for restore are incompatible  |
 |---------|---------|
 |Possible causes   | The source and target systems selected for restore are incompatible        |
-|Recommended action   |   Ensure that your restore scenario is not in the following list of possible incompatible restores: <br><br>   **Case 1:** SYSTEMDB cannot be renamed during restore.  <br><br> **Case 2:** Source - SDC and target - MDC : The source database cannot be restored as SYSTEMDB or tenant DB on the target. <br><br> **Case 3:** Source - MDC and target - SDC : The source database (SYSTEMDB or tenant DB) cannot be restored to the target. <br><br>  For more information, refer to the note 1642148 in the [SAP support launchpad](https://launchpad.support.sap.com). |
+|Recommended action   |   Ensure that your restore scenario isn't in the following list of possible incompatible restores: <br><br>   **Case 1:** SYSTEMDB cannot be renamed during restore.  <br><br> **Case 2:** Source - SDC and target - MDC: The source database cannot be restored as SYSTEMDB or tenant DB on the target. <br><br> **Case 3:** Source - MDC and target - SDC: The source database (SYSTEMDB or tenant DB) cannot be restored to the target. <br><br>  For more information, see note **1642148** in the [SAP support launchpad](https://launchpad.support.sap.com). |
 
 ## Restore checks
 
@@ -106,25 +99,83 @@ Note the following points:
 
 In multiple container databases for HANA, the standard configuration is SYSTEMDB + 1 or more Tenant DBs. Restoring an entire SAP HANA instance means to restore both SYSTEMDB and Tenant DBs. One restores SYSTEMDB first and then proceeds for Tenant DB. System DB essentially means to override the system information on the selected target. This restore also overrides the BackInt related information in the target instance. So after the system DB is restored to a target instance, run the pre-registration script again. Only then the subsequent tenant DB restores will succeed.
 
-## Upgrading from SAP HANA 1.0 to 2.0
+## Back up a replicated VM
+
+### Scenario 1
+
+The original VM was replicated using Azure Site Recovery or Azure VM backup. The new VM was built to simulate the old VM. That is, the settings are exactly the same. (This is because the original VM was deleted and the restore was done from VM backup or Azure Site Recovery).
+
+This scenario could include two possible cases. Learn how to back up the replicated VM in both of these cases:
+
+1. The new VM created has the same name, and is in the same resource group and subscription as the deleted VM.
+
+    - The extension is already present on the VM, but isn't visible to any of the services
+    - Run the pre-registration script
+    - Re-register the extension for the same machine in the Azure portal (**Backup** -> **View details** -> Select the relevant Azure VM -> Re-register)
+    - The already existing backed up databases (from the deleted VM) should then start successfully being backed up
+
+2. The new VM created has either:
+
+    - a different name than the deleted VM
+    - the same name as the deleted VM but is in a different resource group or subscription (as compared to the deleted VM)
+
+    If this is the case, then do the following steps:
+
+    - The extension is already present on the VM, but isn't visible to any of the services
+    - Run the pre-registration script
+    - If you discover and protect the new databases, you'll start seeing duplicate active databases in the portal. To avoid this, [Stop protection with retain data](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) for the old databases. Then continue with the remaining steps.
+    - Discover the databases to enable backup
+    - Enable backups on these databases
+    - The already existing backed up databases (from the deleted VM) will continue to be stored in the vault (with their backups being retained according to the policy)
+
+### Scenario 2
+
+The original VM was replicated using Azure Site Recovery or Azure VM backup. The new VM was built out of the content – to be used as a template. This is a new VM with a new SID.
+
+Follow these  steps to enable backups on the new VM:
+
+- The extension is already present on the VM, but not visible to any of the services
+- Run the pre-registration script. Based on the SID of the new VM, two scenarios can arise:
+  - The original VM and the new VM have the same SID. The pre-registration script will run successfully.
+  - The original VM and the new VM have different SIDs. The pre-registration script will fail. Contact support to get help in this scenario.
+- Discover the databases that you want to back up
+- Enable backups on these databases
+
+## SDC version upgrade or MDC version upgrade on the same VM
+
+Upgrades to the OS, SDC version change, or MDC version change that don't cause a SID change can be handled as follows:
+
+- Ensure that the new OS version, SDC, or MDC version are currently [supported by Azure Backup](sap-hana-backup-support-matrix.md#scenario-support)
+- [Stop protection with retain data](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) for the database
+- Perform the upgrade or update
+- Rerun the pre-registration script. Usually, the upgrade process removes the necessary roles. Running the pre-registration script will help verify all the required roles
+- Resume protection for the database again
+
+## SDC to MDC upgrade with no change in SID
 
-If you're protecting SAP HANA 1.0 databases and wish to upgrade to 2.0, then perform the following steps:
+Upgrades from SDC to MDC that don't cause a SID change can be handled as follows:
 
-- [Stop protection](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) with retain data for old SDC database.
-- Perform the upgrade. After completion, the HANA is now MDC with a system DB and tenant DB(s)
-- Rerun [pre-registration script](https://aka.ms/scriptforpermsonhana) with correct details of (sid and mdc).
-- Re-register extension for the same machine in Azure portal (Backup -> view details -> Select the relevant Azure VM -> Re-register).
-- Click Rediscover DBs for the same VM. This action should show the new DBs in step 2 with correct details (SYSTEMDB and Tenant DB, not SDC).
-- Configure backup for these new databases.
+- Ensure that the new MDC version is currently [supported by Azure Backup](sap-hana-backup-support-matrix.md#scenario-support)
+- [Stop protection with retain data](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) for the old SDC database
+- Perform the upgrade. After completion, the HANA system is now MDC with a system DB and tenant DBs
+- Rerun the [pre-registration script](https://aka.ms/scriptforpermsonhana)
+- Re-register the extension for the same machine in the Azure portal (**Backup** -> **View details** -> Select the relevant Azure VM -> Re-register)
+- Click **Rediscover DBs** for the same VM. This action should show the new DBs in step 3 as SYSTEMDB and Tenant DB, not SDC
+- The older SDC database will continue to exist in the vault and have old backed-up data retained according to the policy
+- Configure backup for these databases
 
-## Upgrading without an SID change
+## SDC to MDC upgrade with a change in SID
 
-Upgrades to OS or SAP HANA that don't cause a SID change can be handled as outlined below:
+Upgrades from SDC to MDC that cause a SID change can be handled as follows:
 
-- [Stop protection](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) with retain data for the database
-- Perform the upgrade.
-- Rerun the [pre-registration script](https://aka.ms/scriptforpermsonhana). Usually, we have seen upgrade process removes the necessary roles. Running the pre-registration script will help verify all the required roles.
-- [Resume protection](sap-hana-db-manage.md#resume-protection-for-an-sap-hana-database) for the database again
+- Ensure that the new MDC version is currently [supported by Azure Backup](sap-hana-backup-support-matrix.md#scenario-support)
+- **Stop protection with retain data** for the old SDC database
+- Perform the upgrade. After completion, the HANA system is now MDC with a system DB and tenant DBs
+- Rerun the [pre-registration script](https://aka.ms/scriptforpermsonhana) with correct details (new SID and MDC). Due to a change in SID, you may face issues with successfully running the script. Contact Azure Backup support if you face issues.
+- Re-register the extension for the same machine in the Azure portal (**Backup** -> **View details** -> Select the relevant Azure VM -> Re-register)
+- Click **Rediscover DBs** for the same VM. This action should show the new DBs in step 3 as SYSTEMDB and Tenant DB, not SDC
+- The older SDC database will continue to exist in the vault and have old backed up data retained according to the policy
+- Configure backup for these databases
 
 ## Re-registration failures
 
@@ -134,7 +185,7 @@ Check for one or more of the following symptoms before you trigger the re-regist
 - If the **Backup Status** area for the backup item is showing **Not reachable**, rule out all the other causes that might result in the same status:
 
   - Lack of permission to perform backup-related operations on the VM
-  - The VM is shutdown, so backups cannot take place
+  - The VM is shut down, so backups can't take place
   - Network issues
 
 These symptoms may arise for one or more of the following reasons:
diff --git a/articles/backup/sap-hana-db-manage.md b/articles/backup/sap-hana-db-manage.md
@@ -203,13 +203,13 @@ To resume protection for an SAP HANA database:
 
 * On the **Backup policy** menu, select a policy, and then select **Save**.
 
-### Upgrading from SAP HANA 1.0 to 2.0
+### Upgrading from SDC to MDC
 
-Learn how to continue backup for an SAP HANA database [after upgrading from SAP HANA 1.0 to 2.0](backup-azure-sap-hana-database-troubleshoot.md#upgrading-from-sap-hana-10-to-20).
+Learn how to continue backup for an SAP HANA database [after upgrading from SDC to MDC](backup-azure-sap-hana-database-troubleshoot.md#sdc-to-mdc-upgrade-with-a-change-in-sid).
 
-### Upgrading without a SID change
+### Upgrading from SDC to MDC without a SID change
 
-Learn how to continue backup of an SAP HANA database whose [SID has not changed after upgrade](backup-azure-sap-hana-database-troubleshoot.md#upgrading-without-an-sid-change).
+Learn how to continue backup of an SAP HANA database whose [SID has not changed after upgrade from SDC to MDC](backup-azure-sap-hana-database-troubleshoot.md#sdc-to-mdc-upgrade-with-no-change-in-sid).
 
 ### Unregister an SAP HANA instance
 
diff --git a/articles/backup/sap-hana-faq-backup-azure-vm.md b/articles/backup/sap-hana-faq-backup-azure-vm.md
@@ -44,9 +44,9 @@ Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [
 
 Running the pre-registration script sets the required permissions to allow Azure to back up SAP HANA databases. You can find more what the pre-registration script does [here](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does).
 
-### Will backups work after migrating SAP HANA from 1.0 to 2.0?
+### Will backups work after migrating SAP HANA from SDC to MDC?
 
-Refer to [this section](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot#upgrading-from-sap-hana-10-to-20) of the troubleshooting guide.
+Refer to [this section](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot#sdc-to-mdc-upgrade-with-a-change-in-sid) of the troubleshooting guide.
 
 ### Can Azure HANA Backup be set up against a virtual IP (load balancer) and not a virtual machine?
 
