Process flow of Tivoli data protection for SAP HANA
SAP recommends backup of data ,log volume and the configuration files. The backup can be taken locally to the disk or to external devices . For 3rd party backups SAP has provided the backint api which can be implemented by the 3rd party tools
This document is focussed on giving a high level understanding on the different components of the tivoli data protection , how they fit together and how to explain how the Data process flows.
Lets look at the different components of TDP.
On a high level SAP HANA Backint process interfaces between Tivoli data protection ( tdp) which uses the TSM API to talk to the TSM Server
SAP HANA Uses the backint API to backup data and log volumes of the HANA Database for 3rd party Backup tools.
hdbbackint is the backint agent used to backup the data and log volume .
The backint agent uses the backint Parameters stored in initSID.utl for the configuration of the the hdbbackint process.
It contains information on how to run the backup/restore process , this can be customized for the HANA backups by modifying the parameters accordingly.
Both the location of the backint agent and the Backint parameter file is specified in the Hana studio under the configuration tab of the backup window
This is particularly very useful in a HANA Scaleout environment where multiple hdbbackint agent runs on different nodes to backup the data and log volume. This process will ensure that the same backup ID is assigned to the backup.
Courtesy : Data Protection for SAP HANA /Installation and User’s Guide — available in public domain.
The Backint agent (hdbbackint) then sends the data to be backed up to the TSM API which in turn backs up the data to the TSM Server.
Lets look at this sequentialy
Step 1 ) Start the backup using HANA Studio
You can also start the backup from command line
Backup datafile using (‘/usr/sap/SID/HDB01/backup/data’)
Step 2 ) Number of hdbbackint processes are started , if its a scale out separate hdbbackint processes are started on different nodes
Step 3 ) hdbbackint process connects to prole ( the process is running ) to get the configuration information from InitSID.utl. Prole also ensures that the right backup id’s are assigned.
Step 4) HANA DB sends data to the backup agent (hdbbackint)
Step 5) hdbbackint sends the data to TSM Server through TSM API
The initSID.utl file stores a whole lot of configurations like ( No of redolog copies , Location of the Backup media , Maximum no of session to run from the TSM Client to the Server etc)
You can even specify mutiple backup locations , for example in a DR scenario.
The backup history can be viewed in the backup catlog under Backup view