FAQ about SAP HANA backup and solutions - Cloud Backup - Alibaba Cloud Documentation Center

This topic provides answers to frequently asked questions (FAQs) about the SAP HANA backup feature of Cloud Backup.

What is SAP HANA backup

You can use Cloud Backup to manage backups for your SAP system on Alibaba Cloud.

SAP has certified Cloud Backup for integration with SAP HANA Backint. Cloud Backup is compatible with SAP HANA 1.0 and 2.0. You can use a Cloud Backup client to back up SAP HANA databases that are deployed on Elastic Compute Service (ECS) instances and restore the databases as needed. For more information, see Overview of the SAP HANA backup feature.

You can also back up on-premises files and VMware virtual machines in your data centers to backup vaults on Alibaba Cloud. Cloud Backup provides easy-to-use native data protection features for various types of data on Alibaba Cloud, such as ECS files, Oracle and MS SQL Server databases, NAS, and data in OSS. For more information, see What is Cloud Backup?.

Scope of SAP HANA backup

SAP HANA instances deployed on Alibaba Cloud ECS instances
Backint supports multitenant database containers (MDCs) in SAP HANA 1.0 SPS 09 (Revision 94) or later and SAP HANA 2.0 SPS 01 or later. Backint does not support single-container systems in SAP HANA 1.0.

How do I check the status and logs of the Cloud Backup client after I register an SAP HANA instance?

After you register an SAP HANA instance in the Cloud Backup console, it enters the Registered state.

The default log path is /opt/alibabacloud/hbrclient/logs.

You can run the ps axu|grep hybrid command to view the status of the Cloud Backup client. If the process information is returned, the Cloud Backup client has started and is running properly.

root     11472  0.0  0.0   9288  1552 pts/2    S+   16:11   0:00 grep --color=auto hybrid
root     30480  0.0  0.2  56296 17028 ?        Ssl  13:26   0:04 /opt/alibabacloud/hbr/client/hybridbackup -p 0

Backup log paths

HANA database backup client logs: /opt/alibabacloud/hbr/logs

HANA database Backint logs: /usr/sap/{SID}/SYS/global/hdb/logs/

HANA database backup logs: /usr/sap/{SID}/HDB{InstanceNumber}/{hostname}/trace/DB_{DBNAME}/backup.log

The HANA database automatically manages and stores log records. You can use HANA Studio or other related tools to run the following SQL statement to query and retrieve the content of these log backups.

select CAT.* from SYS_DATABASES.M_BACKUP_CATALOG CAT JOIN SYS_DATABASES.M_BACKUP_CATALOG_FILES FILS on CAT.BACKUP_ID = FILS.BACKUP_ID where CAT.entry_type_name = 'log backup' and CAT.state_name = 'successful' and FILS.DESTINATION_TYPE_NAME = 'backint' and CAT.database_name = 'SYSTEMDB' order by sys_end_time

What do I do if the SAP HANA client installation fails with the error "multiple /usr/sap/<SID>/SYS/global/hdb/opt paths exist"?

Connect to the target ECS instance.
For the SAP HANA instances that do not require backups, rename /usr/sap/<SID>/SYS/global/hdb/opt to /usr/sap/<SID>/SYS/global/hdb/opt_backup.
Return to the Cloud Backup console and reinstall the Cloud Backup client for the SAP HANA instance.

What do I do if the database cannot be connected during a same-instance restore?

If you create a restore job to restore a database to its source instance and cannot connect to the database, perform the following steps:

Check whether the HANA database is running.
Check whether the SSL certificate has expired. If it has, choose one of the following options:
- Replace the certificate.
- Configure the console to not validate the SSL certificate.

What do I do if no data is retrieved during a same-instance restore?

If you create a restore job to restore a database to its source instance and find that no data is present, check whether the client status is normal.

What do I do if I cannot find the backup record during a restore

Issue
When you create a restore job after you reinstall the operating system, roll back a snapshot, or uninstall and reinstall the SAP HANA database on an ECS instance, you may not be able to find the backup record.
Root Cause Analysis
When you perform a same-instance restore, Cloud Backup first searches for backup records in the preconfigured SAP HANA backup path. If the operating system of the ECS instance is reinstalled, a snapshot is rolled back, or the SAP HANA database is uninstalled and reinstalled, the backup records stored in the HANA database may be cleared.
Solution
- If the backup was created with the Use Backint for Catalog Backup option enabled, you can restore the database. Perform the following steps:
  1. Go to the source SAP HANA instance and delete the ECS instance node.
  2. Register a new HANA instance with the same parameters as before. Install the backup client and add the deleted ECS instance node.
  3. Create a restore job. Select the newly registered HANA instance for restoration. This starts a cross-instance restore job from the source instance.
- After the database is restored, you can delete the source SAP HANA instance if its backup data is no longer needed. If you have not enabled Use Backint for Catalog Backup, the backup records cannot be found, but the backup data still exists. For more information, see Restore a database to an SAP HANA instance by specifying a prefix.

What do I do if an SQL statement fails to run in HANA?

If the HANA log space is full, SQL statements may fail to execute. To resolve this, clear the disk space and try again.

How do I manually delete backup records?

You cannot manually delete SAP HANA backup data from Cloud Backup. The data expires automatically based on the retention period. To delete backup records from the SAP HANA catalog, you can use the following option in SAP Studio.

Instance activated: Internal error on the database page

If an error message appears on the SAP HANA backup page in the Cloud Backup console, check the HANA license. Connect to SYSTEMDB and run the following SQL query to check whether all databases have a license. If the query returns an empty result, it indicates that a database is missing a license.

SELECT * FROM M_LICENSE

For more information, see https://launchpad.support.sap.com/#/notes/2619291.

Why does SAP HANA backup fail, and how do I fix it?

When you perform an SAP HANA backup, the client connects to the HANA instance and sends an SQL statement to start the backup job. If the SQL statement runs successfully, the client continues to send query statements to HANA to retrieve the backup progress and final status. If a failure occurs during the backup, the related error message is recorded in the client log. By correlating the job time with the log records, you can effectively track and analyze the issue. The following are some common errors:

If the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log, it indicates a significant difference between the local time and the server time. Adjust the local time. A best practice is to enable automatic NTP synchronization to ensure time consistency.
```
time="2021-11-04T16:24:17+08:00" level=info msg="InvalidTimeStamp.Expired retry, retryDelay: 5000 ms, retry times: 14" file=client.go line=377
```
If a backup job fails or all backup jobs are canceled (not manually), and the backup.log file contains a 'No space left on device' message, the local disk space is full. Clear the disk space before you try to back up again.

If the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log and no error message is displayed in the console, it may be because you configured another scheduled backup job that conflicts with the SAP HANA backup job.

time="2021-08-29T01:10:00+08:00" level=error msg="Execute hana backup failed : hbr: client returned error: ErrorCode=HanaSqlError, ErrorMessage=SQL Error 447 - backup could not be completed: [110122] A data backup cannot be created because another data backup is running or a storage snapshot has been prepared., Data=, values=map[]" file=hanabackupjob.go line=98

If an unexpected backup failure or a non-execution alert occurs, and you do not see a completed backup record in the backup history, the cause may be an MQTT request timeout. Check the log in /opt/alibabacloud/hbr/logs/hybridbackup.log at the corresponding time.

If the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log, the password may have expired and must be updated.

time="2023-11-26T00:00:08+08:00" level=error msg="SAP Error: SQL Error 447 - backup could not be completed: [110203] Not all data could be written: Expected 4096 but transferred 0, [110507] Backint exited with exit code 1 instead of 0. console output: Internal Error: The user account is in unknown status. " file=errorwrapper.go line=28

If the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log, the server may have rejected the request because the timestamp is inaccurate.
```
time="2024-06-23T01:36:46+08:00" level=error msg="HBR DescribeUserBusinessStatus returns hbr: service returned error: StatusCode=400, Code=InvalidSecurityToken.Expired, Message=Specified SecurityToken is expired., RequestId=A6CDF56F-CA56-53E8-9342-24E19F768D40" file=client.go line=428
```
Check the timestamp in one of the following ways:
- Run the following command and check the System Time in the output. This parameter indicates the difference between the system time and the NTP time. If the drift is within a few milliseconds, the timestamp is normal.
```
sudo chronyc tracking
```
- Run the following command and check the offset in the output. This parameter indicates the difference between the system time and the NTP time. If the drift is within a few milliseconds, the timestamp is normal.
```
ntpd -q
```
If there is no failure record in the console, but you see the following error message in the /opt/alibabacloud/hbr/logs/hybridbackup.log file:
```
SQL Error 447 - backup could not be completed: [110122] A data backup cannot be created because another data backup is running or a storage snapshot has been prepared.
```
You can check this as follows:
- Whether other backup software is performing a HANA backup at the same time.
- Ensure you have a data backup before restarting the HANA instance. For more information, see the official SAP HANA knowledge base.
If the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log:
```
[447] backup could not be completed, [1000002] Allocation failed ; $size$=16777216; $name$=DataPage; $type$=pool; $inuse_count$=6; $allocated_size$=17104896; $failure_type$=GLOBAL_ALLOCATION_LIMIT; $failure_flag$= (early exit)
```
And there is a failure record in the console.
- This issue occurs because SAP HANA is unable to allocate more memory, causing an out-of-memory (OOM) error. For more information, see SAP HANA BACKUP Failing Due to Out of Memory.
- For the solution, see SAP HANA Solutions.
- For more information about the causes of OOM, see SAP HANA Service Support.
If the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log:
```
"SQL Error 3584 - distributed SQL error:  [2617] executor: plan operation execution failed with an exception.exception:exception 30160: Failed to read password from key store. $name=$M_BACKUP_CONFIGURATION. $col=$IS_ROOT_KEY_BACKUP_PASSWORD_SET. $ci=$23\n,Exception in executor plan00468@$spdr-db:31001 while executing pop 1, Data=[], values=[]map[]"
```
And the backup job status is "Failed" in the console.
This error message indicates that the SAP HANA system returned SQL error 3584 when it ran the backup SQL statement. Specifically, an exception occurred when reading the password from the key store. This is usually an issue with SAP HANA components. Contact your SAP HANA operations and maintenance (O&M) engineer or vendor for assistance.
If the InstanceRAMRoleNotFound error message or the following error message appears in the /opt/alibabacloud/hbr/logs/hybridbackup.log file:
```
Failed to get client credential from Instance RAM role. hbr: client returned error: ErrorCode=InstanceRAMRoleNotFound, ErrorMessage=InstanceRAMRoleNotFound
```
And the restore job status is stuck at "Running" in the console and cannot be stopped.
This error indicates that the AliyunECSAccessingHBRRole role on the ECS instance has been revoked. Log on to the ECS console to attach the role again and restart the Cloud Backup client. For more information, see Why is the AliyunECSAccessingHBRRole role attached to an ECS instance? Can the role be revoked?

Why is the AliyunECSAccessingHBRRole role attached to an ECS instance? Can this role be revoked?

To ensure that SAP HANA backup works correctly, you must install the Cloud Backup client on the ECS instance that runs SAP HANA. The client depends on the AliyunECSAccessingHBRRole role to obtain a security token and communicate with the server side. If this role is revoked, the backup and restore features will not work. Therefore, to ensure that SAP HANA backup runs correctly, perform the following steps:

Log on to the ECS console to attach the AliyunECSAccessingHBRRole role to the ECS instance again. For more information, see Attach the RAM role to an ECS instance.
Run the systemctl restart hybridbackup command to restart the Cloud Backup client or uninstall and reinstall the client.

What do I do if an error occurs when I view a backup job?

Issue

The following error occurs when you view a backup job.

And the following error message appears in /opt/alibabacloud/hbr/logs/hybridbackup.log:

time="2023-12-01T14:38:23+08:00" level=error msg="prepare stmt SELECT count(*) FROM sys_databases.M_BACKUP_PROGRESS error : SQL Error 437 - only commands for license handling are allowed in current state" file=db.go line=220

Solution
HANA 2.0 requires multi-user mode for license registration.

What do I do if a restore job fails?

Issue: A restore job fails if you restore data from an earlier backup point by specifying a time or a backup, and then attempt another restore from the latest backup point by specifying a time.

Solution: When you perform multiple consecutive restores, use the specified backup method and select a specific backup point for each restore job.

Can Cloud Backup back up an SAP HANA instance deployed in an on-premises data center?

No. Cloud Backup does not support backups of SAP HANA databases that are deployed in a self-managed data center. However, you can back up the SAP HANA databases to on-premises storage, and then back up the database files to the cloud using the local file backup feature. For more information, see Back up local files.

Do I need to purchase other cloud storage products to back up SAP HANA?

No. Cloud Backup directly calls the SAP HANA backup API through Backint. Backup data is streamed to the cloud storage on the Cloud Backup backend and does not use the storage space of the SAP HANA ECS instance. Therefore, you do not need to purchase other cloud storage products.

Can I use the "SAP HANA Backup" feature of Cloud Backup for a single-container SAP HANA instance?

No. The SAP HANA backup feature in the Cloud Backup console uses the Backint API. There are two solutions:

Solution 1: Back up the SAP HANA database to the disk of an ECS instance, and then use the local file backup feature of Cloud Backup to back up the database. For more information, see Back up local files.
Solution 2: Convert the SAP HANA instance from a single-container to a multi-container system. For specific instructions, see the official SAP documentation or consult your SAP partner.

Can backups for different SAP HANA environments be stored in different backup vaults?

Yes. When you register an SAP HANA instance in the Cloud Backup console, you can create a new backup vault or select an existing one. The following restore methods are currently supported:

Does SAP HANA backup support cross-region or cross-account backup?

Yes, cross-region and cross-account backups are supported.

Cross-region backup: You can use the cross-region backup feature.
Cross-account backup: You can use the Backup Vault Cross-account Replication or Cross-account Backup feature.

What should I note when I configure an SAP HANA backup?

If your SAP HANA is deployed in a high availability (HA) architecture, set the host address to the high-availability virtual IP address (HAVIP) when you register the SAP HANA instance. This ensures that backup jobs can run correctly after a cluster switchover.
By default, the parameters for backing up the SAP HANA log and catalog using Backint are not enabled. You must manually enable this configuration for the System DB and each Tenant DB to ensure that database restore operations can be completed when needed.

Note

The parameter settings of a Tenant DB are inherited from the System DB. Carefully check whether the parameter settings for each database meet your requirements.

How do I set the data retention period for SAP HANA backups?

Log on to the Cloud Backup console and select the instance.
On the Databases tab, select a System DB or Tenant DB and click More > Configure Retention Policy.

The backup retention period defaults to Permanent. You can change this value as needed.

Parameter	Note
Retention Policy	Custom Select this option to set a custom time for the daily retention job and a retention period for the backup data. Permanent If you select this option, Cloud Backup permanently retains your backup data.
Retention Job Interval	This parameter is required only if you set the Retention Policy parameter to Custom. Select the time to run the retention job each day. The time is accurate to the second. Note Avoid periods when backup jobs or other business operations are busy.
Retention period	This parameter is required only if you set the Retention period setting to Custom. Select the retention period for the backup data. Unit: days, weeks, months, or years. The minimum retention period is 1 day, and the maximum retention period is 10 years. Note When the retention period expires, Cloud Backup automatically deletes the catalog records and data associated with the expired BACKINT and File Backup. This data cannot be recovered after deletion. Configure the retention period carefully as needed. Changes to the retention period apply to historical backups. The data retention job runs once per day. However, backup vault statistics may be delayed by 12 to 24 hours. Therefore, after you change the retention period, it can take up to three calendar days for the data volume in the backup vault to reflect the change. If you make a significant change, such as shortening the retention period from 2 years to 2 months, Cloud Backup controls the execution speed of the data retention job. As a result, the reduction in the data volume of the backup vault may take some time.

Why do I receive a text message or email alert that a backup failed, but the backup job is shown as successful in the Cloud Backup console?

Symptoms
You receive a text message or email alert: "The backup of database XXX in your SAP HANA instance XXX (Instance ID: cl-xxxxxxxx) failed. The backup ID is 0. Please log on to the console to check and fix it." However, when you log on to the Cloud Backup console, the backup record for that job shows that it completed successfully.

Cause

Other backup software may also be running during the backup, or SAP HANA experiences an exception. You can check the log file at /opt/alibabacloud/hbrclient/logs/hybridbackup.log for a similar alert snippet around the time of the alert:

time="2024-08-29T01:35:01+08:00" level=error msg="Execute sql `BACKUP DATA FOR PRD USING BACKINT ('/usr/sap/XXX/SYS/global/hdb/backint/DB_HHH/COMPLETE_DATA_BACKUP_2024_08_29_01_30') ASYNCHRONOUS` failed : SQL Error 447 - backup could not be completed: [110122] A data backup cannot be created because another data backup is running or a storage snapshot has been prepared." file=db.go line=163
time="2024-08-29T01:35:01+08:00" level=error msg="SAP Error: SQL Error 447 - backup could not be completed: [110122] A data backup cannot be created because another data backup is running or a storage snapshot has been prepared." file=errorwrapper.go line=28

This error indicates that the Cloud Backup client has executed an SQL statement for backup by connecting to SAP HANA. SAP HANA returns error code 447 to inform the Cloud Backup client that the command fails to be executed. However, the backup job triggered by the command may have been executed correctly in the SAP HANA backend. For more information, see SAP Knowledge Base.

Solution
If this is an occasional issue and you have confirmed on the backup jobs page that the backup was successful, you can ignore this alert. However, if this problem occurs frequently, restart the HANA instance during off-peak hours to resolve the issue, after you ensure that your business will not be affected.

Why is the time I receive an alert different from the actual time the error occurred?

Text message alerts have a nighttime suppression feature. Alerts triggered between 8:00 PM and 8:00 AM the next day are delayed and sent after 8:00 AM. Email alerts are not subject to this restriction and are sent immediately.

Why does the source data volume shown in storage vault management increase abnormally after I back up SAP HANA?

Cause
For SAP HANA data that is backed up to a backup vault, Cloud Backup periodically queries the HANA database for all historical backup records made through Backint. This includes HANA backups performed by other backup software that have not been deleted. Note that the statistics for these historical backup data volumes do not affect billing. Billing is based on the total data volume that is used within the backup vault.
Solution
You can run SQL statements in the HANA database to delete all backup records that were created by methods other than Cloud Backup and are no longer needed. Before you delete these records, make sure that they do not need to be retained.

When I create an SAP HANA restore job, what does it mean if I find duplicate database names in the destination instance?

When you create an SAP HANA restore job, if you encounter multiple databases with the same name but different services when you select a database, you can choose any one of them for the restore operation.

Steps to migrate an SAP HANA instance from an old backup vault to a new one

Assume you have two HANA instances, e1 and e2, that are currently being backed up to the same backup vault, v1. You now need to migrate e1 and e2 to a new backup vault, v2. The following steps describe how to switch the backup vault.

Remove the HANA nodes from the old backup vault.
Important
Do not delete the instance directly, because this will also delete the existing backup data. Before you delete an instance, make sure you no longer need its backup data.
In this step, you will remove e1 and e2 from the list of legacy backup vault nodes to prepare to add the new backup vault v2. The steps are as follows:
1. Click the instance ID to view the node information.
2. On the node information page, delete the corresponding node.
3. After the deletion, the Status of the e1 and e2 HANA instances is "Initialization failed".
Migrate the HANA nodes to the new backup vault.
Take HANA instance e1 as an example. The procedure for e2 is the same. (Note: In the procedure for e2, replace the information for HANA instance e1 with the information for e2 in step b).
1. Click Register HANA Instance.
2. In the Register SAP HANA Instance panel, configure the connection information for the SAP HANA instance and install the client.
  1. On the Edit Connection Information page, select the new backup vault v2 as the backup vault and rename the new HANA instance. Keep the host address, instance number, username, and password the same as those for HANA instance e1. Complete the remaining configurations, and then click Next.
  2. On the Install Backup Client page, select the HANA instance e1, and click Create.
After you configure HANA instances e1 and e2 by following the steps above, the following information is displayed in the new backup vault v2. Check whether the information for the two new HANA instances is correct. Click the ID of each instance to view the HANA instance details page, confirm that the node information is correct, and ensure that the database connection is normal.
After you confirm that the information is correct, immediately perform a manual full backup to ensure data security and to retain at least one complete backup point.
Note
Backup data for a HANA instance cannot be restored across instances between different backup vaults. After migrating to a new backup vault, the backup data of the original instance cannot be restored to the new HANA instance.

How do I limit the CPU usage of the backup client?

To limit the CPU usage of the backup client, you can create an hbr.config file in the /opt/alibabacloud/hbr/client/ directory and add the line cpu_max_procs=1 to the file. After you apply this setting, subsequent backup operations will limit each backup child process to use a maximum of 1 CPU core.

Cloud Backup:FAQ about SAP HANA backup