You are on page 1of 48

HPE StoreOnce Catalyst Plug-in 2.0.

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.

Part Number: EH991-10567


Published: March 2017
Edition: 3
Contents

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

Configuring the StoreOnce System for the SAP HANA Plug-in..............7


Creating StoreOnce Catalyst and Federated Catalyst stores..............................................................7
Configuring StoreOnce Catalyst Store Access Control ...................................................................... 7
Configuring StoreOnce Catalyst over Fibre Channel.......................................................................... 8
Initial configuration....................................................................................................................8
Zoning considerations.............................................................................................................10
Client configurations............................................................................................................... 11

Installing, configuring, and upgrading the SAP HANA Plug-in.............14


Downloading the SAP HANA Plug-in................................................................................................ 14
Opening the SAP HANA Plug-in installer.......................................................................................... 14
Installing and Configuring the SAP HANA Plug-in.............................................................................15
Setting up Plug-in for a SAP HANA Scale out Cluster...................................................................... 17
Setting up a HANA scale out............................................................................................................. 17
Upgrading the SAP HANA Plug-in.....................................................................................................18
Manually configuring the SAP HANA Plug-in.................................................................................... 19

Uninstalling the SAP HANA Plug-in.........................................................23


Securing StoreOnce Catalyst store credentials.................................................................................23

Configuring SAP HANA Studio................................................................ 25

Performing SAP HANA Operations using SAP HANA Studio............... 27


SAP HANA Full Backups...................................................................................................................27
Delta Backups................................................................................................................................... 27
Running Delta Backups.......................................................................................................... 28
Cancelling a Backup..........................................................................................................................28
SAP HANA Restores......................................................................................................................... 28
Resuming restore operations..................................................................................................29
Intelligent Restore Auto Restore of backups using disaster recovery copies.................................29
SAP HANA Deletes........................................................................................................................... 29

Using SAP HANA CLI................................................................................ 31

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

Performing StoreOnce Catalyst Copy Operations................................. 36


Automating the Use of the StoreOnce Catalyst Copy Tool................................................................40

Troubleshooting.........................................................................................41

Best practices............................................................................................ 43
SAP HANA Plug-in............................................................................................................................ 43
StoreOnce Catalyst Best Practices................................................................................................... 43

Support and other resources................................................................... 44


Accessing Hewlett Packard Enterprise Support................................................................................ 44
Accessing updates............................................................................................................................ 44
Websites............................................................................................................................................44
Documentation feedback...................................................................................................................45

Hewlett Packard Enterprise End User License Agreement................... 46

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.

SAP HANA Plug-in supported operating systems and


StoreOnce software
Operating system StoreOnce supported software version

SUSE Enterprise Linux11 Service Pack 2 and later StoreOnce 3.12.2 and later

SUSE Enterprise Linux 12 Service Pack 1 StoreOnce 3.12.2 and later

Red Hat Enterprise Linux 6 Service Pack 5 and later StoreOnce 3.12.2 and later

Red Hat Enterprise Linux 7.2 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 .

SAP HANA Plug-in supported database versions


SAP HANA version SPS 08 and later.

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.

What is StoreOnce Catalyst?


StoreOnce Catalyst is a StoreOnce function that allows backup applications to:
Back up data to a target store on the StoreOnce System. Deduplication may occur on the media server,
backup/database server, or StoreOnce System.
Copy jobs between StoreOnce Systems. Configuration occurs within the backup application, making
StoreOnce Catalyst an attractive alternative to using the replication function on the StoreOnce System.

Benefits of StoreOnce Catalyst


The backup application is in full control of data for the full lifecycle of the backup data.
The backup application has full visibility of all items and jobs on the StoreOnce System.
Deduplication can occur on either the media server or StoreOnce System which ensures efficient use of
the available bandwidth.
There is no enforced limit on the number of StoreOnce Catalyst items within a store.
Copy jobs are initiated from the application and have none of the complexities of replication mapping.
If StoreOnce Catalyst device types are used, space reclamation is more automated and easier to
implement from within the backup application.

StoreOnce Catalyst Terminology


StoreOnce Catalyst: the name of the StoreOnce interface
StoreOnce Catalyst stores: the targets/device types in which backups are stored on the StoreOnce
System
StoreOnce Catalyst Federated stores: a group of up to eight service sets within the same cluster that
share backup jobs as a federation on the StoreOnce System
StoreOnce Catalyst items: the backup items stored in the StoreOnce Catalyst stores on the StoreOnce
System
StoreOnce Catalyst clients: the generic term for applications that connect using the StoreOnce Catalyst
interface
Data jobs: any backup or restore job
StoreOnce Catalyst Optimized Backups: backups performed on the media server or backup server
(instead of the StoreOnce System) so only unique data is sent to the StoreOnce System using a low
bandwidth transfer protocol. Actual performance varies depending upon the data and disk I/O speeds.
Copy jobs: true copies of the data (not mirror images). The backup application specifies the source store
(outbound copy job) and destination store (inbound copy job). Once copied, the two versions are
independent of each other and either version can be deleted, moved, or added to from the backup
application. The backup application initiates copies. Copy jobs are supported over Ethernet and Fibre
Channel.
StoreOnce Catalyst Optimized Copy: the source and destination stores negotiate so that only unique
data is transferred and the copy job is completed in a bandwidth-efficient manner.

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.

6. Click Create. A StoreOnce Catalyst or Federated Catalyst store is created.


7. The store will appear in the top panel indicating the StoreOnce System is configured and ready to accept
backups.

Configuring StoreOnce Catalyst Store Access Control


In setting client access control, two modes can be set on StoreOnce Catalyst stores:
No client credential checking Allows all clients to have access to the StoreOnce Catalyst store.
Client credential checking Allows a select group of client identifiers to have access to the StoreOnce
Catalyst store.
To enable this mode, client access permission checking must be enabled on the StoreOnce > StoreOnce
Catalyst > Settings tab of the StoreOnce GUI. In addition, an individual StoreOnce Catalyst store must
grant access for the client identifier within the Permissions tab of a StoreOnce Catalyst store.

Configuring the StoreOnce System for the SAP HANA Plug-in 7


NOTE:
Access to StoreOnce Catalyst stores is controlled through client identifiers with optional passwords.
When using StoreOnce Catalyst copy operations for "Mirror To Stores" or "Async Copy," the source and
destination StoreOnce Catalyst stores must use identical credentials (client identifier and password).
Failure to do so leads to failed mirror or async copy operations.

Configuring StoreOnce Catalyst over Fibre Channel


NOTE:
If using Fibre Channel, consult the HPE Data Availability, Protection and Retention Compatibility Matrix
to ensure that client HBAs, switches, Fibre Channel driver, and firmware versions are supported.

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

8 Configuring StoreOnce Catalyst over Fibre Channel


systems (Linux, AIX, HPE-UX, Windows, Solaris), and also applies to StoreOnce Catalyst Copy over Fibre
Channel.
Increase this value if multiple concurrent backup/copy streams are required; the maximum allowed is 256
devices per client Fibre Channel port login. If this value is increased, a device file rescan on the client is
needed before the change is recognized. If the number of devices is reduced, client operating systems will
not delete StoreOnce Catalyst over Fibre Channel device files after a rescan. Operating systems will only
clear outdated device files on a reboot.

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

Per Client StoreOnce System Devices per Initiator Number of concurrent


Port backup/restore/copy
sessions
1

1 port zoned to 4 ports 1 4

2 ports zoned to 4 ports 1 8

2 ports zoned to 2 ports 4 16

2 ports zoned to 4 ports 8 64


1 Per client Fibre Channel port to StoreOnce port relationship, and source StoreOnce port to destination
StoreOnce port for StoreOnce Catalyst copy.

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.

Configuring the StoreOnce System for the SAP HANA Plug-in 9


Zoning considerations
Important: Non-optimal Fibre Channel SAN zoning can lead to a lack of Fibre Channel connectivity. HPE
recommends the following configurations:
Every backup/media server should zone at least two Fibre Channel ports with at least two StoreOnce node
Fibre Channel ports across different Fibre Channel cards, ideally across different SANs. Multiple
connections allow for higher availability. If a connection is broken, StoreOnce Catalyst over Fibre Channel
will automatically attempt to connect on a different path without failing the backup. The backup will fail from
a lack of connection only if no paths are available from the media/backup server or to the StoreOnce. The

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.

3. Rescan for Linux device file changes to update the permissions.


The lsscsi --generic command can be used to determine which /dev/sg* device files belong to
Catalyst over Fibre Channel.

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

12 Configuring the StoreOnce System for the SAP HANA Plug-in


By default, /dev/scsi/processor/* 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 -R o
+rwx /dev/scsi/processor/*.
For finer grained permissions, determine which /dev/scsi/processor/* device files relate to Catalyst
over Fibre Channel using:
for i in /dev/scsi/processor/*; do echo $i; ls $i; luxadm inq $i | egrep
"Vendor|Product"; echo; done
Then use chmod -R o+rwx on the appropriate devices.

Configuring the StoreOnce System for the SAP HANA Plug-in 13


Installing, configuring, and upgrading the SAP
HANA Plug-in
Downloading the SAP HANA Plug-in
Download the SAP HANA Plug-in installer zip file. Find the file at www.hpe.com/storage/StoreOnce/SAP.

Opening the SAP HANA Plug-in installer


IMPORTANT:
To ensure the correct file permissions, download the installer file and install the plug-in using the SAP
HANA operating system user <SID>adm. Do not use root. (If the installer is downloaded using root,
change the ownership and permissions to <SID>adm before installation.)
If the SAP HANA Plug-in is being installed on a SAP HANA system which has previously installed a
Backint plug-in from another vendor, first uninstall the other version of Backint. Ensure the directory
usr/sap/<SID>/SYS/global/hdb/opt does not exist before installing the SAP HANA Plug-in.
During installation, you will be prompted to specify if the backup is over a WAN or a LAN network.
Choose the correct option for your network configuration so the plug-in is optimally configured for
performance.
You will also be prompted to optionally choose a separate Backup target for SAP HANA log backups. If
you wish to Backup log files to an alternate location, provide the StoreOnce Appliance and/or Catalyst
Store details suitably.

Procedure
1. Extract the compressed file using the command tar xvf <file name> to access the installer.sh
file.
2. Run installer.sh.

TEST1:/usr/sap/HN3/HDB00/install> tar xvf HPE-*.tar


HPE-Catalyst-SAP-HANA-plugin/
HPE-Catalyst-SAP-HANA-plugin/utils.sh
HPE-Catalyst-SAP-HANA-plugin/installer.sh
HPE-Catalyst-SAP-HANA-plugin/configs.sh
HPE-Catalyst-SAP-HANA-plugin/plugin.tar

3. After the installer begins, the options menu will be displayed as follows:

Welcome to HPE StoreOnce Catalyst SAP HANA Plug-in-2.0 Installation/Un-


installation Wizard

Choose options

+------------------------+-------------+
| Operation | Option |
+------------------------+-------------+
| Install | 1 |

14 Installing, configuring, and upgrading the SAP HANA Plug-in


| Upgrade | 2 |
| Uninstall | 3 |
+------------------------+-------------+
Enter Selected Option [exit]:
4. Enter 1 to install or reinstall the SAP HANA Plug-in, 2 to upgrade the plug-in, or 3 to remove any existing
version of the plug-in.

Installing and Configuring the SAP HANA Plug-in


Procedure
1. Enter the SAP-HANA system ID (for example, HN3). The installer will check for a previous version of the
plug-in.
2. Enter y to continue with the installation.
3. Press the Enter key to accept the default installation path (recommended), or change to the desired
location (only for a specific reason) and press Enter. The Pre-installation Summary screen is shown:

Please enter SAP-HANA system id : HN3


Enter installation path or press 'enter' to install to default location [/
hana/shared/HN3] :
Continuing installation on default path [/hana/shared/HN3]

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

Do you wish to continue? (y/n) [Y] : y

4. HPE StoreOnce Catalyst SAP HANA Plug-in-2.0.0 installation successful

Post 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
Installed binary path : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/bin
Installed log path : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/logs

5. Enter y to configure StoreOnce Catalyst backup options

Do you wish to configure StoreOnce Catalyst backup options? (y/n) [Y] : y


Enter HPE StoreOnce backup node address [IPv4, IPv6, FQDN, CoFC] :
192.68.15.42
Enter HPE StoreOnce Catalyst store name to use for backup / restore :
HANA_Store
Enter HPE StoreOnce Catalyst client ID. If not using Catalyst client
permission checking, leave empty [] Prod_DB

6. You will be prompted to select the type of backup network. Entire Y for WAN, or N for LAN.

Installing and Configuring the SAP HANA Plug-in 15


Are StoreOnce Catalyst backups to be performed over a Wide Area Network (WAN)? (y/n) [N]

Enter y to configure StoreOnce Catalyst copy options (recommended) or n to


skip.
Do you wish to configure StoreOnce Catalyst Copy options? (y/n) [N] : y
Enter HPE StoreOnce Catalyst copy store[1] address [IPv4, IPv6, FQDN,
COFC] :COFC-Y0330805VF02
Enter HPE StoreOnce Catalyst copy store[1] name :DRCopy_Store

7. Enter y to configure separate Backup target for HANA Log backups.

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

8. Final Installation Summary is displayed:


HPE StoreOnce Catalyst SAP HANA Plug-in-2.0.0 installation successful

Final 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
Installed config path : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/config/plugin.conf
: /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/config/plugin_log.conf
Installed log path : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/logs

StoreOnce Catalyst Configuration for DATA Backups

CATALYST_STORE_ADDRESS : 192.68.15.42
CATALYST_STORE_NAME : HANA_Store
CATALYST_COPY1_STORE_NAME : DRCopy_Store
CATALYST_COPY1_STORE_ADDRESS : COFC-Y0330805VF02

16 Installing, configuring, and upgrading the SAP HANA Plug-in


StoreOnce Catalyst Configuration for LOG Backups

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>

Setting up Plug-in for a SAP HANA Scale out Cluster


For setting up a HANA scale out with Catalyst plug-in, the following requirements need to be met:
The plug-in and the associated folders and configuration settings need to be visible on all nodes.
Each node should have a private copy of the obfuscated catalyst credentials (since the logic of password
obfuscation ties it down to a local node and a password file generated on one node would not work on
another node).

Setting up a HANA scale out


Procedure
1. Install the plug-in on one of the cluster nodes (as per install instructions for a standalone setup). The plug-
in installs into /hana/shared directory and will be accessible from all the nodes. When specifying the plug-
in configuration file path, edit the file '/hana/shared/<SID>/global/hdb/custom/config/global.ini', and ensure
that the paths for the data and log backup parameter files are set to their absolute paths.

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

Setting up Plug-in for a SAP HANA Scale out Cluster 17


Upgrading the SAP HANA Plug-in
Procedure
1. Run the installer to view the options menu.

Welcome to HPE StoreOnce Catalyst SAP HANA Plug-in-2.0 Installation/Un-


installation Wizard

Choose options

+------------------------+-------------+
| Operation | Option |
+------------------------+-------------+
| Install | 1 |
| Upgrade | 2 |
| Uninstall | 3 |
+------------------------+-------------+
Enter Selected Option [exit]:2

2. Enter 2 to upgrade the plug-in.


3. The current installation path is shown.

Please enter SAP-HANA system id : HN3


/hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin
Please provide the installation path to upgrade :
/hana/shared/HN3/hp/HPE-Catalyst-SAP-HANA-plugin
4. Enter the same path as the earlier installation or choose the new path for the upgrade: /hana/
shared/HN3/hp/HP-Catalyst-SAP-HANA-plugin
Please provide the installation path to upgrade : /hana/shared/HN3/hp/HP-
Catalyst-SAP-HANA-plugin

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.

Do you want to migrate to new default installation path? (y/n) [N] : y


Copying existing installation files to /hana/shared/HN3/hpe/HPE-Catalyst-SAP-
HANA-plugin
5. The Pre-upgrade Summary screen is shown before completion of the upgrade:

Pre Upgrade Summary


------------------------------------------------------------------------
Product : HPE StoreOnce Catalyst SAP HANA Plug-in
Version : 2.0.0
Installation Base : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin

Do you wish to migrate old configuration files to latest compatible


configuration files? (y/n) [Y] : y

18 Upgrading the SAP HANA Plug-in


Please provide the full path to your existing configuration directory [/hana/
shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin/config] :

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

Product : HPE StoreOnce Catalyst SAP HANA Plug-in


Version : 2.0.0
Installation Base : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin
Installed config path : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/config
Installed log path : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-
plugin/logs

HPE SAP-HANA plug-in version 2.0.0 successfully upgraded. Press any key to exit.

Manually configuring the SAP HANA Plug-in


Creating the SAP HANA Plug-in configuration file via the installation process is recommended; you can edit
this configuration file. In addition, you can manually create and edit a new configuration file.
To create a configuration file, copy and rename the plugin_template.conf file located in the config
installation directory. You will edit the copied file.
To edit the configuration file created by the installer, edit plugin.conf.
Any parameters not listed in the Editable Parameters table are considered advanced; do not edit them unless
advised to by Hewlett Packard Enterprise Support.

Table 2: Editable Parameters of the Configuration File

Name Description Mandatory


/ Optional

Basic StoreOnce Catalyst Settings

CATALYST_STORE_ADDRESS StoreOnce node address used for backups. Supply Mandatory


the address of the StoreOnce service set. Accepts
IPv4, FQDN, StoreOnce Catalyst over Fibre
Channel, and IPv6. Use quotation marks for IPv6
addresses, for example, fdca:cd45:5ab0:995::7.
Table Continued

Manually configuring the SAP HANA Plug-in 19


Name Description Mandatory
/ Optional

CATALYST_STORE_NAME StoreOnce Catalyst store name used for backups Mandatory

CATALYST_CLIENT_NAME If Client Permission Checking is enabled, provide Optional


the StoreOnce Catalyst client identifier defined on
the StoreOnce appliance for granting read/write to
the primary backup target

CATALYST_CLIENT_PASSWORD_FILE If Client Permission Checking is enabled, provide Optional


the name of a StoreOnce Catalyst client password
file. The password file must be created using the
StoreOnce Catalyst Credentials tool.

CATALYST_TAG Identifies the StoreOnce Catalyst images on the Optional


StoreOnce appliances associated with the current
database server

CATALYST_MAX_STREAMS By default, SAP will create as many backup Optional


streams as possible. Use this setting to limit the
number of parallel StoreOnce Catalyst streams per
backup (the default is 20). For maximum
performance and to back up all data files in parallel,
make sure that the number is twice the number of
data files. This can be limited by the number of data
jobs supported by the server (or free when running
the backup).

StoreOnce Catalyst Copy Targets

CATALYST_COPY1_STORE_ADDRES StoreOnce node address of the first StoreOnce Optional


S Catalyst copy target. Accepts IPv4, FQDN, and
IPv6. Use quotation marks for IPv6 addresses, for
example, fdca:cd45:5ab0:995::7.

CATALYST_COPY1_STORE_NAME StoreOnce Catalyst store name used for the first Optional
StoreOnce Catalyst copy target

CATALYST_COPY_REDIRECT_ADDRE Addressing method to split StoreOnce Catalyst Optional


SS command and copy paths. If selected, provide an
address for copy operations:
CATALYST_COPY_REDIRECT_ADDRESS:<Cataly
st Command Traffic Address>:<Catalyst
Copy Address>

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

20 Installing, configuring, and upgrading the SAP HANA Plug-in


Name Description Mandatory
/ Optional

Advanced StoreOnce Catalyst Settings

CATALYST_PAYLOAD_CHECKSUM When StoreOnce Catalyst data payloads are Optional


transferred, a StoreOnce Catalyst payload
checksum is created to ensure data integrity. This
checksum is only required for WAN-based transfers
where network layer checksums are insufficient.
LAN and Catalyst over Fibre Channel backup have
sufficient checksum capabilities. Set to Enable for
WAN environments and Disable for LAN/Catalyst
over Fibre Channel.

CATALYST_BODY_PAYLOAD_COMPR StoreOnce Catalyst data payloads can be Optional


ESSION compressed when they are transferred.
Compression is beneficial for WAN-based transfers
where bandwidth is often limited but compression is
not necessary for LAN and Catalyst over Fibre
Channel data transfers. Set to Enable for WAN
environments and Disable for LAN/Catalyst over
Fibre Channel.

Log File Settings

CATALYST_LOGFILE StoreOnce Catalyst log file located under the Mandatory


logs
folder relative to the installation path (default is
Catalyst_SAPHANA.log
)

CATALYST_LOGLEVEL Specifies the StoreOnce Catalyst client-side logging Mandatory


level. Accepts ERROR, QUIET, INFO, TRACE,
DEBUG, or EXTENDED_DEBUG. The default
(recommended) is ERROR. You can temporarily set
this level to INFO for support investigations; after
the investigation, reset log levels to ERROR.

CATALYST_LOGSIZE Specifies the StoreOnce Catalyst client-side Mandatory


maximum log file size (in MB)

APPLICATION_LOGFILE Application-specific log file located under the Mandatory


logs
folder relative to the installation path (default is
Connector_SAPHANA.log
)
Table Continued

Installing, configuring, and upgrading the SAP HANA Plug-in 21


Name Description Mandatory
/ Optional

APPLICATION_LOGLEVEL Specifies the Application logging level. Accepts: Mandatory


ERROR: Log only error messages
QUIET: Instrumentation logging
INFO: Log function entry/exit points (this level is
the one to use for support investigations)
TRACE: Log extra functions entry/exit points
DEBUG: Detailed logging of operations and
related states
EXTENDED_DEBUG: Verbose logging of
operations and related states. This level will
impact performance.
The default (recommended) is ERROR. You can
temporarily set the level to INFO for support
investigations; after the investigation, reset log
levels to ERROR.

APPLICATION_LOGSIZE Specifies the Application maximum log file size (in Mandatory
MB)

APPLICATION_ROLLUP_LOGS Number of log files for application log rotation Mandatory


(default is 10)

22 Installing, configuring, and upgrading the SAP HANA Plug-in


Uninstalling the SAP HANA Plug-in
Procedure
1. Run installer.sh.
2. After the installer has started, the options menu will be displayed.
3. Enter 3 to uninstall.
4. Enter the SAP-HANA system ID (for example, HN3).
5. The installer will check for a previous version of the plug-in and provide the installation path.
6. Enter y to continue with the uninstallation.
7. Copy the installation path provided and enter it as the installation path to uninstall.
8. The Un-installation Summary screen appears.
9. Enter y to continue.
10. When the plug-in is uninstalled, a confirmation message is displayed.

Enter Selected Option [exit]:3


Please enter SAP-HANA system id : HN3
/hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin
Please provide the installation path to un-install, leave blank to continue to
main screen [ ]:
/hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin

Pre Un-installation Summary


------------------------------
Product : HPE StoreOnce Catalyst SAP HANA Plug-in
Version : 2.0
Installation Base : /hana/shared/HN3/hpe/HPE-Catalyst-SAP-HANA-plugin
HPE SAP-HANA plug-in version 2.0 will be un-installed. Any running jobs may be
interrupted
Do you wish to proceed with un-installation activities (y/n) [N] :y
HPE SAP-HANA plug-in version 2.0 successfully un-installed. Press any key to
exit.

IMPORTANT:
You cannot perform SAP HANA backups until the SAP HANA Plug-in is reinstalled.

Securing StoreOnce Catalyst store credentials


A StoreOnce Catalyst store can be access controlled by selectively allowing access to one or more
StoreOnce Catalyst client identifiers validated by a corresponding password against the store. The plug-in
provides a tool to store client credentials on disk in a secure format. The secure file can then be passed as a
parameter to the plug-in via the plug-in configuration file. Example:
CATALYST_CLIENT_PASSWORD_FILE:passwordstore.pss
A command line utility, StoreOnceCatalystCredentials (located in the plug-in bin directory), accepts
an appliance address along with client IDs and passwords to be passed in as parameters. The password is
obfuscated and stored with the user ID against the appliance address in an output file you specify. The
password file location provided in the plug-in configuration file is used by the plug-in to validate access to
StoreOnce Catalyst stores during execution of database application operations.

Uninstalling the SAP HANA Plug-in 23


Table 3: StoreOnceCatalystCredentials utility command options

Option Description

-u, --username StoreOnce Catalyst client ID

-s, --server StoreOnce server address

-c, --config Configuration file path

-a, --add Add a user entry

-e, --edit Edit a user entry

-d, --delete Delete a user entry

-l, --list List all existing user entries

-o, --output Password file path

-v, --version Output the StoreOnceCatalystCredentials utility


version information

-h, --help Print help information to the console

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.

24 Uninstalling the SAP HANA Plug-in


Configuring SAP HANA Studio
Before you begin configuring, make sure that the SAP HANA system is added to SAP HANA Studio and you
have access to it from the SAP HANA Studio Systems panel.

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:

2. Click the Configuration tab.


3. Expand Backint Settings.
4. The Backint Agent field displays the location of the Backint executable that will be used for backups. The
correct path confirms that SAP HANA has detected the SAP HANA Plug-in.

Configuring SAP HANA Studio 25


IMPORTANT:
If the Backint executable path is not displayed, ensure that the installation was successful on all SAP
HANA nodes.
Also, click Refresh on the Configuration tab.

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.

26 Configuring SAP HANA Studio


Performing SAP HANA Operations using SAP
HANA Studio
Before beginning a backup, restore, or delete, make sure that you have completed all the steps in
Configuring SAP HANA Studio on page 25.
Beginning with SAP HANA SPS 11, backups greater than 128 GB can with run with multiple streams. To
enable this feature:

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.

SAP HANA Full Backups


Procedure
1. On the SAP HANA Studio Systems panel, right-click your system and select Backup and Recovery >
Back up System....
2. Change the Backup Type to Complete Data Backup.
3. Change the Destination Type to Backint. Customize the Backup Prefix field as needed. This prefix can be
used to identify the StoreOnce Catalyst item created during a backup.
4. Click Next. A backup summary is displayed.
5. Click Finish to start the backup. The progress is shown on the screen.
6. At successful completion, the Backup Execution Summary screen is displayed. The SAP HANA system is
now backed up to the StoreOnce System using Backint.

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.

Performing SAP HANA Operations using SAP HANA Studio 27


Running Delta Backups
Procedure
1. In HANA Studio, right-click the database instance.
2. Navigate to Backup and Recovery > Back Up System.
3. In the Specify Backup Settings window, select Differential Data Backup or Incremental Data Backup
as the Backup and Destination Types.
4. Enter other information as needed.
5. Click Next.
6. Review the backup settings.
7. Click Finish.
8. A progress screen is displayed, and then the execution summary.
9. Click Close.
10. The backup is complete.

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.

SAP HANA Restores


Procedure
1. On the SAP HANA Studio Systems panel, right-click your system and select Backup and Recovery >
Recover System....
2. At the Shut Down System window, save your current tasks and click OK. SAP HANA Studio will shut
down the SAP HANA system and prepare for the recovery wizard.
3. At the Specific Recovery Type window, select the recovery required.
4. Click Next.
5. The Log location is listed. If not, add it now.

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.

28 Running Delta Backups


NOTE:
For a recovery from backups that were multi-streamed, SAP HANA automatically uses the same
number of channels for the recovery that were used for the backup. SAP HANA does not check the
value of the parameter
parallel_data_backup_backint_channels
. The backup catalog shows all the parts of a multistreamed backup and SAP HANA can recover these
parts in any order.
With StoreOnce software versioin 3.15 and later, copies of backups and restores can be run in parallel.

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.

Resuming restore operations


The restore operation restores the HANA data and log backups and recovers the database. If the restore was
interrupted during a log recovery, restart it from the same point using the Resume option (available with SPS
11 and later).

Intelligent Restore Auto Restore of backups using disaster


recovery copies
When a restore operation is initiated via SAP HANA and if the primary backup site is inaccessible/unavailable
or the backup is missing/deleted, the plug-in will seamlessly redirect the restore to an alternate disaster
recovery site listed in the plug-in configuration file. The restore can then be completed from the redundant
copy of the backup. The Intelligent Restore feature is enabled by default in the plug-in configuration file using
CATALYST_RESTORE_AUTOREDIRECT:ENABLE.
This feature is useful if, for example, the primary backup is disabled. Administrators can restore the database
from an offline copy.

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.

SAP HANA Deletes


Procedure
1. On the SAP HANA Studio Systems panel, right-click your system and select Backup and Recovery >
Open Backup Console.
2. Click the Backup Catalog tab. A list of previous backups is displayed.
3. Right-click the backup to be deleted and select Delete Data Backup to delete an individual backup or
Delete Older Backups to delete all previous backups.

Resuming restore operations 29


4. Select Catalog and Backup Location (recommended) to delete the catalog entry and the StoreOnce
Catalyst backup objects in the StoreOnce Catalyst store, then check File System and/or Third-Party
Backup Tool (Backint). Selecting Catalog does not delete the StoreOnce Catalyst items from the
StoreOnce Catalyst store.

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.

30 Performing SAP HANA Operations using SAP HANA Studio


Using SAP HANA CLI

Configuring SAP HANA CLI


By default, the SAP HANA Plug-in uses the plugin.conf file for all operations. If the plug-in was installed in
the default location, this file is located in /hana/shared/<SID>/hpe/HPE-Catalyst-SAP-HANA-
plugin/config. To change the configuration file that is used by the SAP HANA CLI to perform all
operations, you must edit the global.ini file in one of the following locations:
/hana/shared/<SID>/global/hdb/custom/config/global.ini
/hana/install/<SID>/global/hdb/custom/config/global.ini
The file includes lines for the data_backup_parameter_file and log_backup_parameter_file
parameters. For example:

[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.

Performing SAP HANA Backup operations


Use the following command and add options/filters as needed:
hdbsql -n <host> -i <instance number> -u <user_name> -p <password> "BACKUP DATA
USING BACKINT (<backint location + backup prefix/tag>')"
For example:
hdbsql -n hanasystem.gbr.hpe.com -i 00 -u SYSTEM -p mypassword "BACKUP DATA
USING BACKINT ('/usr/sap/HN1/SYS/global/hdb/backint/first_backup')"
For more information, see the SAP article Perform a Complete Data Backup (SQL Statements) located here:
http://help.sap.com/saphelp_hanaplatform/helpdata/en/c5/25379bbb571014a389f09d291909a5/
content.htm

Extracting the Backup ID of SAP HANA backup


The backup ID is required to performing a restore, cancel, or to check backups. To display the backup ID,
execute the following command:
hdbsql -n <host> -i <instance number> -u <user_name> -p <password> " SELECT
BACKUP_ID FROM M_BACKUP_CATALOG WHERE ENTRY_TYPE_NAME = 'complete data backup'
ORDER BY SYS_START_TIME DESC"

Using SAP HANA CLI 31


Examples:
To get the backup ID of all running backups:
hdbsql -n hanasystem.gbr.hpe.com -i 00 -u SYSTEM -p mypassword "SELECT
BACKUP_ID FROM M_BACKUP_CATALOG WHERE ENTRY_TYPE_NAME = 'complete data backup'
AND STATE_NAME = 'running' ORDER BY SYS_START_TIME DESC"
To get the backup ID of all existing backups:
hdbsql -n hanasystem.gbr.hpe.com -i 00 -u SYSTEM -p mypassword "SELECT
BACKUP_ID FROM M_BACKUP_CATALOG WHERE ENTRY_TYPE_NAME = 'complete data backup'
ORDER BY SYS_START_TIME DESC"

Cancelling SAP HANA Backup


NOTE:
Canceling a backup requires the backup ID.
A cancel operation can take a long time to complete.

Use the following command:


hdbsql -n <host> -i <instance number> -u <user_name> -p <password> "BACKUP
CANCEL <backup ID>"
For example:
hdbsql -n hanasystem.gbr.hpe.com -i 00 -u SYSTEM -p mypassword "BACKUP CANCEL
1429868930854"
For more information, see the SAP article Canceling a Running Data Backup (SQL Statements) located here:
http://help.sap.com/saphelp_hanaplatform/helpdata/en/c4/f934abbb571014b5fec3c1121b4dad/
content.htm?frameset=/en/c4/edd463bb571014816ed484e45f82a9/frameset.htm&current_toc=/en/
00/0ca1e3486640ef8b884cdf1a050fbb/plain.htm&node_id=462

Checking SAP HANA Backup for Recovery


Determine if the last successful backup is available for recovery.

32 Cancelling SAP HANA Backup


NOTE:
Checking for a specific backup requires the backup ID.
Use the following command:
hdbbackupdiag --check -- useBackintForCatalog --backintDataParamFile <Data config file location> --
backintLogParamFile <Log config file location> --logDirs
<logs directory location>
Examples:
To check the latest backup:
hdbbackupdiag --check -- useBackintForCatalog --backintDataParamFile /hana/shared/HN1/hpe/HPE-
Catalyst-
SAP-HANA-plugin/config/plugin.conf --logDirs /usr/sap/HN1/HDB00/backup/log/
To check a specific backup:
hdbbackupdiag --check -- useBackintForCatalog --backintDataParamFile /hana/shared/HN1/hpe/HPE-
Catalyst-SAP-HANA-plugin/ --logDirs /usr/sap/HN1/HDB00/backup/log/ -i
1429782842461

If you are using a separate configuration file for Log backups you need to add the parameter file for log
backups as well:

To check the latest backup:


hdbbackupdiag --check -- useBackintForCatalog --backintDataParamFile /hana/shared/HN1/hpe/HPE-
Catalyst-SAP-HANA-plugin/config/plugin.conf --backintLogParamFile /hana/shared/HN1/hpe/HPE-Catalyst-
SAP-HANA-plugin/config/plugin_log.conf --logDirs /usr/sap/HN1/HDB00/backup/log/

To check a specific backup:


hdbbackupdiag --check -- useBackintForCatalog --backintDataParamFile /hana/shared/HN1/hpe/HPE-
Catalyst- SAP-HANA-plugin/ --backintLogParamFile /hana/shared/HN1/hpe/HPE-Catalyst-SAP-HANA-plugin/
config/plugin_log.conf --logDirs /usr/sap/HN1/HDB00/backup/log/ -i
1429782842461

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

Checking the integrity of SAP HANA backup objects


Checking the integrity of a specific StoreOnce Catalyst backup requires the EBID. This ID is available from
either HANA Studio under the EBID column for the specific backup or from the StoreOnce GUI.
To get the ID from HANA Studio, use the following command:
hdbbackupcheck -v --backintParamFile <config file location> <location of backint
folder + tag of backup> -e <EBID>
For example:

Checking the integrity of SAP HANA backup objects 33


hdbbackupcheck -v --backintParamFile /hana/shared/HN1/hpe/HPE-Catalyst-SAP-HANA-
plugin/config/plugin.conf /usr/sap/HN1/SYS/global/hdb/backint/
test_tag_databackup_4_1 -e 1429783549395_52271602
To get the ID from the StoreOnce GUI:

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).

Performing SAP HANA restore operations


You can restore your SAP HANA database to either the latest version or to an earlier version. Restoring to an
earlier version requires the backup ID.

IMPORTANT:
Check that the backup exists before starting a recovery.

Use the following command:


HDBSettings.sh recoverSys.py --command="RECOVER DATABASE UNTIL TIMESTAMP '<YYYY-
MM-DD HH:MM:SS>' USING DATA PATH ('<data path location>') USING LOG PATH ('<log
path location>') CHECK ACCESS USING FILE" --wait
Examples:
To restore to the latest version:
HDBSettings.sh recoverSys.py --command="RECOVER DATABASE UNTIL TIMESTAMP
'2015-04-23 15:41:58' USING DATA PATH ('/usr/sap/HN1/SYS/global/hdb/backint/')
USING LOG PATH ('/usr/sap/HN1/HDB00/backup/log') CHECK ACCESS USING FILE" --
wait
To restore to a specific version:
HDBSettings.sh recoverSys.py --command="RECOVER DATABASE UNTIL TIMESTAMP
'2015-04-23 15:41:58' USING DATA PATH ('/usr/sap/HN1/SYS/global/hdb/backint/')
USING LOG PATH ('/usr/sap/HN1/HDB00/backup/log') USING BACKUP_ID 1429782842461
CHECK ACCESS USING FILE" --wait

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.

For more information, see these SAP articles:


Recover the Database Using the Command Line Tool
located here:http://help.sap.com/saphelp_hanaplatform/helpdata/en/8f/
42dffd50b14a3da72f1220cc7b0eaf/content.htm
Parameters for Recovery with Command Line Tool
located here:http://help.sap.com/saphelp_hanaplatform/helpdata/en/27/
ee28dd489545aeaec3872ee05a4269/content.htm

34 Performing SAP HANA restore operations


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.

Performing SAP HANA delete operations


You can delete a specific backup or all backups that came before the one you specify.

NOTE:
Verify that a backup exists before attempting to delete it.

Delete a specific backup:


hdbsql -n <host> -i <instance number> -u <user_name> -p <password> BACKUP
CATALOG DELETE BACKUP_ID <backup ID> [COMPLETE]"
For example:
hdbsql -n hanasystem.gbr.hpe.com -i 00 -u SYSTEM -p mypassword "BACKUP CATALOG
DELETE BACKUP_ID 1430230790389 COMPLETE"
Delete all backups prior to a specific one (does not delete the one
specified): hdbsql -n <host> -i <instance number> -u <user_name> -p <password>
"BACKUP CATALOG DELETE ALL BEFORE BACKUP_ID <backup ID> [COMPLETE]"
For example:
hdbsql -n hanasystem.gbr.hpe.com -i 00 -u SYSTEM -p HPE1nv3nt "BACKUP CATALOG
DELETE ALL BEFORE BACKUP_ID 1430231552343 COMPLETE"

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.

Performing SAP HANA delete operations 35


Performing StoreOnce Catalyst Copy Operations
NOTE:
SAP HANA does not support managed copy. Use the StoreOnce Catalyst Copy tool provided to
manage disaster recovery copies.
If you have configured Data and Log Backups 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 working set of the Backups for Disaster Recovery (DR). Copying 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.
SAP HANA does not implement expiration of backups. Use the StoreOnce Catalyst Copy tool provided
to manage backup retention periods.

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.

The StoreOnce Catalyst Copy tool supports the following operations:

36 Performing StoreOnce Catalyst Copy Operations


Table 4: StoreOnce Catalyst Copy Operations

Command Syntax Description

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.

Cancel StoreOnceCatalystCopy --cancel Cancel all queued StoreOnce Catalyst


copies. Filters can be used to cancel
StoreOnceCatalystCopy -x
specific copies only. Use
--preview
with this command to first preview which
StoreOnce Catalyst copy jobs will be
cancelled.
Table Continued

Performing StoreOnce Catalyst Copy Operations 37


Command Syntax Description

Delete-items StoreOnceCatalystCopy --delete- Delete StoreOnce Catalyst backup items


items from an origin StoreOnce Catalyst store.
This command deletes StoreOnce
StoreOnceCatalystCopy -d
Catalyst items in a source StoreOnce
Catalyst store. Filters must be used to
delete specific StoreOnce Catalyst items
only.
-filter-key
must be supplied for the plug-in name, for
example, SAPHANA. Use
--preview
with this command to first preview which
StoreOnce Catalyst items will be deleted.
The configuration file should contain only
the target appliance and catalyst store
details using parameters -
CATALYST_STORE_ADDRESS,
CATALYST_STORE_NAME. Do not
specify any additional copy targets, would
cause the delete operation to fail. If
desired, a configuration file separate from
the plug-in configuration file can be used
for Delete operations.

Expire-items StoreOnceCatalystCopy -expire- Maintain synchronization between the


items source and target stores. This command
deletes StoreOnce Catalyst items in the
StoreOnceCatalystCopy -e
destination store that no longer exist in
the source StoreOnce Catalyst store but
were created by that source store. Filters
can be used to delete specific copies only.
Use
--preview
with this command to first preview which
StoreOnce Catalyst items will be deleted.

Copyredirect StoreOnceCatalystCopy -- Split StoreOnce Catalyst copy


copyredirect management and data traffic. Helps use
dedicated private networks (like a
StoreOnce appliance replication network)
for transferring data during a StoreOnce
Catalyst copy operation. This option can
be read from the plug-in configuration file
or overridden via command line options.

Version StoreOnceCatalystCopy --version Check the version of the StoreOnce


Catalyst Copy tool.

The following options can be used with the commands above. Run StoreOnceCatalystCopy --help for
more details.

38 Performing StoreOnce Catalyst Copy Operations


Table 5: Options to Modify Copy Operations

Option Description

filterkey Filter items based on their key/name.

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.

filterstatus Filter jobs according to the current copy status.

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.

Performing StoreOnce Catalyst Copy Operations 39


Automating the Use of the StoreOnce Catalyst Copy Tool
The StoreOnce Catalyst Copy tool can be run in a number of ways:
Run StoreOnceCatalystCopy manually at the command line.
Automated via Linux/UNIX Crontab or Windows scheduled task.
Using Linux/UNIX Crontab or Windows scheduled task, StoreOnceCatalystCopy can be scheduled
based on needs.
For instance, if performing log backups to StoreOnce you can create a schedule to copy new logs every
30 minutes, every hour, etc. Use the same approach for scheduled data backups.

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.

40 Automating the Use of the StoreOnce Catalyst Copy Tool


Troubleshooting
Cause
If the installation used the default path, useful log files are located in the following directories:
/hana/shared/<SID>/hpe/HPE-Catalyst-SAP-HANA-plugin/logs
Catalyst_SAPHana.log
Connector_SAPHana.log
/hana/shared/<SID>/HDB<INSTANCE#>/<HOSTNAME>/trace
backint.log
backup.log
The following table lists common SAP HANA Plug-in setup and installation problems and solutions.

Symptom Possible Cause Solutions

Error message: No configuration file assigned Provide the path to the


under Backint Parameter File. configuration file.
Could not back up system
<SID> See Configuring SAP HANA
Studio on page 25 for more
backup could not be
details.
completed, Backint exited
with exit code 1 instead
of 0. console output:
ERROR: Option "-p=" is
required for operation "-
f=".

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

SAP HANA Plug-in


StoreOnce Catalyst Best Practices
Do not delete backup Catalyst items (backups) directly from the StoreOnce GUI. Instead, use the backup
application to expire the backup items. Using the backup application ensures application consistency.
Target similar data types to dedicated StoreOnce Catalyst stores and avoid mixing datatypes within a
StoreOnce Catalyst store. Backups of differing data types, such as two different database types, will
deduplicate against each other very little. Separating different data types into separate StoreOnce Catalyst
stores reduces the store complexity leading to optimum long-term performance.
When performing low bandwidth StoreOnce Catalyst backups, spread the number of backup sessions
across multiple media servers where possible. Distributing the streams across multiple media servers
reduces the possibility of a media server becoming a performance bottleneck.
Where possible, split a backup session into multiple backup streams. Allowing StoreOnce to process
multiple backups streams in parallel will increase backup performance.
When using ProLiant media servers and database servers for low bandwidth StoreOnce Catalyst, enable
HPE Static High Performance Mode via the ProLiant Power Management settings for the best backup
performance. This setting is not the default.
Enable StoreOnce Catalyst client permission checking on each StoreOnce service set to ensure that client
data access is restricted.
When using StoreOnce Catalyst over Fibre Channel, ensure the Number of Devices per Login is set
appropriately for StoreOnce Catalyst Copy, Windows, Linux, HPE-UX, AIX, and Solaris media servers and
database servers. See Initial configuration for details.
When using StoreOnce Catalyst over Fibre Channel, ensure that the correct access permissions have
been set on the StoreOnce Catalyst over Fibre Channel client device files, if running as a non-root or non-
administrator user. See Client configurations for details.
To ensure the backup application and the Fibre Channel (if applicable) configuration being used is
supported, refer to the HPE Data Availability, Protection and Retention Compatibility Matrix.
Ensure StoreOnce Catalyst client log levels are set to the default ERROR log level for optimum
performance.
When performing backups with StoreOnce Catalyst over Fibre Channel or StoreOnce Catalyst Ethernet
backups over LAN, StoreOnce Catalyst compression and checksums can be set to DISABLED via the
backup application configuration file. If performing StoreOnce Catalyst Ethernet backups over WAN,
Catalyst compression and checksums must be ENABLED (the default) via the backup application (plug-in)
configuration file.
If using StoreOnce Federated Catalyst, consider that backups to StoreOnce Federated Catalyst stores will
capacity balance across the available Federated storage. Therefore, a StoreOnce service set running a
VTL or NAS shares as well as a StoreOnce Federated Catalyst store will lead to an imbalanced Federated
Catalyst store. Federated Catalyst is most suited to StoreOnce Federated configurations only.
When configuring a backup application to use a Fully Qualified Domain Name (FQDN) address for a
StoreOnce, ensure that the FQDN is fully registered with a Domain Name Server; do not use local host file
entries. This is important when making use of StoreOnce Catalyst Copy jobs because the source
StoreOnce appliance will use the FQDN to communicate directly with the target StoreOnce appliance.
Using local client host file entries will result in the source StoreOnce appliance not being able to resolve
the target FQDN address.

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

Hewlett Packard Enterprise Information Library www.hpe.com/info/storeonce/docs

Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc

Table Continued

44 Support and other resources


Website Link

Contact Hewlett Packard Enterprise Worldwide www.hpe.com/assistance

Subscription Service/Support Alerts www.hpe.com/support/e-updates

Software Depot www.hpe.com/support/softwaredepot

HPE Data Availability, Protection and Retention www.hpe.com/storage/DAPRCompatibility


Compatibility Matrix

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.

46 Hewlett Packard Enterprise End User License Agreement


HPE-branded software materially conforms to its specifications, if any, and is free of malware at the
time of delivery; if you notify HPE within 90 days of delivery of non-conformance to this warranty, HPE
will replace your copy. This Agreement states all remedies for warranty claims.
HPE does not warrant that the operation of software will be uninterrupted or error free, or that
software will operate in hardware and software combinations other than as authorized by HPE in
Supporting Material. To the extent permitted by law, HPE disclaims all other warranties.
12. Intellectual Property Rights Infringement. HPE will defend and/or settle any claims against you that
allege that HPE-branded software as supplied under this Agreement infringes the intellectual property
rights of a third-party. HPE will rely on your prompt notification of the claim and cooperation with our
defense. HPE may modify the software so as to be non-infringing and materially equivalent, or we may
procure a license. If these options are not available, we will refund to you the amount paid for the
affected product in the first year or the depreciated value thereafter. HPE is not responsible for claims
resulting from any unauthorized use of the software.
13. Limitation of Liability. HPE's liability to you under this Agreement is limited to the amount actually paid
by you to HPE for the relevant software, except for amounts in Section 12 ("Intellectual Property Rights
Infringement"). Neither you nor HPE will be liable for lost revenues or profits, downtime costs, loss or
damage to data or indirect, special or consequential costs or damages. This provision does not limit
either party's liability for: unauthorized use of intellectual property, death or bodily injury caused by their
negligence; acts of fraud; willful repudiation of the Agreement; or any liability that may not be excluded or
limited by applicable law.
14. Termination. This Agreement is effective until terminated or in the case of a limited-term license, upon
expiration; however, your rights under this Agreement terminate if you fail to comply with it. Immediately
upon termination or expiration, you will destroy the software and documentation and any copies, or return
them to HPE. You may keep one copy of software and documentation for archival purposes. We may ask
you to certify in writing you have complied with this section. Warranty disclaimers, the limitation of liability,
this section on termination, and Section 15 ("General") will survive termination.
15. General.
a. Assignment. You may not assign this Agreement without prior written consent of HPE, payment of
transfer fees and compliance with HPE's software license transfer policies. Authorized assignments
will terminate your license to the software and you must deliver software and documentation and
copies thereof to the assignee. The assignee will agree in writing to this Agreement. You may only
transfer firmware if you transfer associated hardware.
b. U.S. Government. If the software is licensed to you for use in the performance of a U.S. Government
prime contract or subcontract, you agree that, consistent with FAR 12.211 and 12.212, commercial
computer software, computer software documentation and technical data for commercial items are
licensed under HPE's standard commercial license.
c. Global Trade Compliance. You agree to comply with the trade-related laws and regulations of the U.S.
and other national governments. If you export, import or otherwise transfer products provided under
this Agreement, you will be responsible for obtaining any required export or import authorizations. You
confirm that you are not located in a country that is subject to trade control sanctions (currently Cuba,
Iran, N. Korea, N. Sudan, and Syria) and further agree that you will not retransfer the products to any
such country. HPE may suspend its performance under this Agreement to the extent required by laws
applicable to either party.
d. Audit. HPE may audit you for compliance with the software license terms. Upon reasonable notice,
HPE may conduct an audit during normal business hours (with the auditor costs being at HPE
expense). If an audit reveals underpayments then you will pay to HPE such underpayments. If
underpayments discovered exceed five (5) percent, you will reimburse HPE for the auditor costs.
e. Open Source Components. To the extent the Supporting Material includes open source licenses, such
licenses shall control over this Agreement with respect to the particular open source component. To
the extent Supporting Material includes the GNU General Public License or the GNU Lesser General
Public License: (a) the software includes a copy of the source code; or (b) if you downloaded the
software from a website, a copy of the source code is available on the same website; or (c) if you
send HPE written notice, HPE will send you a copy of the source code for a reasonable fee.
f. Notices. Written notices under this Agreement may be provided to HPE via the method provided in
the Supporting Material.

Hewlett Packard Enterprise End User License Agreement 47


g. Governing Law. This Agreement will be governed by the laws of the state of California, U.S.A.,
excluding rules as to choice and conflict of law. You and HPE agree that the United Nations
Convention on Contracts for the International Sale of Goods will not apply.
h. Force Majeure. Neither party will be liable for performance delays nor for non-performance due to
causes beyond its reasonable control, except for payment obligations.
i. Entire Agreement. This Agreement represents our entire understanding with respect to its subject
matter and supersedes any previous communication or agreements that may exist. Modifications to
the Agreement will be made only through a written amendment signed by both parties. If HPE doesn't
exercise its rights under this Agreement, such delay is not a waiver of its rights.
16. Australian Consumers. If you acquired the software as a consumer within the meaning of the
&apos;Australian Consumer Law&apos; under the Australian Competition and Consumer Act 2010 (Cth)
then despite any other provision of this Agreement, the terms at this URL apply: www.hpe.com/
software/SWLicensing.

48 Hewlett Packard Enterprise End User License Agreement