Contents

Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide PDF

1 of 39
1 of 39

Summary of Content for Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide PDF

PowerProtect Data Manager for SAP HANA Agent User Guide

Version 19.5

Dell Inc.

June 2020 Rev. 01

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the

problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Preface......................................................................................................................................................................................... 5

Chapter 1: PowerProtect Data Manager for SAP HANA Agent Overview.............................................. 8 PowerProtect Data Manager overview..............................................................................................................................8 About the SAP HANA agent................................................................................................................................................ 8 Prerequisites...........................................................................................................................................................................8 Firewall and port considerations.......................................................................................................................................... 9 PowerProtect Data Manager new deployment overview................................................................................................9 PowerProtect Data Manager existing deployment overview........................................................................................ 10

Chapter 2: Enabling the SAP HANA Agent....................................................................................... 12 SAP HANA data protection and replication requirements.............................................................................................. 12 Protecting a stand-alone SAP HANA server.................................................................................................................... 12 Protecting SAP HANA multinode environments.............................................................................................................. 12 Install and configure the SAP HANA agent...................................................................................................................... 13

Install the SAP HANA agent..........................................................................................................................................13 Upgrade the SAP HANA agent.....................................................................................................................................14 Uninstall the SAP HANA agent.....................................................................................................................................14 Configure the SAP HANA operations.......................................................................................................................... 15

Manage the SAP HANA application agent........................................................................................................................18

Chapter 3: Managing Storage, Assets, and Protection......................................................................20 Add protection storage ......................................................................................................................................................20

Troubleshooting protection policy for DD storage unit............................................................................................. 21 Viewing the DD Boost storage unit password............................................................................................................21

Discover an SAP HANA application host.......................................................................................................................... 21 Add a protection policy for SAP HANA database protection........................................................................................ 22 Manage the PowerProtect agent service........................................................................................................................25

About the PowerProtect agent service......................................................................................................................25 Start, stop, or obtain the status of the PowerProtect agent service.................................................................... 26 Troubleshoot the PowerProtect agent service operations......................................................................................27 Register the PowerProtect agent service to a different server address on Linux............................................... 28 Recovering the PowerProtect agent service from a disaster................................................................................. 28

Manage the cloud tier operations with PowerProtect Data Manager......................................................................... 29 Add a cloud tier schedule to a protection policy........................................................................................................29 Tier the PowerProtect Data Manager backups from Data Domain to the cloud..................................................30 Restore the cloud tier backups to Data Domain.........................................................................................................31

Chapter 4: Performing Self-Service Backups of SAP HANA Databases.............................................. 32 Performing self-service backups of SAP HANA databases...........................................................................................32

Performing backups by using SAP HANA Studio......................................................................................................32 Performing backups by using the SAP HANA CLI.................................................................................................... 33 Canceling backups by using the SAP HANA CLI.......................................................................................................34 Checking backups by using the SAP HANA CLI........................................................................................................34

Restore an SAP HANA application host........................................................................................................................... 34

Contents

Contents 3

Performing restore and recovery by using SAP HANA Studio................................................................................35 Performing restore with dependency chaining or replication storage.................................................................... 37 Performing alternate host recovery............................................................................................................................ 38 Performing restore of backups performed prior to PowerProtect Data Manager registration.......................... 38 Performing recovery by using the SAP HANA CLI................................................................................................... 39

4 Contents

Preface As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in this document, contact a technical support professional.

NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this

document, go to the Support website https://www.dell.com/support.

Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the UI, and

elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the UI has

not yet been updated to reflect this change.

Purpose This document describes how to configure and use the PowerProtect Data Manager with the SAP HANA agent.

Audience This document is intended for the host system administrator who configures and uses the PowerProtect Data Manager with the SAP HANA agent.

Revision history The following table presents the revision history of this document.

Table 1. Revision history

Revision Date Description

01 June 30, 2020 GA release of this document for PowerProtect Data Manager version 19.5

Compatibility information Software compatibility information for the PowerProtect Data Manager software is provided in the eLab Navigator, available at https:// elabnavigator.emc.com/eln/modernHomeDataProtection.

Related documentation The following publications are available on Dell EMC Online Support and provide additional information:

PowerProtect Data Manager Administration and User GuideDescribes how to configure the software. PowerProtect Data Manager Deployment GuideDescribes how to deploy the software. PowerProtect Data Manager Release NotesContains information on new features, known limitations, environment, and system

requirements for the software. PowerProtect Data Manager Security Configuration GuideContains security information. PowerProtect Data Manager AWS Deployment GuideDescribes how to deploy the software in an AWS environment. PowerProtect Data Manager Cloud Disaster Recovery Administration and User GuideDescribes how to deploy Cloud DR, protect

VMs in the AWS or Azure cloud, and run recovery operations. PowerProtect Data Manager for Cyber Recovery User GuideDescribes how to install, upgrade, patch, and uninstall the Dell EMC

PowerProtect Cyber Recovery software. PowerProtect Data Manager for File System Agent User GuideDescribes how to configure and use the software with the File

System agent for file system data protection.

Preface 5

PowerProtect Data Manager for Microsoft Application Agent Exchange Server User GuideDescribes how to configure and use the software in a Microsoft Exchange Server environment.

PowerProtect Data Manager for Microsoft Application Agent SQL Server User GuideDescribes how to configure and use the software in a Microsoft SQL Server environment.

PowerProtect Data Manager for Oracle RMAN Agent User GuideDescribes how to configure and use the software in an Oracle Server environment.

PowerProtect Data Manager for SAP HANA Agent User GuideDescribes how to configure and use the software in an SAP HANA Server environment.

PowerProtect Data Manager API documentation: https://developer.dellemc.comContains the PowerProtect Data Manager APIs and includes tutorials to guide to you in their use.

Typographical conventions The following type style conventions are used in this document:

Table 2. Style conventions

Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area with title, table label, and window.

Italic Used for full titles of publications that are referenced in text.

Monospace Used for:

System code System output, such as an error message or script Pathnames, file names, file name extensions, prompts, and syntax Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means or for the alternate selections.

{ } Braces enclose content that the user must specify, such as x, y, or z.

... Ellipses indicate non-essential information that is omitted from the example.

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation https://www.dell.com/support https://www.dell.com/community

Where to get support The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories, downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Support.

To access a product-specific page:

1. Go to https://www.dell.com/support. 2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Knowledgebase:

6 Preface

1. Go to https://www.dell.com/support. 2. On the Support tab, click Knowledge Base. 3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by typing a

product name in the search box, and then selecting the product from the list that appears.

Live chat To participate in a live interactive chat with a support agent:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Contact Support. 3. On the Contact Information page, click the relevant support, and then proceed.

Service requests To obtain in-depth help from Licensing, submit a service request. To submit a service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests.

NOTE: To create a service request, you must have a valid support agreement. For details about either an account or

obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the

Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests. 3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities For peer contacts, conversations, and content on product support and solutions, go to the Community Network https://www.dell.com/ community. Interactively engage with customers, partners, and certified professionals online.

How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to DPAD.Doc.Feedback@emc.com.

Preface 7

PowerProtect Data Manager for SAP HANA Agent Overview

Topics:

PowerProtect Data Manager overview About the SAP HANA agent Prerequisites Firewall and port considerations PowerProtect Data Manager new deployment overview PowerProtect Data Manager existing deployment overview

PowerProtect Data Manager overview Use PowerProtect Data Manager with the application agent to perform the following operations:

Automate the configuration of the application agent backup policy and protection storage settings. Create a catalog of backups that are produced by the application agent, and then monitor that catalog data to determine if retention

policies are being adhered to. Manage the life cycle of backups that are created by the application agentthat is, ensure that the backups are marked for garbage

collection based on the rules of the retention policy.

PowerProtect Data Manager does not change the way that the application agent works. DBAs or system/backup administrators create the backups and perform the restores.

About the SAP HANA agent The SAP HANA agent enables an application administrator to protect and recover the SAP HANA data on the application host. PowerProtect Data Manager integrates with the SAP HANA agent and enables central scheduling for the SAP HANA backups.

The SAP HANA agent installation is a command-line process whereby the user installs the required SAP HANA agent and PowerProtect Data Manager software. PowerProtect Data Manager then sets the Data Domain host, storage unit, user, and password. Install and configure the SAP HANA agent on page 13 provides instructions.

NOTE: PowerProtect Data Manager supports the coexistence of the SAP HANA agent and the File System agent on

Linux.

Software compatibility information for the PowerProtect Data Manager software and application agents is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

Prerequisites Ensure that your environment meets the requirements for a new deployment or upgrade of PowerProtect Data Manager.

Requirements:

A list of hosts that write backups to DD systems is available. DD OS version 6.1 or later and the DD Management Console (DDMC). All models of DD systems are supported.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and

use a DD system directly without DDMC.

Application agent 19.5 or earlier. License: A trial license is provided with the PowerProtect Data Manager software. DPS Applications, Backup, and Enterprise

customers can contact Dell EMC Licensing Support for assistance with a permanent PowerProtect Data Manager license.

1

8 PowerProtect Data Manager for SAP HANA Agent Overview

Large environments require multiple PowerProtect Data Manager instances. Contact Champions.eCDM@emc.com for assistance with sizing requests.

The PowerProtect Data Manager 19.5 download file requires the following:

ESXi version 6.0, 6.5, 6.7, or 7.0. 8 vCPUs, 18 GB RAM, one 100 GB disk, and one 500 GB disk. The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI. TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.

VMware ESXi server that hosts PowerProtect Data Manager meets the following minimum system requirements:

10 CPU cores 18 GB of RAM for PowerProtect Data Manager Five disks with the following capacities:

Disk 1100 GB Disk 2500 GB Disk 310 GB Disk 410 GB Disk 55 GB

One 1-GB NIC

Firewall and port considerations Table 3. PowerProtect Data Manager port requirements

Description Communication Port

SSH communications Bidirectional communication between the SSH client and the PowerProtect Data Manager appliance

22 TCP/UDP

RestServer Bidirectional communication between the HTTP client and the PowerProtect Data Manager appliance

8443 TCP

UI redirect Inbound only 80 TCP

443

LDAP Outbound only 389 TCP/UDP

636 TCP

Discovery (devices) Outbound between the PowerProtect Data Manager appliance and the device

3009 TCPStorage Direct and DD system

5989 TCPSMI-S

PowerProtect Data Manager agent

Bidirectional communication between the database hosts and the PowerProtect Data Manager appliance

7000 TCP

Embedded VM Direct service Outbound 9090 TCP

PowerProtect Data Manager new deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the application agent.

Steps

1. Design how to group the backups based on the storage requirements and retention policies.

The account team can help with backup storage design.

2. Install DD Management Center (DDMC).

PowerProtect Data Manager for SAP HANA Agent Overview 9

PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and

use a DD system directly without DDMC.

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

4. Add external DD systems or DDMC to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

5. Install the application agent on the appropriate hosts and connect them to PowerProtect Data Manager according to the instructions in the next chapter.

This operation should be performed by DBAs.

NOTE: After you create a centralized protection job, the first backup is a full backup.

6. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next chapter.

7. Add a protection policy for groups of assets that you want to back up.

The PowerProtect Data Manager Administration and User Guide provides instructions.

Configuration is complete. 8. Perform a full backup so that PowerProtect Data Manager can detect the proper backup chain.

Without a full backup, PowerProtect Data Manager treats the backups as partial and assumes that you are out of compliance. DBAs create backups and PowerProtect Data Manager creates a catalog of the backups, monitoring the catalog for retention policy compliance, and, if configured, managing the life cycle of the backups.

PowerProtect Data Manager existing deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the application agent in an existing environment.

Steps

1. Install DD Management Center (DDMC).

PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and

use a DD system directly without DDMC.

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

3. Add external DD systems or DDMC to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

4. Upgrade the application agent or uninstall and then reinstall the application agent on the hosts and connect them to PowerProtect Data Manager according to the instructions in the next chapter.

This action should be performed by DBAs.

NOTE: After you create a centralized protection job, the first backup is a full backup.

5. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next chapter.

6. Add a protection policy for groups of assets that you want to back up.

The PowerProtect Data Manager Administration and User Guide provides instructions.

Configuration is complete. 7. Perform a full backup so that PowerProtect Data Manager can detect the proper backup chain.

10 PowerProtect Data Manager for SAP HANA Agent Overview

Without a full backup, PowerProtect Data Manager treats the backups as partial and assumes that you are out of compliance. DBAs create backups and PowerProtect Data Manager creates a catalog of the backups, monitoring the catalog for retention policy compliance, and, if configured, managing the life cycle of the backups.

PowerProtect Data Manager for SAP HANA Agent Overview 11

Enabling the SAP HANA Agent

Topics:

SAP HANA data protection and replication requirements Protecting a stand-alone SAP HANA server Protecting SAP HANA multinode environments Install and configure the SAP HANA agent Manage the SAP HANA application agent

SAP HANA data protection and replication requirements PowerProtect Data Manager can manage and monitor data protection and replication for SAP HANA assets through integration with the SAP HANA agent.

After installing the SAP HANA agent, review the following information for additional requirements before adding the SAP HANA agent as an asset source in PowerProtect Data Manager and discovering the agent assets.

Verify that the environment meets the following requirements:

Ensure that all clocks on both the SAP HANA host and PowerProtect Data Manager are time-synced to the local NTP server to ensure discovery of the backups.

Ensure that the SAP HANA host and the PowerProtect Data Manager network can see and resolve each other. Ensure that port 7000 is open on the SAP HANA host.

Protecting a stand-alone SAP HANA server Learn how to configure protection of a stand-alone SAP HANA server.

Steps

1. Add a storage system.

Add protection storage on page 20 provides information.

2. Install the SAP HANA agent on the SAP HANA database server host.

Install the SAP HANA agent on page 13 provides information.

3. Add or approve the SAP HANA agent in PowerProtect Data Manager. Manage the SAP HANA application agent on page 18 provides information.

4. Discover and add the credentials for the SAP HANA application host.

Discover an SAP HANA application host on page 21 provides information.

5. Create a protection policy to protect the SAP HANA database server host.

Add a protection policy for SAP HANA database protection on page 22 provides information.

Protecting SAP HANA multinode environments Learn how to configure protection of SAP HANA multinode environments.

About this task

You must repeat the steps to install the SAP HANA agent, and then add and discover the application host in PowerProtect Data Manager on each node in the SAP HANA multinode environment.

2

12 Enabling the SAP HANA Agent

Steps

1. Add a storage system.

Add protection storage on page 20 provides information.

2. Install the SAP HANA agent on each SAP HANA node.

Install the SAP HANA agent on page 13 provides information.

3. Add or approve the SAP HANA agent on each SAP HANA node. Manage the SAP HANA application agent on page 18 provides information.

4. Discover and add the credentials for each SAP HANA application host.

Discover an SAP HANA application host on page 21 provides information.

5. Create a protection policy group to protect the SAP HANA nodes.

Add a protection policy for SAP HANA database protection on page 22 provides information.

Install and configure the SAP HANA agent Learn how to install and configure the SAP HANA agent.

Install the SAP HANA agent Learn how to install the SAP HANA agent on all the Linux database servers that must access the Data Domain system.

About this task

Run the ppdmHanaInstall.sh script to install the SAP HANA agent 19.5. The script installs the SAP HANA agent and the agent service in the default directory, /opt/dpsapps/dbappagent/saphana.

Run the ppdmHanaInstall.sh -h or ppdmHanaInstall.sh --help command to obtain more information about the script operation.

Complete the following steps to download the SAP HANA agent and perform a new installation of the software on Linux.

NOTE: In a multinode system, you must run the ppdmHanaInstall.sh script on each node.

Steps

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from Dashboard > System Settings. b. Select the SAP HANA agent download package, dbappagent195_linux_x86_64.tar.

c. Download the package to the SAP HANA host on Linux.

NOTE: As an alternative, you can download the SAP HANA agent package from the Support website at https://

www.dell.com/support.

2. Uncompress the downloaded tar file by running the following command as the SAP HANA user:

tar -xvf dbappagent195_linux_x86_64.tar.gz

3. Ensure that no backups are running, including log backups. Stop the SAP HANA processes before you install the SAP HANA agent. 4. As the root user, run the ppdmHanaInstall.sh script with the --server option to install the SAP HANA agent and register the

agent with the PowerProtect Data Manager server:

ppdmHanaInstall.sh --server=

5. If you do not specify the --server option with the PowerProtect Data Manager server IP address on the command line, the script prompts for the IP address of the server:

Do you wish to register with server? [y/n] y Enter PowerProtect Data Manager IP address:

Enabling the SAP HANA Agent 13

6. To verify the installed version of the SAP HANA agent, run the following command:

rpm -qa | grep "agent"

emcdbappagent-19.5.0.0.0-1.x86_64 powerprotect-agentsvc-19.5.0.0.0-1.x86_64

Upgrade the SAP HANA agent Learn how to upgrade the SAP HANA agent on the Linux database servers that access the Data Domain system.

About this task

To upgrade the SAP HANA agent from version 19.3 or earlier, you must uninstall and then reinstall the SAP HANA agent according to the following instructions:

Uninstall the SAP HANA agent on page 14 Install the SAP HANA agent on page 13

NOTE: In a multinode system, you must run both the uninstallation and installation scripts on each node.

The SAP HANA agent supports a direct upgrade from version 19.4 to version 19.5. To upgrade the SAP HANA agent from version 19.4, run the ppdmHanaInstall.sh script with the --upgrade option as the root user:

ppdmHanaInstall.sh --upgrade

NOTE: In a multinode system, you must run the ppdmHanaInstall.sh --upgrade command on each node.

To verify the upgraded version of the SAP HANA agent, run the following command:

rpm -qa | grep "agent" emcdbappagent-19.5.0.0.0-1.x86_64 powerprotect-agentsvc-19.5.0.0.0-1.x86_64

Uninstall the SAP HANA agent Learn how to uninstall the SAP HANA agent on the Linux database servers that access the Data Domain system.

About this task

Run the ppdmHanaUninstall.sh script to uninstall the SAP HANA agent 19.5.

Run the ppdmHanaUninstall.sh -h or ppdmHanaUninstall.sh --help command to obtain more information about the script operation.

Perform the following steps to uninstall the SAP HANA agent.

NOTE: In a multinode system, you must run the ppdmHanaUninstall.sh script on each node.

Steps

1. Ensure that backup and restore operations are not in progress when you uninstall the SAP HANA agent. 2. As an SAP HANA user, run the ppdmHanaUninstall.sh script:

ppdmHanaUninstall.sh

3. When the script displays the following prompt, enter y:

Other application agents might be using powerprotect-agentsvc. Do you wish to uninstall powerprotect-agentsvc? [y/n] y

The ppdmHanaUninstall.sh script uninstalls both the SAP HANA agent and the agent service.

14 Enabling the SAP HANA Agent

4. To complete the uninstallation, manually delete the file /opt/dpsapps/dbappagent/saphana/.ppdmintegrated.

Configure the SAP HANA operations You must complete the required configurations to enable the backup and restore operations in an SAP HANA environment. The following topics provide the product configuration details.

Integrate the SAP HANA backup program The SAP HANA agent installation places the hdbbackint program in the /opt/dpsapps/dbappagent/bin directory. However, SAP HANA requires the program to be accessible from the /hana/shared/ /global/hdb/opt directory.

NOTE: You must manually create the opt subdirectory if it does not exist in the /hana/shared/ /global/hdb directory.

You can either copy the hdbbackint file to that directory or create a symbolic link that points from /hana/shared/ / global/hdb/opt to the actual executable file. For example:

ln -s /opt/dpsapps/dbappagent/bin/hdbbackint /hana/shared/S01/global/hdb/opt/hdbbackint

Ensure that the hdbbackint file has the required executable permissions for the operating system user adm to run the program, where is the system ID of the SAP HANA system.

Modify the configuration file parameter settings PowerProtect Data Manager automatically creates two configuration files for each database when you add the assets to a protection policy and auto-configuration is triggered. If required, you can modify the settings of certain parameters in one of the configuration files.

Add a protection policy for SAP HANA database protection on page 22 provides information about adding the assets to a protection policy.

PowerProtect Data Manager automatically creates the two configuration files as follows, where is the system ID of the SAP HANA system. These configuration file pathnames are predetermined and cannot be changed:

User configuration file: /usr/sap/ /SYS/global/ppdmconfig/ _ _data_user.utl Auto configuration file: /usr/sap/ /SYS/global/ppdmconfig/ _ _data_auto.utl In the user configuration file, _ _data_user.utl, you can optionally modify the parameter settings that are described in the following table.

NOTE: The parameters in the auto configuration file _ _data_auto.utl are set automatically

and cannot be changed. The parameter settings in _ _data_user.utl override the settings in

_ _data_auto.utl.

To enable debug logging during the SAP HANA backups, set the DEBUG_LEVEL and DPRINTF parameters as described in the following table. As required for centralized backups, ensure that you also select Troubleshooting under Advanced Option in the Add Primary Backup dialog box in the PowerProtect Data Manager UI, as described in Add a protection policy for SAP HANA database protection on page 22.

Table 4. Parameters that you can modify for SAP HANA operations

Parameter: CLIENT

Specifies the name of the client directory to store the backup save sets on the DD system.

The default name is , which is automatically set in the CLIENT parameter in the configuration file _ _data_auto.utl.

NOTE: To override the default CLIENT parameter value, ensure that you set the CLIENT parameter in the

_ _data_user.utl file.

Valid value: Name of the client directory where the backup save sets are stored.

Parameter: DEBUG_LEVEL

Enabling the SAP HANA Agent 15

Table 4. Parameters that you can modify for SAP HANA operations (continued)

Specifies the level of debug messages that the PowerProtect Data Manager software writes in the debug log file with a .log file name extension in the /opt/dpsapps/dbappagent/logs directory.

NOTE: The DEBUG_LEVEL parameter must be set in the _ _data_user.utl file.

Valid values:

0 (default) = The software does not generate debug messages. 1 to 9 = The software writes the specified level of debug messages in the debug log. The level of detail in the messages increases

with a higher debug level setting.

Parameter: DPRINTF

Specifies whether the PowerProtect Data Manager software writes debug messages in the debug log file with a .log file name extension in the /opt/dpsapps/dbappagent/logs directory.

NOTE: The DPRINTF parameter must be set in the _ _data_user.utl file.

Valid values:

FALSE (default) = The software does not generate debug messages. TRUE = The software writes debug messages in the debug log. The DEBUG_LEVEL setting determines the level of the debug

messages.

Enable the discovery of database application agent backups To enable the PowerProtect Data Manager to discover the SAP HANA backups that were performed by the database application agent, you must update a specific configuration file.

About this task

Restore an SAP HANA application host on page 34 provides more details about the recovery of SAP HANA backups that were performed by the database application agent.

To enable the discovery of the database application agent backups, perform the following steps.

Steps

1. In the PowerProtect Data Manager UI, ensure that the assets are visible. 2. In the directory /opt/dpsapps/dbappagent/saphana/brownfield, rename the file sap_hana_brownfield_ddbda.utl

as brownfield.utl.

3. Open the file /opt/dpsapps/dbappagent/saphana/brownfield/brownfield.utl in an editor and complete the following settings:

Set the DDBOOST_USER parameter to the username of the DD Boost user configured on the Data Domain system.

Set the DEVICE_HOST parameter to the hostname (as the fully qualified domain name) of the Data Domain system where the backups are stored.

Set the DEVICE_PATH parameter to the top-level directory name of the storage unit (without the /data/col1 prefix) on the Data Domain system.

Set the DISCOVERY_DAYS parameter to the number of days to be used for discovery. The PowerProtect Data Manager will discover the database application agent backups that were performed within the specified past number of days.

Set the RETENTION_DAYS parameter to the number of days that the PowerProtect Data Manager will keep the database application agent backups after discovery.

4. Save the file /opt/dpsapps/dbappagent/saphana/brownfield/brownfield.utl.

Results

The PowerProtect Data Manager will discover the database application agent backups during the subsequent backup discovery operations.

16 Enabling the SAP HANA Agent

Configure support of SAP HANA 2.0 The SAP HANA 2.0 user documentation provides a complete list of all the backup and recovery features, including details about how to enable and configure the features. The following list highlights several of the features:

SAP HANA 2.0 SPS 00 supports data encryption in the persistence layer for both data and log volumes. SAP HANA volume encryption can impact the deduplication rates on the Data Domain systems.

SAP HANA 2.0 SPS 00 supports the user-configurable interval mode for log backups. The interval mode enables the creation of log backups after the service-specific timeout is reached, instead of when the log segment becomes full. A log backup can include multiple log segments. The interval mode setting limits the number of log backups in high-transaction databases, which reduces the impact on the databases. You can configure the interval mode by setting the following parameter in the SAP HANA global.ini file:

log_backup_interval_mode = service

Configure automatic backups of SAP HANA logs The SAP HANA database server automatically performs periodic backups of the redo logs for a database. PowerProtect Data Manager does not perform any log or catalog backups. You cannot perform the log backups with any backup commands.

NOTE: Since the log backups and catalog backups are automatically triggered by SAP HANA, these backups continue to

be performed even when the PowerProtect Data Manager protection policy is disabled.

You can use the SAP HANA Studio GUI to configure the frequency of automatic log backups and whether the Backint interface is used for the log backups.

To configure the automatic backups of SAP HANA redo logs, complete the required settings in SAP HANA Studio.

On the Configuration tab of the Backup editor, complete the settings in the Log Backup Settings group box:

Select Enable Automatic Log Backup. For Destination Type, select Backint. For Backup Interval, specify the log backup interval. Type the numeric value in the text box, and then select the unit of time, such as

Minutes, from the menu.

NOTE: The recommended log backup interval is 30 minutes.

The following figure shows a configuration example in SAP HANA Studio.

Figure 1. Configuring automatic log backups in SAP HANA Studio

Enabling the SAP HANA Agent 17

Configure the SAP HANA parallel backup setting The streams usage by the storage unit during an SAP HANA backup varies, depending on the number and type of parallel operations that are performed at a given time. You can set the SAP HANA parameter parallel_data_backup_backint_channels to specify the number of channels to use for the backup.

The SAP HANA agent requires one Data Domain stream for each backed-up pipe. For example, if an SAP HANA scale-out system has 12 running services, then 12 streams are required to back up the data. Starting with SAP HANA SPS 09, each service can also back up multiple logs for each backup, as controlled by the database parameter max_log_backup_group_size.

For a multistream backup with SAP HANA SPS 11 or later, the SAP HANA agent can use multiple SAP HANA channels to write the backup data for each service. The SAP HANA agent uses a separate channel to write each stream of data to the Data Domain system. To specify the number of channels to use for the backup, up to a maximum of 32 channels, you can set the SAP HANA parameter parallel_data_backup_backint_channels. SAP HANA opens the corresponding number of pipe files for the backup, and the agent saves each stream as a separate save set.

For example, if the parallel_data_backup_backint_channels parameter is set to 12 on the SAP HANA database server, then 12 streams are used for the backup, which produces 12 save sets.

A restore uses the same number of streams as the backup, and ignores the parallel_data_backup_backint_channels parameter setting.

During an SAP HANA backup or restore, the storage unit typically uses the following number of streams:

Number of services x max_log_backup_group_size Due to the design of SAP HANA log backups, an SAP HANA system cannot wait until a stream is available because waiting can negatively affect the database performance.

If the Data Domain system runs out of streams during a backup, the backup fails (although not immediately) with the following error message in the operational log:

153004:hdbbackint: Unable to write to a file because the streams limit was exceeded. The error message is: [5519] [16805] [140261664245536] Tue May 10 06:45:23 2016 ddp_write() failed Offset 0, BytesToWrite 317868, BytesWritten 0 Err: 5519-Exceeded streams limit If the Data Domain system runs out of streams during a restore, then the restore fails (although not immediately) with the following error message in the operational log:

163971 11/28/2016 06:55:59 AM hdbbackint SYSTEM critical Unable to read from a file because the streams limit was exceeded. The error message is: [5519] [60299] [140167084230432] Mon Nov 28 06:55:59 2016 ddp_read() failed Offset 192, BytesToRead 262144, BytesRead 0 Err: 5519-nfs readext remote failed (nfs: Resource (quota) hard limit exceeded)

Manage the SAP HANA application agent You can use the PowerProtect Data Manager UI to add an SAP HANA application agent for data protection, approve and reject pending agent requests, and edit and delete existing agents.

Steps

1. Select Infrastructure > Application Agents.

The Application Agents window appears.

NOTE: If the PowerProtect agent service was able to register during the installation, the SAP HANA host is already

listed and does not need to be added.

2. Click Add. The Add Application/FS Agent window appears.

3. Select one of the following options:

Add IP Address or CSV Filename.

This process is also called Whitelisting.

If you select Add IP Address, perform the following steps:

a. Type the IP Address for the application agent. b. Specify the date until which the application agent is preapproved.

18 Enabling the SAP HANA Agent

c. Click Save. If you select CSV Filename, perform the following steps:

a. Click the Choose File icon.

NOTE: The contents of the .csv file must be in the following format, for example:

"10.25.115.113" "10.25.115.112" "10.25.115.145"

The Explorer window appears. b. Select the .csv file, and then click Open.

The file appears in the Application/FS Agents window. c. Select the date until which the application agent is preapproved. d. Click Save.

If you have disabled Auto whitelist, perform the following steps:

NOTE: The Auto whitelist option disabled by default. When Auto whitelist is enabled, all preapproved

application agents are automatically approved.

a. Select the required application agent. b. Click one of the following options:

Approve Reject Edit, then make the required changes. Remove

c. Click Save.

Next steps

Discover an SAP HANA application host on page 21 describes how to set the host credentials before you schedule a backup.

Enabling the SAP HANA Agent 19

Managing Storage, Assets, and Protection

Topics:

Add protection storage Discover an SAP HANA application host Add a protection policy for SAP HANA database protection Manage the PowerProtect agent service Manage the cloud tier operations with PowerProtect Data Manager

Add protection storage About this task

The PowerProtect Data Manager UI enables users with administrator credentials to add the following storage types:

DD Management Center External DD system

NOTE: The most up-to-date software compatibility information for PowerProtect Data Manager is provided in the eLab

Navigator.

When a DD Management Center is added, PowerProtect Data Manager discovers all the supported DD systems that are managed by the DD Management Center. The PowerProtect Data Manager UI displays the discovered DD systems on the Protection Storage tab of the Infrastructure > Storage window. The DD systems that are managed by the DD Management Center are not displayed until discovery is complete. It might take a few minutes for the DD systems to appear in the Storage window.

For each DD system, the DD Management Center that manages the DD system is indicated in the Managed By column in the table.

If a DD system is added directly to PowerProtect Data Manager, the name that was provided for the DD system when it was added to the PowerProtect Data Manager system is displayed in the Managed By column.

NOTE: Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the

UI, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the

UI has not yet been updated to reflect this change.

Steps

1. Select Infrastructure > Storage.

The Storage window appears.

2. In the Protection Storage tab, click Add. 3. In the Add Storage dialog box, select a storage system (DD System, DD Management Center).

NOTE: If using the Storage Direct agent to move snapshot backups from a VMAX storage array to a DD system, you

do not need to add a DD Management Center.

4. Specify the storage system attributes:

a. In the Name field, specify a storage name. b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address. c. In the Port field, specify the port for SSL communication. Default is 3009.

5. Under Host Credentials click Add, if you have already configured DD credentials that are common across DD systems, select an existing password. Alternatively, you can add new credentials, and then click Save .

6. If a trusted certificate does not exist on the storage system, a dialog box appears requesting certificate approval. Click Verify to review the certificate, and then click Accept.

7. Click Save to exit the Add Storage dialog and initiate the discovery of the storage system.

A dialog box appears to indicate that the request to add storage has been initiated.

3

20 Managing Storage, Assets, and Protection

8. In the Storage window, click Discover to refresh the window with any newly discovered storage systems. When a discovery completes successfully, the Status column updates to OK.

9. To modify a storage system location, complete the following steps:

A storage system location is a label that is applied to a storage system. If you want to store your copies in a specific location, the label helps you select the correct storage system during policy creation.

a. In the Storage window, select the storage system from the table. b. Click Set Location.

The Set Location window appears. c. Click Add in the Location list.

The Add Location window appears. d. In the Name field, type a location name for the asset, and click Save.

10. To manage MTrees in the Storage window, select the storage system from the table and click View storage units.

Results

PowerProtect Data Manager displays External DD systems only in the Storage window Name column. PowerProtect Data Manager displays DD Management Center storage types in the Managed By column.

Troubleshooting protection policy for DD storage unit When adding a protection policy in PowerProtect Data Manager, creation of a storage unit on the selected DD system fails if you reach the maximum MTree and Users count on the DD system. PowerProtect Data Manager enables you to finish adding the protection policy without the storage unit. However, if you subsequently run a backup of this protection policy, the backup process is suspended indefinitely with no error message.

To continue backup operations on this device, you must perform a cleanup on the DD system.

Viewing the DD Boost storage unit password PowerProtect Data Manager provides a script to retrieve the password of a DD Boost unit that is configured as a backup target.

Prerequisites

This process requires the name of the DD MTree where the DD Boost storage unit resides.

Steps

1. SSH to the PowerProtect Data Manager appliance as the admin user. 2. Navigate to the /usr/local/brs/puppet/scripts directory.

3. Obtain the DD Boost storage unit password by typing the following command:

./get_dd_mtree_credential.py PLC-PROTECTION-1551667983302

Discover an SAP HANA application host After you register an application host with PowerProtect Data Manager, you can use the Asset Sources window to discover an application host and modify the application host credentials. For application hosts, discovery is required if you want to schedule a backup. You must add credentials to the SAP HANA database so that PowerProtect Data Manager can access the database to create backups.

About this task

Perform the following steps to discover an SAP HANA application host as an asset source in the PowerProtect Data Manager UI.

Steps

1. Select Infrastructure > Asset Sources.

The Asset Sources window appears.

2. Select the App/File System Host tab. 3. If you are adding an SAP HANA database, select the host entry and click Edit Credentials.

The Edit Credential dialog appears.

Managing Storage, Assets, and Protection 21

4. If you select User Name/Password for Authentication, specify the SYSTEM user's credentials. If the credentials belong to the SYSTEMDB database, select the System Database check box.

If you select User Key for Authentication, specify the credentials of the OS user associated with the database instance. If the credentials belong to the SYSTEMDB database, select the System Database check box.

The following figure shows the fields for adding the required credentials.

Figure 2. Adding the credentials for authentication

5. Click Save.

An entry for the application host with the specified information appears as an entry in a table on the Asset Sources window.

Discovery time is based on networking bandwidth. The resources that are discovered and those that are doing the discovery take a performance hit each time that you go through a discovery process. It might appear that PowerProtect Data Manager is not updating the Asset Sources data.

NOTE: Click Discover at any time if any additions or other changes to your Asset Sources have taken place outside of

the PowerProtect Data Manager environment.

Results

If the database is properly configured, the application hosts can now be added to a PowerProtect Data Manager protection policy.

Add a protection policy for SAP HANA database protection Use the PowerProtect Data Manager UI to add a protection policy to protect the SAP HANA databases.

Prerequisites

When you are create protection policies for SAP HANA multinode databases, ensure that all nodes in the multinode environment are powered on. Register each node, one after the other, with an interval of a few minutes between each node. Otherwise the protection might fail.

You cannot add assets from a single SAP HANA host in two or more protection policies with the same Data Domain. You must add additional protection policies for a different Data Domain. This requirement pertains to issue ECDM-39456.

22 Managing Storage, Assets, and Protection

Steps

1. Select Protection > Protection Policies.

The Protection Policy window appears.

2. Click Add.

The Add Policy wizard appears.

3. On the Type page, specify the new protection policies group fields. For example, if you are creating a protection policy for daily backups in the SAP HANA production environment:

a. In the Name field, specify the name of the protection policy, for example, SAP HANA Prod Databases.

NOTE: The name that you specify here becomes part of the Data Domain MTree entry.

b. In the Description field, specify a short description of the protection policy, for example, SAP HANA Prod Daily Backups.

c. In theType field, select SAP HANA Database. d. Click Next.

The Purpose page appears. 4. On the Purpose page, specify the following fields to indicate the purpose of the new protection policy group:

a. The type of protection policies group.

For an SAP HANA database, you can select from three types:

To use PowerProtect Data Manager to manage all protection centrally, click Centralized Protection. To use SAP HANA to create local backup protection, click Self-Service Protection. PowerProtect Data Manager creates a

protection policy and manages extra stages. If there are SAP HANA assets within the protection policy that you plan to exclude from data protection operations, click

Exclusion.

b. To specify the credentials, click Set Credentials. The Set Credentials dialog box appears.

NOTE:

Credentials that you set at the host level supersede the credentials that you set at the protection policy level.

An SAP HANA instance can have one system database SYSTEMDB and multiple tenant databases. The

SYSTEMDB database and each tenant database can have its own credentials. A tenant database can be backed up

with either its own credentials or the SYSTEMDB credentials. Both the SYSTEMDB database and tenant

databases support two types of credentials:

SAP HANA Database credentials, for which you must specify the database username and password.

SAP HANA Userkey credentials, for which you must specify the user key (created with hdbuserstore command) and OS username of the SAP HANA instance.

In the Set Credentials dialog box, the drop-down list includes all the credentials created for SAP HANA. You can select from the existing credentials or you can create new credentials.

To create new credentials, click Add to open the Add Credentials dialog box, where you can set the authentication type as either User name/Password or User Key and then specify the credential values. For a tenant database, you can specify the credentials of either the SYSTEMDB database or the tenant database itself. When you specify the SYSTEMDB credentials for a tenant database, select the IsSystemDB check box; otherwise, clear the IsSystemDB check box.

c. Click Next. The Assets page appears.

5. Select the unprotected assets that you want to add to the backup of this protection policy group. The window enables you to filter by asset name to locate the required assets.

Also, you can change the assets view to display all assets discovered by PowerProtect Data Manager, or a hierarchical view to display the assets in a tree structure underneath the application host. A hierarchical view might be helpful, for example, if you have added multiple SAP HANA databases, so that you can more easily identify which assets belong to which database.

6. Click Next.

If you selected Exclusion in the Purpose page, the Summary window appears. Proceed to the final two steps.

If you selected Centralized Protection or Self-Service Protection, the File Exclusions page appears. To enable exclusions, click Enable.

a. Select one or more filters to apply, provide the parameters, and click Add Filter.

Click Add a saved filter to use an existing filter or group of filters as a template.

Managing Storage, Assets, and Protection 23

b. Enter a name and description for the filter, and then click Save.

7. Click + Backup. The Add Primary Backup dialog box appears.

8. Specify the backup schedule fields:

For Centralized Protection:

a. In the Recurrence field, select the interval at which the backup job runs within the window that you specify.

Recurrence relates to Start Time and End Time fields.

When you select Hourly, Daily, Weekly, and Monthly recurrence, you are selecting the interval at which the backup job runs within the window that you specify.

b. In the Create Full (Level 0) field, specify the interval in hours to create a full backup.

The interval should be between 1 hour to 12 hours. c. To create an incremental backup that backs up the data since the previous full, incremental, or differential backup, select

Incremental and specify the interval in minutes. d. To create a differential backup that backs up the data since the previous full backup, select Differential and specify the

interval in minutes.

NOTE: SAP HANA automatically performs the log backups and catalog backups. PowerProtect Data Manager

refers to a catalog backup as an AUXILIARY BACKUP TYPE.

e. In the Keep For field, specify the retention period for the backup.

You can extend the retention period for the latest primary backup copy by adding a promotion backup. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can apply promotion backups to keep the full backups taken on Mondays for 10 weeks. Step 9 on page 24 provides instructions.

f. In the Start Time field, specify the time when new backups are initiated in this policy. g. In the End Time field, specify the time after which no new backups are initiated in this policy. It does not mean that any policy

that is running is stopped. h. To enable debug logging during the backups, select Troubleshooting under Advanced Option.

Ensure that you also set the DEBUG_LEVEL and DPRINTF parameters in the configuration file /usr/sap/ /SYS/ global/ppdmconfig/ _ _data_user.utl, as described in Modify the configuration file parameter settings on page 15.

i. Click OK. NOTE:

When a new asset is added to a protection policy during a scheduled backup window, the backup starts right

away. However, if an asset is added to a protection policy outside of the scheduled backup window, the

backup does not start until the next time that backups are configured to run.

If a new asset is added to a protection policy that has a weekly or monthly backup schedule and the current

time is within the scheduled Start Time and End Time, the backup runs right away, regardless of the date. If

the current time is not within the scheduled Start Time and End Time, the backup does not start until the next

time that backups are configured to run.

The Schedule page updates with the newly added backup schedule. For Self-Service Protection:

a. In the Keep For field, specify the retention time. b. Click OK.

After completing a backup schedule, you can change any schedule details by selecting the check box next to the added schedule and clicking Edit.

9. To extend the retention period for the latest primary backup copy, add a promotion backup:

a. Select the checkbox next to the added schedule and click + Backup. b. In the Add Promotion Backup dialog box, specify a weekly or monthly recurrence for the promotion backup schedule, a retention

period for the backup, and then click OK. 10. To replicate these backups to a remote DD system:

a. Select the checkbox next to the primary backup schedule and click Replicate.

NOTE: You cannot replicate a promotion backup. When you select a promotion backup schedule, the Replicate

button is disabled.

24 Managing Storage, Assets, and Protection

b. Complete the schedule details in the Add Primary Replication dialog box, and then click OK.

NOTE: To enable replication, ensure that you add a remote DD system as the replication location. Add protection

storage on page 20 provides detailed instructions about adding a remote DD system.

11. Optionally, to add a cloud stage for the purpose of moving backups from DD storage to the cloud tier, select the check box next to the primary, replication, or promotion schedule, and then select Cloud Tier. Add a cloud tier schedule to a protection policy on page 29 provides more information.

NOTE: In order to move a backup or replica to the cloud tier, schedules must have a weekly or monthly recurrence

and a retention time of 14 days or more. Also, discovery of a DD system configured with a cloud unit is required.

12. Select the check box next to the added schedule. When you select the check box, the Storage Name and Network interface lists are enabled for selection.

13. From the Storage Name list:

Select the backup destination from the list of existing Data Domain systems. To add a system, select Add, and complete the details in the Storage Target window.

When you select the destination storage, the Space field updates with the available capacity on the system. 14. From the Network interface list, select a network interface card (NIC), if applicable. 15. Click Set Storage Quotas to set storage space restrictions for a Data Domain MTree or storage unit to prevent the consumption of

excess space. There are two kinds of quota limitshard limits and soft limits. You can set either a soft or hard limit or both a soft and hard limit. Both values must be integers, and the soft value must be less than the hard value.

NOTE: When you set a soft limit and the limit is reached, an alert is generated but data can still be written to the

Data Domain. When you set a hard limit and the limit is reached, data cannot be written to the MTree. All data

protection operations fail until data is deleted from the MTree. The Data Domain Operating System Administration Guide provides more information about MTree quota configuration.

a. Capacity QuotaControls the total size of pre-compression data written to the Data Domain. b. Stream QuotaThe number of concurrent streams allowed on the system during data protection operations. Setting a Stream

Quota limit can help ensure that system performance is not impacted negatively if a data protection operation is consuming too many system resources.

16. Select the Retention Lock check box to enable retention locking for these backups on the selected system. 17. Click Next.

The Summary page appears. 18. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any

information. When completed, click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy. When the new protection policy group is created, PowerProtect Data Manager automatically performs a full backup. Subsequent backups are performed according to the schedule specified.

19. Click OK to exit the window, or click Go to Jobs to open the Jobs window to monitor the backup of the new protection policy group.

Manage the PowerProtect agent service The PowerProtect agent service provides important functionality for the application agent operations with the PowerProtect Data Manager.

Review the following topics to ensure that you enable and manage the PowerProtect agent service functionality as required for application agent operations.

About the PowerProtect agent service The PowerProtect agent service is a REST API based service that is installed by the application agent on the application host. The agent service provides services and APIs for discovery, protection, restore, instant access, and other related operations. The PowerProtect Data Manager uses the agent service to provide integrated data protection for the application assets.

This section uses to represent the PowerProtect agent service installation directory. By default, the agent service installation location is C:\Program Files\DPSAPPS\AgentService on Windows and /opt/ dpsapps/agentsvc on Linux. All files that are referenced in this section are the relative paths to the agent service installation location.

The PowerProtect agent service performs the following operations:

Managing Storage, Assets, and Protection 25

Addon detectionAn addon integrates the application agent into the agent service. The agent service automatically detects the addons on the system for each application asset type and notifies the PowerProtect Data Manager. While multiple addons can operate with different asset types, only one agent service runs on the application host. Specific asset types can coexist on the same application host.

DiscoveryThe agent service discovers both stand-alone and clustered database servers (application systems), databases and file systems (assets), and their backup copies on the application agent host. After the initial discovery, when the agent service discovers any new application systems, assets, or copies, the agent service notifies the PowerProtect Data Manager.

Self-service configurationThe agent service can configure the application agent for self-service operations by using information that is provided by the PowerProtect Data Manager. When you add an asset to a protection policy for self-service or centralized protection, or modify the protection policy, including changing the DD Boost credentials, the PowerProtect Data Manager automatically pushes the protection configuration to the agents.

Centralized backupsThe agent service performs the centralized backups as requested by the PowerProtect Data Manager. Centralized restoresThe agent service performs the centralized restores as requested by the PowerProtect Data Manager.

NOTE: In the current release, the centralized restores are only available for the File System agent and Storage Direct

agent.

Backup deletion and catalog cleanupThe PowerProtect Data Manager deletes the backup files directly from the protection storage when a backup expires or an explicit delete request is received and no dependent (incremental or log) backups exist. The PowerProtect Data Manager goes through the agent service to delete the catalog entries from the database vendor's catalog and the agent's local datastore.

NOTE: Deletion of any backup copies manually or through the command line is not recommended. PowerProtect

Data Manager deletes all the expired copies as needed.

The agent service is started during the agent installation by the installer. The agent service runs in the background as a service and you do not interact with it directly.

The config.yml file contains the configuration information for the agent service, including several parameter settings that you can change within the file. The config.yml file is located in the directory.

The agent service periodically starts subprocesses to perform the discovery jobs. You can see the type and frequency of these jobs in the jobs: section of the config.yml file. The job interval unit is minutes.

The agent service maintains a datastore in the /dbs/v1 directory, which contains information about the application system, assets, and backups discovered on the system. The size of the datastore files depends on the number of applications and copies on the host. The agent service periodically creates a backup of its datastore in the /dbs/v1/backups directory, as used to recover the datastore if this datastore is lost.

NOTE: The size of each datastore backup is the same as the datastore itself. By default, a backup is created every hour.

To save space on the file system, you can reduce this datastore backup frequency for large datastores. By default, the

datastore backup is retained for one week. You can change the datastore backup frequency, retention period, and

backup location in the config.yml file.

Start, stop, or obtain the status of the PowerProtect agent service The PowerProtect agent service is started during the agent installation by the installer. If needed, you can use the appropriate procedure to start, stop, or obtain the status of the agent service.

On Linux, you can start, stop, or obtain the status of the agent service by running the register.sh script that is found in the directory.

To start the agent service:

# register.sh --start

Started agent service with PID - 1234

Alternatively, you can use the following command to start the agent service:

# service agentsvc start

26 Managing Storage, Assets, and Protection

To stop the agent service:

# register.sh --stop

Successfully stopped agent-service.

Alternatively, you can use the following command to stop the agent service:

# service agentsvc stop To obtain the status when the agent service is running:

# register.sh --status

Agent-service is running with PID - 1234 To obtain the status when the agent service is not running:

# register.sh --status

Agent-service is not running. Alternatively, you can use the following command to obtain the status of the agent service when it is running or not running:

# service agentsvc status

Troubleshoot the PowerProtect agent service operations To troubleshoot the agent service operations, you can check the agent service log file agentsvc.log, which is created in the agent service home directory. To modify the log level and retention of temporary files, you can modify specific parameter settings in the config.yml file.

About this task

To modify the log level and retention of temporary files, you can perform the following steps.

Steps

1. Stop the agent service by using the appropriate procedure from the preceding topic. 2. Open the config.yml file in an editor.

3. Modify the log-level settings in the following parameters, as required:

NOTE: These parameters are listed in order of decreasing number of messages in the debug information output. The

default log-level is INFO.

DEBUG INFO WARNING ERROR CRITICAL

4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.

NOTE: The agent service and application agent communicate through the temporary files, which are typically

deleted after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to

True permanently, or the temporary files can use excessive space on the file system.

5. Start the agent service by using the appropriate procedure from the preceding topic.

Managing Storage, Assets, and Protection 27

Register the PowerProtect agent service to a different server address on Linux The PowerProtect agent service is registered to a particular PowerProtect Data Manager server during the agent installation by the installer. If needed, you can register the agent service to a different PowerProtect Data Manager server address. If there are multiple agents installed on a host, all agents will be re-registered to the new PowerProtect server.

The agent service can only be registered to a single PowerProtect Data Manager server.

On Linux, perform the following steps to register the agent service to a different server address.

1. To unregister from the current PowerProtect Data Manager server, go to the /opt/dpsapps/agentsvc directory and run the unregister.sh script.

2. In the dbs/v1 directory, rename the copies.db file to copies-backup.db.

3. To register the agent service to the different server address, go to the /opt/dpsapps/agentsvc directory, run the register.sh script, and provide the PowerProtect Data Manager server IP address or hostname:

The following command prompts for the new IP address or hostname:

# register.sh

Enter the PowerProtect Data Manager IP address or hostname: 10.0.01

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234 The following command includes the new IP address on the command line:

# register.sh --ppdmServer=10.0.0.1

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234 4. Verify that the agentsvc process is started.

5. Verify the agent registration status:

a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents. b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is Registered.

6. To perform asset discovery for the agent:

a. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources.

The Asset Sources window appears. b. Select the App/File System Host tab. c. Select the agent hostname and click Discover. At the confirmation prompt, click Yes.

When you select Infrastructure > Assets, the Assets window displays the discovered assets.

Recovering the PowerProtect agent service from a disaster You can perform self-service restores of application assets by using a file system or application agent, regardless of the state of the agent service or PowerProtect Data Manager. The information in the this section describes how to bring the agent service to an operational state to continue if a disaster occurs and the agent service datastore is lost.

The agent service periodically creates a backup of its datastore in the /dbs/v1/ backups repository. If all these backups are lost, the agent service can still start. The agent service discovers all the application systems, assets, and backup copies on the system again, and notifies PowerProtect Data Manager. Depending on when the failure occurred, the agent service might not be able to find older backup copies for some asset types. As a result, the centralized deletion operations might fail when cleaning up the database vendor catalog or removing older backups that are taken before the asset is added to PowerProtect Data Manager.

By default, the agent service backs up consistent copies of its datastore files to the local disk every hour and keeps the copies for 7 days. Each time the agent service backs up the contents of the datastore, it creates a subdirectory under the

28 Managing Storage, Assets, and Protection

/dbs/v1/backups repository. The subdirectories are named after the time the operation occurred, in the format YYYY-MM-DD_HH-MM-SS_epochTime.

By default, the datastore repository is on the local disk. To ensure that the agent service datastore and its local backups are not lost, it is recommended that you back up the datastore through file system backups. You can also change the datastore backup location to a different location that is not local to the system. To change the datastore backup location, update the values in the config.yml file.

Restore the PowerProtect Data Manager agent service datastore

Prerequisites

NOTE: Ensure that the agent service is powered off. Do not start the agent service until disaster recovery is complete.

About this task

You can restore the datastore from the datastore backup repository. If the repository is no longer on the local disk, restore the datastore from file system backups first.

To restore the datastore from a backup in the datastore backup repository, complete the following steps:

Steps

1. Move the files in the /dbs/v1 directory to a location for safe keeping.

NOTE: Do not move or delete any /dbs/v1 subdirectories.

2. Select the most recent datastore backup.

The directories in the datastore backup repository are named after the time the backup was created.

3. Copy the contents of the datastore backup directory to the /dbs/v1 directory. After the copy operation is complete, the /dbs/v1 directory should contain the following files:

copies.db objects.db resources.db sessions.db

4. Start the agent service.

Manage the cloud tier operations with PowerProtect Data Manager The PowerProtect Data Manager cloud tier feature works in tandem with the Data Domain Cloud Tier feature to move PowerProtect Data Manager backups from Data Domain systems to the cloud. This provides long-term storage of PowerProtect Data Manager backups by seamlessly and securely tiering data to the cloud.

From the PowerProtect Data Manager UI, you configure cloud tier to move PowerProtect Data Manager backups from Data Domain to the cloud, and you can perform seamless recovery of these backups.

Data Domain cloud storage units must be pre-configured on the Data Domain system before they are configured for cloud tier in the PowerProtect Data Manager UI. The Data Domain Operating System Administration Guide provides more information.

Add a cloud tier schedule to a protection policy You can add a cloud tier schedule to a protection policy for SAP HANA centralized and self-service backups to cloud tier.

Prerequisites

Ensure that a Data Domain system is set up for cloud tiering.

Managing Storage, Assets, and Protection 29

About this task

Both SAP HANA centralized and self-service protection policies support cloud tiering. You can create the cloud tier schedule from both primary and replication stages. Schedules must have a minimum weekly recurrence and a retention time of 14 days or greater.

Steps

1. Log in to PowerProtect Data Manager with administrator credentials. 2. Select Protection > Protection Policies > Add. 3. On the Type page, enter a name and description, select SAP HANA as the type of system to back up, and click Next. 4. On the Purpose page, select from the available options to indicate the purpose of the new protection policy, and then click Next. 5. On the Assets page, select the assets to be protected with this policy, and then click Next. 6. On the Schedule page, select + Backup. 7. On the Add Primary page, set the following parameters, and then click OK:

RecurrenceSelect Weekly or Monthly. Keep forCloud Tier backup requires a minimum of 2 weeks. Optionally, change the Start Time or End Time or both.

8. Select the Primary protection policy that you created, and then select Cloud Tier. 9. For Self -Service Protection Policy:

Select a primary backup to create a promotion backup. Keep forCloud Tier backup requires a minimum of 2 weeks.

10. In the Add Promotion Backup dialog box, set the following parameters and then click OK:

RecurrenceSelect Weekly or Monthly. Create Full (Level 0)Add the option as per the recurrence. Keep forCloud Tier backup requires a minimum of 2 weeks.

11. Select the Promotion Backup policy, and then select Cloud Tier. 12. In the Add Cloud Tier dialog box, set the following parameters and then click OK:

Select the appropriate unit from the Cloud Target list. For Tier After, set a time of at least 2 weeks.

The cloud tier protection policy is created. 13. Click Next, verify the information, and then click Finish.

A new job is created, which you can view under the Jobs tab after the job completes.

Tier the PowerProtect Data Manager backups from Data Domain to the cloud Once you add the SAP HANA database assets to a protection policy that contains a cloud tier stage, you can perform tiering of these assets by using the PowerProtect Data Manager UI.

Steps

1. Log in to PowerProtect Data Manager with administrator credentials. 2. Select Infrastructure > Assets > SAP HANA Databases. 3. On the Type Assets page, select the asset, and then click View Copies. 4. Select the Data Domain where the PowerProtect Data Manager backups for SAP HANA reside, and then select Full protection copy

which is older than 2 weeks. 5. Click Tier to tier the backups.

A new job is created, which you can view under the Jobs tab after the job completes. When you monitor the cloud tier progress on backup copies for the asset job, the status remains in the running state until data movement occurs from the Data Domain.

6. Log in to the Data Domain system, and obtain the storage unit details by running the command data-movement policy show. For example:

# data-movement policy show Mtree Target(Tier/Unit Name) Policy Value ----------------------------------------- ---------------------- ----------- -------

30 Managing Storage, Assets, and Protection

/data/col1/rman137-blrv136g140-840dd Cloud/ecs-unit app-managed enabled /data/col1/rman134-copy-blrv136g138-61900 Cloud/ecs-unit app-managed enabled /data/col1/rman-11-blrv136h010-7014f Cloud/ecs-unit app-managed enabled

7. Run the data-movement start mtrees command for the particular MTree. For example:

# data-movement start mtrees /data/col1/rman137-blrv136g140-840dd

After successful data movement to the cloud, the cloud tier job completes. At some point on the Assets > View Copies page, the Location field changes to Cloud.

The Data Domain Operating System Administration Guide provides more details about the cloud tier data movement.

Restore the cloud tier backups to Data Domain The restore operations of backups that have been tiered to the cloud are identical to normal restore operations.

The PowerProtect Data Manager software recalls a copy of the backup from the cloud to the local (active) tier of the Data Domain system, and then performs a restore of the backup from the active tier to the client. The status appears as Cloud. After the restore, the backup copy is removed from cloud tier, and is stored on the active tier of the Data Domain system for a period of 10 days, after which it is deleted.

Recall and restore the cloud tier backup Use the PowerProtect Data Manager UI to recall the backup on the cloud tier to the active tier on the Data Domain system and restore this backup.

Prerequisites

NOTE: When a backup is recalled from the cloud tier to the active tier, the copy is removed from the cloud tier.

Steps

1. Select Recovery > Assets, click Data Domain, and then select one of the available copies in the table with the location as Cloud. 2. Click Recall, and then specify how long to keep the copy on the active tier.

A job is created to recall the backup copy from the cloud tier for the selected asset. The copy is moved from the cloud tier and the location is changed from Cloud to Local.

3. Select the recalled copy, and then click Edit Recall Retention. 4. To re-tier the copy to the active tier, select the recalled copy.

Managing Storage, Assets, and Protection 31

Performing Self-Service Backups of SAP HANA Databases

Topics:

Performing self-service backups of SAP HANA databases Restore an SAP HANA application host

Performing self-service backups of SAP HANA databases To enable self-service protection, when you create the SAP HANA protection policy, select Self-Service Protection.

To perform a self-service or manual backup of an SAP HANA database, you can run either of the supported SAP HANA tools on the SAP HANA database server:

SAP HANA Studio GUI SAP HANA command-line interface (CLI) with the hdbsql command

The following topics provide details about how to perform backups with these supported SAP HANA tools. The SAP HANA documentation provides more information about the SAP HANA backup tools.

Performing backups by using SAP HANA Studio In SAP HANA Studio, you must specify the database for backup and enable the backup to use the Backint interface.

For example, the Specify Backup Settings dialog box appears as follows.

Figure 3. Specifying backup settings in SAP HANA Studio

4

32 Performing Self-Service Backups of SAP HANA Databases

In the Specify Backup Settings dialog box, you must select Backint for Destination Type, and then optionally type a prefix for the backup name in the Backup Prefix text box. If you specify a prefix, the backup name will include the prefix, prefix_databackup_#_#.

For Backup Type, you can select one of the three supported backup types: Complete Data Backup, Differential Backup, Incremental Backup.

Performing backups by using the SAP HANA CLI To perform a database backup, you can run the appropriate hdbsql command. For example:

About this task

hdbsql -U "backup data using backint ('/usr/sap/ /SYS/global/hdb/backint/ ')"

where:

is the user store key created with the SAP HANA hdbuserstore tool. SAP HANA documentation provides details about the tool.

is the system ID of the SAP HANA system. /usr/sap/ /SYS/global/hdb/backint/ is optional in the hdbsql command.

is an optional prefix for the backup name. If you specify in the hdbsql command, then the backup name will include the prefix, _databackup_#_#.

The SAP HANA documentation provides details about how to use the hdbsql command for backups.

Performing backups by using the SAP HANA CLI in an MDC system You must specify the correct credentials and database name in the hdbsql command to perform a backup of an SAP HANA MDC database.

About this task

For a backup of the master system database SYSTEMDB, you must specify the system database administrator credentials with the hdbsql command.

For a backup of a tenant database, you can specify either the system database administrator credentials or the tenant database administrator credentials with the hdbsql command. However, do not try to use the system database administrator credentials for a direct connection to a tenant database.

NOTE: Use the system database administrator credentials to connect to a target database only through the SYSTEMDB

database. Use the tenant database administrator credentials to connect directly to the target database.

For example, the following command backs up the tenant database DB0 by using a connection to the SYSTEMDB database through the system database administrator credentials:

hdbsql -i 00 -u system_database_administrator_username -p system_database_administrator_password [-U user_key] -d SYSTEMDB "backup data for DB0 using backint ('/usr/sap/SID/SYS/global/hdb/backint/DB_DB0/prefix')"

The following command backs up the tenant database DB0 by using a direct connection to the database through the tenant database administrator credentials:

hdbsql -i 00 -u tenant_database_administrator_username -p tenant_database_administrator_password [-U user_key] -d DB0 "backup data using backint ('/usr/sap/SID/SYS/global/hdb/backint/DB_DB0/prefix')"

Performing Self-Service Backups of SAP HANA Databases 33

Canceling backups by using the SAP HANA CLI You can cancel an SAP HANA backup by using the appropriate SQL command with the backup ID of the running data backup.

Steps

1. Determine the backup ID of the running data backup by using the monitoring view M_BACKUP_CATALOG, which provides an overview of information about backup and recovery activities.

To determine the backup ID, run the following SQL command:

select BACKUP_ID from "M_BACKUP_CATALOG" where entry_type_name = 'complete data backup' and state_name = 'running' order by sys_start_time desc;

2. To cancel the running data backup, run the following SQL command:

backup cancel

Checking backups by using the SAP HANA CLI To check the integrity and availability of SAP HANA backups, starting with SAP HANA SPS 07, you can run the hdbbackupcheck and hdbbackupdiag commands.

Using the hdbbackupcheck command to check backup integrity To check the integrity of a data or log backup, you can run the hdbbackupcheck command. The command reads part of the backup, checks the metadata for correctness and consistency, and checks the content for any changes.

The following example command checks the integrity of an SAP HANA backup:

./hdbbackupcheck -v --backintParamFile /usr/sap/space/space_hana/ init.ddp.utl /usr/sap/AAA/SYS/global/hdb/backint/foooo_databackup_0_1 -e 1396019304

In this command, the backup file name is the pipe name provided by SAP HANA during the backup. The pathname is the location where the pipes were created. The -e option provides the external backup ID of the backup file. You can find all these values in the M_BACKUP_CATALOG_FILES view.

The SAP Note 1869119 provides details about the hdbbackupcheck command.

Using the hdbbackupdiag command to check backup availability To check the backup availability, you can run the hdbbackupdiag command.

The following example command checks the availability of an SAP HANA backup:

./hdbbackupdiag --check -i 1393886826664 --useBackintForCatalog --backintDataParamFile /nsr/res/initAAA.utl --backintLogParamFile /nsr/res/initAAA-logs.utl

Ensure that you use the --useBackintForCatalog option.

The SAP Note 1873247 provides more details about the hdbbackupdiag command.

Restore an SAP HANA application host You can perform database restores directly to the SAP HANA application host by using the SAP HANA agent.

To perform a restore and recovery of an SAP HANA database, you can run either of the supported SAP HANA tools on the SAP HANA database server:

SAP HANA Studio GUI (recommended method) SAP HANA command-line interface (CLI) using an SQL command

The following topics provide details about the restore and recovery procedures with these supported SAP HANA tools. The SAP HANA documentation provides more information about the SAP HANA restore and recovery tools.

34 Performing Self-Service Backups of SAP HANA Databases

NOTE: When you restore an SAP HANA backup that was performed by the database application agent, the restore must

use the same UTL file that was originally used for the backup. Before you start the restore, run the SAP HANA Studio

GUI and set data_backup_parameter_file, log_backup_parameter_file, and

catalog_backup_parameter_file to all point to the UTL file that was used for the backup.

Performing restore and recovery by using SAP HANA Studio 1. Start SAP HANA Studio. 2. In the recovery GUI, go to the Specify Recovery Type page.

Figure 4. Specifying the recovery type in SAP HANA Studio

a. Select one of the following types of recovery for the required SID:

Recover the database to its most recent stateRecovers the database as close as possible to the current time. Recover the database to the following point in timeRecovers the database to a specific point-in-time. Recover the database to a specific data backupRestores only the specified data backup.

b. In an exceptional case when a previous recovery has failed, click Advanced >>, and then select Recover the database to the following log position.

c. Click Next >. 3. On the Locate Log Backups page, specify the locations of the log backup files to use to perform recovery.

The backup locations for the single database containers and the multitenant database containers are as follows:

Single database container/usr/sap/ /SYS/global/hdb/backint/ Multitenant database container (System DB)/usr/sap/ /SYS/global/hdb/backint/SYSTEMDB

Performing Self-Service Backups of SAP HANA Databases 35

Multitenant database container (Tenant DB)/usr/sap/ /SYS/global/hdb/backint/DB_

Figure 5. Locating the log backups in SAP HANA Studio 4. On the Select Data Backup page, select the database backup for either restore or recovery.

36 Performing Self-Service Backups of SAP HANA Databases

Figure 6. Selecting the data backup in SAP HANA Studio

To check the availability of a backup, select the backup in the table, and then click Check Availability. The Available column in the table displays either a green icon if the backup is available or a red icon if the backup is not available.

5. On the Other Settings page, select the required options, and then click Next >. 6. On the Review Recovery Settings page, review the information, and then click Finish.

The recovery progress appears for each service that includes the name server, the index server, and the statistics server. A confirmation message appears when the recovery completes.

Performing restore with dependency chaining or replication storage Perform the following steps for a restore that involves dependency chaining between save sets of two different storage targets or a restore from a replication storage target.

1. Edit the existing auto configuration file, and append the following [SECONDARY_SYSTEM] information in the file. Modify the configuration file parameter settings on page 15 provides details about the configuration file.

NOTE:

The secondary CLIENT parameter is optional. If specified, then the query of the secondary storage target is

performed by using the secondary client name. If not specified, then the query is performed by using the primary

client name.

Successive auto-configuration requests will overwrite the auto configuration file. To preserve the details from the

file, make a copy of the file.

Performing Self-Service Backups of SAP HANA Databases 37

[SECONDARY_SYSTEM] CLIENT= DDBOOST_USER = DEVICE_HOST = DEVICE_PATH = For example:

[SECONDARY_SYSTEM] CLIENT=newdb DDBOOST_USER = myplc-0662e093dd6b-37247 DEVICE_HOST = 10.118.156.240 DEVICE_PATH = /myplc-0662e093dd6b-37247

2. In SAP HANA Studio, set all the following parameters to the pathname of the auto configuration file:

log_backup_parameter_file data_backup_parameter_file catalog_backup_parameter_file

3. Start the restore from SAP HANA Studio. Performing restore and recovery by using SAP HANA Studio on page 35 provides details.

Performing alternate host recovery To enable an alternate host recovery, copy the required user configuration file and auto configuration file from the source machine to the destination machine. Modify the configuration file parameter settings on page 15 provides details about the configuration files.

You must replicate the directory path of the configuration files on the destination machine, including the same permissions, and then copy the user and auto configuration files from the source machine to the directory path.

For example, if the source instance is SID, then create the following path on the destination machine:

/usr/sap/SID/SYS/global/ppdmconfig When the configuration files are in place, the steps for performing the alternate host recovery are the same as the steps for restoring the database to the same host.

Performing restore of backups performed prior to PowerProtect Data Manager registration Perform the following steps to restore an existing SAP HANA backup. An existing backup is a backup that you performed before integrating the SAP HANA agent with the PowerProtect Data Manager software and before adding an asset to a PowerProtect Data Manager protection policy.

1. Edit the existing auto configuration file, and append the following [SECONDARY_SYSTEM] information in the file. Modify the configuration file parameter settings on page 15 provides details about the configuration file.

NOTE: The secondary CLIENT parameter is mandatory for the restore of an existing backup. The secondary CLIENT parameter setting is the same as the CLIENT parameter setting at the time of the original backup.

For example, you can obtain the values of all four following parameters from the .utl file used for the original backup:

[SECONDARY_SYSTEM] CLIENT=newdb DDBOOST_USER = myplc-0662e093dd6b-37247 DEVICE_HOST = 10.118.156.240 DEVICE_PATH = /myplc-0662e093dd6b-37247 For a restore with a version 19.5 server and version 19.4 client, you must use the .utl file that was used for the original backup.

NOTE: After you restore the backup that was performed prior to registration with PowerProtect Data Manager, the

catalog entries will not be visible for any new backups that are performed after the PowerProtect Data Manager

registration.

2. In SAP HANA Studio, set all the following parameters to the pathname of the respective .utl file:

log_backup_parameter_file data_backup_parameter_file catalog_backup_parameter_file

3. Start the restore from SAP HANA Studio. Performing restore and recovery by using SAP HANA Studio on page 35 provides details.

38 Performing Self-Service Backups of SAP HANA Databases

Performing recovery by using the SAP HANA CLI To perform a recovery of an SAP HANA backup, starting with SAP HANA SPS 07, you can use an SQL command.

NOTE: The SAP HANA Studio GUI is the recommended method to perform a restore and recovery.

To run the recovery SQL command, you must be logged in to the SAP HANA system as the OS user adm. In a scale-out multinode environment, you must run the command from the master node.

The recovery command must first include the HDBSettings.sh and recoverSys.py scripts in that order. The HDBSettings.sh script sets the environment for recovery. The recoverSys.py script processes the recovery SQL command and performs the database recovery.

The following example command performs a recovery of an SAP HANA backup:

./HDBSettings.sh recoverSys.py --command="recover database until timestamp '2014-02-28 00:00:00' using data path ('/usr/sap/AAA/SYS/global/hdb/backint/') using log path ('/usr/sap/AAA/SYS/global/hdb/backint/') using BACKUP_ID 1593520382350" --wait

You must include the --wait option for proper completion of the recoverSys.py script.

The SAP HANA Administration Guide provides details about the SQL command syntax of the recovery command.

Performing recovery by using the SAP HANA CLI in an MDC system To recover an SAP HANA MDC database with the SAP HANA CLI, you must log in to the SAP HANA SYSTEMDB database and run the required recover command.

For example, run the following command to recover the database application agent back

Manualsnet FAQs

If you want to find out how the 19.5 Dell works, you can view and download the Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide on the Manualsnet website.

Yes, we have the SAP HANA Agent User Guide for Dell 19.5 as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The SAP HANA Agent User Guide should include all the details that are needed to use a Dell 19.5. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell PowerProtect 19.5 Data Manager SAP HANA Agent User Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.