Contents

Dell PowerProtect 19.10 Data Manager SAP HANA User Guide PDF

1 of 61
1 of 61

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

PowerProtect Data Manager 19.10 SAP HANA User Guide

March 2022 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 - 2022 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........................................ 9 PowerProtect Data Manager overview..........................................................................................................................9 Supported Internet Protocol versions............................................................................................................................ 9 About the SAP HANA agent............................................................................................................................................. 9 Prerequisites....................................................................................................................................................................... 10 Firewall and port considerations.....................................................................................................................................10 Role-based security............................................................................................................................................................11 Data-in-flight encryption...................................................................................................................................................11 PowerProtect Data Manager new deployment overview......................................................................................... 11 PowerProtect Data Manager existing deployment overview..................................................................................12

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

Install the SAP HANA agent...................................................................................................................................... 14 Update the SAP HANA agent................................................................................................................................... 15 Uninstall the SAP HANA agent................................................................................................................................. 15 Decommission the SAP HANA agent version pre-19.8....................................................................................... 16 Recommission the SAP HANA agent.......................................................................................................................17 Configure the SAP HANA operations...................................................................................................................... 17

Manage the SAP HANA application agent.................................................................................................................. 22 View application agent details.................................................................................................................................. 23

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

View the storage unit password.............................................................................................................................. 26 Enable an asset source.....................................................................................................................................................27

Disable an asset source..............................................................................................................................................27 Delete an asset source.....................................................................................................................................................28 Discover an SAP HANA application host.....................................................................................................................28 Add and remove the credentials for SAP HANA assets.......................................................................................... 29 Add a protection policy for SAP HANA database protection................................................................................. 30 Cancel an application agent protection job.................................................................................................................35 Extended retention........................................................................................................................................................... 36 Edit the retention period for backup copies............................................................................................................... 38 Delete backup copies....................................................................................................................................................... 38

Retry a failed backup copy deletion........................................................................................................................39 Export data for deleted backup copies.................................................................................................................. 40 Remove backup copies from the PowerProtect Data Manager database.................................................... 40

Enable the SAP HANA agent after hostname change.............................................................................................. 41 Manage the PowerProtect agent service....................................................................................................................41

Contents

Contents 3

About the PowerProtect agent service..................................................................................................................41 Start, stop, or obtain the status of the PowerProtect agent service............................................................ 42 Register the PowerProtect agent service to a different server address on AIX or Linux.........................43 Recovering the PowerProtect agent service from a disaster.......................................................................... 44

Manage the cloud tier operations with PowerProtect Data Manager................................................................. 45 Add a cloud tier schedule to a protection policy................................................................................................. 45 Tier the PowerProtect Data Manager backups from DD to the cloud...........................................................46 Restore the cloud tier backups to DD.................................................................................................................... 46

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

Performing backups by using SAP HANA Studio................................................................................................ 48 Performing backups by using the SAP HANA CLI...............................................................................................49 Canceling backups by using the SAP HANA CLI................................................................................................. 49 Checking backups by using the SAP HANA CLI.................................................................................................. 50

Restore an SAP HANA application host...................................................................................................................... 50 Performing restore and recovery by using SAP HANA Studio..........................................................................51 Performing restore with dependency chaining or replication storage........................................................... 53 Performing alternate host recovery........................................................................................................................54 Performing restore of backups performed prior to PowerProtect Data Manager registration............... 55 Performing recovery by using the SAP HANA CLI..............................................................................................56

Appendix A: SAP HANA Best Practices and Troubleshooting.......................................................57 Troubleshooting storage units........................................................................................................................................57 Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname......................58 Troubleshooting agent registration ............................................................................................................................. 58 Troubleshooting PowerProtect agent service operations...................................................................................... 59 Troubleshooting a negative Reduction % value for self-service catalog backup..............................................59 Troubleshooting a missing duration value for centralized backup........................................................................ 59 Troubleshooting a catalog restore issue for assets with the same SID and database name..........................60 Troubleshooting a backup and delete issue with database authentication type of userkey...........................60 Troubleshooting a shortened retention issue with SAP HANA full backup........................................................ 60 Troubleshooting issues after DD change in protection policy................................................................................60 Troubleshooting an auto-configuration failure in multinode environment........................................................... 61 Troubleshooting an issue with onboarded backup copies........................................................................................61 Troubleshooting a restore of replicated backup from secondary DD................................................................... 61 Troubleshooting an issue with protection policy in multihost configuration....................................................... 61

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 Customer Support.

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

go to the Customer Support website.

Product naming Data Domain (DD) is now PowerProtect DD. References to Data Domain or Data Domain systems in this documentation, in the user interface, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the user interface has not yet been updated to reflect this change.

Language use This document might contain language that is not consistent with Dell Technologies current guidelines. Dell Technologies plans to update the document over subsequent future releases to revise the language accordingly.

This document might contain language from third-party content that is not under Dell Technologies control and is not consistent with the current guidelines for Dell Technologies own content. When such third-party content is updated by the relevant third parties, this document will be revised accordingly.

Website links The website links used in this document were valid at publication time. If you find a broken link, provide feedback on the document, and a Dell employee will update the document as necessary.

Purpose This document describes how to configure and use the Dell EMC PowerProtect Data Manager with the SAP HANA agent to back up and restore the SAP HANA server. The PowerProtect Data Manager Administration and User Guide provides additional details about configuration and usage procedures.

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 March 22, 2022 Initial release of this document for PowerProtect Data Manager version 19.10.

Preface 5

Compatibility information Software compatibility information for the PowerProtect Data Manager software is provided at the E-Lab Navigator.

Related documentation The following publications are available at Customer Support and provide additional information:

Table 2. Related documentation

Title Content

PowerProtect Data Manager Administration and User Guide Describes how to configure the software.

PowerProtect Data Manager Deployment Guide Describes how to deploy the software.

PowerProtect Data Manager Licensing Guide Describes how to license the software.

PowerProtect Data Manager Release Notes Contains information on new features, known limitations, environment, and system requirements for the software.

PowerProtect Data Manager Security Configuration Guide Contains security information.

PowerProtect Data Manager Amazon Web Services Deployment Guide

Describes how to deploy the software to Amazon Web Services (AWS).

PowerProtect Data Manager Azure Deployment Guide Describes how to deploy the software to Microsoft Azure.

PowerProtect Data Manager Google Cloud Platform Deployment Guide

Describes how to deploy the software to Google Cloud Platform (GCP).

PowerProtect Data Manager Cloud Disaster Recovery Administration and User Guide

Describes how to deploy Cloud Disaster Recovery (Cloud DR), protect virtual machines in the AWS or Azure cloud, and run recovery operations.

PowerProtect Data Manager Cyber Recovery User Guide Describes how to install, update, patch, and uninstall the Dell EMC PowerProtect Cyber Recovery software.

PowerProtect Data Manager File System User Guide Describes how to configure and use the software with the File System agent for file-system data protection.

PowerProtect Data Manager Kubernetes User Guide Describes how to configure and use the software to back up and restore namespaces and PVCs in a Kubernetes cluster.

PowerProtect Data Manager Microsoft Exchange Server User Guide

Describes how to configure and use the software to back up and restore the data in a Microsoft Exchange Server environment.

PowerProtect Data Manager Microsoft SQL Server User Guide

Describes how to configure and use the software to back up and restore the data in a Microsoft SQL Server environment.

PowerProtect Data Manager Oracle RMAN User Guide Describes how to configure and use the software to back up and restore the data in an Oracle Server environment.

PowerProtect Data Manager SAP HANA User Guide Describes how to configure and use the software to back up and restore the data in an SAP HANA Server environment.

PowerProtect Data Manager Storage Direct User Guide Describes how to configure and use the software with the Storage Direct agent to protect data on VMAX storage arrays through snapshot backup technology.

PowerProtect Data Manager Network Attached Storage User Guide

Describes how to configure and use the software to protect and recover the data on network-attached storage (NAS) shares and appliances.

PowerProtect Data Manager Virtual Machine User Guide Describes how to configure and use the software to back up and restore virtual machines and virtual-machine disks (VMDKs) in a vCenter Server environment.

6 Preface

Table 2. Related documentation (continued)

Title Content

VMware Cloud Foundation Disaster Recovery With PowerProtect Data Manager

Provides a detailed description of how to perform an end-to- end disaster recovery of a VMware Cloud Foundation (VCF) environment.

PowerProtect Data Manager Disaster Recovery Best Practices Guide

Provides guidance and best practices for a PowerProtect Data Manager server disaster-recovery solution.

PowerProtect Data Manager Public REST API documentation Contains the PowerProtect Data Manager APIs and includes tutorials to guide you in their use.

vRealize Automation Data Protection Extension for Data Protection Systems Installation and Administration Guide

Describes how to install, configure, and use the Dell EMC vRealize Data Protection Extension.

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

Table 3. Style conventions

Formatting Description

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 The Customer Support website The Community Network

Where to get support The Customer Support website 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 Customer Support.

To access a product-specific page:

1. Go to the Customer Support website.

Preface 7

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:

1. Go to the Customer Support website. 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 the Customer Support website. 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 a support agent, submit a service request. To submit a service request:

1. Go to the Customer Support website. 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 the Customer Support website. 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. 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.

8 Preface

PowerProtect Data Manager for SAP HANA Agent Overview

Topics:

PowerProtect Data Manager overview Supported Internet Protocol versions About the SAP HANA agent Prerequisites Firewall and port considerations Role-based security Data-in-flight encryption 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 the application agent creates. Then monitor that catalog data to determine if retention

policies are being adhered to. Manage the life cycle of backups that the application agent creates. 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, system administrators, or backup administrators create the backups and perform the restore operations.

Supported Internet Protocol versions PowerProtect Data Manager only supports the use of IPv4 addresses.

Using an IPv6 address can result in errors or other unexpected behavior. When configuring devices to connect over the network with PowerProtect Data Manager, use only IPv4 addresses.

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 DD host, storage unit, user, and password. Install and configure the SAP HANA agent 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 E-Lab Navigator.

1

PowerProtect Data Manager for SAP HANA Agent Overview 9

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

Requirements: NOTE: The most up-to-date software compatibility information for the PowerProtect Data Manager software and the

application agents is provided in the E-Lab Navigator.

Oracle Server is installed and configured on one of the following systems:

Stand-alone configuration. Oracle RAC in active/active configuration only.

NOTE: PowerProtect Data Manager does not support an Oracle database installation in a Data Guard environment.

A list of hosts that write backups to DD systems is available. DDOS version 6.1 or later and the PowerProtect DD Management Center are required. All models of DD systems are

supported.

NOTE: PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version

6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.

Application agent 19.10 or earlier is required. License: A trial license is provided with the PowerProtect Data Manager software. Dell EMC Data Protection Suite

Applications, Backup, and Enterprise customers can contact Dell EMC Licensing Support for assistance with a permanent PowerProtect Data Manager license.

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

The PowerProtect Data Manager 19.10 download file requires the following: ESXi version 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 4. PowerProtect Data Manager port requirements

Description Communication Port

SSH communications Bi-directional communication between the SSH client and the PowerProtect Data Manager appliance

22 TCP/UDP

RestServer Bi-directional 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

10 PowerProtect Data Manager for SAP HANA Agent Overview

Table 4. PowerProtect Data Manager port requirements (continued)

Description Communication Port

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

Bi-directional communication between the database hosts and the PowerProtect Data Manager appliance

7000 TCP

Embedded VM Direct service

Outbound 9090 TCP

Role-based security PowerProtect Data Manager provides predefined user roles that control access to areas of the user interface and to protected operations. Some of the functionality in this guide is reserved for particular roles and may not be accessible from every user account.

By using the predefined roles, you can limit access to PowerProtect Data Manager and to backup data by applying the principle of least privilege.

The PowerProtect Data Manager Security Configuration Guide provides more information about user roles, including the associated privileges and the tasks that each role can perform.

Data-in-flight encryption PowerProtect Data Manager provides centralized management of backup and restore encryption for application agents. Backup and restore encryption is supported for both centralized and self-service operations where applicable.

You can ensure that the backup and restore content is encrypted when read on the source system, transmitted in encrypted form, and then decrypted before it is saved on the destination storage. This prevents another party from intercepting private data.

PowerProtect Data Manager only supports encryption in-flight for Microsoft SQL Server with Application Direct, Microsoft Exchange Server, Oracle RMAN, File System, SAP HANA, and network attached storage (NAS) workloads. This is a global setting that is applicable to all supported workloads. For File System agents, restore encryption is supported for image-level restore only. For Microsoft SQL Server agents, restore encryption is supported for database-level restore only.

The PowerProtect Data Manager Administration and User Guide and PowerProtect Data Manager Security Configuration Guide provide more information about encryption in-flight, such as how to enable the feature and important considerations to understand before enabling.

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 PowerProtect DD Management Center.

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

NOTE: PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version

6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.

PowerProtect Data Manager for SAP HANA Agent Overview 11

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

4. Add external DD systems or PowerProtect DD Management Center 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.

DBAs should perform this operation.

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 PowerProtect DD Management Center.

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

NOTE: PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version

6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

3. Add external DD systems or PowerProtect DD Management Center to PowerProtect Data Manager.

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

4. Update 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.

DBAs should perform this action.

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.

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.

12 PowerProtect Data Manager for SAP HANA Agent Overview

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 provides information.

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

Install the SAP HANA agent provides information.

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

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

Discover an SAP HANA application host provides information.

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

Add a protection policy for SAP HANA database protection provides information.

2

Enabling the SAP HANA Agent 13

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

About this task

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.

Steps

1. Add a storage system.

Add protection storage provides information.

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

Install the SAP HANA agent provides information.

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

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

Discover an SAP HANA application host provides information.

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

Add a protection policy for SAP HANA database protection 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 DD system.

About this task

Run the ppdmHanaInstall.sh script to install the SAP HANA agent 19.10. 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 install 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, dbappagent1910_linux_x86_64.tar.

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

NOTE: Refer to Chapter 8 in the PowerProtect Data Manager Security Configuration Guide for details on how to verify

the authenticity and integrity of the downloaded package.

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

tar -xvf dbappagent1910_linux_x86_64.tar.gz

14 Enabling the SAP HANA Agent

NOTE: To verify the authenticity and integrity of the RPM files before you install the software, follow the instructions in

the PowerProtect Data Manager Security Configuration Guide.

3. 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=

NOTE: If you specify a hostname or fully qualified domain name (FQDN) with an underscore (_) for the PowerProtect

Data Manager server, then the communication will be done by the system's IP, if provided by the system on registration.

4. 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:

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

rpm -qa | grep "agent"

emcdbappagent-19.10.0.0.0-1.x86_64 powerprotect-agentsvc-19.10.0.0.0-1.x86_64

Update the SAP HANA agent

Learn how to update the SAP HANA agent on the Linux database servers that access the DD system. Use the following method to update from the SAP HANA agent 19.4 or later to the SAP HANA agent version 19.10.

The SAP HANA agent supports a direct update from version 19.4 or later to version 19.10. To update the SAP HANA agent from version 19.4 or later, 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 updated version of the SAP HANA agent, run the following command:

rpm -qa | grep "agent" emcdbappagent-19.10.0.0.0-1.x86_64 powerprotect-agentsvc-19.10.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 DD system.

About this task

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

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.

Enabling the SAP HANA Agent 15

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.

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

Decommission the SAP HANA agent version pre-19.8

Learn how to manually decommission the client with SAP HANA agent version earlier than 19.8.

Steps

1. To identify the SAP HANA instances, run the following command:

/usr/sap/hostctrl/exe/saphostctrl -function ListInstances

2. Locate the ppdmconfig directory for each instance. The directory pathname includes the instance name. For example, instances I1 and I2 have the following ppdmconfig directories:

/usr/sap/I1/SYS/global/ppdmconfig/ /usr/sap/I2/SYS/global/ppdmconfig/

3. In the ppdmconfig directory for each instance, search for the UTL files with names ending in _data_user.utl and _data_auto.utl. For example:

a. In the /usr/sap/I1/SYS/global/ppdmconfig/ directory, run the following commands to search for the UTL files:

ls *_data_user.utl ls *_data_auto.utl

b. In the /usr/sap/I2/SYS/global/ppdmconfig/ directory, run the following commands to search for the UTL files:

ls *_data_user.utl ls *_data_auto.utl

4. Open each UTL file in an editor, add the following comment, and save the file:

# is no longer using this file

NOTE: This comment is added because the UTL files are located on a shared drive and used by multiple nodes.

5. Delete the following files on the local drive:

/opt/dpsapps/dbappagent/saphana/.ppdmintegrated /opt/dpsapps/dbappagent/saphana/sqlite/*

Next steps

After the client is decommissioned, PowerProtect Data Manager deletes the remaining backup copies from the DD system according to the schedule. However, the SAP HANA catalog might still have entries for the deleted backup copies. You must clean up these catalog entries manually by using the SAP HANA Studio or hdbsql command.

After you decommission the SAP HANA client from PowerProtect Data Manager, the agent software binary remains on the client host. You can configure the client host as a stand-alone agent by following the instructions in the PowerProtect Database Application Agent Installation and Administration Guide. The previous .utl files are located under the directory /usr/sap/ /SYS/global/ppdmconfig. Use the configuration files with the auto.utl file name suffix to perform the configuration with SAP HANA Studio.

16 Enabling the SAP HANA Agent

Recommission the SAP HANA agent

Learn how to recommission the client with the SAP HANA agent. NOTE: With a PowerProtect Data Manager version earlier than 19.8, you cannot use the following method to recommission

the client to the PowerProtect Data Manager server. You must uninstall and reinstall the client software and then register

the client with the required PowerProtect Data Manager server.

When the client with the SAP HANA agent has been decommissioned, use one of the following methods to recommission and register the client with the PowerProtect Data Manager server:

To continue with the same version of the client, run the ppdmHanaInstall.sh command to register the client with PowerProtect Data Manager.

NOTE: If you specify a hostname or fully qualified domain name (FQDN) with an underscore (_) for the PowerProtect

Data Manager server, then the communication will be done by the system's IP, if provided by the system on registration.

To update the client and also register the client with PowerProtect Data Manager, run the ppdmHanaInstall.sh -u command.

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.

PowerProtect Data Manager automatically creates the required symbolic link (if it is not present) to the hdbbackint program under the /hana/shared/ /global/hdb/opt directory. This symbolic link creation occurs when you add any assets of a given SID (system ID of the SAP HANA system) to a protection policy and then auto-configuration is triggered.

NOTE: The symbolic link is only created after the successful creation of the protection policy.

You can ensure that the symbolic ink has been created by going to the /hana/shared/ /global/hdb/opt directory and running the ls -l hdbbackint command.

If the protection policy creation fails due to failure of the symbolic link creation, you must complete the following steps to manually create the symbolic link to the hdbbackint program and then trigger the auto-configuration.

1. Run the ln -s command to create the symbolic link. For example:

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

2. Use one of the following methods to trigger the auto-configuration:

Click the set lockbox option on the failed protection policy. Add a new asset with the same SID to the failed protection policy. Re-create the protection policy from scratch.

If you delete the symbolic link for some reason, you must re-create the symbolic link by either of the following methods:

Run the preceding step 1 to manually create the symbolic link. Click the set lockbox option on the protection policy under which the specific SID assets are managed.

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.

Enabling the SAP HANA Agent 17

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

To specify a parallelism value for self-service backups, set the PARALLELISM parameter as described in the following table.

Table 5. 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

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.

Parameter: PARALLELISM

18 Enabling the SAP HANA Agent

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

Specifies the parallelism value for self-service SAP HANA backups. The parallelism value controls the number of parallel streams that the SAP HANA agent uses to write the backup data to DD.

NOTE: For centralized backups, you must set the parallelism value in the PowerProtect Data Manager UI as described in Enable multi-stream backups for SAP HANA protection policy.

Valid values:

1 (default) = The software does not use parallel streams for the self-service backups. 2 or greater = The software uses the specified number of parallel streams for the self-service backups.

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 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 DD system.

Set the DEVICE_HOST parameter to the hostname (as the fully qualified domain name) of the DD 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 DD 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.

NOTE: Ensure that the RETENTION_DAYS parameter is set correctly. When RETENTION_DAYS is set to 0 or is

unspecified, all copies from the database application agent that are discovered in PowerProtect Data Manager will have

the retention value set to 30 days from the backup creation date. For copies from the database application agent that

PowerProtect Data Manager discovers, the retention value is set based on the copy creation date, not on the date when

the copies are discovered.

Results

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

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 DD systems.

Enabling the SAP HANA Agent 19

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

20 Enabling the SAP HANA Agent

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

Enable multi-stream backups for SAP HANA protection policy

To enable multi-stream SAP HANA backups for a centralized protection policy, you can set the parallelism value in the PowerProtect Data Manager UI. The parallelism value controls the number of parallel streams that the SAP HANA agent uses to write the backup data to DD.

The preceding topic describes the SAP HANA parameter parallel_data_backup_backint_channels that you can set in SAP HANA Studio to control the number of data pipes provided by SAP HANA.

NOTE:

As a SAP requirement to enable multiple streams for SAP HANA databases, the protected data size must be 128 GB or

greater. You must also enable the multi-stream SAP HANA backups with PowerProtect Data Manager and configure the

parallel streams in SAP HANA. The SAP HANA documentation provides the latest information about the requirement for

multiple streams.

For self-service backups, you must set the parallelism value through the PARALLELISM parameter as described in Modify

the configuration file parameter settings.

Use the following guidelines to set the parallelism value in the PowerProtect Data Manager UI:

Enabling the SAP HANA Agent 21

Set the parallelism to a value that is equal to or very close to the parallel_data_backup_backint_channels parameter setting. When the two settings are equal or almost equal, the SAP HANA agent can take full advantage of the parallelism provided by SAP HANA.

Set the parallelism to a value that is not more than the maximum number of connections provided by DD. Set the parallelism to a value that is at least 3 less than the maximum number of connections provided by DD. Reserve 3

connections for the log backups. For example, when DD can provide a maximum of 10 connections, set the parallelism value to 7 (10 minus 3).

In the PowerProtect Data Manager UI, perform the following steps to set the parallelism for multi-stream backups:

1. Select Infrastructure > Assets > SAP HANA. 2. Select the SAP HANA asset. 3. Select More Actions > Set Stream Count. 4. Set the stream count for each backup level as a value between 1 and 28 in the Full, Differential, and Incremental fields. 5. Click Save.

Deploy the SAP HANA agent in Microsoft Azure environment

When you deploy the PowerProtect Data Manager with the SAP HANA agent in a Microsoft Azure environment and you use the Azure provided DNS service, you must add the required entry in the /etc/hosts file.

To enable the SAP HANA operations in the Azure environment, add an entry in the /etc/hosts file for the fully qualified domain name (FQDN) of the Azure virtual machine that hosts the SAP HANA agent. For example, add the following type of entry in the /etc/hosts file on the SAP HANA agent host:

10.6.0.12 host123.internal.cloudapp.net host123

If you do not add this type of entry in the /etc/hosts file, the SAP HANA backup and restore operations might fail.

NOTE:

In a multinode environment, ensure that you add the FQDN of every node in the /etc/hosts file on every host. For

example, in an SAP HANA multinode environment with two nodes, N1 and N2:

In the /etc/hosts file on node N1, add the FQDN of both N1 and N2.

In the /etc/hosts file on node N2, add the FQDN of both N1 and N2.

The PowerProtect Data Manager Azure Deployment Guide on Customer Support provides more details about the deployment requirements and procedures in an Azure environment.

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 FQDN or CSV Filename.

If you select Add FQDN, perform the following steps: a. Type the fully qualified domain name (FQDN) for the application agent. b. Specify the date until which the application agent is preapproved. c. Click Save.

22 Enabling the SAP HANA Agent

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:

"ppdm.dell.com" "ppdm2.emc.com" "ppdm.dellemc.com"

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 Allow List, perform the following steps:

NOTE: The Auto Allow List option disabled by default. When Auto Allow List 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 describes how to set the host credentials before you schedule a backup.

View application agent details

Use the Application Agents window in the PowerProtect Data Manager UI to monitor the registration and update status of application agents, and view details for individual application agents.

To view application agent details, from the left navigation pane, select Infrastructure > Application Agents.

Agent Registration Status displays the total number of application agents that are awaiting approval, approved, registered, or rejected.

Agent Update Status displays the total number of application agents that are up-to-date, available, scheduled, in progress, or failed. You can also view information about scheduled updates by clicking the arrow at the end of the row. The Schedules table appears and displays the following information:

Update/Precheck Name Date and Time Schedule Status Host Count Actions

The lower table in the Application Agents window displays information about individual application agents. The following table describes the available information.

Table 6. Application agent information

Column Description

Details Click in the Details column to view details and summary information for the application agent, including registration status.

Host The name of the application agent host.

Enabling the SAP HANA Agent 23

Table 6. Application agent information (continued)

Column Description

IP The IP address of the application agent host.

Registration Status The registration status of the application agent: Waiting Pending Registered Approved Rejected Expired Acceptingcerts

OS The operating system of the application agent host.

Agent Types The application agent type.

Current Version The current version of the application agent.

Update Status The update status of the application agent host: Up to Date Available Scheduled In Progress Failed Not Supported

NOTE: In this release of PowerProtect Data Manager, the update status of application agents is always Up to Date.

Registered Date The date that the application agent was registered in PowerProtect Data Manager.

Created Date The creation date of the application agent.

Filter and sort information

Use the filtering and sorting options to find specific application agents, and to organize the information that you see.

You can filter and sort the information that appears in table columns. Click in the column heading to filter the information in a table column, or click a table column heading to sort that column.

Use the Search field to filter application agents based on a search string. When you type a keyword in the Search field, the PowerProtect Data Manager UI filters the results as you type. To clear the search filter, remove all keywords from the Search field.

24 Enabling the SAP HANA Agent

Managing Storage, Assets, and Protection

Topics:

Add protection storage Enable an asset source Delete an asset source Discover an SAP HANA application host Add and remove the credentials for SAP HANA assets Add a protection policy for SAP HANA database protection Cancel an application agent protection job Extended retention Edit the retention period for backup copies Delete backup copies Enable the SAP HANA agent after hostname change Manage the PowerProtect agent service Manage the cloud tier operations with PowerProtect Data Manager

Add protection storage Add and configure protection storage to use as a target for protection policies. Adding protection storage requires the Administrator role.

Prerequisites

NOTE:

When adding a High Availability PowerProtect DD system, observe the following points:

Do not add the individual active and standby DD systems to PowerProtect Data Manager.

In the Address field, use the hostname that corresponds to the floating IP address of the High Availability PowerProtect

DD system.

The High Availability PowerProtect DD system is verified with the root certificate.

About this task

The PowerProtect Data Manager Administration and User Guide provides more information about protection storage and related concepts:

High availability options Smart Scale system pools, a single interface to a flexible group of pool members Working with protection storage Working with storage units

Steps

1. From the left navigation pane, 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 (PowerProtect DD System or PowerProtect DD Management Center).

For a system pool, select DDMC.

4. To add a High Availability PowerProtect DD system, select the checkbox.

3

Managing Storage, Assets, and Protection 25

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

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

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

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

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

10. 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 More Actions > 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.

Results

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

View the storage unit password

PowerProtect Data Manager provides a script to retrieve the password for a storage unit that you configured as a backup target.

Prerequisites

This task requires the name of the PowerProtect DD MTree where the storage unit resides.

Steps

1. Connect to the PowerProtect Data Manager console as an admin user.

2. Navigate to the /usr/local/brs/puppet/scripts directory.

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

python get_dd_mtree_credential.py MTree-name For example:

python get_dd_mtree_credential.py ppdm-1910-blrv034d018-75914 ==============PowerProtect DD MTree credential============== Full MTree path: /data/col1/ppdm-1910-blrv034d018-75914 User name: ppdm-1910-blrv034d018-75914 Password: IwWXT#DC93m={XV+K ========================================================

26 Managing Storage, Assets, and Protection

Enable an asset source An asset source must be enabled in PowerProtect Data Manager before you can add and register the asset source for the protection of assets.

About this task

Only the Administrator role can manage asset sources.

In some circumstances, the enabling of multiple asset sources is required. For example, a vCenter Server and a Kubernetes cluster asset sources must be enabled for Tanzu Kubernetes guest cluster protection.

There are other circumstances where enabling an asset source is not required, such as the following:

For application agents and other agents such as File System and Storage Direct, an asset source is enabled automatically when you register and approve the agent host. For example, if you have not enabled an Oracle asset source but have registered the application host though the API or the PowerProtect Data Manager user interface, PowerProtect Data Manager automatically enables the Oracle asset source.

When you update to the latest version of PowerProtect Data Manager from an earlier release, any asset sources that were previously enabled appear in the PowerProtect Data Manager user interface. On a new deployment, however, no asset sources are enabled by default.

Steps

1. From the PowerProtect Data Manager user interface, select Infrastructure > Asset Sources, and then click + to reveal the New Asset Source tab.

2. In the pane for the asset source that you want to add, click Enable Source. The Asset Sources window updates to display a tab for the new asset source.

Results

You can now add or approve the asset source for use in PowerProtect Data Manager. For a vCenter server, Kubernetes cluster, SMIS Server, or PowerProtect Cloud Snapshot Manager tenant, select the appropriate tab in this window and click Add. For an application host, select Infrastructure > Application Agents and click Add or Approve as required.

NOTE: Although you can add a Cloud Snapshot Manager tenant to PowerProtect Data Manager in order to view its health,

alerts, and the status of its protection, recovery, and system jobs, you cannot manage the protection of its assets from

PowerProtect Data Manager. To manage the protection of its assets, use Cloud Snapshot Manager. For more information,

see the PowerProtect Cloud Snapshot Manager Online Help.

Disable an asset source

If you enabled an asset source that you no longer require, and the host has not been registered in PowerProtect Data Manager, perform the following steps to disable the asset source.

About this task

NOTE: An asset source cannot be disabled when one or more sources are still registered or there are backup copies of the

source assets. For example, if you registered a vCenter server and created policy backups for the vCenter virtual machines,

then you cannot disable the vCenter asset source. But if you register a vCenter server and then delete it without creating

any backups, you can disable the asset source.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab of the asset source that you want to disable. If no host registration is detected, a red Disable button appears.

2. Click Disable.

Results

PowerProtect Data Manager removes the tab for this asset source.

Managing Storage, Assets, and Protection 27

Delete an asset source If you want to remove an asset source that you no longer require, perform the following steps to delete the asset source in the PowerProtect Data Manager UI.

About this task

Only the Administrator role can manage the asset sources.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab for the type of asset source that you want to delete.

2. Select the asset source name in the asset source list, and then click Delete.

3. At the warning prompt that appears, click Continue. The asset source is deleted from the list.

Results

PowerProtect Data Manager removes the specified asset source in the Asset Sources window.

Any associated assets that are protected by the protection policy are removed from the protection policy and their status is changed to deleted. These assets can be deleted automatically or manually. The PowerProtect Data Manager Administration and User Guide provides details on how to remove assets from PowerProtect Data Manager.

The copies of assets from the asset source are retained (not deleted). You can delete the copies from the copies page, if required.

If the asset source deletion completes with an exception from PowerProtect Data Manager, you must manually decommission the SAP HANA client by running the command ./unregister.sh --full_decommission from the directory where the agent service is installed.

After you decommission the SAP HANA client from PowerProtect Data Manager, the agent software binary remains on the client host. You can configure the client host as a stand-alone agent by following the instructions in the PowerProtect Database Application Agent Installation and Administration Guide. Information about the previous DD setup is located under the directory /usr/sap/ /SYS/global/ppdmconfig.

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 SAP HANA tab.

3. If you are adding an SAP HANA database, select the host entry and click Edit Credentials. The Edit Credential dialog appears.

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.

28 Managing Storage, Assets, and Protection

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. You can initiate a full discovery of assets by selecting the Initiate a Full

Discovery option.

Results

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

Add and remove the credentials for SAP HANA assets Starting with PowerProtect Data Manager 19.7, you can optionally add and remove the credentials for one or more SAP HANA database assets at the same time in the PowerProtect Data Manager UI. The asset-level credentials take precedence over policy-level credentials for SAP HANA databases. Asset-level credentials have the highest precedence.

About this task

NOTE:

You can only add the asset-level credentials when the SAP HANA host agent version is 19.7 or later.

The SAP HANA agent does not support the asset source-level (host) credentials.

Use the following procedure to add or remove the credentials for the SAP HANA database assets.

Steps

1. In the PowerProtect Data Manager UI, select Infrastructure > Assets, and then click the SAP HANA tab.

2. Select one or more assets by clicking the checkbox next to each required asset name.

Managing Storage, Assets, and Protection 29

3. Select More Actions > Set Credential.

4. In the Set Credential dialog box, add or remove the credentials for the selected SAP HANA assets:

To add the credentials for the assets, select the appropriate value from the drop-down list in the Credential field:

To create new credentials, select Create New.

In the Add Credentials dialog box that appears, set the authentication type as either User name/Password or User Key, specify the credential values, and click Save.

To add existing credentials, select the credentials name from the credentials list. To remove the credentials for the assets, select Remove Credentials.

5. Click Save in the Set Credential dialog box.

Results

After you add the credentials by using this procedure, the asset-level credentials are used for the selected assets during SAP HANA centralized backups, overriding the policy-level credentials.

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 create the 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 DD. You must add additional protection policies for a different DD. This requirement pertains to issue PPDM-39456.

Before you perform a backup on a weekly or monthly schedule from the protection policy, ensure that the PowerProtect Data Manager time zone is set to the local time zone. If the PowerProtect Data Manager time zone is not set to the local time zone, the weekly or monthly backup still runs but is triggered based on the PowerProtect Data Manager time zone.

The PowerProtect Data Manager Administration and User Guide provides more information about working with storage units, such as the relationships between storage units and policies, and applicable limitations.

If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The PowerProtect Data Manager Administration and User Guide provides more information.

NOTE: PowerProtect Data Manager does not recognize the SAP HANA System Replication systems. When a replication

site is registered to the same PowerProtect Data Manager as a primary site, PowerProtect Data Manager considers the

replication site assets to be different assets than the primary site assets. When the primary site is down, PowerProtect

Data Manager does not automatically send the backup request to the replication site. In that case, you must manually

change the protection policy to use the replication site assets, which are the new primary site assets.

Steps

1. In the left navigation pane, select Protection > Protection Policies.

The Protection Policies window appears.

2. Click Add.

The Add Policy wizard appears.

3. On the Type page, specify the new protection policy group fields, and then click Next:

NameType a descriptive name for the protection policy, for example, SAP HANA Prod Databases.

NOTE: The name that you specify becomes part of the DD MTree entry.

DescriptionType a short description for the protection policy, for example, SAP HANA Prod Daily Backups.

TypeSelect SAP HANA.

4. On the Purpose page, select from the following options to indicate the purpose of the new protection policy group, and then click Next:

30 Managing Storage, Assets, and Protection

Centralized ProtectionThe backup is triggered according to the schedule. PowerProtect Data Manager manages all protection centrally.

Set CredentialsClick this option to specify the credentials. The Set Credentials dialog appears.

NOTE:

Policy-level credentials are mandatory. Credentials that you set at the asset level take precedence over the

credentials that you set at the protection policy level. Asset-level credentials have the highest precedence.

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, 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 Create New to open the Add Credentials dialog, 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 System Database check box; otherwise, clear the System Database check box.

Self-Service ProtectionYou trigger the backup manually from the SAP HANA server. PowerProtect Data Manager creates a protection policy and manages extra stages.

ExclusionSelect this option when the protection policy contains SAP HANA assets that you want to exclude from data protection operations.

5. On the Assets page, 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.

You can also change the assets view to display all assets discovered by PowerProtect Data Manager or a hierarchical view with the assets in a tree structure underneath the application host. For example, a hierarchical view might be helpful when 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 on the Purpose page, the Summary page appears. Proceed to the final two steps.

If you selected Centralized Protection or Self-Service Protection on the Purpose page, the Objectives page appears for creating the protection policy backup configuration.

7. Complete the required steps for the specified type of protection policy group:

For Centralized Protection:

a. Click Add under Primary Backup.

The Add Primary Backup dialog appears.

b. On the Target pane of the Add Primary Backup dialog, specify the following fields:

Storage NameSelect a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.

Storage UnitSelect whether this protection policy should use a New storage unit on the selected DD system, or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for available capacity and total capacity, for example, testvmpolicy-ppdm-daily-123ab (300 GB/1 TB).

When you select New, a new storage unit in the format policy name hostname unique identifier is created in the storage system upon policy completion, for example, testvmpolicy-ppdm-daily-123cd.

NOTE: The Space field indicates the total amount of space, and the percentage of available space, on the

storage system.

Network InterfaceSelect a network interface from the list, if applicable. Retention LockMove the Retention Lock slider to the right to enable retention locking for these backups on

the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that

Managing Storage, Assets, and Protection 31

the lock can be reverted at any time if necessary. Toggling the Retention Lock slider on or off applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

c. On the Schedules pane of the Add Primary Backup dialog:

i. To schedule the full backup of this protection policy, specify the following fields:

Create a Full backup everySpecify how often to create a full backup. Retain forSpecify the retention period for the backup.

You can extend the retention period for the earliest primary backup copy within the backup schedule by using the Extend Retention feature. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can apply extended retention to keep the full backups taken on Mondays for 10 weeks. Step 8 provides instructions.

NOTE: For database backups, PowerProtect Data Manager chains the dependent backups together. For

example, the incremental or transaction log backups are chained to their base full backup. The backups do

not expire until the last backup in the chain expires. This ensures that all incremental and transaction log

backups are recoverable until they have all expired.

Start and EndThe activity window. Specify a time of day to start the full backup, and a time of day after which backups cannot be started.

NOTE: Any backups started before the End time occurs continue until completion.

ii. To add an incremental or differential backup, click Add backup and then specify the following fields to schedule the backup of this protection policy:

NOTE: When you select this option, the backup chain is reset.

Create a backup every For , select Incremental or Differential from the drop-down list, and then specify the interval at which the backup job runs within the window that you specify. The backup interval depends on the backup interval of the full backup schedule:

If the full backup schedule is hourly or daily, the backup interval of subsequent backup levels can be between 1 and 12 hours or between 1 and 60 minutes.

If the full backup schedule is weekly or monthly, the backup interval of subsequent backup levels can be daily, between 1 and 12 hours, or between 1 and 60 minutes.

NOTE:

An incremental backup backs up the data since the previous full, incremental, or differential backup.

A differential backup backs up the data since the previous full backup.

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

refers to a catalog backup as an AUXILIARY BACKUP TYPE.

Retain forSpecify the retention period for the backup.

CAUTION: If you set a shorter retention period for an incremental or differential backup than for

the corresponding full backup, then data loss might occur and you might be unable to recover

the point-in-time copies.

NOTE: The retention time of the log backup is set to the retention time of the full backup.

Start and EndThe activity window. Specify a time of day to start the backup, and a time of day after which backups cannot be started.

NOTE: Any backups started before the End time occurs continue until completion.

d. Click Save to save the changes and return to the Objectives page.

The Objectives page updates to display the name of the target storage system under Primary Backup.

NOTE: After completing the backup schedule, you can change any schedule details by clicking Edit under

Primary Backup.

For Self-Service Protection:

a. Click Add under Primary Retention.

The Add Primary Retention dialog appears.

32 Managing Storage, Assets, and Protection

b. On the Target pane of the Add Primary Retention dialog, specify the following fields:

Storage NameSelect a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.

Storage UnitSelect whether this protection policy should use a New storage unit on the selected DD system, or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for available capacity and total capacity, for example, testvmpolicy-ppdm-daily-123ab (300 GB/1 TB).

When you select New, a new storage unit in the format policy name hostname unique identifier is created in the storage system upon policy completion, for example, testvmpolicy-ppdm-daily-123cd.

NOTE: The Space field indicates the total amount of space, and the percentage of available space, on the

storage system.

Network InterfaceSelect a network interface from the list, if applicable. Retention LockMove the Retention Lock slider to the right to enable retention locking for these backups on

the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that the lock can be reverted at any time if necessary. Toggling the Retention Lock slider on or off applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

c. On the Retention (Self Service) pane of the Add Primary Retention dialog, change any required retention times.

CAUTION: If you set a shorter retention period for an incremental or differential backup than for

the corresponding full backup, then data loss might occur and you might be unable to recover the

point-in-time copies.

By default, all backup types have the same retention time. To change the retention times for specific backup types, clear Set the same retention time for all backup types and change the Retain For field values as required.

NOTE: The retention time of the log backup is set to the retention time of the full backup.

d. Click Save to save the changes and return to the Objectives page.

The Objectives page updates to display the name of the target storage system under Primary Retention.

NOTE: After completing the backup retention setting, you can change the setting by clicking Edit under

Primary Retention.

8. Optionally, extend the retention period for the earliest primary backup copy within the backup schedule by using the Extend Retention feature:

Extended retention provides more information.

a. Click Extend Retention next to Primary Backup or Primary Retention. An entry for Extend Retention is created below Primary Backup or Primary Retention.

b. Under Extend Retention, click Add. The Add Extended Retention dialog appears. c. Extend the retention of a full primary backup copy everySpecify the preferred recurrence for the extended

retention backup schedule. d. Repeat onDepending on the frequency of the backup schedule, specify the day of the week, the date of the month, or

the date of the year that the extended retention backup will occur. e. Retain forSpecify the retention period for the backup. You can retain an extended retention backup for a maximum of

70 years. f. Click Save to save your changes and return to the Objectives page.

9. Optionally, you can extend the retention of a replicated copy:

a. Click Replicate next to Primary Backup, Primary Retention, or Extend Retention. An entry for Replicate is created to the right of the primary or extended retention backup schedule.

NOTE: PowerProtect Data Manager supports extending the retention of a replicated backup only if the primary

backup already has one or more replication stages. Also, for extending the retention of a replicated backup, you can

only select the DDs that are used by the replication stages based on the primary stage.

For example, if there are 6 DDs available (DD001-DD006), and the primary backup is on DD0001:

Replicate1 based on the primary backup is replicated to DD002

Replicate2 based on the primary backup is replicated to DD003

Extended retention backup is backed up to DD001

Replicate3 based on the extended retention backup must extend the retention of copies on DD002 or DD003.

Managing Storage, Assets, and Protection 33

b. Under Replicate, click Add. The Add Replication dialog appears.

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

storage provides detailed instructions about adding a remote DD system.

c. Complete the schedule details in the Add Replication dialog.

CAUTION: If you set a shorter retention period for an incremental or differential backup than for the

corresponding full backup, then data loss might occur and you might be unable to recover the point-in-

time copies.

By default, all replicated copies have the same retention time. To change the retention times for specific replicated copies, clear Set the same retention time for all replicated copies and click Edit to change the Retain for field values as required.

NOTE: The retention time of the log backup is set to the retention time of the full backup.

Click Save to save the changes and return to the Objectives page.

NOTE: The schedule frequency can be every day, week, month, or x hours for replication of the primary backup,

and every day, week, month, year, or x hours for replication of the extended retention backup. For daily, weekly, and

monthly schedules, the numeric value cannot be modified. For hourly, however, you can edit the numeric value. For

example, if you set Create a Full backup every 4 hours, you can set a value of anywhere 1 to 12 hours.

10. Optionally, add a cloud stage for a primary, replication, or extended retention backup schedule for the purpose of moving backups from DD storage to cloud tier:

a. Click Cloud Tier next to Primary Backup or Extend Retention or, if adding a cloud stage for a replication schedule that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary or extended retention backup schedule, or below the replication schedule.

b. Under the entry for Cloud Tier, click Add. The Add Cloud Tier Backup dialog appears, with summary schedule information for the parent node to indicate whether you are adding this cloud tier stage for the primary backup schedule, the extended retention backup schedule, or the replication schedule.

c. Complete the schedule details in the Add Cloud Tier Backup dialog, and then click Save to save your changes and return to the Objectives page.

Add a cloud tier schedule to a protection policy provides detailed instructions for adding a cloud stage for a primary, replication, or extended retention backup schedule.

NOTE: In order to move a backup or replica to the cloud tier, schedules must have a retention time of 14 days or more.

Also, discovery of a DD system configured with a cloud unit is required.

11. Click Next. The Options page appears.

12. On the Options page, select the additional option if required for the policy:

TroubleshootingSelect this option to enable the debug logs for troubleshooting purposes.

When you set the troubleshooting 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.

To enable logging by the ddbmcon program, create the file /opt/dpsapps/dbappagent/tmp/.ddbmcon.debug.

13. Click Next. The Summary page appears.

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

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

You can monitor and view detailed information in the Jobs window for both centralized and self-service backups and restores of database application agents.

34 Managing Storage, Assets, and Protection

NOTE:

The Cancel and Retry options are not available for self-service jobs that are created by database application agents.

The Jobs window does not display the system database recovery statistics for an MDC configuration or the SDC

recovery statistics because the databases are inaccessible during the restores.

Cancel an application agent protection job Starting with PowerProtect Data Manager 19.9, you can cancel an application agent protection job from the PowerProtect Data Manager UI. The job must be in a queued or running state. The protection job runs for a primary backup that is configured through an application agent protection policy.

About this task

You can perform two types of application agent job cancellations in the PowerProtect Data Manager UI:

Cancellation of a job group that includes one or more asset jobs. Cancellation of an individual asset job.

NOTE:

When a job completes before the cancel request reaches the application host, the status of the canceled job transitions to

either success or failure.

You can cancel many other types of jobs, in addition to protection jobs. The PowerProtect Data Manager Administration

and User Guide provides more information.

Perform the following steps to cancel an application agent protection job in the PowerProtect Data Manager UI.

Steps

1. From the PowerProtect Data Manager UI left navigation pane, select Jobs > Protection Jobs.

The Protection Jobs window opens to display a list of protection jobs and job groups.

2. In the Protection Jobs window, perform the required type of job cancellation:

To cancel a job group:

a. In the Protection Jobs window, select the required job group and click Cancel.

A job group warning prompt appears.

b. Click OK at the prompt.

You can monitor the job group cancellation in the Protection Jobs window. The job group status changes to Canceled when the cancellation of all the asset jobs is complete.

To monitor the cancellation of individual asset jobs within the job group, click the job ID in the Protection Jobs window. The Job ID Summary window opens, where you can view the status of each asset job.

To cancel an asset job:

a. In the Protection Jobs window, click the job ID.

The Job ID Summary window opens to display the job details of the assets in the job group.

b. In the Job ID Summary window, select the required asset job and click Cancel.

A job warning prompt appears.

c. Click OK at the prompt.

You can monitor the asset job cancellation in the Job ID Summary window. The asset job status changes to Canceled when the job cancellation is complete.

NOTE: When the cancel request for a job cannot be completed, an informational alert is displayed.

Managing Storage, Assets, and Protection 35

Extended retention You can extend the retention period for the primary backup copy for long term retention. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can extend the retention period to keep the full backups taken on Mondays for 10 weeks.

Both centralized and self-service protection policies support weekly, monthly, and yearly recurrence schedules to meet the demands of your compliance objectives. For example, you can retain the last full backup containing the last transaction of a fiscal year for 10 years. When you extend the retention period of a backup in a protection policy, you can retain scheduled full backups with a repeating pattern for a specified amount of time.

For example:

Retain full yearly backups that are set to repeat on the first day of January for 5 years. Retain full monthly backups that are set to repeat on the last day of every month for 1 year. Retain full yearly backups that are set to repeat on the third Monday of December for 7 years.

Preferred alternatives

When you define an extended retention stage for a protection policy, you define a set of matching criteria that select preferred backups to retain. If the matching criteria do not identify a matching backup, PowerProtect Data Manager automatically retains the preferred alternative backup according to one of the following methods:

Look-backRetain the last available full backup that was taken before the matching criteria. Look-forwardRetain the next available full backup that was taken after the matching criteria.

For example, consider a situation where you configured a protection policy to retain the daily backup for the last day of the month to extended retention. However, a network issue caused that backup to fail. In this case, look-back matching retains the backup that was taken the previous day, while look-forward matching retains the backup that was taken the following day.

By default, PowerProtect Data Manager uses look-back matching to select the preferred alternative backup. A grace period defines how far PowerProtect Data Manager can look in the configured direction for an alternative backup. If PowerProtect Data Manager cannot find an alternative backup within the grace period, extended retention fails.

You can use the REST API to change the matching method or the grace period for look-forward matching. The PowerProtect Data Manager Public REST API documentation provides instructions. If there are no available backups for the defined matching period, you can change the matching method to a different backup.

For look-forward matching, the next available backup can be an ad-hoc backup or the next scheduled backup.

Selecting backups by weekday

This section applies to centralized protection policies. Self-service protection policies have no primary backup schedule configuration.

When you configure extended retention to match backups by weekday, PowerProtect Data Manager may identify a backup that was taken on one weekday as being taken on a different weekday. This behavior happens where the backup window does not align with the start of the day. PowerProtect Data Manager identifies backups according to the day on which the corresponding backup window started, rather than the start of the backup itself.

For example, consider a backup schedule with an 8:00 p.m. to 6:00 a.m. backup window:

Backups that start at 12:00 a.m. on Sunday and that end at 6:00 a.m. on Sunday are identified as Saturday backups, since the backup window started on Saturday.

Backups that start at 8:01 p.m. on Sunday and that end at 12:00 a.m. on Monday are identified as Sunday backups, since the backup window started on Sunday.

Backups that start at 12:00 a.m. on Monday and that end at 6:00 a.m. on Monday are identified as Sunday backups, since the backup window started on Sunday.

In this example, when you select Sunday backups for extended retention, PowerProtect Data Manager does not retain backups that were taken between 12:00 a.m. and 8:00 p.m. This behavior happens even though the backups occurred on Sunday. Instead, PowerProtect Data Manager selects the first available backup that started after 8:00 p.m. on Sunday for extended retention.

If no backups were created between 8:01 p.m. on Sunday and 6:00 a.m. on Monday, PowerProtect Data Manager retains the next alternative to extended retention. In this example, the alternative was taken after 6:00 a.m. on Monday.

36 Managing Storage, Assets, and Protection

Extended retention backup behavior

When PowerProtect Data Manager identifies a matching backup, automatic extended retention creates a job at the beginning of the backup window for the primary stage. This job remains queued until the end of the backup window and then starts.

The following examples describe the behavior of backups with extended retention for centralized and self-service protection.

Centralized protection

For an hourly primary backup schedule that starts on Sunday at 8:00 p.m. and ends on Monday at 6:00 p.m. with a weekly extended retention schedule that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup starting after 8:00 p.m. on Sunday for long-term retention.

The following diagram illustrates the behavior of backups with extended retention for a configured protection policy. In this example, full daily backups starting at 10:00 p.m. and ending at 6:00 a.m. are kept for 1 week. Full weekly backups are set to repeat every Sunday and are kept for 1 month.

Figure 3. Extend retention backup behavior

Self-service protection

For self-service backups, PowerProtect Data Manager uses a default backup window of 24 hours. For a backup schedule that starts on Sunday at 12:00 p.m and ends on Monday at 12:00 p.m. with a weekly extended retention schedule that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup that is taken between 12:00 p.m. on Sunday and 12:00 p.m. on Monday for long-term retention.

Replication of extended retention backups

You can change the retention time of selected full primary backups in a replication stage by adding a replication stage to the extended retention backup. The rules in the extended retention stage define the selected full primary backups. Review the following information about replication of extended retention backups.

Before you configure replication of extended retention backups, create a replication stage for the primary backup. Configure the replication stage of the extended retention and match this stage with one of the existing replication stages

based on the primary backup. Any changes to a new or existing storage unit in the extended retention replication stage or the replication stage of the primary backup is applied to both replication stages.

The replication stage of extended retention backups only updates the retention time of replicated backup copies and does not create any new backup copies in the replication storage.

Managing Storage, Assets, and Protection 37

Edit the retention period for backup copies You can edit the retention period of one or more backup copies to extend or shorten the amount of time that backups are retained.

About this task

You can edit the retention period for all asset types and backup types.

Steps

1. Select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to edit the retention period. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies from the table, and click Edit Retention.

6. Select one of the following options: To select a calendar date as the expiration date for backups, select Retention Date. To define a fixed retention period in days, weeks, months, or years after the backup is performed, select Retention

Value. For example, you can specify that backups expire after 6 months.

NOTE: When you edit the retention period for copies that are retention locked, you can only extend the retention

period.

7. When satisfied with the changes, click Save. The asset is displayed in the list with the changes. The Retention column displays both the original and new retention periods, and indicates whether the retention period has been extended or shortened.

Delete backup copies In addition to deleting backups upon expiration of the retention period, PowerProtect Data Manager enables you to manually delete backup copies from protection storage.

About this task

If you no longer require a backup copy and the retention lock is not enabled, you can delete backup copies prior to their expiration date.

Starting with PowerProtect Data Manager version 19.6, you can perform a backup copy deletion that deletes only a specified part of a backup copy chain, without impacting the ability to restore other backup copies in the chain. When you select a specific backup copy for deletion, only that backup copy and the backup copies that depend on the selected backup copy are deleted:

When you select to delete a full backup copy, any other backup copies in the chain that depend on the full backup copy are also deleted.

NOTE:

You can delete a full backup copy only if an archive log exists and the previous full backup copy is available. If you delete

a full backup of an incomplete chain, you cannot restore the whole chain until you perform the next full backup.

Deletion of the last remaining full backup from DD does not delete the entry for that backup in the SAP HANA catalog.

This behavior applies to both scheduled deletion and manual deletion operations.

When you select to delete an incremental backup copy, any incremental backup copies that depend on the selected incremental backup copy are also deleted. The whole backup chain is not deleted.

When you select to delete a differential backup copy, any incremental backup copies that depend on the selected differential backup copy are also deleted. The whole backup chain is not deleted.

When you select to delete a log backup copy, any other log backup copies that depend on the selected log backup copy are also deleted. The whole backup chain is not deleted.

38 Managing Storage, Assets, and Protection

NOTE: Deletion of log backups might affect a point-in-time restore that depends on those log backups.

Regarding expired copy deletion for a backup chain, the full backup expires last. The other incremental, differential, and log backups can be expired and deleted earlier:

The full backup expires only when every other backup in the chain has expired. A differential backup expires only when all the incremental backups that depend on it have expired. An incremental backup expires when its retention time expires. A log backup expires only when all the log backups that depend on it have expired.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more copies from the table that you want to delete from the DD system, and then click Delete.

A preview window opens and displays the selected backup copies.

NOTE: For assets with backup copies that are chained together such as SAP HANA databases, the preview window

lists all the backup copies that depend on the specified backup copy. If you delete a backup copy, PowerProtect Data

Manager deletes the specified backup copy and all backup copies that depend on the specified backup copy.

6. For all asset types, you can choose to keep the latest backup copies or delete them. By default, PowerProtect Data Manager keeps the latest backup copies. To delete the latest backup copies, clear the check box next to Include latest copies.

7. To delete the backup copies, in the preview window, click Delete.

NOTE: The delete operation may take a few minutes and cannot be undone.

An informational dialog box opens to confirm the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

NOTE: If the data deletion is successful but the catalog deletion is unsuccessful, then the overall deletion job status

appears as Completed with Exceptions.

When the job completes, the task summary provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC.

An audit log is also generated and provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC. Go to Alerts > Audit Logs to view the audit log.

8. Verify that the copies are deleted successfully from protection storage. If the deletion is successful, the deleted copies no longer appear in the table.

Retry a failed backup copy deletion

If a backup copy is not deleted successfully, you can manually retry the operation.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies with the Deletion Failed status from the table, and then click Delete.

Managing Storage, Assets, and Protection 39

You can also filter and sort the list of backup copies by status in the Copy Status column.

The system displays a warning to confirm you want to delete the selected backup copies.

6. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

7. Verify that the copies are successfully deleted from protection storage. If the deletion is successful, the deleted copies no longer appear in the table.

Export data for deleted backup copies

This option enables you to export results of deleted backup copies to a .csv file so that you can download an Excel file of the data.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to export results of deleted backup copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select one or more protected assets from the table and then select More Actions > Export Deleted Copies.

If you do not select an asset, PowerProtect Data Manager exports the data for deleted backup copies for all assets for the specific asset type.

4. Specify the following fields for the export:

a. Time Range

The default is Last 24 Hours.

b. Copy Status

In order to export data for deleted backup copies, the backup copies must be in one of the following states:

DeletedThe copy is deleted successfully from protection storage, and, if applicable, the agent catalog is deleted successfully from the agent host.

DeletingCopy deletion is in progress. Deletion FailedCopy deletion from protection storage is unsuccessful. Deletion Failed (Agent Catalog)The copy is deleted successfully from protection storage, but is not deleted

from the agent host.

NOTE: This state is not applicable to virtual machine and Kubernetes backup copies.

NOTE: You cannot export data for backup copies that are in an Available state.

5. Click Download. If applicable, the navigation window appears for you to select the location to save the .csv file.

6. Save the .csv file in the desired location and click Save.

Remove backup copies from the PowerProtect Data Manager database

This option enables you to delete the backup copy records from the PowerProtect Data Manager database, but keep the backup copies in protection storage.

About this task

For backup copies that could not be deleted from protection storage, you can remove the backup copies from the PowerProtect Data Manager database. Removing the backup copies from PowerProtect Data Manager does not delete the copies in protection storage.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

40 Managing Storage, Assets, and Protection

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies with the Deletion Failed or Deletion Failed (Agent Catalog) status from the table, and then click Remove from PowerProtect.

For backup copies with the Deletion Failed (Agent Catalog) status, click Remove from PowerProtect to remove the information from PowerProtect Data Manager for any backup copies that were successfully deleted from protection storage but for which the agent catalog was not deleted from the agent host.

The system displays a warning to confirm you want to delete the selected backup copies.

6. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

7. Verify that the copies are deleted from the PowerProtect Data Manager database. If the deletion is successful, the deleted copies no longer appear in the table. The backup copies remain in protection storage.

Enable the SAP HANA agent after hostname change After the hostname of the SAP HANA agent host is changed, you must update the lockbox setting for the protection policy.

About this task

Perform the following steps to enable the SAP HANA agent operations after the hostname is changed.

Steps

1. Re-register the SAP HANA agent with PowerProtect Data Manager by running register.sh from the /opt/dpsapps/ agentsvc directory.

2. Delete the existing ddboost.config* lockbox files in the /opt/dpsapps/dbappagent/saphana/config directory.

3. In the PowerProtect Data Manager UI, configure the lockbox:

a. In the left navigation pane, select Protection > Protection Policies. b. On the Protection Policies page, select the applicable protection policy in the list and click Set Lockbox.

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:

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

Managing Storage, Assets, and Protection 41

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.

NOTE: If you change the DD Boost credentials to include \ in the password, the protection policy configuration will not

be pushed to the agents unless you also select the protection policy from the Protection Policies window, and then

click Set LockBox.

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, Microsoft SQL

Server 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 AIX or 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 on Linux, you can use the following command to start the agent service:

# service agentsvc start

42 Managing Storage, Assets, and Protection

To stop the agent service:

# register.sh --stop

Successfully stopped agent-service.

Alternatively on Linux, 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 on Linux, you can use the following command to obtain the status of the agent service when it is running or not

running:

# service agentsvc status

Register the PowerProtect agent service to a different server address on AIX or 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 AIX or 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.0.1

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 --PowerProtectServer=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.

Managing Storage, Assets, and Protection 43

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 tab for your application agent or file system host. 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 /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

44 Managing Storage, Assets, and Protection

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 Cloud Tier feature to move PowerProtect Data Manager backups from DD 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 DD to the cloud, and you can perform seamless recovery of these backups.

Cloud storage units must be pre-configured on the DD system before they are configured for cloud tier in the PowerProtect Data Manager UI. The DDOS 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 DD system is set up for cloud tiering.

To ensure the success of the cloud tier archival jobs, ensure that the data movement schedule is enabled and set on the DD system.

About this task

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

Cloud tiering happens at 00:00 UTC each day. Depending on your time zone, this time may be within business hours and thus cloud tiering may impact available network bandwidth.

Steps

1. Log in to PowerProtect Data Manager with administrator credentials.

2. From the PowerProtect Data Manager UI, select Protection > Protection Policies, and then click Add.

The Add Policy wizard appears.

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 Objectives page, click Add under Primary Backup if the primary backup schedule is not already created, and fill out the fields in the Target and Schedules panes on the Add Primary Backup dialog.

NOTE: There is no minimum recurrence required for the cloud stage. However, the cloud tier schedule requires a

minimum retention period of 14 days in the Retain for field.

7. Click Cloud Tier next to Primary Backup or Extend Retention or, if adding a cloud stage for a replication schedule that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary or extended retention backup schedule, or below the replication schedule.

8. Under the entry for Cloud Tier, click Add. The Add Cloud Tier Backup dialog appears, with summary schedule information for the parent node. This information indicates whether you are adding this cloud tier stage for the primary backup schedule, the extended retention schedule, or the replication schedule.

9. In the Add Cloud Tier Backup dialog, set the following parameters and then click Save:

Managing Storage, Assets, and Protection 45

Select the appropriate storage unit from the Cloud Target list. For Tier After, set a time of 14 days or more.

The protection policy schedule is now enabled with cloud tiering.

10. Click Next to proceed with the remaining pages of the Add Policy wizard, 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 DD 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 DD 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 DD.

6. Log in to the DD 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 ----------------------------------------- ---------------------- ----------- ------- /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 DDOS Administration Guide provides more details about the cloud tier data movement.

Restore the cloud tier backups to DD

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 DD 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 the cloud tier, and is stored on the active tier of the DD system for a minimum of 14 days, after which the backup may be returned to the cloud, depending on the protection policy.

Recall and re-tier the cloud tier backup

About this task

You can manually recall the backup from the cloud tier and restore the local copy.

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

46 Managing Storage, Assets, and Protection

Steps

1. In the PowerProtect Data Manager UI, go to Infrastructure > Assets and select the SAP HANA tab.

2. Select the required asset, and then click View Copies.

3. Select the backup in the cloud, 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 moves from the cloud tier, and the status changes from Cloud to Local_Recalled. Then you can perform the restore from the SAP HANA host.

4. To re-tier the recalled copy, select the recalled copy and click Re-tier.

5. To change the retention period for the recalled copy, select the recalled copy and click Edit Recall Retention.

Managing Storage, Assets, and Protection 47

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 4. Specifying backup settings in SAP HANA Studio

4

48 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:

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.

For a backup of the primary 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')"

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.

Performing Self-Service Backups of SAP HANA Databases 49

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

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.

50 Performing Self-Service Backups of SAP HANA Databases

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 5. 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 Multitenant database container (Tenant DB)/usr/sap/ /SYS/global/hdb/backint/DB_

Performing Self-Service Backups of SAP HANA Databases 51

Figure 6. Locating the log backups in SAP HANA Studio

4. On the Select Data Backup page, select the database backup for either restore or recovery.

52 Performing Self-Service Backups of SAP HANA Databases

Figure 7. 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 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 53

[SECONDARY_SYSTEM] CLIENT= DDBOOST_USER = DEVICE_HOST = DEVICE_PATH =

For example:

[SECONDARY_SYSTEM] CLIENT=newdb DDBOOST_USER = mypolicy-0662e093dd6b-37247 DEVICE_HOST = 10.118.156.240 DEVICE_PATH = /mypolicy-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 provides details.

Performing alternate host recovery

To enable an alternate host recovery, you must copy the required user configuration file and auto configuration file from the source host to the destination host. If the target asset is in a different protection policy than the source asset, then you must also store the password of the source storage unit in the lockbox on the destination host.

About this task

Modify the configuration file parameter settings provides details about the user configuration file and auto configuration file.

Steps

1. Replicate the directory path of the configuration files on the destination host by using either of the following methods:

Create the directory path on the destination host by creating each subdirectory in the path separately with the same permissions, user, and group as the destination SID. For example, create the following directory path, where the source instance is SID:

/usr/sap/SID/SYS/global/ppdmconfig Create the directory path on the destination host, and assign full permissions. For example:

a. Go to the /usr/sap directory:

cd /usr/sap b. Create the required directory path, where the source instance is SID:

mkdir -p SID/SYS/global/ppdmconfig c. Assign full permissions to the directory path:

chmod -R 777 SID/

2. Copy the user and auto configuration files from the source host to the directory path on the destination host.

3. If the target asset is in a different protection policy than the source asset, store the password of the source storage unit in the lockbox on the destination host:

a. To obtain the password of the source storage unit, run the required script from the PowerProtect Data Manager server. You can fetch the MTree pathname details from the source .utl files:

i. Connect to the PowerProtect Data Manager console as an admin user. ii. Navigate to the /usr/local/brs/puppet/scripts directory.

iii. Obtain the storage unit password by typing the following command:

python get_dd_mtree_credential.py MTree-name

54 Performing Self-Service Backups of SAP HANA Databases

For example:

python get_dd_mtree_credential.py mtree1 ==============PowerProtect DD MTree credential============== Full MTree path: /data/col1/mtree1 User name: user1 Password: pass1 ============================================================

b. Store the source credentials in the lockbox on the destination host:

i. Create a separate file lockbox_reg.utl.

ii. Add the following lines in the lockbox_reg.utl file:

[PRIMARY_SYSTEM] DDBOOST_USER = DEVICE_HOST = DEVICE_PATH = /

iii. To store the source lockbox password, run the command ddbmadmin -P -z lockbox_reg.utl on the destination host. When prompted for the password, enter the password from step 3a.

iv. To store any additional credentials, such as for secondary storage, modify the lockbox_reg.utl file with the following lines and then run the command ddbmadmin -P -z lockbox_reg.utl again:

[PRIMARY_SYSTEM] DDBOOST_USER = DEVICE_HOST = DEVICE_PATH = /

4. When the configuration files are in place and any required credentials are stored, perform the alternate host recovery by using the same steps as for the restore of a 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 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 = mypolicy-0662e093dd6b-37247 DEVICE_HOST = 10.118.156.240 DEVICE_PATH = /mypolicy-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 provides details.

Performing Self-Service Backups of SAP HANA Databases 55

Performing recovery by using the SAP HANA CLI

To perform a recovery of an SAP HANA backup, 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 primary 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 backup of an SAP HANA MDC database:

RECOVER DATABASE FOR DB0 UNTIL TIMESTAMP '2015-08-29 01:25:25' USING DATA PATH ('/usr/sap/AAA/SYS/global/hdb/backint/DB_DB0/') USING LOG PATH ('/usr/sap/AAA/HDB00/ backup/log/DB_DB0') USING BACKUP_ID 1440811502099 CHECK ACCESS USING BACKINT

The SAP HANA Administration Guide provide details about the recover command and procedures in an SAP HANA MDC system.

56 Performing Self-Service Backups of SAP HANA Databases

SAP HANA Best Practices and Troubleshooting

Topics:

Troubleshooting storage units Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname Troubleshooting agent registration Troubleshooting PowerProtect agent service operations Troubleshooting a negative Reduction % value for self-service catalog backup Troubleshooting a missing duration value for centralized backup Troubleshooting a catalog restore issue for assets with the same SID and database name Troubleshooting a backup and delete issue with database authentication type of userkey Troubleshooting a shortened retention issue with SAP HANA full backup Troubleshooting issues after DD change in protection policy Troubleshooting an auto-configuration failure in multinode environment Troubleshooting an issue with onboarded backup copies Troubleshooting a restore of replicated backup from secondary DD Troubleshooting an issue with protection policy in multihost configuration

Troubleshooting storage units Review the following issues related to storage units in PowerProtect Data Manager.

Discrepancy between storage unit capacity reported in PowerProtect Data Manager and DD Virtual Edition

Due to differences in space calculation (physical capacity vs. logical capacity), there is a discrepancy between storage unit capacity reported in PowerProtect Data Manager and DD Virtual Edition. For example, the DD storage unit capacity displayed in the Protection > Storage > Manage Storage window of the PowerProtect Data Manager UI might be greater than the amount displayed in DDVE.

To determine storage unit capacity, use DDVE instead.

Creating storage unit fails when maximum MTree and Users count on DD system reached

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

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

A

SAP HANA Best Practices and Troubleshooting 57

Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname In the PowerProtect Data Manager UI, the Application Agents, Asset Sources, and Protection Jobs windows might list the asset primary hostname as localhost.localdomain instead of the expected FQDN.

The display of localhost.localdomain as the hostname in the PowerProtect Data Manager UI windows might occur when you specify the host's actual FQDN setting for the loopback address in the /etc/hosts file. For example, when you add the following settings in the /etc/hosts file, the first setting value, localhost.localdomain, appears as the hostname in the PowerProtect Data Manager UI windows, instead of the actual FQDN:

127.0.0.1 localhost.localdomain localhost6 localhost6.localdomain6 127.0.0.1 blrv027d233.blr.lab.emc.com blrv027d233

Ensure that the host's actual FQDN is not specified for the loopback address and do not specify hostnames that start with "local" in the /etc/hosts file.

Troubleshooting agent registration Review the following information that is related to troubleshooting agent registration issues.

On Windows, if the agent fails to establish a connection with the PowerProtect Data Manager server, agent registration might fail with the following error message:

During a network connectivity test, the agent is unable to reach the PowerProtect Data Manager server by using ping.

1. If the ping command is blocked in the environment, the agent registration can still complete successfully. Review the agent service logs at INSTALL_DIR\DPSAPPS\AgentService\logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI. 2. If the ping command is not blocked in the environment, the agent registration might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

On Linux or AIX, if the agent fails to establish a connection with the PowerProtect Data Manager server, agent registration might fail with the following error message:

During a network connectivity test, the agent is unable to reach the PowerProtect Data Manager server by using ping and curl.

1. If the ping command is blocked in the environment and curl is not installed, the agent registration can still complete successfully. Review the agent service logs at /opt/dpsapps/agentsvc/logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI. 2. If the ping command is not blocked in the environment, the agent registration might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

If agent registration fails with these error messages, complete the following operation:

1. Use any network packet tracing tool to trace the packets from the agent system to PowerProtect Data Manager. 2. Start the packet tracing between the source IP of the agent system and the destination IP of PowerProtect Data Manager. 3. Start the network traffic between the agent system and PowerProtect Data Manager.

Wait 10 to 15 seconds.

4. Analyze the captured packets. 5. Look for SYN and SYN_ACK packets to see if a 3-way handshake is being performed.

Determine whether the source agent or the destination PowerProtect Data Manager is blocking the connection.

If network traffic is blocked, contact your network security team to resolve the port communication issue.

58 SAP HANA Best Practices and Troubleshooting

Troubleshooting PowerProtect agent service operations To troubleshoot agent service operations, you can check the agent service log file OpAgentSvc- .log, which is created in \logs on Windows and /logs on AIX or Linux. 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.

Troubleshooting a negative Reduction % value for self-service catalog backup When the backup size of a self-service SAP HANA catalog backup is less than a megabyte, a negative Reduction % value might appear for the backup job in the details section of the Job ID Summary window in the PowerProtect Data Manager UI.

You can access the Job ID Summary window by selecting Jobs > Protection Jobs and clicking the job ID next to the job name.

Troubleshooting a missing duration value for centralized backup A centralized SAP HANA backup succeeds, but the backup job duration at the asset level appears as 0 ms on the Step Log tab and Details tab in the PowerProtect Data Manager UI.

The Step Log tab and Details tab appear in the Job ID Summary window, which you can access by selecting Jobs > Protection Jobs and clicking the job ID next to the job name.

As a workaround, view the correct backup duration in the Duration column in the left pane that has a grid format.

SAP HANA Best Practices and Troubleshooting 59

Troubleshooting a catalog restore issue for assets with the same SID and database name When two or more different assets in the same protection policy have the same SID and database name, the catalog restore of one of the assets is affected by the save sets of the other assets.

As a workaround, after successful auto-configuration and before you start any backups, specify a customized CLIENT value in the user configuration file for one or more of these assets.

Troubleshooting a backup and delete issue with database authentication type of userkey With an SAP HANA client version earlier than 19.6 and PowerProtect Data Manager server version later than 19.6, the SAP HANA backup and delete workflow fails for protection policies with the database authentication type of userkey.

Perform either of the following workarounds:

Update the SAP HANA client to the latest supported version. Change the database authentication type to username/password.

Troubleshooting a shortened retention issue with SAP HANA full backup You might encounter an issue with retention of an SAP HANA full backup after the retention time has been shortened.

When you shorten the retention time of an SAP HANA full backup from time T1 to time T2, the retention time value remains at time T1. The full backup is not cleaned up at the expected time T2.

Troubleshooting issues after DD change in protection policy You might encounter specific issues after you change the DD in an SAP HANA protection policy.

After you change the DD in a protection policy:

The PowerProtect Data Manager UI does not display any of the log backups. Scheduled incremental and differential backups are not started until the next scheduled or manual full backup is started. Incremental and differential backups can be started manually from SAP HANA Studio or the command line. The PowerProtect Data Manager UI displays the following status for the incremental and differential backups:

A copy this copy depends on was deleted. Manual deletion of any of these backups does not produce the expected results. Backups between the two storage units can be recovered without errors. Performing restore with dependency chaining or

replication storage provides details.

As a workaround, perform a full backup to the new DD system. Subsequent backups are displayed correctly in the PowerProtect Data Manager UI, and you can properly delete the subsequent user-specified backup copies as expected.

60 SAP HANA Best Practices and Troubleshooting

Troubleshooting an auto-configuration failure in multinode environment PowerProtect Data Manager might not discover a newly created SAP HANA database until the database is operational. As a result, auto-configuration might fail in a multinode SAP HANA environment.

NOTE: Once the database is operational, PowerProtect Data Manager will automatically discover the database in

subsequent scheduled discovery calls.

As a workaround, once the database is operational, you can retry the auto-configuration. You can use one of the following methods to trigger the auto-configuration:

Click the set lockbox option on the protection policy. Add a new asset with the same SID to the protection policy. Re-create the protection policy from scratch.

Troubleshooting an issue with onboarded backup copies You might encounter an issue with onboarded SAP HANA backup copies.

PowerProtect Data Manager does not delete any SAP HANA backup copies that are onboarded but not associated with a protection policy, even when the backup copies are expired.

Troubleshooting a restore of replicated backup from secondary DD You might encounter an issue with the restore of a replicated backup from a secondary DD.

For protection policies that have replication enabled, if you try to restore a replicated backup from a secondary DD system with the default settings in the replica UTL file ( _data_replica.utl), the SAP HANA agent is unable to fetch the catalog.

As a workaround, manually set the CLIENT parameter in the file _data_replica.utl and configure the file path in SAP HANA Studio.

Troubleshooting an issue with protection policy in multihost configuration You might encounter an issue when you create or edit a protection policy in a multihost configuration.

If you create a protection policy for an asset that is spanned across only some, but not all, nodes in a multihost configuration, you might see a complete with failures warning in the user interface.

If you edit an existing protection policy and add the same type of asset, you might see a valid assets are not provid

Manualsnet FAQs

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

Yes, we have the SAP HANA User Guide for Dell PowerProtect 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 User Guide should include all the details that are needed to use a Dell PowerProtect. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell PowerProtect 19.10 Data Manager SAP HANA 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.10 Data Manager SAP HANA 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.10 Data Manager SAP HANA 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.10 Data Manager SAP HANA User Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell PowerProtect 19.10 Data Manager SAP HANA User Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.