4 4 3 Tigon:SAP HANA Configuration

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2020. 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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Tigon/4.4.3 Beefalo V2. For previous documentation version(s), check SAP HANA archive.


Information sign.png SEP AG has discontinued support for SEP sesam version 4.4.3 Tigon (V1 and V2). Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version.


Overview

SEP sesam provides efficient data protection for your SAP HANA V1 and V2 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:

  • Check the support matrix for the list of supported SAP HANA versions.
  • Installed SAP HANA database.
  • Installed SEP sesam Client for Linux on the SAP HANA server.
    • HANA V2: SEP sesam Client v. ≥ 4.4.3.60
    • HANA V1: SEP sesam Client v. ≥ 4.4.1.14 (≥ 4.4.3.12 for IBM ppc64)
    • It is recommended to use the latest available SEP sesam Client for Linux on the SAP HANA server.
  • Regular file backups must work (the sample /etc backup has to be successful). For details on backup configuration, see Standard Backup Procedure.

Configuring SAP HANA as a client on SEP sesam Server (SAP HANA V1 and V2)

The procedure for configuring the SAP HANA server as a SEP sesam Client is exactly the same for SAP HANA V1 and V2.

  1. Add the SAP HANA server as a SEP sesam Client in the SEP sesam GUI and check that access mode is SM SSH. For details, see Configuring Clients.
  2. Create a backup task HANA <DB_SID> with SAP HANA task type and <DB_SID> as a source. For general details on backup procedure, see Creating a Backup Task. Note that SAP HANA task cannot be used for regular file backups. It is necessary only for enabling the SEP sesam Server to accept backups from the SAP HANA system; 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 (Path task type) to back up SAP HANA config files and all other required files by specifying all files except the database files as a source.
  4. 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>/<host>
      

      Example:

      /usr/sap/SEP/HDB00/saphanix1
      
  5. Once you created a task, create a schedule to specify when you want to back up your data. Then you must create a new backup event. Select FULL as a backup level to perform a full backup. For general details, see Creating a Backup Event.
  6. Optionally, create a separate media pool to store the backups.

Installing and configuring SAP HANA module on the database server

The installation procedure differs depending on your SAP HANA version and SEP sesam version. SEP provides a useful binary/script for the installation and configuration of the SEP sesam module for SAP HANA. The binary tool makes your installation easier by:

  • generating *.utl files in /var/opt/sesam/var/ini/
  • inserting the right values with the correct syntax in the *.utl files
  • setting appropriate filesystem rights
  • activating the backint usage for database/archive log backup
  • inserting the appropriate path and filename for the *.utl file in the HANA database (resp. global.ini)

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

Installing and configuring SAP HANA V2

The following instructions are relevant for SAP HANA V2 (SEP sesam ≥ Beefalo V2).

For the installation use the binary:

/opt/sesam/bin/sesam/sm_install_saphana2
Information sign.png Note
You have to run the script for each database in your instance (SYSTEMDB, TenantDB1, TenantDB2, ... TenantDB<number>).

If you use a SEP sesam Client < Beefalo V2, you have to use the sm_install_saphana binary for installation/configuration and configure the backup of the SAP HANA backup catalog manually.

You can run the sm_install_saphana2 script by using either SAP user key or SAP HANA backup user/password combination. The tool also activate the backup of the backup catalog introduced in SAP HANA Version 2.

Steps

  1. Evaluate and write down the following values:
  2. SEP sesam Server hostname
    SAP HANA database name
    Backup task name
    Target media pool for DB backup
    Target media pool for log backup
    SEP sesam Remote Device Server (if used)
    SEP sesam drive number (optional)
    SAP HANA SID
    SAP HANA instance number
    SAP user key for backup user (if used)
    SAP HANA backup user
    SAP HANA backup user password
    Hostname (for hdbsql connection)
    SAP HANA hostname for TRACE path creation (default is OS hostname). Path for standard installation is /usr/sap/<SID>/HDB<Instance>/<SAP HANA Hostname>/trace.
    
    • 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).
  3. Run the configuration tool as Linux root user on the SAP HANA host.
    • Running the script by using the SAP user key
    • sm_install_saphana2 -s  <SID_name> -i  <instance_number> -U  <user_key> -D  <database> -j  <backup_task_name> -m  <media_pool_for_DB_backup> -C  <server_hostname>
      

      For example:

      sm_install_saphana2 -s SEP -i 90 -U BackupUser -D SYSTEMDB -j HANA_SystemDB -m MP_HANA -C backup-srv.sep.de
      
       <SID_name>= SEP
       <instance_number>= 90
       <user_key>= BackupUser ( For details, see Using a User Key when Logging On to a Database.)
       <database>= SYSTEMDB
       <backup_task_name>= HANA_SystemDB
       <media_pool_for_DB_backup>= MP_HANA
       <server_hostname>= backup-server.sep.de
      
    • Running the script by using the SAP HANA backup user password
    • sm_install_saphana2 -s  <SID_name> -i  <instance_number> -u  <username> -p  <password> -D  <database> -j  <backup_task_name> -m  <media_pool_for_DB_backup> -l  <media_pool_for_log_backup> -C  <server_hostname> -S  <RDS_hostname> -d  <drive_number>
      

      For example:

      sm_install_saphana2 -s SH2 -i 01 -u SYSTEM -p secret! -D PRD -j HANA_Production_DB -m MP_HANA_DB -l MP_HANA_LOG -C https://backup-server.sep.de:11443 -S http://rds01.sep.de:11000 -d 7
      
       <SID_name>= SH2
       <instance_number>= 01
       <username>= SYSTEM
       <password>= secret!
       <database>= PRD
       <backup_task_name>= HANA_Production_DB
       <media_pool_for_DB_backup>= MP_HANA_DB
       <media_pool_for_log_backup>= MP_HANA_LOG
       <server_hostname>= https://backup-server.sep.de:11443
       <RDS_hostname>= http://rds01.sep.de:11000
       <drive_number>= 7 (exclusive reserved drive for SAP HANA backups, for best performance create a separate drive)
      
      In this example the SEP sesam SAP HANA Client connects the SEP sesam Server via https on port 11443 for control information and transfers the data via http on port 11000 to the SEP sesam RDS.

    For more detailed information, see the integrated online help by using the relevant command:

    For usage with user/password combination

    /opt/sesam/bin/sesam/sm_install_saphana2 -h
    

    For usage with SPA HANA user key, on your SAP HANA host

    /opt/sesam/bin/sesam/sm_install_saphana2 -H
    

Checking installation/configuration result (SAP HANA V2)

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, double-click one instance to open it and select the tab Configuration.
  3. Go to global.ini -> backup and expand the backup section, or write backup in the Filter field. Then verify that the following values are set:
    • catalog_backup_using_backint should be set to true.
    • log_backup_using_backint should be set to true.
    • catalog_backup_parameter_file should have the correct values for System and for all already configured Database(s).
    • data_backup_parameter_file should have the correct values for System and for all already configured Database(s).
    • log_backup_parameter_file should have the correct values for System and for all already configured Database(s).

    20181024 catalog-via-backint.png

The SAP HANA backup catalog registers all backups and contains all backup history details. It enables SAP HANA to check and validate whether recovery is possible, which backups are required for recovery and which backups are no longer needed. Note that the backup catalog does not record the progress of a backup; this is done by the backup.log.

SEP Warning.png Warning
Backup catalog is mandatory to be able to restore the SAP HANA instance to a different system! Make sure that you configure backup for SAP HANA catalog as shown above.

Installing and configuring SAP HANA V1

The following instructions are relevant for SAP HANA V1 (SEP sesam ≥ Tigon V2).

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

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

Steps

  1. Evaluate and write down the following values:
  2. SEP sesam server hostname
    Backup task name
    Target media pool for DB backup
    Target media pool for log backup
    SEP sesam Remote Device Server (if used)
    SEP sesam drive number (optional)
    SAP HANA SID
    SAP HANA instance number
    SAP user key for backup user (if used)
    SAP HANA backup user
    SAP HANA backup user password
    SAP HANA hostname (for hdbsql connection)
    SAP HANA multitenancy (yes/no)
    
    • 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://nbck-srv.sep.de:11443).
  3. The installation command differs for single and multi instance as follows:
    • SAP HANA single instance
    • /opt/sesam/bin/sesam/sm_install_saphana -C <server_hostname> -j hana_backup_task -m sesam_media_pool -l sesam_media_pool -s <SID_name> -i <instance_number> -u <username> -p <password>
      

      where hana_backup_task is the name of the task you created before and the same sesam_media_pool is specified twice in the given command!

    • SAP HANA multi instance
    • For each instance, run the following command:

      /opt/sesam/bin/sesam/sm_install_saphana -C <server_hostname> -j hana_backup_task -m sesam_media_pool -l sesam_media_pool -s <SID_name> -i <instance_number> -u SYSTEM -p <password> -M
      

      where hana_backup_task is the name of the task you created before, <SID_name> is for example H02, <instance_number> is for example 04, and the same sesam_media_pool is specified twice in the given command!

      For more detailed information, see the integrated online help by using the following command on your SAP HANA host:

      /opt/sesam/bin/sesam/sm_install_saphana -h
      

Checking installation/configuration result (SAP HANA V1)

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.
    • Hana studio01.PNG

The SAP HANA backint parameter file (*.utl)

The SAP HANA backint parameter file contains all relevant information for backing up SAP HANA with SEP sesam. It contains a special keywords 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 adjust it to suite your environment. Note that all specified parameters are case sensitive.

Information sign.png Note
If you have used the sm_install_saphana or sm_install_saphana2 setup utility for installing the module, the parameter file has already been generated and registered, according to the values you entered during the execution of the script. You may have to go through the values of the file if some of the criteria for the automatic installation could not be met.

SAP HANA V1 and V2 parameters

At least the following entries are mandatory to be configured in the parameter file:

SESAM_SERVER=<SEP sesam Server>
Hostname of the SEP sesam Server
SESAM_JOB=<SEP sesam SAP Client task>
Name of the backup task created during configuration
SESAM_POOL=<SEP sesam media pool>
Exact name of the SEP sesam media pool that you want to use for the backup
SESAM_TAPESERVER=<Remote device server>
Hostname of the RDS that you want to send the backup to (only mandatory if your backup target is connected to an RDS).
SSB_LOGFILE=<Log file name>
Full path of the SEP sesam backint log file

Additional optional configuration parameter is:

SESAM_DRIVE=<SEP sesam 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 in SESAM_POOL.

Additional parameters for SAP HANA V2

Additional optional configuration parameters for SAP HANA V2 are:

SESAM_TASKEVENT=<Preconfigured HANA task event in SEP sesam DB>
For future use, special configuration tasks and settings in SEP sesam database are required.
SESAM_HANA_SOURCE=/<HANA SID>/<instance>/<HANA DB name>
For future use, e.g, with backup and housekeeping scripts.
SESAM_PARALLEL_STREAMS=<integer value>
Count of parallel streams that SEP sesam uses for SAP HANA database backup.
Information sign.png Note
The SAP HANA database engine may split a database backup in more then one stream or not. To use the parallel backup streams on SAP HANA side you must configure this option in the SAP HANA database configuration (global.ini -> backup section).

The parameter SESAM_PARALLEL_STREAMS sets only the maximum parallel backup streams on the SEP sesam side (default is 2 streams).

The SSB_LOGFILE parameter

If you use the sm_install_saphana binary (SAP HANA V1 or older SEP sesam Client), the log file path is set to /var/opt/sesam/var/log/lgc/.

As of SEP sesam Client Beefalo V2 the SSB_LOGFILE path is set to SAP HANA trace folder. The log file name now contains more useful information and every day a new file is generated. It is recommended that you change the parameter manually to:

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

Note that the path and variables for the date are important.

Troubleshooting installation: Manual installation

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:
  2. root@hanasrv:~# mkdir -p /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig
    
  3. Copy the parameter file template from the skel/templates to the SEP sesam ini directory.
  4. root@hanasrv:~# cp /opt/sesam/skel/templates/backint_saphana.utl /var/opt/sesam/var/ini/
    
  5. Rename the backint_saphana.utl if you need more then one utl file (recommended).
  6. Adapt the parameter of the *.utl to suit your SEP sesam environment, see the section SAP HANA backint parameter file (*.utl).
  7. 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.
  8. root@hanasrv:~# ln -s /opt/sesam/bin/sesam/hdbbackint /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
    
  9. 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:
  10. root@hanasrv:~# ln -s /var/opt/sesam/var/ini/backint_saphana.utl 
    /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/
    
  11. Then start SAP HANA Studio, double-click one instance to open it and insert the correct values for the configured database, as described in the above section Checking installation/configuration result (SAP HANA V2).
  12. Repeat steps 1-7 on every node of a scale-out system and for every database on the same system, if given.