HANA Backup failing with "[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

SAP HANA Error [hdbsql execution Faild. *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. SQLSTATE: HT000]. 

Symptoms

The backup job fails with the following error:

SAP HANA Error [hdbsql execution Faild. *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. SQLSTATE: HT000].

Causes

• The previously run backup is still running.
• The previously run backint process is in hung/stuck/waiting state.

Resolution

Contact SAP HANA database administrator to troubleshoot using the following instructions:

1. Check that no backup is running, currently. You can check this with the following SQL statement: select from "SYS"."MBACKUPCATALOG" where STATENAME = 'running'; To cancel a running backup, see the SAP HANA documentation BACKUP CANCEL Statement (Backup and Recovery)
2. Check that no internal database snapshot is in the PREPARED state as per the SAP HANA Administration guide documentation Create a Data Snapshot (Native SQL). If any internal database snapshot is in the PREPARED state, you need to confirm or cancel the database snapshot as per the documentation. In case, a HANA service is restarted while a database snapshot is running, you might need to restart the system again to resolve the problem.
3. If you have checked and resolved any potential issues found in steps 1 and 2, you should try to run the HANA Backup again.
4. If the above steps do not help to resolve the issue. Perform the following steps:

• Firstly, try to delete the named pipes that SAP HANA uses to send data to hdbbackint. This way both SAP HANA and hdbbackint will most likely realize that the data transfer has ended, and will terminate their backup operation. To find the pipes, check the backup.log and backint.log backup files. Normally, there are two entries in the backint.log for each backup operation (start and finish). The hanging backint process will only have one entry (start) and it will show you the processID of the backint process and the related pipe. To find the directory where the pipes are created, you can query the system view M_BACKUP_CONFIGURATION, the column BACKINT_DATA_BACKUP_PATH (Data backup directory for backint) will have the required path. The backint.log file example:

  command:

  • /usr/sap/TST/SYS/global/hdb/opt/hdbbackint -f backup -i /var/tmp/hdbbackint_TST.XXXXXX -o /var/tmp/hdbbackint_TST.XXXXXX -u TST -s 1504925958336 -c 1 -l LOG
  • pid: 2000

  Input: #SOFTWAREID "backint 1.04" "HANA HDB server 4.50.000.00.0000000000" #PIPE "/usr/sap/TST/SYS/global/hdb/backint/DB_TST/log_backup_0_0_0_0"

• If deleting the pipes does not resolve the issue, it can help to terminate the backint process (hdbbackint). To execute the kill command, you may need to use the root user or another superuser with the required permissions. For additional information on finding the PID responsible see the 'Resolution' section of the SAP KB 2827950 - How-To: Cancel Hanging Backup on SAP HANA. The backint.log file example:

  Command:

  • /usr/sap/TST/SYS/global/hdb/opt/hdbbackint -f backup -i /var/tmp/hdbbackint_TST.XXXXXX -o /var/tmp/hdbbackint_TST.XXXXXX -u TST -s 1504925958336 -c 1 -l LOG
  • pid: 2000 <-- Process to kill

  Input: #SOFTWAREID "backint 1.04" "HANA HDB server 4.50.000.00.0000000000" #PIPE "/usr/sap/TST/SYS/global/hdb/backint/DB_TST/log_backup_0_0_0_0"

• If deleting the pipes or terminating the backint process (hdbbackint) does not resolve the issue then you need to do a soft stop of the SAP HANA Database as described in Stop a Database and then restart the SAP HANA Database. For more information, See Note: https://launchpad.support.sap.com/#/notes/0002452735 (You require a SAP User id ).