Contents

Dell PowerProtect 19.4 Data Manager Oracle RMAN Agent User Guide PDF

1 of 58
1 of 58

Summary of Content for Dell PowerProtect 19.4 Data Manager Oracle RMAN Agent User Guide PDF

PowerProtect Data Manager for Oracle RMAN Agent Version 19.4

User Guide REV 01

March 2020

Copyright 2020 Dell Inc. or its subsidiaries. All rights reserved.

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property

of their respective owners. Published in the USA.

Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com

2 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Preface 5

PowerProtect Data Manager for Oracle RMAN Agent Overview 9 PowerProtect Data Manager overview..............................................................10 Prerequisites..................................................................................................... 10 Firewall and port considerations.........................................................................11 PowerProtect Data Manager new deployment overview....................................11 PowerProtect Data Manager existing deployment overview..............................12

Enabling the Oracle RMAN Agent 15 About the Oracle RMAN agent.......................................................................... 16 Review Oracle data protection and replication requirements.............................16

Prerequisites........................................................................................ 16 Protecting a stand-alone Oracle server............................................................. 16 Protecting Oracle RAC environments................................................................ 17 Install and configure the Oracle RMAN agent.................................................... 17

Install the Oracle RMAN agent..............................................................17 Upgrade the Oracle RMAN agent......................................................... 19 Uninstall the Oracle RMAN agent.........................................................22 Integration with PowerProtect Data Manager software.......................24 Install the PowerProtect Data Manager agent..................................... 25 Uninstall the PowerProtect agent service............................................26 How the Oracle RMAN agent communicates with PowerProtect Data Manager...............................................................................................27 Verify the connectivity from ddbmcon..................................................31 Discover the storage units................................................................... 33

Manage the Oracle application agent................................................................34 Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager........................................................................................................... 35

Support existing Oracle RMAN agent backups with PowerProtect Data Manager...............................................................................................36

Enabling multi-stream backups for Oracle protection policy............................. 36 Enabling app-optimization for storage unit created by Oracle protection policy... 37

Managing Storage, Assets, and Protection 39 Add protection storage .................................................................................... 40

Troubleshooting protection policy for Data Domain storage unit.......... 41 Viewing the DD Boost storage unit password....................................... 41

Discover an Oracle application host...................................................................41 Add a protection policy for Oracle database protection.................................... 42 Manage the PowerProtect agent service..........................................................46

About the PowerProtect agent service................................................ 46 Start, stop, or obtain the status of the PowerProtect agent service.... 47 Troubleshoot the PowerProtect agent service operations................... 48 Register the PowerProtect agent service to a different server address... 49 Recovering the PowerProtect agent service from a disaster............... 49

Chapter 1

Chapter 2

Chapter 3

CONTENTS

PowerProtect Data Manager for Oracle RMAN Agent User Guide 3

Manage the cloud tier operations with PowerProtect Data Manager................50 Add a cloud tier schedule to a protection policy....................................51 Tier the PowerProtect Data Manager backups from Data Domain to the cloud.................................................................................................... 52 Restore the cloud tier backups to Data Domain................................... 52

Performing Self-Service Backups of Oracle Databases 55 Performing self-service backups of Oracle databases.......................................56 Restore an Oracle application host....................................................................57

Chapter 4

Contents

4 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Preface

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

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

Note: This document was accurate at publication time. To ensure that you are using the latest version of this document, go to the Support website https://www.dell.com/support.

Note: References to Data Domain systems in this documentation, in the UI, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems.

Purpose

This document describes how to configure and use the PowerProtect Data Manager with the Oracle RMAN agent to back up and restore Oracle Server.

Audience

This document is intended for the host system administrator who configures and uses the PowerProtect Data Manager with the Oracle RMAN agent to back up and restore Oracle Server.

Revision history

The following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

01 March 31, 2020 Initial release of this document for PowerProtect Data Manager 19.4.

Compatibility information

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

Related documentation

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

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

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

l PowerProtect Data Manager Security Configuration Guide Contains security information.

l PowerProtect Data Manager Cloud Disaster Recovery Administration and User Guide Describes how to deploy Cloud DR, protect VMs in the AWS or Azure cloud, and run recovery operations.

PowerProtect Data Manager for Oracle RMAN Agent User Guide 5

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

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

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

Special notice conventions that are used in this document

The following conventions are used for special notices:

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

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

Typographical conventions

The following type style conventions are used in this document:

Table 2 Style conventions

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

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

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, file name extensions, prompts, and syntax

l 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

l https://www.dell.com/support

l https://community.emc.com

Preface

6 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Where to get support

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

To access a product-specific page:

1. Go to https://www.dell.com/support.

2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase

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

To search the Knowledgebase:

1. Go to https://www.dell.com/support.

2. On the Support tab, click Knowledge Base.

3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by typing a product name in the search box, and then selecting the product from the list that appears.

Live chat

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

1. Go to https://www.dell.com/support.

2. On the Support tab, click Contact Support.

3. On the Contact Information page, click the relevant support, and then proceed.

Service requests

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

1. Go to https://www.dell.com/support.

2. On the Support tab, click Service Requests.

Note: To create a service request, you must have a valid support agreement. For details about either an account or obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to https://www.dell.com/support.

2. On the Support tab, click Service Requests.

3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities

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

How to provide feedback

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

Preface

PowerProtect Data Manager for Oracle RMAN Agent User Guide 7

Preface

8 PowerProtect Data Manager for Oracle RMAN Agent User Guide

CHAPTER 1

PowerProtect Data Manager for Oracle RMAN Agent Overview

l PowerProtect Data Manager overview.................................................................................. 10 l Prerequisites..........................................................................................................................10 l Firewall and port considerations............................................................................................. 11 l PowerProtect Data Manager new deployment overview........................................................ 11 l PowerProtect Data Manager existing deployment overview.................................................. 12

PowerProtect Data Manager for Oracle RMAN Agent User Guide 9

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

l Automate the configuration of the application agent backup policy and protection storage settings.

l Create a catalog of backups that are produced by the application agent, and then monitor that catalog data to determine if retention policies are being adhered to.

l Manage the life cycle of backups that are created by the application agentthat is, ensure that the backups are marked for garbage collection based on the rules of the retention policy.

PowerProtect Data Manager does not change the way that the application agent works. DBAs create the backups and perform the restores.

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

Requirements:

l A list of hosts that write backups to DD systems is available.

l DD OS version 6.1 or later and the DD Management Console (DDMC). All models of DD systems are supported.

l Application agent 19.4 or earlier.

l License: A trial license is provided with the PowerProtect Data Manager software. DPS Applications, Backup, and Enterprise customers can contact Dell EMC Licensing Support for assistance with a permanent PowerProtect Data Manager license.

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

l The PowerProtect Data Manager 19.4 download file requires the following:

n ESXi version 6.0, 6.5, 6.7, or 7.0.

n 8 vCPUs, 18 GB RAM, one 100 GB disk, and one 500 GB disk.

n The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI.

n TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.

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

n 10 CPU cores

n 18 GB of RAM for PowerProtect Data Manager

n Five disks with the following capacities:

Disk 1100 GB

Disk 2500 GB

Disk 310 GB

PowerProtect Data Manager for Oracle RMAN Agent Overview

10 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Disk 410 GB

Disk 55 GB

n One 1-GB NIC

Firewall and port considerations

Table 3 PowerProtect Data Manager port requirements

Description Communication Port

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

22 TCP/UDP

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

8443 TCP

UI redirect Inbound only 80 TCP

443

LDAP Outbound only 389 TCP/UDP

636 TCP

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

3009 TCPStorage Direct and DD system

5989 TCPSMI-S

443 TCPXtremIO

7225 TCPRecoverPoint

PowerProtect Data Manager agent

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

7000 TCP

Embedded VM Direct service

Outbound 9090 TCP

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

Procedure

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

The account team can help with backup storage design.

2. Install DD Management Center (DDMC).

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

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

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

PowerProtect Data Manager for Oracle RMAN Agent Overview

PowerProtect Data Manager for Oracle RMAN Agent User Guide 11

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 "Enabling" chapter.

This operation should be performed by DBAs.

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

7. After the approval of agent requests, PowerProtect Data Manager must run a discovery operation to discover the assets.

The PowerProtect Data Manager Administration and User Guide provides information.

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

You must add credentials to the database so that PowerProtect Data Manager can access the database and create backups. The PowerProtect Data Manager Administration and User Guide provides instructions.

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

9. Add Service Level Objectives to the protection policy to verify that the protected assets meet the Service Level Agreements (SLAs).

The PowerProtect Data Manager Administration and User Guide provides instructions.

Configuration is complete.

10. Monitor protection compliance in the PowerProtect Data Manager dashboard.

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.

Procedure

1. Install DD Management Center (DDMC).

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

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

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

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

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

This operation should be performed by DBAs.

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

6. After the approval of agent requests, PowerProtect Data Manager must run a discovery operation to discover the assets.

The PowerProtect Data Manager Administration and User Guide provides information.

PowerProtect Data Manager for Oracle RMAN Agent Overview

12 PowerProtect Data Manager for Oracle RMAN Agent User Guide

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

You must add credentials to the database so that PowerProtect Data Manager can access the database and create backups. The PowerProtect Data Manager Administration and User Guide provides instructions.

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

8. Add Service Level Objectives to the protection policy to verify that the protected assets meet the Service Level Agreements (SLAs).

The PowerProtect Data Manager Administration and User Guide provides instructions.

Configuration is complete.

9. Monitor protection compliance in the PowerProtect Data Manager dashboard.

PowerProtect Data Manager for Oracle RMAN Agent Overview

PowerProtect Data Manager for Oracle RMAN Agent User Guide 13

PowerProtect Data Manager for Oracle RMAN Agent Overview

14 PowerProtect Data Manager for Oracle RMAN Agent User Guide

CHAPTER 2

Enabling the Oracle RMAN Agent

This section includes the following topics:

l About the Oracle RMAN agent...............................................................................................16 l Review Oracle data protection and replication requirements................................................. 16 l Protecting a stand-alone Oracle server..................................................................................16 l Protecting Oracle RAC environments.....................................................................................17 l Install and configure the Oracle RMAN agent.........................................................................17 l Manage the Oracle application agent.................................................................................... 34 l Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager........... 35 l Enabling multi-stream backups for Oracle protection policy..................................................36 l Enabling app-optimization for storage unit created by Oracle protection policy.................... 37

PowerProtect Data Manager for Oracle RMAN Agent User Guide 15

About the Oracle RMAN agent The Oracle RMAN agent enables an application administrator to protect and recover the Oracle data on the application host. PowerProtect Data Manager integrates with the Oracle RMAN agent to check and monitor backup compliance against protection policies. PowerProtect Data Manager also enables central scheduling for backups.

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

Note: PowerProtect Data Manager supports the coexistence of the Oracle RMAN agent and the File System agent on Linux.

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

Review Oracle data protection and replication requirements PowerProtect Data Manager can manage and monitor data protection and replication for Oracle assets through integration with the Oracle RMAN agent.

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

Prerequisites Ensure that you meet the required prerequisites before you add an Oracle asset.

Verify that the environment meets the following requirements:

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

l Ensure that the Oracle host and the PowerProtect Data Manager network can see and resolve each other.

l Ensure that port 7000 is open on the Oracle host.

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

Procedure

1. Add a storage system.

Add protection storage on page 40 provides information.

2. Install the Oracle RMAN agent on the Oracle server host.

Install the Oracle RMAN agent on page 17 provides information.

3. Add or approve the Oracle RMAN agent in PowerProtect Data Manager.

Manage the Oracle application agent on page 34 provides information.

Enabling the Oracle RMAN Agent

16 PowerProtect Data Manager for Oracle RMAN Agent User Guide

4. Discover and add the credentials for the Oracle application host.

Discover an Oracle application host on page 41 provides information.

5. Create a protection policy to protect the Oracle server host.

Add a protection policy for Oracle database protection on page 42 provides information.

Protecting Oracle RAC environments Learn how to configure protection of Oracle RAC environments.

About this task

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

Procedure

1. Add a storage system.

Add protection storage on page 40 provides information.

2. Install the Oracle RMAN agent on each Oracle RAC node.

Install the Oracle RMAN agent on page 17 provides information.

3. Add or approve the Oracle RMAN agent on each Oracle RAC node.

Manage the Oracle application agent on page 34 provides information.

4. Discover and add the credentials for each Oracle application host.

Discover an Oracle application host on page 41 provides information.

5. Create a protection policy group to protect the Oracle RAC nodes.

Add a protection policy for Oracle database protection on page 42 provides information.

Install and configure the Oracle RMAN agent Learn how to install and configure the Oracle RMAN agent.

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

About this task

Note: You must use the Oracle RMAN agent version 19.4 with PowerProtect Data Manager version 19.4. If a previous version of Oracle RMAN agent is installed, you must upgrade to version 19.4.

Run the install.sh script to install the Oracle RMAN agent 19.4 or to upgrade from an earlier version of the Oracle RMAN agent. The script installs the Oracle RMAN agent in a user-specified directory or in the default installation directory, $HOME/opt/dpsapps/rmanagent.

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

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

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 17

Note: In a RAC system, you must install the Oracle RMAN agent and PowerProtect Data Manager agent on each node.

Procedure

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from Dashboard > System Settings.

b. Select the Oracle RMAN agent download package, ddrman194_linux_x86_64.tar.

c. Download the package to the Oracle server host on Linux.

Note: As an alternative, you can download the Oracle RMAN agent package from the Support website at https://support.emc.com.

2. Change the ownership of the tar file to the oracle user by running the following command:

chown -R oracle:oinstall ddrman194_linux_x86_64.tar

Uncompress the downloaded tar file using the oracle user by running the following command:

tar -xvf ddrman194_linux_x86_64.tar.gz

3. Ensure that no backups are running. Stop the RMAN processes before you install the Oracle RMAN agent.

4. As one of the system's Oracle users (recommended), run the install.sh script:

install.sh

5. The install.sh script displays the following prompt:

Do you want to install under the default installation directory /home/ oracle/opt/dpsapps/rmanagent? (y or n)

Type the appropriate value:

l To install in the default directory, type y.

l To install in a non-default directory that already exists, type n.

The script then prompts you to enter the installation directory pathname:

Enter the full pathname of the installation destination:

Type the pathname of an already created installation directory.

Note: The user-specified installation directory must be a directory that is created specifically for the Oracle RMAN agent 19.4 installation, and must not be the ORACLE_HOME directory. The complete directory pathname must be specified, without a slash (/) at the end.

The install.sh script displays the following output:

The lib directory /home/oracle/opt/dpsapps/rmanagent/lib is created. The config directory /home/oracle/opt/dpsapps/rmanagent/config is created.

Enabling the Oracle RMAN Agent

18 PowerProtect Data Manager for Oracle RMAN Agent User Guide

The bin directory /home/oracle/opt/dpsapps/rmanagent/bin is created. The breadcrumbs directory /home/oracle/opt/dpsapps/rmanagent/breadcrumbs is created. Installing the Oracle RMAN agent. Copying the lockbox libraries to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying libddobk.so to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying libDDBoost.so to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying ddutil to /home/oracle/opt/dpsapps/rmanagent/bin/. Copying the dependency libraries to /home/oracle/opt/dpsapps/rmanagent/ lib/. Copying the configuration file to /home/oracle/opt/dpsapps/rmanagent/ config/. Copying the ddbmcon program to /home/oracle/opt/dpsapps/rmanagent/bin/. Creating the lockbox. Successfully installed the Oracle RMAN agent.

6. If ORACLE_HOME is set in the environment, the install.sh script displays the following type of prompt. Type n, as required for a new installation:

The Oracle RMAN agent library, libddobk.so, does not exist in /space/ oracle/app/oracle/product/12.1.0/dbhome_1/lib. Do you want to update settings in /space/oracle/app/oracle/product/ 12.1.0/dbhome_1 directory so that RMAN scripts from previous installation can be reused? (y or n) n

The installation script exits.

7. To verify the installed version of Oracle RMAN agent, run the following command:

/home/oracle/opt/dpsapps/rmanagent/bin/ddutil -i

Upgrade the Oracle RMAN agent An upgrade of the Oracle RMAN agent to version 19.4 requires additional steps when the pre-19.4 Oracle RMAN agent is integrated with Enterprise Copy Data Management (eCDM). In that case, you must also upgrade the eCDM integration to a PowerProtect Data Manager integration.

About this task

Note: If Oracle RMAN agent versions earlier than version 4.0 are installed, refer to the latest PowerProtect Oracle RMAN Agent Administration Guide for information about how to upgrade the pre-4.0 versions.

Procedure

1. To obtain details about the Data Domain hosts and storage units that eCDM or PowerProtect has registered with the Oracle RMAN agent, run the ddutil -s command on the Oracle RMAN agent client host. For example:

ddutil -s

Data Domain Hostname: 10.36.52.98

FC Service Name: None FC Service Enabled: false

Storage Unit: PLC-PROTECTION-1557475568457

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 19

User: PLC-PROTECTION-1557475568457 Type: PRIMARY

2. If the pre-19.4 Oracle RMAN agent is integrated with eCDM, perform the following steps to upgrade the eCDM software to PowerProtect Data Manager software:

a. In the eCDM UI menu, select Upgrade under System Settings.

b. To upload the upgrade package, click Upload Package.

The following message appears when the package has been uploaded:

Package uploaded successfully.

c. To run the upgrade process, click Perform Upgrade.

d. When prompted to verify the certificate details and confirm the upgrade, click Yes.

The following message appears when each package component has been upgraded:

State: UPGRADED

3. To stop the eCDM agent on the Oracle RMAN agent client host, run the following command:

/usr/local/ecdm/ecdm-agent/bin/ecdm-agent.bin stop

The following message appears when the eCDM agent is stopped:

eCDM Agent daemon control 'stop' is successful

4. Upgrade the Oracle RMAN agent by using either of the following methods:

l Interactive upgrade method:

To upgrade the Oracle RMAN agent by using the interactive method that prompts for input, follow the instructions in Install the Oracle RMAN agent on page 17.

For example, when you run the install.sh script to perform the interactive upgrade, the following type of prompts and output appear:

install.sh Do you want to install under the default installation directory /home/ oracle/opt/dpsapps/rmanagent? (y or n) y An Oracle RMAN agent already exists. Do you want to continue the installation? (y or n) y Installing the Oracle RMAN agent. Copying the lockbox libraries to /home/oracle/opt/dpsapps/rmanagent/ lib/. Copying libddobk.so to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying libDDBoost.so to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying ddutil to /home/oracle/opt/dpsapps/rmanagent/bin/. Copying the dependency libraries to /home/oracle/opt/dpsapps/ rmanagent/lib/. Copying the ddbmcon program to /home/oracle/opt/dpsapps/rmanagent/ bin/. Upgrading the lockbox. Import operation is not needed because the lockbox version is already updated. As a PowerProtect Data Manager user, update the existing Data Domain details? (y or n) y Data Domain server name: 10.36.52.98

Enabling the Oracle RMAN Agent

20 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Data Domain Storage Unit name: PLC-PROTECTION-1557475568457 Successfully updated the DD Boost credentials in the lockbox. As a PowerProtect Data Manager user, update the existing Data Domain details? (y or n) n Updated the lockbox. Successfully installed the Oracle RMAN agent. Do you want to uninstall the previous Oracle RMAN agent in /u01/app/ oracle/product/12.1.0/dbhome_1 directory? (y or n) y The Oracle RMAN agent is uninstalled. Do you want to update settings in /u01/app/oracle/product/12.1.0/ dbhome_1 directory so that RMAN scripts from previous installation can be reused? (y or n) y Updating settings in the /u01/app/oracle/product/12.1.0/dbhome_1 directory. Settings are updated. Installation is completed.

l Silent upgrade method:

To upgrade the Oracle RMAN agent by using the silent upgrade method that does not prompt for input, follow these steps:

a. Set the three environment variables as follows:

export RMAN_AGENT_HOME=<$RMAN_AGENT_HOME> export RMAN_AGENT_INSTALL_OPTIONS=OVERWRITE export DD_CREDENTIALS_UPDATE=TRUE

b. Run the following upgrade command, including the two -a command-line options that specify the Data Domain server and storage unit credentials to be updated. If the credentials of more than one server or storage unit must be updated, specify a comma-separated list of the server names and storage unit names:

install.sh -a DD_SERVER_NAME={[, ,...]} -a DD_STORAGE_UNIT={[, ,...]}

5. If you upgraded the eCDM software to PowerProtect Data Manager software in step 2, perform the following steps to uninstall the eCDM agent and install the PowerProtect agent:

a. To uninstall the eCDM agent, run the rpm -e ecdm-agent-3.0.0-15_1.x86_64 command. For example:

rpm -e ecdm-agent-3.0.0-15_1.x86_64 Uninstalling ecdm-agent... ecdmagent.service - eCDM Agent Service Loaded: loaded (/etc/systemd/system/ecdmagent.service; enabled) :

b. To install the PowerProtect agent service, run the rpm -ivh powerprotect- agentsvc-19.4.0.0.0-1.x86_64.rpm command. For example:

rpm -ivh powerprotect-agentsvc-19.4.0.0.0-1.x86_64.rpm warning: powerprotect-agentsvc-19.4.0.0.0-1.x86_64.rpm: Header V4 RSA/ SHA1 Signature, key ID c5dfe03d: NOKEY Preparing... ################################# [100%] Updating / installing... 1:powerprotect-agentsvc-19.4.0.0.0-################################# [100%]

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 21

c. To complete the required addons configuration and registration with PowerProtect Data Manager, run the configureAddOn.sh script from the RMAN agent addon directory / home/oracle/opt/dpsapps/rmanagent/addon. For example:

/home/oracle/opt/dpsapps/rmanagent/addon/configureAddOn.sh Enter the Oracle RMAN agent home pathname. Press ENTER for the default home pathname /home/oracle/opt/dpsapps/rmanagent: Creating the /opt/dpsapps/agentsvc/AddOns directory. Creating the /opt/dpsapps/agentsvc/AddOns/ D2B24128_9482_44D2_8723_6D211DB49BFB directory. Copying the D2B24128_9482_44D2_8723_6D211DB49BFB.zip file. Copying the addon.cfg file. Enter PowerProtect Data Manager IP Address: 10.63.102.140 Do you want to set the default retention time? (y or n) y Provide the default retention time as the number of days: 2 Setting RETENTION_TIME=2. Allow SYSDBA access for RMAN agent? (y or n) y Setting SYSADMIN_ACCESS=TRUE. Addons configuration is completed.

6. To register or re-register the Oracle RMAN agent with the new PowerProtect Data Manager server, run the register.sh script from the agent service directory /opt/ dpsapps/agentsvc. For example:

/opt/dpsapps/agentsvc/register.sh Enter the PowerProtect Data Manager IP address or hostname: 10.63.102.138 Warning: Changing IP of PowerProtect Server from 10.118.159.140 to 10.63.102.138 Started agent service with PID - 20795

7. To complete the upgrade, manually approve the Oracle RMAN agent from the PowerProtect Data Manager server. Manage the Oracle application agent on page 34 provides information.

Uninstall the Oracle RMAN agent Run the uninstall.sh script to uninstall the Oracle RMAN agent 19.4. You can also run the script to uninstall a previous version of the Oracle RMAN agent.

About this task

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

You can run the uninstall.sh script manually or automatically. To enable the automatic operation, you must set the appropriate environment variables as listed in Table 4 on page 23:

l When the variables are not set, the script runs manually and prompts for the required values.

l When the variables are set, the script runs automatically and performs the uninstallation according to the environment variable settings.

Enabling the Oracle RMAN Agent

22 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Table 4 Environment variables for uninstallation of Oracle RMAN agent

Environment variable Description Default and valid values

RMAN_AGENT_HOME Specifies the installation directory for the Oracle RMAN agent.

l /home/oracle1/opt/ dpsapps/rmanagent (default).

l Valid complete pathname of the directory for installation of Oracle RMAN agent.

Note: The directory pathname must not end with a slash (/).

RMAN_AGENT_UNINSTALL_OPTIONS Specifies the software components to uninstall.

l Undefined (default).

l NONE or noneSpecifies to keep the Oracle RMAN agent software, and not perform the uninstallation.

l BINARY or binarySpecifies to uninstall the software, but not the lockbox or the configuration file.

l FULL or fullSpecifies to uninstall the software, lockbox, and configuration file.

Note: It is not necessary to uninstall the Oracle RMAN agent for an upgrade. An existing Oracle RMAN agent is overwritten during an upgrade.

Perform the following steps to uninstall the Oracle RMAN agent.

Procedure

1. Ensure that backup and restore operations are not in progress when you uninstall the Oracle RMAN agent.

2. If you want the uninstallation script to run automatically, ensure that RMAN_AGENT_HOME and RMAN_AGENT_UNINSTALL_OPTIONS are set as described in Table 4 on page 23.

To verify the value of an environment variable, run the echo command. For example:

# echo $RMAN_AGENT_HOME

/home/oracle/opt/dpsapps/rmanagent

To set an environment variable, run the export command. For example:

# export RMAN_AGENT_HOME=/opt/dpsapps/rmanagent

3. As an Oracle user, run the uninstall.sh script:

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 23

Note: It is recommended that you set the RMAN_AGENT_HOME environment variable before you run the uninstall.sh script.

# ./uninstall.sh

4. If the script does not run automatically, type the appropriate values at the prompts:

a. When prompted, specify whether you want to enter the directory pathname of the Oracle RMAN agent installation:

An installation directory pathname is not specified. Do you want to enter the installation pathname? (y or n)

If you type y, then the script prompts for the installation location. Type the complete pathname of the installation location, without a slash (/) at the end.

b. When prompted, specify whether you want the lockbox and configuration file to be removed:

Do you want to remove the lockbox and the configuration file? (y or n)

c. If the script detects an additional installation of Oracle RMAN agent, the script prompts whether to uninstall that version. You can specify to keep or uninstall the software.

The script removes the Oracle RMAN agent software and prints the following message:

The Oracle RMAN agent is uninstalled from the /home/oracle/opt/dpsapps/ rmanagent directory. Uninstallation is completed.

Integration with PowerProtect Data Manager software This procedure enables the integration of Oracle RMAN agent with PowerProtect Data Manager, which enables PowerProtect Data Manager to monitor, manage, and analyze the Oracle RMAN agent backups on Linux.

Note: PowerProtect Data Manager can create and manage replication copies based on the protection policies.

PowerProtect Data Manager performs these operations whether the backup is created by the DBA or by the PowerProtect Data Manager centralized backup scheduler.

Because PowerProtect Data Manager controls the replication, when the Oracle RMAN agent is deployed with PowerProtect Data Manager, the following self-service replication operations are disabled:

l Creation of multiple backup copies with the RMAN BACKUP COPIES command.

l MTree replication to create backup copies on a secondary Data Domain system.

You can restore from replicated copies of backups that were performed with a previous version of Oracle RMAN agent.

When you perform a self-service backup managed by PowerProtect Data Manager, the PowerProtect Data Manager protection policy settings for the given database will override the

Enabling the Oracle RMAN Agent

24 PowerProtect Data Manager for Oracle RMAN Agent User Guide

target protection storage settings specified in the RMAN backup script, including the Data Domain server hostname and storage unit name.

1. Install and register the required PowerProtect Data Manager agent service on the Oracle RMAN agent host as described in Install the PowerProtect Data Manager agent on page 25.

2. Enable the ddbmcon program to connect to the local Oracle databases during PowerProtect Data Manager operations. How the Oracle RMAN agent communicates with PowerProtect Data Manager on page 27 provides details.

3. Verify the connectivity from the ddbmcon program to the Oracle database by using the ddutil program with the required options. Verify the connectivity from ddbmcon on page 31 provides details.

4. Ensure that the /etc/oratab file contains a complete list of all the Oracle SIDs on the host. The Oracle RMAN agent uses the information in the file to discover the database resources on the system, which enables the PowerProtect Data Manager operations.

In an Oracle RAC environment, ensure that the /etc/oratab file contains an entry for each database instance. Manually add any database instance entries that do not yet exist in the file. Each entry must have the following format:

: :

Note: Only with Oracle RAC 12.2 or later, each entry can have the following format:

: :

As recommended by Oracle, ensure that all the archived redo logs in the Oracle RAC environment reside on shared storage or a shared cluster file system that is accessible from all the RAC nodes. Select one node to be the backup node and set the IS_RAC_BACKUP_NODE parameter accordingly, as described in Configuration file requirements for connection to local databases on page 27.

Install the PowerProtect Data Manager agent You must install the PowerProtect Data Manager agent as the root user on the Oracle RMAN host so that the Oracle RMAN agent can communicate with the PowerProtect Data Manager server.

About this task

Note: In a RAC system, you must install the Oracle RMAN agent and PowerProtect Data Manager agent on each node.

Procedure

1. Log in as the root user on the Oracle RMAN host.

2. To install the PowerProtect agent service, run the rpm -ivh powerprotect- agentsvc-19.4.0.0.0-1.x86_64.rpm command. For example:

rpm -ivh powerprotect-agentsvc-19.4.0.0.0-1.x86_64.rpm warning: powerprotect-agentsvc-19.4.0.0.0-1.x86_64.rpm: Header V4 RSA/ SHA1 Signature, key ID c5dfe03d: NOKEY Preparing... ################################# [100%] Updating / installing... 1:powerprotect-agentsvc-19.4.0.0.0-################################# [100%]

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 25

3. To complete the required addons configuration and registration with PowerProtect Data Manager, run the configureAddOn.sh script from the RMAN agent addon directory / home/oracle/opt/dpsapps/rmanagent/addon. For example:

/home/oracle/opt/dpsapps/rmanagent/addon/configureAddOn.sh Enter the Oracle RMAN agent home pathname. Press ENTER for the default home pathname /home/oracle/opt/dpsapps/rmanagent: Creating the /opt/dpsapps/agentsvc/AddOns directory. Creating the /opt/dpsapps/agentsvc/AddOns/ D2B24128_9482_44D2_8723_6D211DB49BFB directory. Copying the D2B24128_9482_44D2_8723_6D211DB49BFB.zip file. Copying the addon.cfg file. Enter PowerProtect Data Manager IP Address: 10.63.102.140 Do you want to set the default retention time? (y or n) y Provide the default retention time as the number of days: 2 Setting RETENTION_TIME=2. Allow SYSDBA access for RMAN agent? (y or n) y Setting SYSADMIN_ACCESS=TRUE. Addons configuration is completed.

4. To register or re-register the Oracle RMAN agent with the new PowerProtect Data Manager server, run the register.sh script from the agent service directory /opt/ dpsapps/agentsvc. For example:

/opt/dpsapps/agentsvc/register.sh Enter the PowerProtect Data Manager IP address or hostname: 10.63.102.138 Warning: Changing IP of PowerProtect Server from 10.118.159.140 to 10.63.102.138 Started agent service with PID - 20795

Uninstall the PowerProtect agent service You must uninstall the PowerProtect agent service as the root user on the Oracle RMAN host.

Procedure

1. Log in as the root user on the Oracle RMAN host.

2. To delete the Oracle addon files in the agent service addon directory, run the unConfigureAddOn.sh script from the RMAN agent addon directory /home/ oracle/opt/dpsapps/rmanagent/addon directory. For example:

/home/oracle/opt/dpsapps/rmanagent/addon/unConfigureAddOn.sh Enter the Oracle RMAN agent home pathname. Press ENTER for the default home pathname /home/oracle/opt/dpsapps/rmanagent:

3. Query the Oracle client for an installed agent service by running the following command:

# rpm -qa | grep agent

powerprotect-agentsvc-19.4.0.0.0-1.x86_64

Enabling the Oracle RMAN Agent

26 PowerProtect Data Manager for Oracle RMAN Agent User Guide

4. If the agent service exists on the Oracle client, uninstall the agent service by running the following command:

# rpm -e powerprotect-agentsvc-19.4.0.0.0-1.x86_64

How the Oracle RMAN agent communicates with PowerProtect Data Manager The Oracle RMAN agent program ddbmcon handles all communication between the Oracle RMAN agent and PowerProtect Data Manager.

Note: You cannot run the ddbmcon program manually. The program is only run by the PowerProtect Data Manager agent.

When the ddbmcon program performs discovery, backup, or deletion operations, it connects to the Oracle database. The following authentication methods are supported:

1. Database authenticationThe ddbmcon program first tries to connect to the Oracle database instance by using database authentication. The program tries to use the database administrator username and password to connect to the database instance.

2. Oracle wallet authenticationIf database authentication fails or is not enabled, the ddbmcon program tries to connect by using Oracle wallet authentication. The program tries to use the parameter settings from the configuration file to connect to the database instance.

3. Operating system authenticationIf Oracle wallet authentication also fails or is not enabled, the ddbmcon program tries to connect by using operating system authentication. The program tries to change the real process user ID to the Oracle installation user ID, to connect to the database instance.

The ddbmcon program tries all these authentication methods for each Oracle database instance. The program reports a connection error if it cannot connect to the database instance by using any of these methods. If one of these methods succeeds, the ddbmcon program ignores the other authentication methods and proceeds to retrieve the information as used by the PowerProtect Data Manager.

Ensure that you enable one of these three authentication methods for the ddbmcon program. For maximum ease of use, it is recommended that you enable the operating system authentication method. Both the database and Oracle wallet authentication methods require additional configuration steps on the Oracle host and parameter settings in the configuration file rman_agent.cfg.

Configuration file requirements for connection to local databases As required for certain ddbmcon program operations, you must complete the required configuration settings to enable the authentication method that you want the program to use. Each authentication method has its own requirements for parameter settings in the configuration file.

During the Oracle RMAN agent installation, the configuration file template, rman_agent.cfg, is installed in the $RMAN_AGENT_HOME/config directory. To enable a particular authentication method, you must set the required parameters in the rman_agent.cfg configuration file.

The configuration file template includes the following information.

# ############################################################################# # # rman_agent.cfg # # All rights reserved.

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 27

# # Oracle RMAN agent 19.4 # # This template is designed to help users to configure the authentication of # RMAN agent. Check the product administration guide for a complete list of # all the supported parameters and rules for editing the configuration file. # # Make a copy of this file before making any modifications. # To enable a parameter, uncomment or add the parameter in the file and # specify its value. # # ############################################################################# # # ############################################################################# # Oracle parameters. # There can be repetitive sections of Oracle parameters. The Oracle database # the parameters belong to is described in the section name: SID_name. The # name here must be replaced by the SID of the database. # ############################################################################# [SID_name] # ORACLE_SERVICE = # ORACLE_USER = # ORACLE_OS_USER = # TNS_ADMIN = # RMAN_CATALOG_SERVICE = # RMAN_CATALOG_USER = # IS_RAC_BACKUP_NODE =

To set a particular parameter in the configuration file, such as ORACLE_SERVICE, remove the # symbol at the start of the parameter line and add the parameter value after the equal sign (=).

You can complete the following settings in the configuration file:

l SID_name is mandatory for each authentication method when you set any parameters in the file for a particular system ID (SID). [SID_name] (for example, [SID_orcl]) must appear on a separate line before all the parameter settings for the SID:

n For Oracle 10g, 11g, and non-RAC systems, SID_name must match the SID in the /etc/ oratab file.

n For Oracle 12c RAC systems, SID_name must match the SID that runs on the local host.

Note: Each Oracle SID on the same system requires its own entries in the configuration file. You must use the same configuration file for all the Oracle SIDs.

l ORACLE_SERVICE is mandatory for database authentication and Oracle wallet authentication. Specifies the TNS or Net service name of the Oracle database.

l ORACLE_USER is mandatory for database authentication only. Specifies the database username as saved in the lockbox.

l ORACLE_OS_USER is mandatory for operating system authentication when the username for connection is different than the ORACLE_OSDBA_USER username. Specifies the operating system user that will connect to the Oracle database for operating system authentication. When this parameter is set, ORACLE_OSDBA_USER is ignored.

l TNS_ADMIN is mandatory for database authentication and Oracle wallet authentication when the Oracle Net configuration files including tnsnames.ora reside in a non-default directory. Specifies the pathname of the non-default directory. When this parameter is not set, the system default directory $ORACLE_HOME/network is used.

l RMAN_CATALOG_SERVICE is mandatory when an RMAN catalog is used for backup or recovery of the database. Specifies the TNS name of the RMAN catalog.

l RMAN_CATALOG_USER is mandatory for each authentication method when an RMAN catalog is used. Specifies the catalog database username as saved in the lockbox.

Enabling the Oracle RMAN Agent

28 PowerProtect Data Manager for Oracle RMAN Agent User Guide

l IS_RAC_BACKUP_NODE is highly recommended in an Oracle RAC environment only. In the Oracle RAC environment, select a single node to be the backup node and set this parameter to TRUE to specify that the SID_name node is the backup node. Set this parameter to FALSE when the SID_name node is not the backup node.

The following topics provide more details about the configuration requirements of each particular authentication method.

Authentication requirements The following subtopics provide details about the three authentication methods that the ddbmcon program supports.

Database authentication requirements

Before the ddbmcon program can use database authentication to connect to an Oracle database, you must complete the required configuration to enable the database authentication method. Database authentication can be used to connect to a target database or catalog database.

To enable the database authentication method, run the ddutil command with the appropriate options to store the database administrator credentials in the lockbox:

ddutil -C -a USER_TYPE=DATABASE_ADMIN [-a DATABASE_SIDS= ] [-a USERNAME= ]

Note: If the lockbox does not exist when you run the ddutil command, the command creates the lockbox in the default directory.

The options -C and -a USER_TYPE=DATABASE_ADMIN are mandatory. If you do not specify the other -a options, -a DATABASE_SIDS= and -a USERNAME= , the command prompts for the database SIDs and administrator username. The command always prompts for the administrator password.

If multiple databases exist on the system and all use the same administrator username and password, you can add the credentials for all the databases to the lockbox with the same ddutil command. You must specify the database SIDs as a comma-separated list. For example:

ddutil -C -a USER_TYPE=DATABASE_ADMIN

'RMAN_AGENT_HOME' is retrieved from ddutil runtime location as '/home/ oracle/opt/dpsapps/rmanagent' Database SIDs (to a maximum of 19 SIDs): orcl1,orcl2,orcl3,orcl4,orcl5,db1,db2 Database administrator name: SYS Password: xxxxx Re-enter password: xxxxx Successfully set the Oracle database administrator credentials in the lockbox. Enabling the Oracle RMAN application agent.

The following example command includes all the supported -a options:

ddutil -C -a USER_TYPE=DATABASE_ADMIN -a DATABASE_SIDS=orcl1,orcl2,orcl3,orcl4,orcl5,db1,db2 -a USERNAME=SYS

'RMAN_AGENT_HOME' is retrieved from ddutil runtime location as '/home/ oracle/opt/dpsapps/rmanagent'

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 29

Password: xxxxx Re-enter password: xxxxx Successfully set the Oracle database administrator credentials in the lockbox.

To enable the database authentication method, you must also set the following parameters for each required SID in the rman_agent.cfg configuration file:

l Set ORACLE_SERVICE and ORACLE_USER. ORACLE_USER must match the username that is saved in the lockbox.

l If the Oracle Net configuration files reside in a non-default directory, set TNS_ADMIN to the directory pathname.

l If an RMAN catalog is used, set RMAN_CATALOG_SERVICE and RMAN_CATALOG_USER.

For example, the rman_agent.cfg configuration file includes the following settings to enable the database authentication for the database SID orcl:

[SID_orcl] ORACLE_SERVICE = DBFS ORACLE_USER = ORACLE1 TNS_ADMIN = /home/oracle/wallet

To confirm that database authentication is enabled, you can log in as the root user and run the ddutil commands as described in Verify the connectivity from ddbmcon on page 31.

Oracle wallet authentication requirements

Before the ddbmcon program can use Oracle wallet authentication to connect to an Oracle database, you must complete the required configuration to enable the Oracle wallet authentication method. Oracle wallet authentication can be used to connect to a target database or catalog database.

To enable the Oracle wallet authentication method, you must set the following parameters for each required SID in the rman_agent.cfg configuration file:

l Set ORACLE_SERVICE to the TNS or Net service name. For example, set the parameter to the value DBFS.

l If the Oracle Net configuration files reside in a non-default directory, set TNS_ADMIN to the directory pathname.

l If an RMAN catalog is used, set RMAN_CATALOG_SERVICE and RMAN_CATALOG_USER.

For example, the rman_agent.cfg configuration file includes the following settings to enable the Oracle wallet authentication for the database SID orcl:

[SID_orcl] ORACLE_SERVICE = DBFS TNS_ADMIN = /home/oracle/

To confirm that Oracle wallet authentication is enabled, you can log in as the root user and run the ddutil commands as described in Verify the connectivity from ddbmcon on page 31.

Operating system authentication requirements

The operating system authentication method can only be used on systems with a single Oracle home or with multiple Oracle homes that were all installed by the same user. During authentication, the ddbmcon program either obtains the Oracle installation user ID or reads the operating system username from the rman_agent.cfg configuration file. Then the program changes the real user of the process to the Oracle installation user or the operating system user, to connect to the database instance.

Enabling the Oracle RMAN Agent

30 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Note: The operating system user specified in the configuration file takes precedence over the Oracle installation user.

When the ddbmcon program uses the authentication method on a system with multiple Oracle homes that were installed by different users, the program returns information for only one Oracle home. The program returns a connection error for the other Oracle homes.

During the backup discovery, the ddbmcon program tries to use the operating system authentication method only after the database authentication and Oracle wallet authentication methods have both failed to connect to the Oracle database.

To enable the operating system authentication method, you must set the following parameters for each required SID in the rman_agent.cfg configuration file:

l If the username to be used for the connection is different than ORACLE_OSDBA_USER, set ORACLE_OS_USER.

l If an RMAN catalog is used, set RMAN_CATALOG_SERVICE and RMAN_CATALOG_USER.

For example, the rman_agent.cfg configuration file includes the following settings to enable the operating system authentication for the database SID orcl:

[SID_orcl] ORACLE_OS_USER = ORACLE1

To confirm that operating system authentication is enabled, you can log in as the root user and run the ddutil commands as described in Verify the connectivity from ddbmcon on page 31.

Verify the connectivity from ddbmcon You can run the ddutil command as the root user with the appropriate -v option to verify the connectivity from the ddbmcon program to the Oracle database.

The following subtopics describe the three supported levels of verification with the ddutil -v command:

l System verification

l Asset verification

l RMAN verification

System verification

To perform the system verification, run the ddutil -v system command as the root user.

The ddutil -v system command verifies the connectivity to the Oracle instances.

For example, the following ddutil -v system command lists one Oracle instance and the authentication type as operating system user:

ddutil -v system

Reported application instance: Version: 12.2.0.1.0 Install location: /u01/app/oracle/product/12.2.0/dbhome_1 Database identifier: testdb Oracle SID: testdb Authentication type: operating system user

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 31

Asset verification

To perform the asset verification, run the ddutil -v asset command as the root user. The command verifies the ability to read the Oracle database objects, and provides similar output to the system verification command.

For example, the following ddutil -v asset command lists one Oracle instance, the database type, and the storage capacity:

ddutil -v asset

Reported application instance: Version: 12.2.0.1.0 Install location: /u01/app/oracle/product/12.2.0/dbhome_1 Database identifier: testdb Oracle SID: testdb Database type: ORACLE_NON_CDB

Storage Capacity: 1530920960

RMAN verification

To perform the RMAN verification, run the ddutil -v rman command as the root user. This verification is required only if you use an RMAN catalog. Database authentication or Oracle wallet authentication can be used to connect to an RMAN catalog. (Operating system authentication cannot be used with the RMAN catalog.)

The ddutil -v rman command tests whether the ddbmcon program can connect to the target database and catalog database through an RMAN script, as required to perform an active deletion of Oracle backups.

Note: To enable an active deletion through RMAN, the Data Domain credential must be stored in the lockbox.

The ddutil -v rman command displays the following three sections of output for the RMAN verification:

1. Target database connection information:

l Authentication type, listed as operating system user, Oracle database user, or Oracle wallet user.

l For operating system authentication, only the operating system user is listed.

l For database authentication, the operating system user, Oracle service, and database user are listed.

l For Oracle wallet authentication, the Oracle service and TNS_ADMIN value are listed.

2. Catalog database connection information:

l Authentication method, listed as Oracle database user or Oracle wallet user.

l For database authentication, the database service and database user are listed.

l For Oracle wallet authentication, the Oracle service and TNS_ADMIN value are listed.

3. Output of the RMAN script, which shows the connection information and any error messages.

Enabling the Oracle RMAN Agent

32 PowerProtect Data Manager for Oracle RMAN Agent User Guide

For example, the following ddutil -v rman command displays the three sections of output, showing that the database authentication method is used for both the target database and catalog database:

ddutil -v rman

'RMAN_AGENT_HOME' is retrieved from ddutil runtime location as '/opt/dpsapps/ rmanagent'. The ORACLE_HOME environment variable could not be retrieved. Reported RMAN instance connection: Oracle SID: CER

Target database authentication: Oracle database user Oracle OS dba user: oracer Oracle service: CER Oracle database user: system

RMAN catalog authentication: Oracle database user Catalog database service: SAP.world Catalog database user: catowner

RMAN output:

Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 15 14:30:15 2017 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. RMAN> connect ******** 2> 3> connect ********* 4> 5> connected to target database: CER (DBID=1040017416) connected to recovery catalog database Recovery Manager complete

Discover the storage units When a PowerProtect Data Manager protection policy is created, the PowerProtect Data Manager server assigns its storage unit to the Oracle databases that are protected by the protection policy. Both the manual backups and scheduled backups of these Oracle databases are sent to this storage unit.

To display the storage units and their assigned databases on the Oracle RMAN agent host, run the ddutil -s command.

Note: The ddutil -s command might display a storage unit type of "secondary." However, you cannot perform a backup to a secondary device. You can only restore from a secondary device.

For example:

ddutil -s

Data Domain Hostname: 10.36.52.98

FC Service Name: None FC Service Enabled: false

Storage Unit: RMAN87-SS-CT-blrv35a029-a7bc3

User: RMAN87-SS-CT-blrv35a029-a7bc3 Type: PRIMARY

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 33

Storage Unit: RMAN87-SS-CT-blrv35b179-c9de5

User: RMAN87-SS-CT-blrv35b179-c9de5 Type: PRIMARY

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

Procedure

1. Select Infrastructure > Application Agents.

The Application Agents window appears.

Note: If the PowerProtect agent service was able to register during the installation, the Oracle 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:

l Add IP Address or CSV Filename.

This process is also called Whitelisting.

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

a. Type the IP Address for the application agent.

b. Specify the date until which the application agent is preapproved.

c. Click Save.

n If you select CSV Filename, perform the following steps:

a. Click the Choose File icon.

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

"10.25.115.113" "10.25.115.112" "10.25.115.145"

The Explorer window appears.

b. Select the .csv file, and then click Open.

The file appears in the Application/FS Agents window.

c. Select the date until which the application agent is preapproved.

d. Click Save.

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

Note: The Auto whitelist option disabled by default. When Auto whitelist is enabled, all preapproved application agents are automatically approved.

Enabling the Oracle RMAN Agent

34 PowerProtect Data Manager for Oracle RMAN Agent User Guide

a. Select the required application agent.

b. Click one of the following options:

n Approve

n Reject

n Edit, then make the required changes.

n Remove

c. Click Save.

After you finish

Discover an Oracle application host on page 41 describes how to set the host credentials before you schedule a backup.

Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager

The Oracle RMAN agent 19.1 introduced the capability to onboard existing stand-alone deployments, including their existing backups, to PowerProtect Data Manager. Existing backups are Oracle RMAN agent backups that you performed before you have integrated the Oracle RMAN agent with the PowerProtect Data Manager software and added an asset to a PowerProtect Data Manager protection policy.

Note: Retention lock is not supported for discovered existing backups in PowerProtect Data Manager.

Onboarding of DD Boost-over-FC backups is not supported.

With the onboarding capability, PowerProtect Data Manager provides the following centralized features:

l Visibility of both existing backups and any new self-service or PowerProtect Data Manager policy-driven backups of onboarded assets.

l Retention management of all backups. The retention time of existing backups can be set during the PowerProtect Data Manager registration.

l Automatic configuration of target protection storage based on the PowerProtect Data Manager protection policies that are used for your database.

l All the other functionality that is provided for PowerProtect Data Manager protection policies.

Self-service operations use the Data Domain backup host and storage unit managed by PowerProtect Data Manager

With Oracle RMAN agent 19.1 or later, you can provide the Data Domain backup host and storage unit in the RMAN scripts. After you use PowerProtect Data Manager to add an asset to the protection policy, you might want to keep using the existing RMAN scripts instead of or along with scheduling backups through PowerProtect Data Manager.

When you create a protection policy, the PowerProtect Data Manager software creates a storage unit on the specified Data Domain backup host that is managed by PowerProtect Data Manager. All subsequent backups will go to this new storage unit. This implementation overrides the backup host and storage unit information that is provided in the script with the backup host and storage unit information that is provided by PowerProtect Data Manager.

Setting and reporting the retention time for existing backups

With Oracle RMAN Agent 19.1 or later, any backups that are performed before you add an asset to a PowerProtect Data Manager protection policy are considered existing backups. You can set the

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 35

retention time for existing backups during registration with the PowerProtect Data Manager server by using the register.sh script. This retention time is reported to PowerProtect Data Manager during backup discovery.

Note: If a retention time is not specified for existing backups, the backup copies in PowerProtect Data Manager will never expire.

Support existing Oracle RMAN agent backups with PowerProtect Data Manager Learn how to support existing Oracle RMAN agent backups.

Procedure

1. Upgrade the Oracle RMAN agent on the Oracle server host.

Upgrade the Oracle RMAN agent on page 19 provides information.

2. Register and approve the Oracle RMAN agent in PowerProtect Data Manager.

Manage the Oracle application agent on page 34 provides information.

After a few minutes of approving the Oracle agent, all the old backup copies start to be discovered. Depending on the number of backups, the discovery and subsequent visibility of the backups in PowerProtect Data Manager can take some time. The retention time of the discovered existing backup copies will be equal to the retention time set in the protection policy plus 14 days and 1 day.

3. Discover and add the credentials for the Oracle RMAN agent host.

Discover an Oracle application host on page 41 provides information.

4. Create a protection policy to protect the Oracle RMAN agent host.

Add a protection policy for Oracle database protection on page 42 provides information.

The first backup after onboarding must be a full backup:

l The first centralized backup is automatically promoted to a full backup.

l For the first self-service backup after onboarding, the Oracle DBA must run a full backup script.

Note: You cannot perform a backup to a secondary Data Domain device. You can only restore from a secondary Data Domain device.

5. Perform a self-service Application Direct backup of Oracle databases. Onboarded assets can be part of either a centralized or self-service protection policy.

Performing self-service backups of Oracle databases on page 56 provides information.

Enabling multi-stream backups for Oracle protection policy The PARALLELISM parameter setting in the configuration file rman_agent.cfg enables the multi-streams feature for Oracle RMAN agent backups that are created through a PowerProtect Data Manager protection policy. With this parameter setting, you can override the number of backup channels from the Oracle RMAN agent client side.

To enable the multi-streams feature, specify the number of backup channels in the PARALLELISM parameter in the $RMAN_AGENT_HOME/config/rman_agent.cfg file on the Oracle RMAN agent host.

Enabling the Oracle RMAN Agent

36 PowerProtect Data Manager for Oracle RMAN Agent User Guide

For example, when you set the PARALLELISM parameter value to 6, the Oracle RMAN agent backups run with 6 channels:

PARALLELISM = 6

Enabling app-optimization for storage unit created by Oracle protection policy

Perform the following steps to enable app-optimization for a storage unit that is created by a PowerProtect Data Manager protection policy for Oracle RMAN agent backups on a PowerProtect X400 appliance.

Procedure

1. To identify the storage unit and PowerProtect X400 server IP address, run the ./ddutil -s command in the $RMAN_AGENT_HOME/bin directory on the Oracle RMAN agent host.

2. To enable the app-optimization, run the following commands on the Virtual Cluster Manager (VCM) node:

mtree option set app-optimized-compression oracle1 mtree /data/col1/orcl-16k-x4-m-re-07- sip1-1dfae

mtree option show mtree /data/col1/orcl-16k-x4-m-re-07-sip1-1dfae

Name Option Value ----------------------------------------- ------------------------- ------- /data/col1/orcl-16k-x4-m-re-07-sip1-1dfae app-optimized-compression oracle1

Enabling the Oracle RMAN Agent

PowerProtect Data Manager for Oracle RMAN Agent User Guide 37

Enabling the Oracle RMAN Agent

38 PowerProtect Data Manager for Oracle RMAN Agent User Guide

CHAPTER 3

Managing Storage, Assets, and Protection

This chapter includes the following topics:

l Add protection storage .........................................................................................................40 l Discover an Oracle application host....................................................................................... 41 l Add a protection policy for Oracle database protection.........................................................42 l Manage the PowerProtect agent service.............................................................................. 46 l Manage the cloud tier operations with PowerProtect Data Manager.................................... 50

PowerProtect Data Manager for Oracle RMAN Agent User Guide 39

Add protection storage About this task

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

l Data Domain Management Center

l External Data Domain system

Note: References to Data Domain systems in this documentation, in the UI, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems.

Procedure

1. Select Infrastructure > Storage.

The Storage window appears.

2. In the Protection Storage tab, click Add.

3. In the Add Storage dialog box, select a storage system (Data Domain System, Data Domain Management Center).

Note: If using the Storage Direct agent to move snapshot backups from a VMAX storage array to a Data Domain system, you do not need to add a Data Domain Management Center.

4. Specify the storage system attributes:

a. In the Name field, specify a storage name.

b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address.

If you specify a virtual machine for the storage name, use the FQDN.

c. In the Port field, specify the port for SSL communication.

5. Under Add Credentials, if you have already configured Data Domain credentials that are common across Data Domain systems, select an existing keychain from the Select Keychain list. Alternatively, you can add new credentials, and then click Save .

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

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

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

Note: 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 storage data while the discovery is in progress.

PowerProtect Data Manager can add up to three assets of the same type simultaneously and up to 10 assets simultaneously.

8. In the Storage window, click Discover to refresh the window with any newly discovered storage systems.

When a discovery completes successfully, the Status column updates to OK.

Managing Storage, Assets, and Protection

40 PowerProtect Data Manager for Oracle RMAN Agent User Guide

9. To modify a storage system location:

a. In the Storage window, select the storage system from the table.

b. Click Set Location.

The Set Location window appears.

c. Click Location > Add.

The Add Location window appears.

d. In the Name field, type a location name for the asset, and click Save.

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

Results

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

Troubleshooting protection policy for Data Domain storage unit

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

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

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

Before you begin

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

Procedure

1. SSH to the PowerProtect Data Manager appliance as the admin user.

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

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

./get_dd_mtree_credential.py PLC-PROTECTION-1551667983302

Discover an Oracle 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 Oracle database so that PowerProtect Data Manager can access the database to create backups.

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 41

About this task

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

Procedure

1. Select Infrastructure > Asset Sources.

The Asset Sources window appears.

2. Select the App/File System Host tab.

3. If you are adding an Oracle database, select the host entry and click Edit Credentials.

The Edit Credentials dialog appears.

4. If you are adding credentials for an Oracle database, ensure that you specify CredentialType as tnsName or FileName for DBUSER, RMAN, and WALLET users. If you do not specify tnsName or FileName Credential Type for DBUSER, RMAN, and WALLET, backups fail. The OS user does not require tnsName or FileName CredentialType.

Authentication requirements on page 29 provides details about the authentication requirements for an Oracle database.

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

5. Click Save.

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

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

Note: Click Discover at any time if any additions or other changes to your Asset Sources have taken place outside of the PowerProtect Data Manager environment.

Results

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

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

Before you begin

l When you create protection policies for RAC databases, ensure that all nodes in the RAC environment are powered on and registered at the time of the protection policy creation. Otherwise the protection might fail.

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

l For Oracle Instance Group assets, ensure that the maximum length of the hostname plus storage unit is 59. There are no special character limitations. For example, oracle_database_department_123_accounts.

Managing Storage, Assets, and Protection

42 PowerProtect Data Manager for Oracle RMAN Agent User Guide

Procedure

1. Select Protection > Protection Policies.

The Protection Policy window appears.

2. Click Add.

The Add Policy wizard appears.

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

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

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

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

c. In theType field, select Oracle database.

d. Click Next.

The Purpose page appears.

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

a. The type of protection policies group.

For an Oracle database, you can select from three types:

l To use PowerProtect Data Manager to manage all protection centrally, click Centralized Protection.

l To use Oracle to create local backup protection, click Self-Service Protection. PowerProtect Data Manager creates a protection policy and manages extra stages.

l If there are Oracle assets within the protection policy that you plan to exclude from data protection operations, click Exclusion.

b. To specify the credentials, click Set Credentials. You can specify new credentials or select existing credentials from the list.

Authentication requirements on page 29 provides details about the authentication requirements for an Oracle database.

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

c. Click Next.

The Assets page appears.

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

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

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 43

6. Click Next.

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

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

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

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

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

7. Click + Backup.

The Add Primary Backup dialog box appears.

8. Specify the backup schedule fields:

l For Centralized Protection:

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

Recurrence relates to Start Time and End Time fields.

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

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

The interval should be between 1 hour to 12 hours.

c. To create an incremental cumulative backup, click Incremental Cumulative, and then specify the interval in minutes.

d. To create an incremental differential backup, click Incremental Differential, and then specify the interval in minutes.

e. To create a log, click Log, and then specify the interval in minutes.

f. In the Keep For field, specify the retention time.

g. In the Start Time field, specify the time when new backups are initiated in this policy.

h. In the End Time field, specify the time after which no new backups are initiated in this policy. It does not mean that any policy that is running is stopped.

i. Click OK. Note: When a new asset is added to a protection policy during a scheduled backup window, the backup starts right away. However, if an asset is added to a protection policy outside of the scheduled backup window, the backup does not start until the next time that backups are configured to run.

If a new asset is added to a protection policy that has a weekly or monthly backup schedule and the current time is within the scheduled Start Time and End Time, the backup runs right away, regardless of the date. If the current time is not within the scheduled Start Time and End Time, the backup does not start until the next time that backups are configured to run.

The Schedule page updates with the newly added backup schedule.

l For Self-Service Protection:

a. In the Keep For field, specify the retention time.

b. Click OK.

Managing Storage, Assets, and Protection

44 PowerProtect Data Manager for Oracle RMAN Agent User Guide

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

9. To reduce the number of backups when daily, weekly, and/or monthly backups coincide, turn on auto promotion:

a. Select the check box next to the added schedule and click + Backup.

b. Complete the schedule details in the Add Promotion Backup dialog box, and then click OK.

10. To replicate these backups to a remote Data Domain system:

a. Select the check box next to the added schedule, and then click Replicate.

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

Note: To enable replication, ensure that you add a remote Data Domain system as the replication location. Add protection storage on page 40 provides detailed instructions about adding a remote Data Domain system.

11. Select the check box next to the added schedule.

When you select the check box, the SLA, Storage Name, and Network interface lists are enabled for selection.

12. From the SLA list, select an existing service level agreement that you want to apply to this schedule, or click Add to create a SLA within the Add Backup Service Level Agreement window.

13. From the Storage Name list:

l Select the backup destination from the list of existing Data Domain systems.

l To add a system, select Add, and complete the details in the Storage Target window.

When you select the destination storage, the Space field updates with the available capacity on the system.

14. From the Network interface list, select a network interface card (NIC), if applicable.

15. Click Set Storage Quotas to set storage space restrictions for a Data Domain MTree or storage unit to prevent the consumption of excess space. There are two kinds of quota limitshard limits and soft limits. You can set either a soft or hard limit or both a soft and hard limit. Both values must be integers, and the soft value must be less than the hard value.

Note: When you set a soft limit and the limit is reached, an alert is generated but data can still be written to the Data Domain. When you set a hard limit and the limit is reached, data cannot be written to the MTree. All data protection operations fail until data is deleted from the MTree. The Data Domain Operating System Administration Guide provides more information about MTree quota configuration.

a. Capacity QuotaControls the total size of precompression data that is written to the Data Domain.

b. Stream QuotaThe number of concurrent streams allowed on the system during data protection operations. Setting a Stream Quota limit can help ensure that system performance is not impacted negatively if a data protection operation is consuming too many system resources.

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

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 45

Note: Primary backups are assigned a default retention lock period of 14 days. Replicated backups, however, are not assigned a default retention lock period. If you select this check box for a replicated backup, ensure that you set the Keep For field in the Add Primary Replicate backup schedule dialog box to a minimum number of 14 days so that the replicated backup does not expire before the primary backup.

17. Click Next.

The Summary page appears.

18. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any information. When completed, click Finish.

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

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

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

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

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

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

The PowerProtect agent service performs the following operations:

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

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

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

Managing Storage, Assets, and Protection

46 PowerProtect Data Manager for Oracle RMAN Agent User Guide

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

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

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

l 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 perform the following operations during deletion:

n Deletion of the catalog entries from the database vendor's catalog and the agent's local datastore.

n Deletion of the older backups that the stand-alone application agent created, before the asset was added to PowerProtect Data Manager.

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

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

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

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

Note: The size of each datastore backup is the same as the datastore itself. By default, a backup is created every hour. To save space on the file system, you can reduce this datastore backup frequency for large datastores. By default, the datastore backup is retained for one week. You can change the datastore backup frequency, retention period, and backup location in the config.yml file.

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

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

l To start the agent service:

# register.sh --start

Started agent service with PID - 1234

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 47

l To stop the agent service:

# register.sh --stop

Successfully stopped agent-service.

l To obtain the status when the agent service is running:

# register.sh --status

Agent-service is running with PID - 1234

l To obtain the status when the agent service is not running:

# register.sh --status

Agent-service is not running.

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

About this task

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

Procedure

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.

l DEBUG l INFO l WARNING l ERROR l CRITICAL

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

Note: The agent service and application agent communicate through the temporary files, which are typically deleted after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True permanently, or the temporary files can use excessive space on the file system.

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

Managing Storage, Assets, and Protection

48 PowerProtect Data Manager for Oracle RMAN Agent User Guide

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

The agent service can only be registered to a single PowerProtect Data Manager server. When you register the agent service to a new server, the agent service will automatically unregister from the previous server address.

On Linux, you can register the agent service to a different server address by running the register.sh script that is found in the directory.

Note: The register.sh script stops the currently running agent service.

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

# register.sh

Enter the PowerProtect Data Manager IP address or hostname: 10.0.01

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234

l The following command includes the new IP address on the command line:

# register.sh --ppdmServer=10.0.0.1

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234

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

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 49

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

Before you begin

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:

Procedure

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:

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

4. Start the agent service.

Manage the cloud tier operations with PowerProtect Data Manager

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

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

Managing Storage, Assets, and Protection

50 PowerProtect Data Manager for Oracle RMAN Agent User Guide

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

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

Before you begin

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

About this task

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

Procedure

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

2. Select Protection > Protection Policies > Add.

3. On the Type page, enter a name and description, select Oracle as the type of system to back up, and click Next.

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

5. On the Assets page, select the assets to be protected with this policy, and then click Next.

6. On the Schedule page, select + Backup.

7. On the Add Primary page, set the following parameters, and then click OK:

l RecurrenceSelect Weekly or Monthly.

l Keep forCloud Tier backup requires a minimum of 2 weeks.

l Optionally, change the Start Time or End Time or both.

8. Select the Primary protection policy that you created, and then select Cloud Tier.

9. For Self -Service Protection Policy:

l Select a primary backup to create a promotion backup.

l Keep forCloud Tier backup requires a minimum of 2 weeks.

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

l RecurrenceSelect Weekly or Monthly.

l Create Full (Level 0)Add the option as per the recurrence.

l Keep forCloud Tier backup requires a minimum of 2 weeks.

11. Select the Promotion Backup policy, and then select Cloud Tier.

12. In the Add Cloud Tier dialog box, set the following parameters, and then click OK:

l Select the appropriate unit from the Cloud Target list.

l For Tier After, set a time of at least 2 weeks.

The cloud tier protection policy is created.

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 51

13. Click Next, verify the information, and then click Finish.

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

Tier the PowerProtect Data Manager backups from Data Domain to the cloud Once you add the Oracle 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.

Procedure

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

2. Select Infrastructure > Assets > Oracle Databases.

3. On the Type Assets page, select the asset, and then click View Copies.

4. Select the Data Domain system where the PowerProtect Data Manager backups for Oracle 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 of backup copies for the asset job, the status remains in the running state until the data movement occurs from the Data Domain system.

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

# data-movement policy show

Mtree Target(Tier/Unit Name) Policy Value ----------------------------------------- ---------------------- ----------- ------- /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 the successful data movement to the cloud, the cloud tier monitoring job completes. After some time, on the Assets > View Copies page, the Location field of the protection backups changes to Cloud.

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

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

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

Managing Storage, Assets, and Protection

52 PowerProtect Data Manager for Oracle RMAN Agent User Guide

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

Before you begin

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

Procedure

1. Select Recovery > Assets, click Data Domain, and then select one of the available copies in the table with the location as Cloud.

2. Click Recall, and then specify how long to keep the copy on the active tier.

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

3. Select the recalled copy, and then click Edit Recall Retention.

4. To re-tier the copy to the active tier, select the recalled copy.

Managing Storage, Assets, and Protection

PowerProtect Data Manager for Oracle RMAN Agent User Guide 53

Managing Storage, Assets, and Protection

54 PowerProtect Data Manager for Oracle RMAN Agent User Guide

CHAPTER 4

Performing Self-Service Backups of Oracle Databases

This chapter includes the following topics:

l Performing self-service backups of Oracle databases........................................................... 56 l Restore an Oracle application host........................................................................................ 57

PowerProtect Data Manager for Oracle RMAN Agent User Guide 55

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

To perform a self-service or manual backup of an Oracle database, you must create and run an RMAN backup script. The Oracle RMAN documentation provides detailed information about how to create the backup scripts. The documentation also describes all the supported backup features.

To identify the storage unit and Data Domain hostname or PowerProtect X400 server IP address, run the ddutil -s command on the Oracle client. For example, run the following command in the $RMAN_AGENT_HOME/bin directory:

./ddutil -s

Specify the storage unit and Data Domain hostname or PowerProtect X400 server IP address in the RMAN backup script.

The following example shows an RMAN script that performs a full backup of the database and its archive logs:

connect target username/password;

run { allocate channel c1 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);

backup database include current controlfile format %U plus archvielog;

release channel c1; }

The libddobk.so library location and the RMAN_AGENT_HOME, STORAGE_UNIT, and BACKUP_HOST settings must be specified in the allocate channel command. All other parts of the script are standard RMAN commands.

To increase the parallelism of the backup, you can allocate more channels:

connect target username/password;

run { allocate channel c1 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);); allocate channel c2 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);); allocate channel c3 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);); allocate channel c4 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com););

backup database include current controlfile format %U plus archivelog;

release channel c1; release channel c2; release channel c3;

Performing Self-Service Backups of Oracle Databases

56 PowerProtect Data Manager for Oracle RMAN Agent User Guide

release channel c4; }

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

To perform an Oracle database restore, you must prepare the database and then run an RMAN script to restore the data. The RMAN documentation provides detailed information about how to prepare the database and create the RMAN restore script. The documentation also describes all the supported restore features.

To identify the storage unit and Data Domain hostname or PowerProtect X400 server IP address, run the ddutil -s command on the Oracle client. For example, run the following command in the $RMAN_AGENT_HOME/bin directory:

./ddutil -s

Specify the storage unit and Data Domain hostname or PowerProtect X400 server IP address in the RMAN restore script.

The following example shows an RMAN script that performs a complete restore of the database to the current time, after the database has been prepared:

connect target username/password;

run { allocate channel c1 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com););

restore database; recover database;

release channel c1; }

The libddobk.so library location and the RMAN_AGENT_HOME, STORAGE_UNIT, and BACKUP_HOST settings must be specified in the allocate channel command. All other parts of the script are standard RMAN commands.

To increase the parallelism of the restore, you can allocate more channels:

connect target username/password;

run { allocate channel c1 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);); allocate channel c2 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);); allocate channel c3 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com);); allocate channel c4 type SBT_TAPE parms SBT_LIBRARY=rman_agent_home/lib/ libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com););

restore database;

Performing Self-Service Backups of Oracle Databases

PowerProtect Data Manager for Oracle RMAN Agent User Guide 57

recover database;

release channel c1; release

Manualsnet FAQs

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

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

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

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

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

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