You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-sap-hana-database-troubleshoot.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,7 @@
1
1
---
2
-
3
-
4
2
title: Troubleshoot SAP HANA databases backup errors
5
3
description: Describes how to troubleshoot common errors that might occur when you use Azure Backup to back up SAP HANA databases.
6
-
ms.topic: conceptual
4
+
ms.topic: troubleshooting
7
5
ms.date: 11/7/2019
8
6
---
9
7
@@ -81,27 +79,27 @@ Take care of inputs while restoring a single container database (SDC) for HANA t
81
79
82
80
Assume an SDC HANA instance "H21" is backed up. The backup items page will show the backup item name as **"h21(sdc)"**. If you attempt to restore this database to another target SDC, say H11, then following inputs need to be provided.
- By default, the restored db name will be populated with the backup item name i.e., h21(sdc)
86
+
- By default, the restored db name will be populated with the backup item name. In this case, h21(sdc).
89
87
- Selecting the target as H11 will NOT change the restored db name automatically. **It should be edited to h11(sdc)**. Regarding SDC, the restored db name will be the target instance ID with lowercase letters and 'sdc' appended in brackets.
90
88
- Since SDC can have only single database, you also need to click the checkbox to allow override of the existing database data with the recovery point data.
91
-
- Linux is case-sensitive. Therefore, be careful to preserve the case.
89
+
- Linux is case-sensitive. So be careful to preserve the case.
92
90
93
91
### Multiple Container Database (MDC) restore
94
92
95
-
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. Therefore, after the system DB is restored to a target instance, one needs to run the pre-registration script again. Only then the subsequent tenant DB restores will succeed.
93
+
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.
96
94
97
95
## Upgrading from SAP HANA 1.0 to 2.0
98
96
99
-
If you're protecting SAP HANA 1.0 databases and wish to upgrade to 2.0, then perform the steps outlined below:
97
+
If you're protecting SAP HANA 1.0 databases and wish to upgrade to 2.0, then perform the following steps:
100
98
101
99
-[Stop protection](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) with retain data for old SDC database.
102
100
- Perform the upgrade. After completion, the HANA is now MDC with a system DB and tenant DB(s)
103
101
- Rerun [pre-registration script](https://aka.ms/scriptforpermsonhana) with correct details of (sid and mdc).
104
-
- Re-register extension for the same machine in Azure Portal (Backup -> view details -> Select the relevant Azure VM -> Re-register).
102
+
- Re-register extension for the same machine in Azure portal (Backup -> view details -> Select the relevant Azure VM -> Re-register).
105
103
- 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).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-system-state-troubleshoot.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: Troubleshoot System State Backup
3
3
description: In this article, learn how to troubleshoot issues in System State Backup for on-premises Windows servers.
4
4
ms.reviewer: srinathv
5
-
ms.topic: conceptual
5
+
ms.topic: troubleshooting
6
6
ms.date: 07/22/2019
7
7
---
8
8
9
9
# Troubleshoot System State Backup
10
10
11
-
This article describes solutions for issues that you might encounter while using System State Backup.
11
+
This article describes solutions for issues that you might come across while using System State Backup.
12
12
13
13
## Basic troubleshooting
14
14
@@ -24,16 +24,16 @@ We recommend you perform the below validation, before you start troubleshooting
24
24
-[Ensure unsupported drives and files with unsupported attributes are excluded from backup](backup-support-matrix-mars-agent.md#supported-drives-or-volumes-for-backup)
25
25
- Ensure **System Clock** on the protected system is configured to correct time zone <br>
26
26
-[Ensure that the server has at least .Net Framework version 4.5.2 and higher](https://www.microsoft.com/download/details.aspx?id=30653)<br>
27
-
- If you are trying to **reregister your server** to a vault, then: <br>
28
-
- Ensure the agent is uninstalled on the server and it is deleted from portal <br>
27
+
- If you're trying to **reregister your server** to a vault, then: <br>
28
+
- Ensure the agent is uninstalled on the server and it's deleted from the portal <br>
29
29
- Use the same passphrase that was initially used for registering the server <br>
30
-
-In case of offline backup, ensure that Azure PowerShell version 3.7.0 is installed on both source and copy computer before you begin offline backup operation
30
+
-If this is an offline backup, ensure that Azure PowerShell version 3.7.0 is installed on both source and copy computer before you begin offline backup operation
31
31
-[Consideration when Backup agent is running on an Azure virtual machine](https://aka.ms/AB-AA4dwtr)
32
32
33
33
### Limitation
34
34
35
35
- Recovering to different hardware using System State recovery is not recommended by Microsoft
36
-
- System State backup currently supports "on-premises" Windows servers, this functionality is not available for Azure VMs.
36
+
- System State backup currently supports "on-premises" Windows servers. This functionality isn't available for Azure VMs.
37
37
38
38
## Prerequisites
39
39
@@ -47,7 +47,7 @@ Ensure Windows Server Backup is installed and enabled in the server. To check th
47
47
Get-WindowsFeature Windows-Server-Backup
48
48
```
49
49
50
-
If the output displays the **Install State** as **available**, then it means Windows Server backup feature is available for the installation but not installed on the server. However if Windows Server Backup is not installed, then use one of the below methods to install it.
50
+
If the output displays the **Install State** as **available**, then it means Windows Server backup feature is available for the installation but not installed on the server. However, if Windows Server Backup isn't installed, then use one of the methods below to install it.
51
51
52
52
#### Method 1: Install Windows Server Backup using PowerShell
53
53
@@ -81,7 +81,7 @@ To install Windows Server Backup using Server Manager, perform the steps below:
81
81
82
82
### System Volume information permission
83
83
84
-
Ensure that the Local SYSTEM has full control on **System Volume Information** folder located in the volume where windows is installed. Usually this is **C:\System Volume Information**. Windows Server backup can fail if the above permissions are not set correctly
84
+
Ensure that the Local SYSTEM has full control on the **System Volume Information** folder located in the volume where Windows is installed. Usually this is **C:\System Volume Information**. Windows Server backup can fail if the above permissions are not set correctly
To validate Windows Server Backup status, perform the steps below:
100
+
To validate Windows Server Backup status, perform the following steps:
101
101
102
102
- Ensure WSB PowerShell is running
103
103
104
-
- Run `Get-WBJob` from an elevated PowerShell and make sure it does not return the following error:
104
+
- Run `Get-WBJob` from an elevated PowerShell and make sure it doesn't return the following error:
105
105
106
106
> [!WARNING]
107
107
> Get-WBJob: The term 'Get-WBJob' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
108
108
109
-
- If it fails with this error, then reinstall the Windows Server Backup feature on the server machine as mentioned in the step 1 prerequisites.
109
+
- If it fails with this error, then reinstall the Windows Server Backup feature on the server machine as mentioned in step 1 of the prerequisites.
110
110
111
111
- Ensure WSB backup is working properly, by running the below command from elevated command prompt:
112
112
@@ -126,7 +126,7 @@ If the job fails, it indicates a WSB issue that would result in MARS agent Syste
126
126
127
127
| Symptom | Cause | Resolution
128
128
| -- | -- | --
129
-
| - MARS agent fails with error message: “WSB job failed with VSS errors. Check VSS event logs to resolve the failure”<br/><br/> - Following error log is present in VSS Application event logs: “A VSS writer has rejected an event with error 0x800423f2, the writer's timeout expired between the Freeze and Thaw events.”| VSS writer is unable to complete in time due to lack of CPU and memory resources on the machine <br/><br/> Another backup software is already using the VSS writer, as a result snapshot operation could not complete for this backup | Wait for CPU/memory to be freed up on system or abort processes taking too much memory/CPU and try the operation again <br/><br/> Wait for the ongoing backup to complete and try the operation at a later point when no backups are running on the machine
129
+
| - MARS agent fails with error message: “WSB job failed with VSS errors. Check VSS event logs to resolve the failure”<br/><br/> - Following error log is present in VSS Application event logs: “A VSS writer has rejected an event with error 0x800423f2, the writer's timeout expired between the Freeze and Thaw events.”| VSS writer is unable to complete in time due to lack of CPU and memory resources on the machine <br/><br/> Another backup software is already using the VSS writer, as a result snapshot operation could not complete for this backup | Wait for CPU/memory to be freed up on system or abort the processes taking too much memory/CPU and try the operation again. <br/><br/> Wait for the ongoing backup to complete and try the operation at a later point when no backups are running on the machine.
0 commit comments