5 1 0:SAP HANA V1 Configuration

Overview

SEP sesam provides efficient data protection for your SAP HANA V1 environment. Among the main technical advantages for using the SEP sesam HDBBackint integration to back up your SAP HANA database are:

• SEP sesam HDBBackint integration is certified and supported by SAP.
• Data consistency checks at the block level.
• Ease of use due to integration into SAP HANA Studio.
• Integration into your existing backup infrastructure.
• Additional backup-efficient features, such as deduplication for eliminating redundant backup data.
• Backups are immediately available for recovery.
• Only allocated data size has to be backed up.
• High automation is possible.

Prerequisites

To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:

• Ensure that both SEP sesam and SAP HANA are running compatible versions. Check the support matrix for the list of supported SAP HANA versions.
• SEP sesam must have network access to the SAP HANA database.
• SEP sesam Client for Linux must be installed on the SAP HANA server. It is recommended to use the latest available SEP sesam Client.
• Properly configured SAP HANA database with Backint enabled.
• Appropriate user permissions must be set up to allow SEP sesam to perform backup and restore operations.
• Regular file backups must work (the sample /etc backup must be successful). For details on backup configuration, see Standard Backup Procedure.

Configuration procedure

The configuration of SEP sesam with SAP HANA Backint involves several steps.

	Note
	The installation procedure depends on the SAP HANA version you are using and differs between SAP HANA V2 and V1. This article covers the installation and configuration for SAP HANA V1. For instructions on configuring SAP HANA V2, refer to the SAP HANA Configuration.

1. Add and configure SAP HANA V1 as SEP sesam Client.

   Add the SAP HANA database server as a SEP sesam Client and create an SAP HANA backup task to enable transporting database and log backups to the SEP sesam Server or RDS.

2. Install and configure the SAP HANA Extension on the SAP HANA V1 database server.

   Prepare the backup environment in SEP sesam and then install and configure the SEP sesam extension for SAP HANA. SAP HANA database backup is configured on the SAP HANA server with available SEP sesam parameters in the utl file. Changes to the backup process must be made on the database server.

3. Verify and test the integration.

   Make sure that the integration between SEP sesam and SAP HANA V1 is functioning as expected and perform tests to validate backups and restores.

Configuring SAP HANA V1 as a Client

The procedure for configuring the SAP HANA database server as a SEP sesam Client involves adding the SAP HANA server as a SEP sesam Client and setting up two backup tasks. The first task, with the task type SAP HANA and <SID> as the source, enables the SEP sesam Server to accept backups from the SAP HANA system and serves to transport the database and log backups to the SEP sesam Server or RDS. The second task is intended for backing up SAP HANA configuration files and associated data.

1. To add a client, in GUI go to Main selection -> Components -> Clients, select a location, and then click New client. Define the settings and options as required. Make sure that the selected access mode is SM SSH. For more detailed instructions, see Configuring Clients.
2. Create a backup task named HANA <SID>. In the Task type drop-down list select SAP HANA and as Source set <SID>. For more details on backup procedure, see Creating a Backup Task.
   Note that the SAP HANA backup task cannot be used for regular file backups. It is required only for enabling the SEP sesam Server to accept backups from the SAP HANA server. Once all configuration steps are performed, this task is used to transport the database and log backups to the SEP sesam Server or RDS.
3. Create a backup task with task type Path to back up SAP HANA config files and all other required files by specifying all files except the database files as a source.
   The files are located in the following directories:
   • Global config files: /usr/sap/<SID>/SYS/global/hdb/custom/config

   Example: /usr/sap/SEP/SYS/global/hdb/custom/config

   • Local config files (on each host): /usr/sap/<SID>/HDB<instance>/<SAP_hostname>

   Example: /usr/sap/SEP/HDB00/saphanix1

4. Once you created a task, select or create a schedule to specify when you want to back up your data, and then create a new backup event. Select FULL as a backup level to perform a full backup. For more details, see Creating a Backup Event.
5. Optionally, create dedicated media pools for storing the backups.

Installing and configuring SEP sesam extension for SAP HANA V1

To manage the backup of a SAP HANA database with SEP sesam externally, SEP sesam HDBBackint module uses the SAP HANA Backint functionality. On the SAP HANA server a Backint utl parameter file must be created. This file contains all the necessary SEP sesam parameters that SAP HANA needs for performing the backup operation. The *.utl file must reference the SEP sesam server, the SSB logfile, and other SEP sesam parameters that are available.

To install and configure SAP HANA extension, SEP provides a useful binary/script for the installation and configuration of the SEP sesam module for SAP HANA V1.

Preparing backup environment in SEP sesam

Before starting the installation of the SAP HANA extension, prepare the backup environment in SEP sesam. This involves setting up the backup task, media pools, migration task, follow-up task, and optionally the SEP sesam RDS. Then, on the SAP HANA server, you configure the backup process using the SEP sesam backup parameters in the utl file. The backup process is managed and adjusted directly on the SAP HANA server.

1. Create a SAP HANA backup task and set the general settings and parameters for the backup. In the Task type drop-down list select SAP HANA and set the Task name. The Source field is not used for backup and you can use it to write any descriptive name for the backup source. For detailed instructions on configuring the backup task, see Creating a Backup Task.
2. Select or create media pools for database and log backups. For detailed instructions on configuring a media pool, see Configuring a Media Pool.
3. Optionally, configure a migration task for your SAP Hana database backup. For detailed instructions on configuring the migration task, see Creating a Migration Task.
4. Optionally, configure a follow-up task for your SAP HANA database backup. For more information on configuring the follow-up task, see Follow-up Events.
5. Collect and prepare the following information:
   • SAP HANA database name: <database_name>
   • SAP HANA SID: <SID>
   • SAP HANA instance number: <instance>
   • SAP HANA backup user credentials: <username> and <password>
   • Hostname (required for hdbsql connection)
   • SAP HANA server hostname (default is OS hostname; required for creating TRACE path: /usr/sap/<SID>/HDB<instance>/<SAP_hostname>/trace): <SAP_hostname>
   • SEP sesam Server hostname: <sesam_server_hostname>
   • SEP sesam Remote Device Server hostname (if used): <sesam_RDS_hostname>
   • Backup task name: <backup_task_name>
   • Target media pool for database backup: <media_pool_for_DB_backup>
   • Target media pool for log backup (optional): <media_pool_for_log_backup>
   • SEP sesam drive number (optional): <drive_number>

Note that:

• The backup user needs appropriate rights to configure your SAP HANA database, e.g. the SYSTEM user of the SYSTEMDB.
• The syntax of SEP sesam Server hostname and SEP sesam Remote Device Server determines the type of connection between the SAP HANA host client and the SEP sesam Server and/or SEP sesam RDS including a control connection and/or data transfer. You have to use the same syntax as you find in the SEP sesam GUI -> Client properties (of your SEP sesam Server/RDS) -> Interface field (e.g., bck-srv.sep.de, http://bck-srv.sep.de:11000, https://bck-srv.sep.de:11443).

Installing SAP HANA extension on SAP HANA database server

For the installation use the binary:

/opt/sesam/bin/sesam/sm_install_saphana

If you use SEP sesam Client < 4.4.3 Tigon V2, use the bash script for the installation:

/opt/sesam/skel/templates/sm_install_saphana.sh

The binary tool makes your installation easier by:

• generating .utl files in /var/opt/sesam/var/ini/
• inserting the SEP sesam Backint parameters with the correct syntax in the *.utl files
• setting the appropriate filesystem rights
• activating the usage of Backint for database/archive log backup
• adding the correct path and filename for the *.utl file into the HANA database configuration file (specifically, the global.ini file).

You can also perform all these steps manually, if required.

Be aware that the syntax and functionality may differ from the procedures described in this document. SEP recommends using the latest available SEP sesam Client version.

SAP HANA single instance

To install SAP HANA extension on a single instance, run the following command:

/opt/sesam/bin/sesam/sm_install_saphana -C <sesam_server_hostname> -j <backup_task_name> -m <media_pool_for_DB_backup> [-l <media_pool_for_log_backup>] [-S <sesam_RDS_hostname>] [-d <drive_number>] -s <SID> -i <instance> -u <username> -p <password>

SAP HANA multiple instances

To install SAP HANA extension on a multiple instance, run the following command for each instance:

/opt/sesam/bin/sesam/sm_install_saphana -C <sesam_server_hostname> -j <backup_task_name> -m <media_pool_for_DB_backup> [-l <media_pool_for_log_backup>] [-S <sesam_RDS_hostname>] [-d <drive_number>] -s <SID> -i <instance> -u SYSTEM -p <password> -M

Verify and test the integration

To check if your installation/configuration has been successful, proceed as follows:

1. Search in the folder /var/opt/sesam/var/ini/ for files with the extension utl and check the content. Be aware that all the values in these files are case sensitive.
2. Start SAP HANA Studio and click one instance to open it.
3. Select Configuration, expand Backint Settings and verify that the following is set:
• Backint Agent should be /opt/sesam/bin/sesam/hdbbackint.
• Make sure that the Destination type has changed from file to BACKINT.

Screenshots

SEP sesam Backint parameters

The SAP HANA Backint parameter file contains all relevant information for backing up SAP HANA with SEP sesam. It contains parameters, which are used by the SEP sesam HDBBackint module. The file(s) are generated in /var/opt/sesam/var/ini/.

You can use different parameter files for different purposes (e.g., to store backups in different media pools). The parameter file used is declared by the -P PARAMETERFILE option for HDBBackint. A template parameter file /opt/sesam/skel/templates/backint_saphana.utl is available. You can copy the file to /var/opt/sesam/var/ini/backint_saphana.utl, rename it and modify it for your environment. Note that all specified parameters are case sensitive.

	Note
	If you have used the sm_install_saphana setup utility for installing the extension, the parameter file has already been generated and registered, and the SEP sesam parameters have been inserted with the values that were specified with the installation command.

Mandatory SEP sesam Backint parameters are:

SESAM_SERVER=<sesam_server_hostname>

Hostname of the SEP sesam Server

SSB_LOGFILE=<log_file_name>

Full path of the SEP sesam HDBBackint log file. As of SEP sesam Client ≥ Beefalo V2 the SSB_LOGFILE path is set to SAP HANA trace folder. The log file name contains more useful information and a new file is generated daily. It is recommended that you set the path and dynamic value for the log file name in the parameter as follows:

SSB_LOGFILE=/usr/sap/<SID>/HDB<instance>/<SAP_hostname>/trace/hdbbackint_<database>_$u-%Y-%m-%d.log

SESAM_JOB=<backup_task_name>

Name of the backup task that was created for the SAP Client.

SESAM_POOL=<media_pool_for_DB_backup>

Exact name of the SEP sesam media pool that you want to use for backup.

SESAM_TAPESERVER=<sesam_RDS_hostname>

Hostname of the RDS that you want to send the backup to (mandatory only if your backup target storage is connected to an RDS).

The following SEP sesam Backint parameters are optional:

SESAM_DRIVE=<drive_number>

Number of the SEP sesam drive that you want the backup to be written to. The drive number must match the media pool (drive group of the media pool) that you defined with SESAM_POOL.

SESAM_MIGRATION_TASK=<migration_task_name>

This optional parameter references the name of the preconfigured migration task that will be started when SAP HANA backup completes successfully. If SESAM_TASKEVENT is used, the migration task can be specified in the backup event configuration.

SESAM_FOLLOW_EVENT=<follow-up_event>

This optional parameter references the name of the preconfigured follow-up that will be started when SAP HANA backup completes successfully. For more information refer to Follow-up Events. If SESAM_TASKEVENT is used, the follow-up event can be specified in the backup event configuration.

Manual installation procedure

Note that these instructions work with the default SAP HANA directories. You may have to adjust every path in the commands to the path that you have used in a customized installation.

1. Create the directories needed for the HDBBackint binary and utility file:

 root@hanasrv:~# mkdir -p /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig

2. Copy the parameter file template from the skel/templates to the SEP sesam ini directory.

 root@hanasrv:~# cp /opt/sesam/skel/templates/backint_saphana.utl /var/opt/sesam/var/ini/

3. Rename the backint_saphana.utl if you need more than one .utl file (recommended).
4. Adapt the parameter of the *.utl to suit your SEP sesam environment, see the section SEP sesam Backint parameters.
5. Create a symbolic link from /opt/sesam/bin/sesam/hdbbackint to the directory where SAP HANA expects the Backint executable.
   Note that usually root permissions are required. The configuration has to be adjusted accordingly. The file must be executable for the SAP HANA user.

 root@hanasrv:~# ln -s /opt/sesam/bin/sesam/hdbbackint /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint

6. Create another symbolic link from /var/opt/sesam/var/ini/backint_saphana.utl (your .utl file) to the directory where SAP HANA expects the parameter file:

 root@hanasrv:~# ln -s /var/opt/sesam/var/ini/backint_saphana.utl 
 /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/

7. Then start SAP HANA Studio, double-click one instance to open it and insert the correct values for the configured database, as described in section Checking installation/configuration result.

Repeat this procedure on every node of a scale-out system and for every database on the same system, if required.

External reference

SAP HANA Administration Guide

See also

SAP HANA Installation Checklist – SAP HANA Backup – SAP HANA Restore

Copyright © SEP AG 1999-2024. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.