Detailed System Requirements
Abstract
This document details the backup and restore requirements for SAP HANA for IBM Storage Copy Data Management 2.2.25.
Content
Note: The product now known as IBM Storage Copy Data Management was named IBM Spectrum Copy Data Management in levels earlier than 2.2.20. To learn more about the brand change, see IBM Spectrum Protect brand change to IBM Storage Protect.
This document is divided into linked sections for ease of navigation. Use the following links to jump to the section of the document that you require:
- General
- Configuration
- Software
- Connectivity
- Authentication, registration, and privileges
- Restore and revert
- Sample Configuration
- IBM Storage Copy Data Management installs an agent on application servers when it is registered. Some anti-virus software might flag or attempt to remove the agent software. If you run anti-malware software application servers, exclude the installation path of the IBM Storage Copy Data Management agent.
- The agent installation directory must be excluded for any anti-virus software scans. Add this path to the exclusion list for all anti-virus software that is installed on the application server. For Oracle, InterSystems Caché and IRIS, and SAP HANA:
Where username of the account used to register the application server in IBM Storage Copy Data Management./tmp/cdm_guestapps_username - IBM Storage Copy Data Management support for third-party operating systems, applications, services, and hardware depend on the respective vendor. If a third-party product or version moves into extended support, self-service support, or end-of-life, IBM Storage Copy Data Management supports the product or version at the same level as the vendor. See also IBM Support General Guidelines and Limitations - IBM support for software on unsupported operating systems
Supported platforms and configurations
| Operating system | ||
|---|---|---|
|
||
| Storage system | ||
|
||
| Server types | Operating Systems | Storage Configuration |
| Physical [4, 10] |
|
|
| Virtual (VMware) [1, 3, 4, 10] |
|
|
Notes:
1. For supported VMware vSphere versions, see in System requirements: IBM Storage Copy Data Management 2.2.25.
2. Select the Physical provider type when you register the provider in IBM Storage Copy Data Management. NetApp ONTAP Storage Systems are not supported.
3. SAP HANA servers registered as virtual need VMware Tools installed and running.
4. Supported platforms: Intel based x86, IBM Power Systems (Little Endian).
5. Single tenant configurations can be automatically protected by using storage snapshots.
6. Only the XFS file system is supported for SAP HANA data and log locations.
7. On IBM Systems Storage, condense is run during maintenance jobs.
8. IBM Storage Copy Data Management supports protection and recovery of multitenant databases on SAP HANA 2.0 SPS 04 and SPS 05.
9. Non-scale-out SAP HANA configurations are only supported.
10. Supported platforms: IBM Power Systems (Little Endian).
11. For Dell PowerMax Storage:
- Use separate Storage Groups (SG) for different databases for improved performance.
- IBM Storage Copy Data Management supports one parent SG, and it can contain different child SG for different databases.
- Keep datafiles and log files in separate SG.
- When using Parent SG with child SGs, use separate child SGs for data and log.
- For Instant Disk Restore, Host on Dell PowerMax array must have at-least one Masking View created for itself, even if the host is a part of a hostgroup having active Masking View.
-Physical servers listed in table above are not supported.
Note: If you are using IBM Storage Systems running IBM Spectrum Accelerate level 11.5.3 or later, including FlashSystem A9000/A9000R and IBM XIV Storage Systems use IBM Spectrum Copy Data Management 2.2.13.
Prerequisites
- The SAP HANA Client must be installed on your SAP HANA machine.
- Create a symbolic link to the SAP HANA Client installation directory through the following command:
For example, if SAP HANA Client is installed in /hana/shared/<SID>/hdbclient, you would enter the following:ln -s <installation directory of SAP HANA Client> /opt/hana.ln -s /hana/shared/<SID>/hdbclient/ /opt/hana
- For SAP HANA 2.0 SPS 04 and SPS 05, the hdbcli module must be installed. The hdbcli module must be installed only after the complete installation of the SAP HANA client. The module might be extracted from <path to directory>/hdbclient/hdbcli-<version>.tar.gz.
- Log backups require that the log backup option is enabled on the SAP HANA system. Additionally, the Universal Destination Directory for log backups must match the directory that is configured on the SAP HANA system when you enable log backups.
- Each SAP HANA system has a system ID (SID). It is good practice to have the SID in the path. For example, if /hana/logbackup is the mount point, create these directories:
To make sure that database logs can be saved, permissions need to be specified for the created directories:mkdir /hana/logbackup/<SID> mkdir /hana/logbackup/<SID>/catalogchown --reference=/hana/shared/<SID>/HDB01 /hana/logbackup/<SID> chmod --reference=/hana/shared/<SID>/HDB01 /hana/logbackup/<SID> chown --reference=/hana/shared/<SID>/HDB01 /hana/logbackup/<SID>/catalog chmod --reference=/hana/shared/<SID>/HDB01 /hana/logbackup/<SID>/catalog
- The bash and sudo packages must be installed. Sudo must be version 1.7.6p2 or later. Run sudo -V to check the version.
- Python version 3.x must be installed.
It might be necessary to add your python3 binary file location to the system PATH or to create a symbolic link. For example, if your python3 is installed at /opt/freeware/bin, you need to create a link as follows:
SLES only: Run the following commands before hdbcli installation:ln -s /opt/freeware/bin/python3 /usr/bin/python3
Note: The hdbcli module need to be version 2.17 or later.python3 -m ensurepip pip3 install hdbcli - RHEL/CentOS 6.x only: Verify the util-linux-ng package is up to date by running:
Depending on your version or distribution, the package might be named: util-linux.yum update util-linux-ng - RHEL/CentOS 7.3 or later: A required Perl module, Digest::MD5, is not installed by default. Install the module by running:
yum install perl-Digest-MD5 - SLES only: The Python pip package needs to be installed. Follow these steps to install the pip module on SLES:
Note: The SLES equivalent of yum is zypper.$ sudo zypper addrepo https://download.opensuse.org/repositories/Cloud:Tools/<SLES_verision_SP_level>/Cloud:Tools.repo $ sudo zypper refresh $ sudo zypper python-pip - Linux only: If data stays on LVM volumes, verify that the LVM version is 2.0.2.118 or later. To check the LVM version and if necessary to update the package, run:
lvm version yum update lvm2 - Linux only: If data stays on LVM volumes, the lvm2-lvmetad service must be disabled as it can interfere with IBM Storage Copy Data Management's ability to mount and resignature volume group snapshots and clones.
Run the following commands to stop and disable the service:
Additionally, disable lvmetad in the LVM config file. Edit the file /etc/lvm/lvm.conf and set:systemctl stop lvm2-lvmetad systemctl disable lvm2-lvmetaduse_lvmetad = 0
- The SSH service must be running on port 22 on the server and any firewalls must be configured to allow IBM Storage Copy Data Management to connect to the server by using SSH. The SFTP subsystem for SSH must also be enabled.
- The server can be registered by using a DNS name or IP address. DNS names must be resolvable by IBM Storage Copy Data Management.
- To mount clones or copies of data, IBM Storage Copy Data Management automatically maps and unmaps LUNs to the servers. Each server must be preconfigured to connect to the relevant Storage Systems at that site.
- For Fibre Channel, the appropriate zoning must be configured beforehand.
- For iSCSI, the servers must be configured beforehand to discover and log in to the targets on the storage servers.
Authentication, registration, and privileges
Authentication
- The application server must be registered in IBM Storage Copy Data Management by using an operating system user that exists on the server (referred to as "IBM Storage Copy Data Management agent user" for the rest of this topic).
- During registration, you must provide either a password or a private SSH key that IBM Storage Copy Data Management uses to log in to the server.
- For password-based authentication, make sure that the password is correctly configured, and that the user can log in without facing any other prompts, such as prompts to reset the password.
Registration
When you register an SAP HANA provider in IBM Storage Copy Data Management, note the following:
- The format for the port number is 3<instance number>15. So, for example, if the instance number is 07, then enter the following port number: 30715.
- HANA database user credentials are required to query the database. These credentials are used to log in to the SYSTEMDB and TENANTDB to run restore operations. A "SYSTEM" user or NON-SYSTEM user can be used for database operations. When creating a NON-SYSTEM user specific privilege must be granted to the user, also the username and password must be same in both SYSTEMDB and SXX tenant database.
- The NON-SYSTEM database user must have BACKUP ADMIN, CATALOG READ, DATABASE RECOVERY OPERATOR on SYSTEMDB and BACKUP ADMIN, CATALOG READ on the TENANT database (e.g. SXX).
Note: For examples on creating a new user with the necessary privileges, see Sample Configuration in SAP HANA requirements.
Privileges
The IBM Storage Copy Data Management agent user needs the following privileges:
- Privileges to run commands as root and other users by using sudo. IBM Storage Copy Data Management requires these privileges for various tasks such as discovering storage layouts and mounting and unmounting disks.
- The sudoers configuration must allow the IBM Storage Copy Data Management agent user to run commands without a password.
- The !requiretty setting must be set.
For examples on creating a new user with the necessary privileges, see Sample Configuration in SAP HANA requirements.
- Restore Jobs
If the xfsprogs package version on the destination server is between 3.2.0 and 4.1.9, the restore process might fail when you restore a database or file system from an XFS file system. To resolve the issue, upgrade xfsprogs to version 4.2.0 or later.
Restriction: The Restore (Instant Disk and Instant Database) operations for SAP HANA are not supported on an alternate host. You need to restore it on the same source host.
- Revert Jobs
File system revert jobs are File system revert jobs
When you run revert jobs on SAP HANA, there are special considerations that must be met for jobs to successfully complete:
- SAP HANA data and the operating system (OS) file system must be on separate datastores.
- Make sure that the databases are on independent storage. The underlying storage volume for the reverted databases must not contain data for other databases. Also, must not contain a datastore that is shared by other virtual machines (VMs) or by other databases not being reverted.
- Make sure that the production databases are not on VMDK disks that are part of a VMware VM snapshot.
- All VM snapshots need to be removed from the SAP HANA server before you run the revert function.
- Production databases are automatically shut down during the revert.
- Revert is available only after a restore is completed.
When you create a job, you need to set the default revert action for the job. Only SAP HANA can use the revert database function. This behavior is controlled through the Revert Database option during the job creation process:
- Enabled – Always revert the database.
- Disabled – Never reverts the database.
- User Selection – Allows the user to make the determination to revert the database when the job session is pending.
Restriction: The revert function is not supported for HyperSwap environments, see APAR IT42565
The following commands are examples for creating and configuring an operating system user that IBM Storage Copy Data Management uses to log in to the application server. The command syntax might vary depending on your operating system type and version.
- Create the user that is designated as the IBM Storage Copy Data Management agent user:
useradd -m cdmagent - If you use password-based authentication, set a password:
passwd cdmagent
- Place the following lines at the end of your sudoers configuration file, typically /etc/sudoers. If the existing sudoers file is configured to import configuration from another directory (for example, /etc/sudoers.d), you can also place the lines in a new file in that directory:
Defaults:cdmagent !requiretty cdmagent ALL=(ALL) NOPASSWD:ALL
- The following commands are examples for creating and configuring a HANA database with minimum privileges to perform query / backup / restore operations. The prompt $> indicates command to execute from UNIX shell prompt and the prompt => indicates the command to execute on hdbsql prompt.
- Connect as SYSTEM user to SYSTEMDB
$> hdbsql -j -i 01 -n localhost -u SYSTEM -p <PASSWORD-FOR-SYSTEM-USER> -d SYSTEMDB
- Create required user with a temporary password and grant privileges
hdbsql SYSTEMDB=> CREATE USER scdm_admin PASSWORD change_on_first_logon_01;
hdbsql SYSTEMDB=> GRANT BACKUP ADMIN, CATALOG READ, DATABASE RECOVERY OPERATOR TO scdm_admin;
- Log in to SYSTEMDB with newly created user and change the password
$> hdbsql -j -i 01 -n localhost -u scdm_admin -p change_on_first_logon_01 -d SYSTEMDB
- You have to change your password.
- Enter new Password: <ENTER_NEW_PASSWORD_HERE>
- Confirm new Password: <ENTER_NEW_PASSWORD_HERE>
- Connect to SXX tenant database as SYSTEM user (without -d SYSTEMDB)
$> hdbsql -j -i 01 -n localhost -u SYSTEM -p <PASSWORD_FOR_SYSTEM_USER>
- Create user with same name (as the one created in SYSTEMDB) in tenant database and grant privileges
hdbsql S12=> CREATE USER scdm_admin PASSWORD change_on_first_logon_01;
hdbsql S12=> GRANT BACKUP ADMIN, CATALOG READ TO scdm_admin;
- Log into the tenant database with newly created user and change the password
$> hdbsql -j -i 01 -n localhost -u scdm_admin -p change_on_first_logon_01
- You have to change your password.
- Enter new Password: <ENTER_NEW_PASSWORD_HERE>
- Confirm new Password: <ENTER_NEW_PASSWORD_HERE>
Note: The username and password for the database user created in both SYSTEMDB and SXX tenant database must be identical. The privileges for the user differ in the respective databases. The table below lists the privileges.
| Database Type | Username | Password | Privileges |
|---|---|---|---|
| SYSTEMDB | scdm_admin | <password_for_scdm_admin> | BACKUP ADMIN, CATALOG READ, DATABASE RECOVERY OPERATOR |
| SXX tenant db | scdm_admin | <password_for_scdm_admin> | BACKUP ADMIN, CATALOG READ |
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCY00","label":"IBM Storage Copy Data Management"},"ARM Category":[{"code":"a8m3p000000hBYdAAM","label":"HW\/SW Requirements"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.25"}]
Product Synonym
IBM Spectrum Copy Data Management;
Was this topic helpful?
Document Information
Modified date:
12 June 2025
UID
ibm17177865