Escolar Documentos
Profissional Documentos
Cultura Documentos
0 for
SAP HANA User Guide
Abstract
This document provides instructions on using the HPE StoreOnce Catalyst Plug-in 2.0.0 for SAP
HANA. This document is intended for backup administrators and information technology (IT)
administrators familiar with the StoreOnce System and SAP HANA software. Always check
www.hpe.com/info/storeonce/docs for the most current plug-in documentation (listed under the
Installation information type). Refer to the HPE Data Availability, Protection and Retention
Compatibility Matrix on www.hpe.com/storage/DAPRCompatibility for supported client hardware.
Overview.......................................................................................................5
SAP HANA Plug-in supported operating systems and StoreOnce software....................................... 5
SAP HANA Plug-in supported database versions............................................................................... 5
StoreOnce Catalyst......................................................................................6
What is StoreOnce Catalyst?.............................................................................................................. 6
Benefits of StoreOnce Catalyst........................................................................................................... 6
StoreOnce Catalyst Terminology......................................................................................................... 6
2 Contents
Configuring SAP HANA CLI.............................................................................................................. 31
Performing SAP HANA Backup operations....................................................................................... 31
Extracting the Backup ID of SAP HANA backup............................................................................... 31
Cancelling SAP HANA Backup..........................................................................................................32
Checking SAP HANA Backup for Recovery...................................................................................... 32
Checking the integrity of SAP HANA backup objects........................................................................33
Performing SAP HANA restore operations........................................................................................34
Performing SAP HANA delete operations......................................................................................... 35
Troubleshooting.........................................................................................41
Best practices............................................................................................ 43
SAP HANA Plug-in............................................................................................................................ 43
StoreOnce Catalyst Best Practices................................................................................................... 43
Contents 3
Copyright 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use,
or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
SAP and SAP HANA are registered trademarks of SAP.
The StoreOnce Catalyst Plug-in for SAP HANA includes software developed by Jansson (www.digip.org/
jansson) and by the OpenSSL Project for use in the OpenSSL Toolkit (www.openssl.org/).
Overview
SAP HANA, an in-memory database, provides two primary backup and restore interfaces: file (including NFS)
and the more intelligent, third-party Backint interface. The StoreOnce Catalyst Plug-in for SAP HANA (SAP
HANA Plug-in) delivers a Backint integration for backing up and restoring SAP HANA instances directly to
StoreOnce Catalyst. The plug-in backs up and restores SAP HANA databases or logs in single server, scale
out cluster, or cloud SAP HANA deployments.
The SAP HANA Plug-in supports StoreOnce Catalyst stores as well as Federated Catalyst stores.
SUSE Enterprise Linux11 Service Pack 2 and later StoreOnce 3.12.2 and later
Red Hat Enterprise Linux 6 Service Pack 5 and later StoreOnce 3.12.2 and later
NOTE:
For the latest compatibility information, see the StoreOnce Catalyst section of the HPE Data Availability,
Protection and Retention Compatibility Matrix at www.hpe.com/storage/DAPRCompatibility .
IMPORTANT:
To run multi-stream backups on HANA installations, you need one of the following at a minimum:
SAP HANA version SPS11.2 PL06
SAP HANA version SPS12.2 PL02
Multi-stream backups with earlier versions can cause backup failures.
NOTE:
A SAP HANA instance is required to install the SAP HANA Plug-in.
Overview 5
StoreOnce Catalyst
This chapter provides an overview of StoreOnce Catalyst.
IMPORTANT:
For more information, including how to create, edit, and delete StoreOnce Catalyst and Federated
Catalyst stores, see the StoreOnce System user guide for your product.
6 StoreOnce Catalyst
Configuring the StoreOnce System for the SAP
HANA Plug-in
Creating StoreOnce Catalyst and Federated Catalyst stores
Manually create a StoreOnce Catalyst or Federated Catalyst store on your StoreOnce appliance to work with
the SAP HANA Plug-in.
Procedure
1. Log on to the StoreOnce Management Console (StoreOnce GUI) with administrator privileges.
2. Navigate to StoreOnce > StoreOnce Catalyst > Stores.
3. Click Create.
4. If using a StoreOnce B6200, 6500, or 6600 System, select a service set for the new store and click OK. To
create a Federated store, select multiple service sets; these service sets become the Federation
members.
5. Change the store details as appropriate. A table describing the store details can be found in the
StoreOnce Catalyst Stores page section of the StoreOnce System user guide for your product.
a. Name the StoreOnce Catalyst or Federated Catalyst store using a meaningful name.
b. Set the Primary (Default) Transfer Policy to Low Bandwidth or High Bandwidth. If the priority is
network efficiency and offloading processing to the media/backup server, select Low Bandwidth.
Before configuring StoreOnce Catalyst over Fibre Channel, ensure that media/database servers can
communicate with the StoreOnce appliance over a Fibre Channel network. The storage administrator must
ensure that any network segregation, such as zoning, is set up to handle required connectivity between the
server and appliance. See Zoning considerations for more information.
NOTE:
When using StoreOnce Catalyst over Fibre Channel:
Backups and optimized copies are supported on StoreOnce Catalyst over Fibre Channel interface
and over Ethernet networks.
Running StoreOnce Catalyst over Fibre Channel requires Administrator privileges to access OS-
specific device files associated with StoreOnce Catalyst over Fibre Channel devices.
StoreOnce Catalyst over Fibre Channel functions the same way as standard StoreOnce Catalyst (over
Ethernet); the backup application will not perceive a difference. However, some configuration is required to
set up the backup and restore connections between the ports on the StoreOnce System and the ports on the
client servers. Use the Fibre Channel Settings tab (available within the StoreOnce GUI only if StoreOnce
Catalyst over Fibre Channel is supported).
Initial configuration
Procedure
1. Locate the Identifier at the top of the screen. This Identifier is the Fibre Channel address of the StoreOnce
System and is used to identify the StoreOnce System in the backup application. It is in the format COFC-
<device-id>; you may provide an Identifier Alias to make it easier to identify from the backup
application. This Catalyst over Fibre Channel Identifier is provided to the backup application where an
Ethernet address would otherwise be provided.
2. In the Target Ports section, the default values are recommended. However, you can edit the speed if
necessary.
3. In the Devices section, locate the World Wide Port Name (WWPN) for each port on the StoreOnce
System. The WWPN is required to zone the client with the StoreOnce System. Use this information to
zone your client Fibre Channel ports with your StoreOnce Fibre Channel ports. When making use of
StoreOnce Catalyst Copy over Fibre Channel, both the source/destination initiator and the target devices
must also be zoned to communicate with each other over Fibre Channel. See Zoning considerations for
more information.
4. Important: Locate the Number of Devices per Initiator Port for each port. This value determines the
number of concurrent backup/restore and copy connections allowed from a single client Fibre Channel port
to a single StoreOnce Fibre Channel port, or from a source StoreOnce Fibre Channel port to a destination
StoreOnce Fibre Channel port. The setting applies to all StoreOnce Catalyst supported client operating
NOTE:
StoreOnce Catalyst-supported operating systems do not support opening multiple concurrent
StoreOnce Catalyst over Fibre Channel connections to a target StoreOnce Fibre Channel port by
default. Set the Number of Devices per Login correctly in the StoreOnce GUI so that multiple Fibre
Channel LUNs are presented to the client Fibre Channel port. This setting allows multiple
connections to be opened over Fibre Channel.
The "Number of Devices per Login" also applies to Linux Fibre Channel clients. Failure to set the
"Number of Devices per Login" correctly will result in backup failure due to lack of connectivity until
the configuration is corrected.
The number of paths available from one particular client or source StoreOnce node to a destination
StoreOnce service set is calculated as:
number of a client's ports zoned to a StoreOnce service set * number of
StoreOnce service set ports zoned to that client * devices per initiator count
Table 1: Example relationships between Device per Initiator Port and Number of
Connections
NOTE:
If the backup application or plug-in can open command sessions during a backup or restore, the
number of StoreOnce Catalyst over Fibre Channel devices available must be at least one more than
the number of streams.
10 Zoning considerations
same approach should be taken for StoreOnce Catalyst Copy over Fibre Channel zoning of source and
destination copy devices.
When zoning for StoreOnce Catalyst Copy over Fibre Channel, ensure that the source Initiator WWN is
zoned with the destination target WWN, and that the destination Initiator WWN is zoned with the source
target WWN. StoreOnce Catalyst Copy is a two way protocol and both the source and destination must be
able to communicate with each other over Fibre Channel.
Use small Fibre Channel zones limiting the number of Fibre Channel ports in each zone.
When using StoreOnce Federated Catalyst, the backup/media server communicates with each Federation
member directly. Ensure that at least one port belonging to each Federation member node is zoned with
the backup/media server. HPE recommends zoning multiple ports for higher availability and performance.
When using StoreOnce Catalyst over Fibre Channel to StoreOnce 6500 and 6600 appliances, ensure that
a backup/media server is zoned with both StoreOnce nodes in the couplet. On a failover event, the World
Wide Name of the sister node will be used to communicate with both StoreOnce service sets. This is
transparent to the backup application because applications connect using the StoreOnce Catalyst over
Fibre Channel Identifier or alias.
StoreOnce Catalyst over Fibre Channel does not make use of or rely on any external multi-path drivers.
Connections are balanced using StoreOnce Catalyst over Fibre Channel internal algorithms. Installed
multi-path drivers are ignored by Catalyst over Fibre Channel.
Client configurations
Once the client has been Fibre Channel zoned with the StoreOnce appliance, there are a number of
considerations for each operating system.
Windows Clients
Administrator permissions are required to run Catalyst over Fibre Channel backups.
StoreOnce Catalyst over Fibre Channel presents a device type of Processor. In Windows Device Manager,
these devices are shown as Other Devices. After zoning the devices or changing the Number of Devices per
Initiator Port, right-click Other Devices and select Scan for hardware changes to detect the new devices.
Linux Clients
StoreOnce Catalyst over Fibre Channel presents a device type of Processor. On Linux, these devices files
are created in /dev/sg*. By default, /dev/sg* devices are accessible by root users only. If backups are run
as a non-root user, first grant the backup user permissions to access these device files using a Linux udev
rule.
To create a udev rule:
1. Create a udev file in the following location on every backup server:
/etc/udev/rules.d/70-cofc.rules
2. Add the following rule to the file:
KERNEL=="sg[0-9]*", ATTRS{vendor}=="HPE*", ATTRS{model}=="StoreOnce CoFC*",
ATTRS{rev}=="CAT1", GROUP="##CORRECT_USER_GROUP##"
where ##CORRECT_USER_GROUP## is replaced by the Linux user group that will perform backups and
restores. For example, sapsys.
NOTE:
This rule is broken into separate lines to fit the confines of the PDF. Enter the rule as a continuous
line in the udev file.
Client configurations 11
AIX Clients
StoreOnce Catalyst over Fibre Channel presents a device type of Sequential on AIX. These device files
are created in /dev/rmt*. After zoning the devices or changing the Number of Devices per Initiator Port,
scan for device file changes by executing the cfgmgr command as a root user.
By default, /dev/rmt* device files are accessible by root users only. Running backups as a non-root user
requires an additional one-time configuration step of running storeonce-cofc-passthrough-
install.sh. This installation script must be run as root and can be found in the backup application
installation bin directory.
When using Catalyst over Fibre Channel from AIX in StoreOnce version 3.14.0 and later, an additional
configuration step is required in the StoreOnce GUI. Find the WWPN of the client AIX Fibre Channel port
and set the Emulation Mode to AIX on the Fibre Channel settings tab. Scan for device file changes by
executing the cfgmgr command as a root user.
HPE-UX Clients
StoreOnce Catalyst over Fibre Channel presents a device type of Processor. On HPE-UX, these devices
files are created in /dev/pt/ptX. After zoning the devices or changing the Number of Devices per Initiator
Port, scan for device file changes. Execute the ioscan -fnC /dev/pt command as a root user. By
default, /dev/pt/ptX devices are accessible by root users only. If backups are run as a non-root user, first
grant the backup user permissions to access these device files using chmod o+rwx /dev/pt/pt*.
For finer grained permissions, determine which /dev/pt/ptX device files relate to Catalyst over Fibre
Channel using:
/usr/sbin/scsimgr -p get_attr all_lun -a device_file -a dev_type -a pid | grep
StoreOnce
Then use chmod o+rwx on the appropriate devices.
Solaris Clients
StoreOnce Catalyst over Fibre Channel presents a device type of Processor. On Solaris, these devices files
are created in /dev/scsi/processor/*. After zoning the devices or changing the Number of Devices per
Initiator Port, scan for device file changes. Execute the following commands as a root user. These operations
will not affect Fibre Channel devices already configured on the Solaris system.
add_drv -vi scsiclass,03 sgen
update_drv -vai scsiclass,03 sgen
Procedure
1. Extract the compressed file using the command tar xvf <file name> to access the installer.sh
file.
2. Run installer.sh.
3. After the installer begins, the options menu will be displayed as follows:
Choose options
+------------------------+-------------+
| Operation | Option |
+------------------------+-------------+
| Install | 1 |
Pre-installation Summary
-----------------------------------------------------------------------
Product : HPE StoreOnce Catalyst SAP HANA Plug-in
Version : 2.0.0
Installation Base : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin
6. You will be prompted to select the type of backup network. Entire Y for WAN, or N for LAN.
NOTE:
A separate configuration for log backups would be generated which can be specified when
configuring HANA Studio for log backups or invoking command line interface.
Do you wish to configure StoreOnce Catalyst backup options for LOG backups?
(y/n) [Y] : y
Enter HPE StoreOnce backup node address [IPv4, IPv6, FQDN, CoFC] :
192.68.15.43 Enter HPE StoreOnce Catalyst store name to use for backup /
restore : HANA-log_Backup
Enter HPE StoreOnce Catalyst client ID. If not using Catalyst client
permission checking, leave empty [] Prod_DB_logs
CATALYST_STORE_ADDRESS : 192.68.15.42
CATALYST_STORE_NAME : HANA_Store
CATALYST_COPY1_STORE_NAME : DRCopy_Store
CATALYST_COPY1_STORE_ADDRESS : COFC-Y0330805VF02
CATALYST_STORE_ADDRESS : 192.68.15.43
CATALYST_STORE_NAME : HANAlog_Backup
CATALYST_COPY1_STORE_NAME : copy2
CATALYST_COPY1_STORE_ADDRESS : 192.168.15.87
HPE SAP-HANA plug-in version 2.0.0 installed successfully. Press any key to exit:
hn3adm@rhel65.uk:/hana/shared/tmp/HPE-Catalyst-SAP-HANA-plugin-2.0.0.1165-LINUX>
Example:
data_backup_parameter_file = /hana/shared/AM1/hpe/HPE-Catalyst-SAP-HANA-plugin/config/plugin.conf
log_backup_parameter_file=/hana/shared/AM1/hpe/HPE-Catalyst-SAP-HANA-plugin/config/plugin.conf
2. As HANA user <sid>adm, create a local directory on each of the cluster nodes under, /usr/sap/<SID>/
CatalystCredentials.
Example:
/usr/sap/AM1/CatalystCredentials (for am1adm user). The directory thus created should have permissions
for the Database user group (sapsys) and the SID user. This would enable all database users to access
the password file under the CatalystCredentials directory.
Run the StoreOnceCatalystCredentials tool on each of the cluster nodes and save the password file (using
-o option) to a file under the Credentials folder created above.
For more details, see Securing StoreOnce Catalyst Store Credentials.
NOTE:
The name of the password file generated on each of the node should be the same on all nodes (Ex:
password.pss), though each node will have a private copy of the file.
3. Edit the plug-in configuration file to point to the password file stored under the above location,
#CATALYST_CLIENT_PASSWORD_FILE:<PASSWORD_FILE_NAME>
Example:
CATALYST_CLIENT_PASSWORD_FILE:/usr/sap/AM1/CatalystCredentials/password.pss
Choose options
+------------------------+-------------+
| Operation | Option |
+------------------------+-------------+
| Install | 1 |
| Upgrade | 2 |
| Uninstall | 3 |
+------------------------+-------------+
Enter Selected Option [exit]:2
NOTE:
Our default installation path is changed to: /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin.
You can migrate to the new installation path.
NOTE:
The existing plug-in configuration shall be migrated during the upgrade. An option to configure Log
backups to a separate Catalyst target shall not be presented so that continuity of access to earlier
Backups for recovery is preserved. If you wish to still redirect Log Backups, you can manually edit
the template configuration file, plugin_log.conf, and configure Log backups.
However this change would render earlier Backups inaccessible for recovery.
To access or restore earlier Backups, revert to a single plug-in configuration file used before upgrade
so that both Data/log backups on same Backup target can be accessed.
6. The Final Upgrade Summary is displayed.
HPE StoreOnce Catalyst SAP HANA Plug-in-2.0.0 Upgrade successful:
Final Upgrade Summary
HPE SAP-HANA plug-in version 2.0.0 successfully upgraded. Press any key to exit.
CATALYST_COPY1_STORE_NAME StoreOnce Catalyst store name used for the first Optional
StoreOnce Catalyst copy target
NOTE:
Catalyst Command Traffic Address
accepts IPv4, IPv6, FQDN, and Catalyst
over Fibre Channel addresses
Catalyst Copy Address accepts IPv4,
IPv6, and FQDN addresses
Table Continued
APPLICATION_LOGSIZE Specifies the Application maximum log file size (in Mandatory
MB)
IMPORTANT:
You cannot perform SAP HANA backups until the SAP HANA Plug-in is reinstalled.
Option Description
Users are added, not echoed, when specifying user names and passwords on the CLI. Optionally, a
configuration file containing a client identifier can be specified and the utility will prompt for the password
which is then secured and stored in the output password file.
NOTE:
When using secured passwords, you must specify the location of the password file in the plug-in
configuration file.
Passwords specified in plain text will override the use of the password file option. (The
CATALYST_CLIENT_PASSWORD option is now deprecated and is not recommended.)
Options not specified on the command line will be pulled from the configuration file.
NOTE:
You cannot backup, copy, restore, or delete until you successfully complete the following steps.
Procedure
1. On the Systems panel, right-click your system and select Backup and Recovery > Open Backup
Console The following image is displayed:
The SAP HANA Plug-in can co-exist with other Backup application agents such as NetBackup agent.
However, at any given point of time, there can be only one symbolic link to Backint pointing to an
application agent or Plug-in. Therefore, only one application can be used at a time.
For example, a Netbackup agent can be configured as follows:
ln s /usr/openv/netbackup/bin/hdbbackint_script /usr/sap/<SID>/SYS/
global/hdb/opt/hdbbackint
To use the SAP HANA Catalyst Plug-in again you would need to remove the above symbolic link and
create a new one for the Plug-in:
ln s /hana/shared/<SID>/hp/HP-Catalyst-SAP-HANA-Plugin/bin/
backint /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
5. In the Data Backup section, in the Backint Parameter File field, enter the location of the configuration file
(the default is /hana/shared/hpe/HPE-Catalyst-SAP-HANA-plugin/config/plugin.conf).
This path is provided in the SAP HANA installation summary.
6. Save the configuration. SAP HANA Studio is now successfully configured.
IMPORTANT:
SAP HANA Backint does not support SAP HANA-managed StoreOnce Catalyst copy. Use the
StoreOnce Catalyst Copy tool, located in the bin directory of the SAP HANA Plug-in installation, to
perform StoreOnce Catalyst copy operations. The tool uses the same configuration file used for backup,
restore, and delete operations.
See Performing StoreOnce Catalyst Copy Operations for more information.
IMPORTANT:
You can also perform Log Backups using the SAP HANA Plug-in. Use the Data Backup configuration
file, or create and assign a dedicated Log Backup configuration file within SAP HANA Studio. You can
send Data Backups using Backint and Log backups using file" or both can be backed up using Backint.
Procedure
1. Double click the database instance and navigate to the Configuration tab.
2. Open the global.ini file and locate the backup information.
TIP:
To show only the backup information, enter
parallel_data_backup
in the filter.
3. Right-click the value of parallel_data_backup_backint_channels and change the parallel stream
to the desired number of parallel backup streams. A maximum of 32 streams are allowed.
NOTE:
Set the stream count at the host level only if you are using a multiple-host system.
Delta Backups
Delta backups are data backups supported from SPS 10 and onwards. They can be differential or incremental
backups:
Differential backup backs up all changes from the last full backup. They are slower (except when
performed for the first time) than incremental backups but have a faster recovery time.
Incremental backup only backs up changes from the last backup (full or delta). Incremental backups
consume less space than differential backups.
Cancelling a Backup
Cancel a backup on the HANA Studio Backup Progress Information page by clicking Cancel Backup.
You can also cancel a backup from the Backup Overview page.
NOTE:
Though log backups are also configured to write to StoreOnce Catalyst stores during backup
operations, the location specified here will not point to the StoreOnce Catalyst store.
6. Click Next.
7. SAP HANA will list the available data backups.
8. Select the backup to be restored, and click Check Availability to see if the backup is available on the
StoreOnce appliance.
NOTE:
Click Show More if you do not see the required backup in the list.
9. With the desired backup selected, click Next.
10. In the Check Availability of Log Backups section, select Third-Party Backup Tool (Backint) and change
other settings as needed.
11. Click Next. The screen displays a review of the settings.
12. Click Finish. A progress screen is displayed.
13. When the process is complete, the SAP HANA system will automatically restart and will be restored to
the selected backup from the StoreOnce Catalyst store.
IMPORTANT:
To restore from a StoreOnce Catalyst copy, you must modify the CATALYST_STORE_ADDRESS and
CATALYST_STORE_NAME parameters in your plug-in configuration file. Modifying the copy-specific
parameters is not enough when doing a restore because the CATALYST_STORE_ADDRESS and
CATALYST_STORE_NAME parameters are used to determine the location of the Catalyst backups.
NOTE:
The CATALYST_RESTORE_AUTOREDIRECT:ENABLE parameter:
Is required for restoring from alternate backups from disaster recovery sites.
Can be used to turn off Auto restore (by setting it to DISABLE) if you prefer not to trigger a redirect of
the restore by default. For example, if the the remote StoreOnce is connected over a low bandwidth
link and you do not want a slow restore to initiate automatically.
NOTE:
To delete log or delta backups, right-click on a full backup and select Delete older Backups. All
earlier backups (including full, delta, and log backups) will be deleted.
5. Click Next. The Review Backup Deletion Settings screen is displayed.
6. Click Finish. A confirmation screen is displayed.
7. Click OK to confirm the deletion. The catalog entry, and the associated backup items in the StoreOnce
Catalyst store if applicable, are now deleted.
NOTE:
Deleting a backup does not delete the copies made using the StoreOnce Catalyst Copy tool; use the
same tool to delete StoreOnce Catalyst copied items.
See Performing StoreOnce Catalyst Copy Operations on page 36 for more information.
[backup]
data_backup_parameter_file = <config file path>
log_backup_parameter_file = <config file path>
If these lines are not already in the file, add them and then change the data_backup_parameter_file
and log_backup_parameter_file parameters to the desired location of the SAP HANA Plug-in
configuration file. The default location of the plugin.conf file is: /hana/shared/HN1/hpe/HPE-
Catalyst-SAS-HANA-plugin/config/plugin.conf.
For more information, see the SAP article Customer-Specific Configuration Files.
NOTE:
If you are using the CLI for the first time on this server, set the configuration file location to the default
location because the location might not have already been configured.
If you are using a separate configuration file for Log backups you need to add the parameter file for log
backups as well:
For more information, see the SAP article Determining and checking Backups for Recovery
(hdbbackupdiagTool) located here:
Cancelling SAP HANA Backup 33
http://help.sap.com/saphelp_hanaplatform/helpdata/en/f6/0cd67cd71846a9ae3da198a78f7851/
content.htm
Procedure
1. Log in to the StoreOnce Management Console.
2. Navigate to StoreOnce > StoreOnce Catalyst > Stores.
3. Select the store containing the backups.
4. Select the Catalyst Item Summary tab.
5. Select the appropriate item.
For more information, see the SAP article Manual Backup Checks (hdbbackupcheck Tool).
IMPORTANT:
Check that the backup exists before starting a recovery.
NOTE:
Use --wait to make the script wait until the recovery has finished before reporting back. Otherwise,
you must manually check to find out if the recovery has finished.
NOTE:
Verify that a backup exists before attempting to delete it.
NOTE:
Use the COMPLETE option to delete the backup from both the server and the catalog. To delete the
backup from the catalog only, omit the COMPLETE option.
For more information, see the SAP article SQL Statements for Deleting Backups from the Backup Catalog.
Before running the StoreOnce Catalyst Copy tool, make sure that you configured your source and destination
store details in the configuration file either during the installation process or by manually editing the
configuration file.
The executable file StoreOnceCatalystCopy is located in the bin directory of the SAP HANA Plug-in
installation on the SAP HANA appliance; if you used the default installation path, the directory location is: /
hana/shared/<SID>/hpe/HPE-Catalyst-SAP-HANA-plugin/bin.
NOTE:
By default, the source and destination StoreOnce Catalyst store details are read from the
plugin.conf file located in the config folder. This file can be modified. See Performing StoreOnce
Catalyst Copy Operations.
When StoreOnce Catalyst client credential checking is enabled, the source and destination StoreOnce
Catalyst stores must use the same StoreOnce Catalyst credentials r to initiate a StoreOnce Catalyst
copy.
Help StoreOnceCatalystCopy --help Show the help for the StoreOnce Catalyst
Copy tool.
StoreOnceCatalystCopy -h
Copy StoreOnceCatalystCopy --copy Queue a copy job from the origin to the
destination StoreOnce Catalyst store.
StoreOnceCatalystCopy c
Different options and filters can be used to
choose which objects to copy. The
configuration file is read, by default, to
determine the origin and destination
addresses and StoreOnce Catalyst store
names. These names can be overridden
on the command line if necessary.
Copy operations of asynchronous, non-
blocking operations: after initiating a copy,
the command prompt will return. Use in
combination with --limit-copies to
poll for completed StoreOnce Catalyst
copies.
List StoreOnceCatalystCopy --list List the status of all running and queued
StoreOnce Catalyst copy jobs. Filters can
StoreOnceCatalystCopy -l
be used to limit or filter the output.
The following options can be used with the commands above. Run StoreOnceCatalystCopy --help for
more details.
Option Description
filtertagsand Filter items based on their StoreOnce Catalyst tag (exact match only).
filtercreateddaterange Only display StoreOnce Catalyst items that were created within a specific
date range. The date uses local time in the
dd/mm/yyyy-hr:min:sec
format.
filterqueuedfromaddress Filter jobs according to the client address that queued the copy job.
preview Do not execute the command, but preview what will happen if executed.
Always use the
--preview
option before calling
expire-items
and
cancel
.
config Change the configuration file the parameters are read from.
limit-copies By default, after all requested StoreOnce Catalyst copy jobs have been
queued,
StoreOnceCatalystCopy
will exit. Polling for completion is not performed. The
-limit-copies
option will poll for job completion before exiting. An optional parameter
[#]
can be provided to limit the number of copies that are queued in parallel.
IMPORTANT:
The StoreOnce Catalyst Copy tool uses the configuration file plugin.conf to determine the source
and destination information. These details can be overridden on the command line or by providing the
tool with the name of a different configuration file.
IMPORTANT:
Run the StoreOnce Catalyst Copy tool soon after performing a data backup. In cases where multiple
data backups are copied in one operation, deduplicaton ratios can be lower compared to copying them
sequentially. If copying many data backups in one operation, use the --limit-copies parameter of
StoreOnceCatalysCopy to limit the number of parallel copy jobs.
NOTE:
If you have configured SAP HANA database and transaction logs to be backed up to separate Backup
targets(StoreOnce Appliance/Catalyst Store), ensure you run the StoreOnceCatalystCopy utility twice
when making copies of the Backup,
1. Once for copying over SAP HANA Database files (Data Backup) and
2. Once for copying over the transaction logs (Log Backups)
So that you have a full working set of the Backups for Disaster Recovery (DR). Copying over only Data
Backups and ignoring the log Backups can render your DR copy unusable and potentially lead to
situations where the SAP HANA database is unrecoverable in the event of loss of primary Backup set.
Error message: The configuration file assigned Verify that the configuration file
does not exist or is in the wrong exists. If so, compare the file with
Could not back up system
format. the template (
<SID>
plugin_template.conf
backup could not be
completed, Backint exited ) to check formatting and values.
with exit code 1 instead
of 0. console output:
Logger not initialized.
Message : Unable to read
config file '<file path>'
Table Continued
Troubleshooting 41
Symptom Possible Cause Solutions
Backint agent is not shown in SAP The symbolic link to Backint does Navigate to the
HANA Studio. not exist.
/usr/sap/<SID>/SYS/
global/hdb/opt
path and ensure a symbolic link to
backint
exists. This path assumes that the
installation used the default path. If
you changed the location of the
plug-in, update the path and try
again.
If running on a scale out SAP
HANA appliance, ensure the plug-
in is installed on all nodes in the
cluster.
Error message: The backup ID is not valid. Check if the backup you are trying
to restore is valid by using the
ERROR RECOVERY RECOVER
check backup tool. See Checking
DATA finished with error:
SAP HANA Backup for
[449] recovery strategy
Recovery on page 32
could not be determined,
[111014] The backup with for more details.
backup id '1430' cannot
be used for recovery
recoverSys failed
A retry a of backup/restore The open backup/restore session Use one of the following methods:
operation that failed due to a remains open but idle on the
Wait for the idle job to time-out
connection failure can fail again. StoreOnce.
(in four hours) and retry the
operation.
Restart the StoreOnce service
set to release/terminate all
open sessions.
42 Troubleshooting
Best practices
Best practices 43
Support and other resources
Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:www.hpe.com/
assistance
To access documentation and support services, go to the Hewlett Packard Enterprise Support Center
website:www.hpe.com/support/hpesc
Information to collect
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
Accessing updates
Some software products provide a mechanism for accessing software updates through the product
interface. Review your product documentation to identify the recommended software update method.
To download product updates, go to either of the following:
Hewlett Packard Enterprise Support Center
Get connected with updates
page: www.hpe.com/support/e-updates
Software Depot website: www.hpe.com/support/softwaredepot
To view and update your entitlements, and to link your contracts and warranties with your profile, go to the
Hewlett Packard Enterprise Support Center
More Information on Access to Support Materials
page:www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HPE Passport set up with relevant
entitlements.
Websites
Website Link
Table Continued
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us
improve the documentation, send any errors, suggestions, or comments to Documentation Feedback
(docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition,
and publication date located on the front cover of the document. For online help content, include the product
name, product version, help edition, and publication date located on the legal notices page.
Documentation feedback 45
Hewlett Packard Enterprise End User License
Agreement
1. Applicability. This end user license agreement (the "Agreement") governs the use of accompanying
software, unless it is subject to a separate agreement between you and Hewlett Packard Enterprise
Company and its subsidiaries ("HPE"). By downloading, copying, or using the software you agree to this
Agreement. HPE provides translations of this Agreement in certain languages other than English, which
may be found at: www.hpe.com/software/SWLicensing.
2. Terms. This Agreement includes supporting material accompanying the software or referenced by HPE,
which may be software license information, additional license authorizations, software specifications,
published warranties, supplier terms, open source software licenses, and similar content ("Supporting
Material"). Additional license authorizations are at: www.hpe.com/software/SWLicensing.
3. Authorization. If you agree to this Agreement on behalf of another person or entity, you warrant you
have authority to do so.
4. Consumer Rights. If you obtained software as a consumer, nothing in this Agreement affects your
statutory rights.
5. Electronic Delivery. HPE may elect to deliver software and related software product or license
information by electronic transmission or download.
6. License Grant. If you abide by this Agreement, HPE grants you a non-exclusive non-transferable license
to use one copy of the version or release of the accompanying software for your internal purposes only,
and is subject to any specific software licensing information that is in the software product or its
Supporting Material.
Your use is subject to the following restrictions, unless specifically allowed in Supporting Material:
You may not use software to provide services to third parties.
You may not make copies and distribute, resell, or sublicense software to third parties.
You may not download and use patches, enhancements, bug fixes, or similar updates unless you
have a license to the underlying software. However, such license doesn't automatically give you a
right to receive such updates and HPE reserves the right to make such updates only available to
customers with support contracts.
You may not copy software or make it available on a public or external distributed network.
You may not allow access on an intranet unless it is restricted to authorized users.
You may make one copy of the software for archival purposes or when it is an essential step in
authorized use.
You may not modify, reverse engineer, disassemble, decrypt, decompile or make derivative works of
software. If you have a mandatory right to do so under statute, you must inform HPE in writing about
such modifications.
7. Remote Monitoring. Some software may require keys or other technical protection measures and HPE
may monitor your compliance with the Agreement, remotely or otherwise. If HPE makes a license
management program for recording and reporting license usage information, you will use such program
no later than 180 days from the date it is made available.
8. Ownership. No transfer of ownership of any intellectual property will occur under this Agreement.
9. Copyright Notices. You must reproduce copyright notices on software and documentation for authorized
copies.
10. Operating Systems. Operating system software may only be used on approved hardware and
configurations.
11. 90-day Limited Warranty for HPE Software.