PowerProtect Data Manager 19.

8
Oracle RMAN Agent User Guide
Version 19.8

Dell Inc.

January 2022
Rev. 02
Notes, cautions, and warnings

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

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

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

© 2020 - 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.
 Contents
Preface.........................................................................................................................................................................................5

Chapter 1: Quick Start Guide......................................................................................................... 9

PowerProtect Data Manager overview..........................................................................................................................9
About the Oracle RMAN agent........................................................................................................................................ 9
Prerequisites......................................................................................................................................................................... 9
Firewall and port considerations.....................................................................................................................................10
PowerProtect Data Manager new deployment overview......................................................................................... 11
PowerProtect Data Manager existing deployment overview..................................................................................12

Chapter 2: Enabling the Oracle RMAN Agent................................................................................13

Review Oracle data protection and replication requirements................................................................................. 13
Prerequisites..................................................................................................................................................................13
Protecting a stand-alone Oracle server........................................................................................................................13
Protecting Oracle RAC environments...........................................................................................................................14
Install and configure the Oracle RMAN agent............................................................................................................ 14
Install the Oracle RMAN agent................................................................................................................................. 14
Integration with PowerProtect Data Manager software....................................................................................16
Install the PowerProtect Data Manager agent..................................................................................................... 17
Uninstall the Oracle RMAN agent............................................................................................................................ 18
Uninstall the PowerProtect agent service............................................................................................................. 19
Upgrade the Oracle RMAN agent........................................................................................................................... 20
Upgrade the eCDM agent or PowerProtect agent..............................................................................................21
How the Oracle RMAN agent communicates with PowerProtect Data Manager...................................... 23
Verify the connectivity from ddbmcon...................................................................................................................27
Discover the storage units........................................................................................................................................ 28
Manage the Oracle application agent...........................................................................................................................29
Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager....................................30
Support existing Oracle RMAN agent backups with PowerProtect Data Manager.................................... 31
Enable multi-stream backups for Oracle protection policy......................................................................................31
Enabling app-optimization for storage unit created by Oracle protection policy.............................................. 32

Chapter 3: Managing Storage, Assets, and Protection.................................................................33

Add protection storage ...................................................................................................................................................33
Troubleshoot storage units....................................................................................................................................... 34
View the storage unit password.............................................................................................................................. 34
Storage unit considerations............................................................................................................................................ 35
Enable an asset source.................................................................................................................................................... 35
Disable an asset source..............................................................................................................................................35
Discover an Oracle application host............................................................................................................................. 36
Add and remove the credentials for Oracle assets...................................................................................................36
Add a protection policy for Oracle database protection..........................................................................................37
Add a Service Level Agreement.....................................................................................................................................42
Extended retention........................................................................................................................................................... 44
Edit the retention period for backup copies............................................................................................................... 45

Contents 3
 Delete backup copies....................................................................................................................................................... 46
Retry a failed backup copy deletion........................................................................................................................ 47
Export data for deleted backup copies.................................................................................................................. 47
Remove backup copies from the PowerProtect Data Manager database.................................................... 48
Troubleshooting the PowerProtect RMAN operation.............................................................................................. 48
Manage the PowerProtect agent service................................................................................................................... 49
About the PowerProtect agent service................................................................................................................. 49
Start, stop, or obtain the status of the PowerProtect agent service............................................................50
Troubleshoot the PowerProtect agent service operations...............................................................................50
Register the PowerProtect agent service to a different server address on Linux...................................... 51
Recovering the PowerProtect agent service from a disaster.......................................................................... 52
Manage the cloud tier operations with PowerProtect Data Manager................................................................. 53
Add a cloud tier schedule to a protection policy................................................................................................. 53
Tier the PowerProtect Data Manager backups from Data Domain to the cloud.........................................54
Restore the cloud tier backups to Data Domain.................................................................................................. 54

Chapter 4: Performing Self-Service Backups of Oracle Databases...............................................56

Performing self-service backups of Oracle databases............................................................................................ 56
Restore an Oracle application host............................................................................................................................... 57
Restore to an alternate host.................................................................................................................................... 58
Change the DBID of an Oracle instance................................................................................................................ 67
Remove a client registration from the lockbox.................................................................................................... 69

4 Contents
 Preface
As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of
the software or hardware currently in use might not support some functions that are described in this document. The product
release notes provide the most up-to-date information on product features.
If a product does not function correctly or does not function as described in this document, contact Customer Support.
NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this document,
go to the Customer Support website.

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

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

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

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

Audience
This document is intended for the host system administrator who configures and uses the PowerProtect Data Manager with the
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
02 January 12, 2022 This revision includes the following updates:
● Updated the bulleted list in the topic "Integration with
PowerProtect Data Manager software" in Chapter 2.
● Updated the Note in the topic "Self-service operations use
the Data Domain backup host and storage unit managed by
PowerProtect Data Manager" in Chapter 2.
01 May 4, 2021 Initial release of this document for PowerProtect Data
Manager version 19.8.

Compatibility information
Software compatibility information for the PowerProtect Data Manager software is provided at the eLab Navigator.

Preface 5
Related documentation
The following publications are available at Dell EMC Online Support and provide additional information:
● PowerProtect Data Manager Administration and User Guide—Describes how to configure the software.
● PowerProtect Data Manager Deployment Guide—Describes how to deploy the software.
● PowerProtect Data Manager Release Notes—Contains information on new features, known limitations, environment, and
system requirements for the software.
● PowerProtect Data Manager Security Configuration Guide—Contains security information.
● PowerProtect Data Manager AWS Deployment Guide—Describes how to deploy the software to Amazon Web Services
(AWS).
● PowerProtect Data Manager Azure Deployment Guide—Describes how to deploy the software to Microsoft Azure.
● PowerProtect Data Manager GCP Deployment Guide—Describes how to deploy the software to Google Cloud Platform
(GCP).
● PowerProtect Data Manager Cloud Disaster Recovery Administration and User Guide—Describes how to deploy Cloud DR,
protect VMs in the AWS or Azure cloud, and run recovery operations.
● PowerProtect Data Manager for Cyber Recovery User Guide—Describes how to install, upgrade, patch, and uninstall the
Dell EMC PowerProtect Cyber Recovery software.
● PowerProtect Data Manager for File System Agent User Guide—Describes how to configure and use the software with the
File System agent for file system data protection.
● PowerProtect Data Manager for Microsoft Application Agent Exchange Server User Guide—Describes how to configure
and use the software in a Microsoft Exchange Server environment.
● PowerProtect Data Manager for Microsoft Application Agent SQL Server User Guide—Describes how to configure and use
the software in a Microsoft SQL Server environment.
● PowerProtect Data Manager for Oracle RMAN Agent User Guide—Describes how to configure and use the software in an
Oracle Server environment.
● PowerProtect Data Manager for SAP HANA Agent User Guide—Describes how to configure and use the software in an SAP
HANA Server environment.
● PowerProtect Data Manager for Storage Direct Agent User Guide—Describes how to configure and use the software with
the Storage Direct agent to protect data on VMAX storage arrays through snapshot backup technology.
● PowerProtect Data Manager documentation—Contains the PowerProtect Data Manager APIs and includes tutorials to guide
to you in their use.

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

Table 2. Style conventions

Formatting Description
Bold Used for interface elements that a user specifically selects or clicks, for example, names of
buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page,
pane, screen area with title, table label, and window.
Italic Used for full titles of publications that are referenced in text.
Monospace Used for:
● System code
● System output, such as an error message or script
● Pathnames, file names, file name extensions, prompts, and syntax
● Commands and options
Monospace italic Used for variables.
Monospace bold Used for user input.
[] Square brackets enclose optional values.
| Vertical line indicates alternate selections. The vertical line means or for the alternate
selections.
{} Braces enclose content that the user must specify, such as x, y, or z.

6 Preface
Table 2. Style conventions (continued)
Formatting Description
... Ellipses indicate non-essential information that is omitted from the example.

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

Where to find product documentation

● The Customer Support website
● The Community Network

Where to get support

The Customer Support website provides access to product licensing, documentation, advisories, downloads, and how-to and
troubleshooting information. The information can enable you to resolve a product issue before you contact Customer Support.
To access a product-specific page:
1. Go to the Customer Support website.
2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx)
or by keyword.
To search the Knowledgebase:
1. Go to the Customer Support website.
2. On the Support tab, click Knowledge Base.
3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by
typing a product name in the search box, and then selecting the product from the list that appears.

Live chat
To participate in a live interactive chat with a support agent:
1. Go to the Customer Support website.
2. On the Support tab, click Contact Support.
3. On the Contact Information page, click the relevant support, and then proceed.

Service requests
To obtain in-depth help from Licensing, submit a service request. To submit a service request:
1. Go to the Customer Support website.
2. On the Support tab, click Service Requests.
NOTE: To create a service request, you must have a valid support agreement. For details about either an account or
obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the
Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to the Customer Support website.
2. On the Support tab, click Service Requests.
3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Preface 7
Online communities
For peer contacts, conversations, and content on product support and solutions, go to the Community Network. Interactively
engage with customers, partners, and certified professionals online.

How to provide feedback

Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to
[email protected].

8 Preface
 1
Quick Start Guide
Topics:
• PowerProtect Data Manager overview
• About the Oracle RMAN agent
• Prerequisites
• Firewall and port considerations
• PowerProtect Data Manager new deployment overview
• PowerProtect Data Manager existing deployment overview

PowerProtect Data Manager overview

Use PowerProtect Data Manager with the application agent to perform the following operations:
● Automate the configuration of the application agent backup policy and protection storage settings.
● Create a catalog of backups that the application agent creates. Then monitor that catalog data to determine if retention
policies are being adhered to.
● Manage the life cycle of backups that the application agent creates. Ensure that the backups are marked for garbage
collection, based on the rules of the retention policy.
PowerProtect Data Manager does not change the way that the application agent works. DBAs, system administrators, or
backup administrators create the backups and perform the restore operations.

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

Prerequisites
Ensure that your environment meets the requirements for a new deployment or upgrade of PowerProtect Data Manager.
Requirements:
NOTE: The most up-to-date software compatibility information for the PowerProtect Data Manager software
and the application agents is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/
modernHomeDataProtection.
● A list of hosts that write backups to DD systems is available.
● DD OS version 6.1 or later and the DD Management Console (DDMC) are required. All models of DD systems are supported.
NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use
a DD system directly without DDMC.

Quick Start Guide 9

● Application agent 19.8 or earlier is required.
● 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.
● Large environments require multiple PowerProtect Data Manager instances. Contact [email protected] for
assistance with sizing requests.
● The PowerProtect Data Manager 19.8 download file requires the following:
○ ESXi version 6.5, 6.7, or 7.0.
○ 8 vCPUs, 18 GB RAM, one 100 GB disk, and one 500 GB disk.
○ The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI.
○ TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.
● VMware ESXi server that hosts PowerProtect Data Manager meets the following minimum system requirements:
○ 10 CPU cores
○ 18 GB of RAM for PowerProtect Data Manager
○ Five disks with the following capacities:
￭ Disk 1—100 GB
￭ Disk 2—500 GB
￭ Disk 3—10 GB
￭ Disk 4—10 GB
￭ Disk 5—5 GB
○ One 1-GB NIC

Firewall and port considerations

The latest version of the PowerProtect Data Manager Security Configuration Guide provides more details about the port
requirements.

Table 3. PowerProtect Data Manager port requirements

Description Communication Port
SSH communications Bi-directional communication between the SSH client and the 22 TCP/UDP
PowerProtect Data Manager appliance.
SQL, Oracle, Exchange, Bi-directional communication between the PowerProtect 7000 TCP
SAP HANA, File System Data Manager agent and the PowerProtect Data Manager
appliance.

Requirement applies to Application Direct and VM Direct.

REST Server Bi-directional communication between the HTTP client and the 8443 TCP
PowerProtect Data Manager appliance.
RESTAPI Server - VM Bi-directional communication between the PowerProtect 8443 TCP
Direct Data Manager agent and the PowerProtect Data Manager
appliance.

Requirement applies to SQL VM application-aware.

UI redirect Inbound only. 80 TCP

443

LDAP Outbound only. 389 TCP/UDP

636 TCP

Discovery (devices) Outbound between the PowerProtect Data Manager appliance 3009 TCP—Storage Direct and
and the device. DD system

5989 TCP—SMI-S

443 TCP—XtremIO

10 Quick Start Guide

Table 3. PowerProtect Data Manager port requirements (continued)
Description Communication Port

7225 TCP—RecoverPoint

PowerProtect Data Bi-directional communication between the database hosts and 7000 TCP
Manager agent the PowerProtect Data Manager appliance.

This requirement applies to both Application Direct and VM

Direct.

Embedded VM Direct Outbound. 9090 TCP

service

PowerProtect Data Manager new deployment

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

Steps
1. Design how to group the backups, based on the storage requirements and retention policies.
The account team can help with backup storage design.
2. Install PowerProtect DD Management Center (DDMC).
PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and
Administration Guide provides instructions.
NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use
a DD system directly without DDMC.

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.
4. Add external DD systems or DDMC to PowerProtect Data Manager.
The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.
5. Install the application agent on the appropriate hosts and connect them to PowerProtect Data Manager according to the
instructions in the next "Enabling" chapter.
DBAs should perform this operation.
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.
NOTE: After you create a centralized protection job, the first backup is a full backup.

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

Quick Start Guide 11

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

Steps
1. Install PowerProtect DD Management Center (DDMC).
PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and
Administration Guide provides instructions.
NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use
a DD system directly without DDMC.

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.
3. Add external DD systems or DDMC to PowerProtect Data Manager.
The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.
4. Upgrade the application agent or uninstall and then reinstall the application agent on the hosts and connect them to
PowerProtect Data Manager. Follow the instructions in the next "Enabling" chapter.
DBAs should perform this operation.
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.
7. Add a protection policy for groups of assets that you want to back up.
NOTE: After you create a centralized protection job, the first backup is a full backup.

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

12 Quick Start Guide

 2
Enabling the Oracle RMAN Agent
Topics:
• Review Oracle data protection and replication requirements
• Protecting a stand-alone Oracle server
• Protecting Oracle RAC environments
• Install and configure the Oracle RMAN agent
• Manage the Oracle application agent
• Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager
• Enable multi-stream backups for Oracle protection policy
• Enabling app-optimization for storage unit created by Oracle protection policy

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:
● 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.
● Ensure that the Oracle host and the PowerProtect Data Manager network can see and resolve each other.
● 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.

Steps
1. Add a storage system.
Add protection storage on page 33 provides information.
2. Install the Oracle RMAN agent on the Oracle server host.
Install the Oracle RMAN agent on page 14 provides information.
3. Add or approve the Oracle RMAN agent in PowerProtect Data Manager.
Manage the Oracle application agent on page 29 provides information.
4. Discover and add the credentials for the Oracle application host.
Discover an Oracle application host on page 36 provides information.
5. Create a protection policy to protect the Oracle server host.
Add a protection policy for Oracle database protection on page 37 provides information.

Enabling the Oracle RMAN Agent 13

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

About this task

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.

Steps
1. Add a storage system.
Add protection storage on page 33 provides information.
2. Install the Oracle RMAN agent on each Oracle RAC node.
Install the Oracle RMAN agent on page 14 provides information.
3. Add or approve the Oracle RMAN agent on each Oracle RAC node.
Manage the Oracle application agent on page 29 provides information.
4. Discover and add the credentials for each Oracle application host.
Discover an Oracle application host on page 36 provides information.
5. Create a protection policy group to protect the Oracle RAC nodes.
Add a protection policy for Oracle database protection on page 37 provides information.

Install and configure the Oracle RMAN agent

Learn how to install and configure the Oracle RMAN agent.
NOTE:

The installation and configuration of the Oracle RMAN agent is supported only on English language operating systems.

PowerProtect Data Manager does not support an Oracle database installation in a High Availability (active/passive) OS
cluster configuration.

DD Boost currently supports only active-standby configurations.

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: To enable the latest software features, it is recommended that you use the same version of the PowerProtect Data
Manager and Oracle RMAN agent.
Run the install.sh script to install the Oracle RMAN agent 19.8 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.

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

Steps
1. In the PowerProtect Data Manager UI:
a. Select Agent Downloads from Dashboard > System Settings.
b. Select the Oracle RMAN agent download package, ddrman198_linux_x86_64.tar.
c. Download the package to the Oracle server host on Linux.

14 Enabling the Oracle RMAN Agent

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

chown -R oracle:oinstall ddrman198_linux_x86_64.tar

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

tar -xvf ddrman198_linux_x86_64.tar.gz

The Oracle RMAN agent installation files are uncompressed under the ddrman folder.

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:

● To install in the default directory, type y.
● 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.8 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.
The settings directory /home/oracle/opt/dpsapps/rmanagent/settings is created.
The addon directory /home/oracle/opt/dpsapps/rmanagent/addon is created.
The Oracle addon directory /home/oracle/opt/dpsapps/rmanagent/addon/
D2B24128_9482_44D2_8723_6D211DB49BFB is created.
The bin directory /home/oracle/opt/dpsapps/rmanagent/bin is created.
The log directory /home/oracle/opt/dpsapps/rmanagent/logs is created.
The tmp directory /home/oracle/opt/dpsapps/rmanagent/tmp 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 ddbmoim configuration file to /home/oracle/opt/dpsapps/rmanagent/config/.
Copying the ddbmcon program to /home/oracle/opt/dpsapps/rmanagent/bin/.
Copying the addon library program to /home/oracle/opt/dpsapps/rmanagent/addon/
D2B24128_9482_44D2_8723_6D211DB49BFB/.
Copying the configureAddOn.sh program to /home/oracle/opt/dpsapps/rmanagent/addon/.
Copying the unConfigureAddOn.sh program to /home/oracle/opt/dpsapps/rmanagent/addon/.
Copying the ddbmoim 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.

Enabling the Oracle RMAN Agent 15

 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

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.
Review the following features of the integration with PowerProtect Data Manager:
● 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 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:
○ Creation of multiple backup copies with the RMAN BACKUP COPIES command.
○ 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 override the target protection storage settings that are specified in the
RMAN backup script, including the Data Domain server hostname and storage unit name.
● For clients that are configured with a self-service protection policy, you must perform each type of data backup (full,
incremental, cumulative) in a separate RMAN session. You can perform the archived log, spfile, and controlfile backups either
with the data backups or in separate RMAN sessions.
● When you perform the different types of data backups in the same RMAN session, the backups are reported incorrectly.
● If any asset on the host is being managed by PowerProtect Data Manager, only the delete operations performed through
PowerProtect Data Manager are supported. Self-service delete operations through rman delete or ddutil delete are
not supported.
● If you plan to manage all assets on a host by using the stand-alone RMAN agent and not PowerProtect Data Manager,
ensure that the hidden files .app.settings and .ddbmcon.gatherinfo are removed from the $RMAN_AGENT_HOME/
settings directory.
NOTE: On a host where at least one asset is being managed by PowerProtect Data Manager, do not remove the hidden
files .app.settings and .ddbmcon.gatherinfo. In this case, the file removal will result in unexpected behavior.
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 17.
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 23 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 27 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:

<ORACLE_SID>:<ORACLE_HOME>:<N|Y>

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 RAC_BACKUP_NODE_IP parameter accordingly, as described in Configuration file requirements for connection to local
databases on page 24.

16 Enabling the Oracle RMAN Agent

 NOTE: The parameter is only applicable for a centralized protection policy, not for a self-service protection policy.

Install the PowerProtect Data Manager agent

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.

Steps
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.8.0.0.0-1.x86_64.rpm command. For example:
NOTE: To validate the agent service .rpm file before you run the command, follow the instructions in Knowledgebase
article number 546613 at https://www.dell.com/support/kbdoc/en-us/546613.

rpm -ivh powerprotect-agentsvc-19.8.0.0.0-1.x86_64.rpm

Preparing... ################################# [100%]
Updating / installing...
1:powerprotect-agentsvc-19.8.0.0.0-################################# [100%]
Created symlink from /etc/systemd/system/multi-user.target.wants/agentsvc.service to
/etc/systemd/system/agentsvc.service.

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. The following examples show the results when the retention time is set and the retention time is not set.
When the retention time is set to days:

./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 the PowerProtect Data Manager IP address or hostname: 10.63.102.140
TMPDIR set to value /opt/dpsapps/agentsvc/tmp
agent service (pid 20006) started successfully
Do you want to set the default retention time for automatic retention management of
existing backups by PowerProtect Data Manager? (y or n) y
Provide the default retention time as the number of days: 2
Setting RETENTION_TIME=2. When PowerProtect Data Manager protects the asset, the
existing backup copies are deleted after 2 days.
Allow SYSDBA access for RMAN agent? (y or n) y
Setting SYSADMIN_ACCESS=TRUE.
Addons configuration is completed.

When the retention time is not set:

./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 the PowerProtect Data Manager IP address or hostname: 10.63.102.140
TMPDIR set to value /opt/dpsapps/agentsvc/tmp
agent service (pid 20680) started successfully

Enabling the Oracle RMAN Agent 17

 Do you want to set the default retention time for automatic retention management of
existing backups by PowerProtect Data Manager? (y or n) n
When PowerProtect Data Manager protects the asset, the existing backup copies are
deleted after 30 days.
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 Oracle RMAN agent

Run the uninstall.sh script to uninstall the Oracle RMAN agent 19.8. 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 Environment variables for uninstallation of Oracle RMAN agent on page 18:
● When the variables are not set, the script runs manually and prompts for the required values.
● When the variables are set, the script runs automatically and performs the uninstallation according to the environment
variable settings.

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 ● /home/oracle1/opt/
the Oracle RMAN agent. dpsapps/rmanagent (default).
● 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 ● Undefined (default).

to uninstall. ● NONE or none—Specifies to
keep the Oracle RMAN agent
software, and not perform the
uninstallation.
● BINARY or binary—Specifies to
uninstall the software, but not the
lockbox or the configuration file.
● FULL or full—Specifies 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.

18 Enabling the Oracle RMAN Agent

Steps
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 Environment variables for uninstallation of Oracle RMAN
agent on page 18.
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=/home/oracle/opt/dpsapps/rmanagent

3. To unconfigure the Oracle addon for PowerProtect Data Manager, log in as the root user on the Oracle RMAN host
and run the unConfigureAddOn.sh script from the RMAN agent addon directory /home/oracle/opt/dpsapps/
rmanagent/addon.
This step deletes the Oracle addon files in the agent service 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:

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

NOTE: Before you run the uninstall.sh script, it is recommended that you run the unConfigureAddOn.sh script
to delete the Oracle addon files and then set the RMAN_AGENT_HOME environment variable.

# ./uninstall.sh

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

Uninstall the PowerProtect agent service

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

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

Enabling the Oracle RMAN Agent 19

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.8.0.0.0-1.x86_64

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

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

Upgrade the Oracle RMAN agent

An upgrade of the Oracle RMAN agent to version 19.8 requires additional steps when the pre-19.8 Oracle RMAN agent is
integrated with Enterprise Copy Data Management (eCDM) or a previous version of the PowerProtect agent. A later topic
provides details about upgrading from the eCDM agent or a previous version of the PowerProtect agent.

About this task

NOTE: Perform the upgrade of the Oracle RMAN agent and PowerProtect agent service after the upgrade of
PowerProtect Data Manager. Ensure that the Oracle RMAN agent and PowerProtect agent service are the same version.

Steps
1. Log in as an Oracle user.
2. 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

User: PLC-PROTECTION-1557475568457
Type: PRIMARY

3. Upgrade the Oracle RMAN agent by using either of the following methods:
● 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 14.
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/.

20 Enabling the Oracle RMAN Agent

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

● 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. Log in as the Oracle user.
b. 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

c. 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={<server_name1>[,<server_name2>,...]} -a
DD_STORAGE_UNIT={<storage_unit1>[,<storage_unit2>,...]}

Upgrade the eCDM agent or PowerProtect agent

You must complete the required steps to upgrade from the Enterprise Copy Data Management (eCDM) agent or a previous
version of the PowerProtect agent. Use the following methods to upgrade from either the eCDM agent 19.3 or earlier or the
PowerProtect agent 19.4 or later to the current version of the PowerProtect agent.

Upgrade from eCDM agent 19.3 or earlier

Complete the following steps to upgrade from the eCDM agent 19.3 or earlier to the current version of the PowerProtect agent.
1. To stop the eCDM agent on the Oracle RMAN agent client host, run the following command as the root user:

/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

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

Enabling the Oracle RMAN Agent 21

 Loaded: loaded (/etc/systemd/system/ecdmagent.service; enabled)
:

3. To install the PowerProtect agent, run the rpm -ivh powerprotect-agentsvc-19.8.0.0.0-1.x86_64.rpm

command. For example:

rpm -ivh powerprotect-agentsvc-19.8.0.0.0-1.x86_64.rpm

warning: powerprotect-agentsvc-19.8.0.0.0-1.x86_64.rpm:
Header V3 RSA/SHA1 Signature, key ID c5dfe03d: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:powerprotect-agentsvc-19.8.0.0.0-################################# [100%]
Created symlink from /etc/systemd/system/multi-user.target.wants/agentsvc.service to
/etc/systemd/system/agentsvc.service.

4. 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 the PowerProtect Data Manager IP address or hostname: 10.63.102.140
Agent service (pid 32047) started successfully.
Do you want to set the default retention time? (y or n) y
Provide the default retention time as the number of days: 1
Setting RETENTION_TIME=1.
Allow SYSDBA access for RMAN agent? (y or n) y
Setting SYSADMIN_ACCESS=TRUE.
Addons configuration is completed.

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

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

Upgrade from PowerProtect agent 19.4 or later

Complete the following steps to upgrade from the PowerProtect agent 19.4 or later to the current version of the PowerProtect
agent.
1. Log in as the root user.
2. To upgrade the PowerProtect agent, run the rpm -Uvh powerprotect-agentsvc-19.8.0.0.0-1.x86_64.rpm
command. For example:
NOTE: To validate the agent service .rpm file before you run the command, follow the instructions in Knowledgebase
article number 546613 at https://www.dell.com/support/kbdoc/en-us/546613.

rpm -Uvh powerprotect-agentsvc-19.8.0.0.0-1.x86_64.rpm

Preparing... ################################# [100%]
Stopping agent service (pid 25731, count=1) ...
Stopping agent service (pid 25732, count=2) ...
Stopping agent service (pid 25740, count=3) ...
Removed symlink /etc/systemd/system/multi-user.target.wants/agentsvc.service.
Updating / installing...
1:powerprotect-agentsvc-19.8.0.0.0-################################# [ 50%]
Cleaning up / removing...
2:powerprotect-agentsvc-19.7.0.0.0-################################# [100%]

22 Enabling the Oracle RMAN Agent

 Created symlink from /etc/systemd/system/multi-user.target.wants/agentsvc.service to
/etc/systemd/system/agentsvc.service.

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 the PowerProtect Data Manager IP address or hostname: 10.63.102.140
Agent service (pid 32047) started successfully.
Do you want to set the default retention time? (y or n) y
Provide the default retention time as the number of days: 1
Setting RETENTION_TIME=1.
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

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

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 authentication—The 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 authentication—If 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 authentication—If 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.

Enabling the Oracle RMAN Agent 23

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.
#
# Oracle RMAN agent 19.8
#
# 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]
# RAC_BACKUP_NODE_IP =
# ORACLE_SERVICE =
# ORACLE_USER =
# ORACLE_OS_USER =
# TNS_ADMIN =
# RMAN_CATALOG_SERVICE =
# RMAN_CATALOG_USER =

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:
● 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:
○ For any supported Oracle version in a stand-alone setup, SID_name must match the SID in the /etc/oratab file.
○ For any supported Oracle version in a RAC system, 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.
● RAC_BACKUP_NODE_IP 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 the hostname or IP address of the backup node.
NOTE: This parameter setting might take 1 hour to come into effect. When you upgrade from a pre-19.5 version
of Oracle RMAN agent, you must manually add the RAC_BACKUP_NODE_IP setting in the configuration file. This
parameter is not applicable for self-service and stand-alone backups.
● ORACLE_SERVICE is mandatory for database authentication and Oracle wallet authentication. Specifies the TNS or Net
service name of the Oracle database.
● ORACLE_USER is mandatory for database authentication only. Specifies the database username as saved in the lockbox.

24 Enabling the Oracle RMAN Agent

● 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.
● 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.
● 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.
● 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.
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=<database_SIDs>] [-a

USERNAME=<administator_username>]

NOTE: If the lockbox does not exist when you run the ddutil command, the command creates the lockbox in the
$RMAN_AGENT_HOME/config directory.

The options -C and -a USER_TYPE=DATABASE_ADMIN are mandatory. If you do not specify the other -a options, -a
DATABASE_SIDS=<database_SIDs> and -a USERNAME=<administator_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'
Password: xxxxx
Re-enter password: xxxxx
Successfully set the Oracle database administrator credentials in the lockbox.

Enabling the Oracle RMAN Agent 25

To enable the database authentication method, you must also set the following parameters for each required SID in the
rman_agent.cfg configuration file:
● Set ORACLE_SERVICE and ORACLE_USER. ORACLE_USER must match the username that is saved in the lockbox.
● If the Oracle Net configuration files reside in a non-default directory, set TNS_ADMIN to the directory pathname.
● 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 27.

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:
● Set ORACLE_SERVICE to the TNS or Net service name. For example, set the parameter to the value DBFS.
● If the Oracle Net configuration files reside in a non-default directory, set TNS_ADMIN to the directory pathname.
● 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/<alternate_TNS_location>

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

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.
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:
● If the username to be used for the connection is different than ORACLE_OSDBA_USER, set ORACLE_OS_USER.
● 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:

26 Enabling the Oracle RMAN Agent

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

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:
● System verification
● Asset verification
● 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

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

Enabling the Oracle RMAN Agent 27

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:
● Authentication type, which is listed as operating system user, Oracle database user, or Oracle wallet user.
● For operating system authentication, only the operating system user is listed.
● For database authentication, the operating system user, Oracle service, and database user are listed.
● For Oracle wallet authentication, the Oracle service and TNS_ADMIN value are listed.
2. Catalog database connection information:
● Authentication method, which is listed as Oracle database user or Oracle wallet user.
● For database authentication, the database service and database user are listed.
● 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.
For example, the following ddutil -v rman command displays the three sections of output. The output shows 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

28 Enabling the Oracle RMAN Agent

 Data Domain Hostname: 10.118.211.13

FC Service Name: None

FC Service Enabled: false

Storage Unit: demo-storage-blrv034d018-65f26

Top Level Path: PLCTLP-ae3a3ffa-ab1a-450e-a582-f4ed41f5cf05
PLC Name: demo-storage

User: demo-storage-blrv034d018-65f26
Type: PROTECTION

Storage Unit: demo-storage-blrv034d018-65f26

Top Level Path: PLCTLP-fe256ae9-359a-4e56-9a2f-b4b760b96899
PLC Name: self_service

User: demo-storage-blrv034d018-65f26
Type: PROTECTION

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.

Steps
1. Select Infrastructure > Application Agents.
The Application Agents window appears.
NOTE: If the PowerProtect agent service was able to register during the installation, the 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:
● Add FQDN or CSV Filename.
○ If you select Add FQDN, perform the following steps:
a. Type the fully qualified domain name (FQDN) for the application agent.
b. Specify the date until which the application agent is preapproved.
c. Click Save.
○ If you select CSV Filename, perform the following steps:
a. Click the Choose File icon.
NOTE: The contents of the .csv file must be in the following format, for example:

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

The Explorer window appears.

b. Select the .csv file, and then click Open.
The file appears in the Application/FS Agents window.
c. Select the date until which the application agent is preapproved.
d. Click Save.
● If you have disabled Auto 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 29

 a. Select the required application agent.
b. Click one of the following options:
○ Approve
○ Reject
○ Edit, then make the required changes.
○ Remove
c. Click Save.

Next steps
Discover an Oracle application host on page 36 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:
● Visibility of both existing backups and any new self-service or PowerProtect Data Manager policy-driven backups of
onboarded assets.
● Retention management of all backups. The retention time of existing backups can be set during the PowerProtect Data
Manager registration.
● Automatic configuration of target protection storage based on the PowerProtect Data Manager protection policies that are
used for your database.
● 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 can either create or reuse a storage unit on the
specified DD system backup host, subject to limitations. All subsequent backups of assets in that protection policy go to this
storage unit. This implementation overrides the backup host and storage unit information from the script with the backup host
and storage unit information from PowerProtect Data Manager.
NOTE:

If any asset on the host is being managed by PowerProtect Data Manager, only the delete operations performed through
PowerProtect Data Manager are supported. Self-service delete operations through rman delete or ddutil delete
are not supported.

If you plan to manage all assets on a host by using the stand-alone RMAN agent and not the PowerProtect
Data Manager, ensure that the hidden files .app.settings and .ddbmcon.gatherinfo are removed from the
$RMAN_AGENT_HOME/settings directory.

On a host where at least one asset is being managed by PowerProtect Data Manager, do not remove the hidden
files .app.settings and .ddbmcon.gatherinfo. In this case, the file removal will result in unexpected behavior.

30 Enabling the Oracle RMAN Agent

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 retention time for existing backups during
registration with the PowerProtect Data Manager server by using the configureAddOn.sh script with version 19.5 or later.
This retention time is reported to PowerProtect Data Manager during backup discovery.

Support existing Oracle RMAN agent backups with PowerProtect

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

Steps
1. Upgrade the Oracle RMAN agent on the Oracle server host.
Upgrade the Oracle RMAN agent on page 20 provides information.
2. Register and approve the Oracle RMAN agent in PowerProtect Data Manager.
Manage the Oracle application agent on page 29 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 is the value that is set during
the configuration with the configureAddOn.sh script. You can verify the applied retention time value from the
RETENTION_TIME=<number_of_days> setting in the $RMAN_AGENT_HOME/config/rman_options.cfg file.
When the RETENTION_TIME parameter is not set and the reply to the script prompt about setting the default retention
time is n, the default retention time for the backups is 30 days.
NOTE: This value is applied to all the assets that PowerProtect Data Manager discovers from the client. The RMAN
traditional retention time that uses the KEEP options is not honored.

3. Discover and add the credentials for the Oracle RMAN agent host.
Discover an Oracle application host on page 36 provides information.
4. Create a protection policy to protect the Oracle RMAN agent host.
Add a protection policy for Oracle database protection on page 37 provides information.
The first backup after onboarding must be a full backup:
● The first centralized backup is automatically promoted to a full backup.
● 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.

Enable multi-stream backups for Oracle protection

policy
To enable multi-stream Oracle backups for a centralized protection policy, you can set the parallelism value as the number of
Oracle backup channels in the PowerProtect Data Manager UI. As an alternative, you can set the PARALLELISM parameter in
the configuration file rman_agent.cfg.
Determine the required number of Oracle backup channels based on the system capacity. With the parallelism setting, you can
override the number of backup channels from the Oracle RMAN agent client side.

Enabling the Oracle RMAN Agent 31

 NOTE: After you have set the parallelism, if you encounter an RMAN ORA-00020 error, the following Oracle document
provides information to help in resolving the issue:

https://docs.oracle.com/cd/E29633_01/CDMIG/GUID-06C3ACB1-B48C-49E9-830A-B1F3B84B3DA7.htm
In the PowerProtect Data Manager UI, perform the following steps to set the parallelism for multi-stream backups:
1. Select Infrastructure > Assets > Oracle.
2. Select the Oracle asset.
3. Select More Actions > Set Parallelism.
4. Set the parallelism for each backup level as a value between 1 and 255 in the Full, Incremental Cumulative, Incremental
Differential, and Log fields.
5. Click Save.
As an alternative, you can set the PARALLELISM parameter in the $RMAN_AGENT_HOME/config/rman_agent.cfg file on
the Oracle RMAN agent host. For example, when you set the PARALLELISM parameter to 6, the Oracle backups run with 6
channels:

PARALLELISM = 6

NOTE: A parallelism setting in the rman_agent.cfg file takes precedence over a parallelism setting in the PowerProtect
Data Manager UI.

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

Steps
1. To identify the storage unit and Data Domain 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

32 Enabling the Oracle RMAN Agent

 3
Managing Storage, Assets, and Protection
Topics:
• Add protection storage
• Storage unit considerations
• Enable an asset source
• Discover an Oracle application host
• Add and remove the credentials for Oracle assets
• Add a protection policy for Oracle database protection
• Add a Service Level Agreement
• Extended retention
• Edit the retention period for backup copies
• Delete backup copies
• Troubleshooting the PowerProtect RMAN operation
• Manage the PowerProtect agent service
• Manage the cloud tier operations with PowerProtect Data Manager

Add protection storage

About this task
The PowerProtect Data Manager UI enables users with administrator credentials to add the following storage types:
● DD Management Center (DDMC)
● External DD system
You can also add a DD system in High Availability (HA) mode.
NOTE:
● Adding the DDMC is not required for the Storage Direct agent.
● The most up-to-date software compatibility information for PowerProtect Data Manager is provided in the eLab
Navigator.
When a DDMC is added, PowerProtect Data Manager discovers all the supported DD systems that are managed by the DDMC.
The PowerProtect Data Manager UI displays the discovered DD systems on the Protection Storage tab of the Infrastructure
> Storage window. The DD systems that are managed by the DDMC are not displayed until discovery is complete. It might take
a few minutes for the DD systems to appear in the Storage window.
For each DD system, the DDMC that manages the DD system is indicated in the Managed By column in the table.
If a DD system is added directly to PowerProtect Data Manager, the name that was provided for the DD system when it was
added to the PowerProtect Data Manager system is displayed in the Managed By column.
NOTE: Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the UI,
and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the UI has
not yet been updated to reflect this change.

Steps
1. Select Infrastructure > Storage.
The Storage window appears.
2. In the Protection Storage tab, click Add.
3. In the Add Storage dialog box, select a storage system (DD System, DDMC).
4. To add a DD HA system, select the checkbox.

Managing Storage, Assets, and Protection 33

 NOTE:
● Do not add the individual active and standby DD systems to PowerProtect Data Manager.
● Use the hostname corresponding to the floating IP address of the HA DD system.
● The DD HA system is verified with the root certificate.

5. Specify the storage system attributes:

a. In the Name field, specify a storage name.
b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address.
NOTE: If you selected the High Availability option, use the hostname corresponding to the floating IP address of
the HA DD system.

c. In the Port field, specify the port for SSL communication. Default is 3009.
6. Under Host Credentials click Add, if you have already configured DD credentials that are common across DD systems,
select an existing password. Alternatively, you can add new credentials, and then click Save .
7. If a trusted certificate does not exist on the storage system, a dialog box appears requesting certificate approval. Click
Verify to review the certificate, and then click Accept.
8. Click Save to exit the Add Storage dialog and initiate the discovery of the storage system.
A dialog box appears to indicate that the request to add storage has been initiated.
9. In the Storage window, click Discover to refresh the window with any newly discovered storage systems.
When a discovery completes successfully, the Status column updates to OK.
10. To modify a storage system location, complete the following steps:
A storage system location is a label that is applied to a storage system. If you want to store your copies in a specific location,
the label helps you select the correct storage system during policy creation.
a. In the Storage window, select the storage system from the table.
b. Click Set Location.
The Set Location window appears.
c. Click Add in the Location list.
The Add Location window appears.
d. In the Name field, type a location name for the asset, and click Save.

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

Troubleshoot storage units

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

View the storage unit password

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

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

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

34 Managing Storage, Assets, and Protection

3. Obtain the storage unit password by typing the following command:
./get_dd_mtree_credential.py MTree-name

Storage unit considerations

Oracle RMAN agent 19.6 and earlier releases do not support the mapping structure that allows protection policies to share
the same storage unit. Backups of databases that are protected by older agents and different policies cannot target the same
storage unit.
PowerProtect Data Manager 19.7 and later releases contain logic that detects this condition when you add or edit a protection
policy. The policy rules alert you to the conflict and fall back to the previous structure that mapped one policy to one storage
unit. You can resolve this condition by upgrading the Oracle RMAN agent to release 19.7 or later.
All references in this guide for configuring a protection policy to target an existing storage unit apply in the context of
protecting databases with Oracle RMAN agent 19.7 or later installed on the host.

Enable an asset source

An asset source, such as a vCenter Server, must be enabled in PowerProtect Data Manager before you can add and register the
asset source for the protection of assets.

About this task

There are some circumstances where enabling an asset source is not required, such as the following:
● For application agents and other agents such as File System and Storage Direct, an asset source is enabled automatically
when you register and approve the agent host. For example, if you have not enabled an Oracle asset source but have
registered the application host though the API or the PowerProtect Data Manager UI, PowerProtect Data Manager
automatically enables the Oracle asset source.
● When you upgrade to the latest version of PowerProtect Data Manager from an earlier release, any asset sources that
were previously enabled appear in the PowerProtect Data Manager UI. On a new installation, however, no asset sources are
enabled by default.

Steps
1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then click + to reveal the New
Asset Source tab.
2. In the pane for the asset source that you want to add, click Enable Source.
The Asset Sources window updates to display a tab for the new asset source.

Results
You can now add or approve the asset source for use in PowerProtect Data Manager. For a vCenter Server, Kubernetes cluster,
SMIS Server, or PowerProtect Cloud Snapshot Manager tenant, select the appropriate tab in this window and click Add. For an
application agent, select Infrastructure > Application Agents and click Add or Approve as required.
NOTE: Although you can add a Cloud Snapshot Manager tenant to PowerProtect Data Manager in order to view its health,
alerts, and the status of its protection, recovery, and system jobs, you cannot manage the protection of its assets from
PowerProtect Data Manager. To manage the protection of its assets, use Cloud Snapshot Manager. For more information,
see the PowerProtect Cloud Snapshot Manager Online Help.

Disable an asset source

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

About this task

NOTE: An asset source cannot be disabled when one or more sources are still registered or there are backup copies of the
source assets. For example, if you registered a vCenter Server and created policy backups for the vCenter virtual machines,

Managing Storage, Assets, and Protection 35

 then you cannot disable the vCenter asset source. But if you register a vCenter Server and then delete the vCenter without
creating any backups, you can disable the asset source.

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

Results
PowerProtect Data Manager removes the tab for this asset source.

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.

About this task

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

Steps
1. Select Infrastructure > Asset Sources.
The Asset Sources window appears.
2. Select the App/File System Host tab.
3. If you are adding an 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, specify CredentialType as OS User and provide the Oracle username
and password.
Authentication requirements on page 25 provides details about the authentication requirements for an Oracle database.
NOTE: Credentials that you set at the asset level and asset source level supersede the credentials that you set at the
protection policy level. Credentials at the asset level have the highest precedence.

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 and remove the credentials for Oracle assets

Starting with PowerProtect Data Manager 19.7, you can optionally add and remove the credentials for one or more Oracle
database assets at the same time in the PowerProtect Data Manager UI. The asset-level credentials take precedence over

36 Managing Storage, Assets, and Protection

asset source-level (host) credentials and policy-level credentials for Oracle databases. Asset-level credentials have the highest
precedence.

About this task

NOTE:

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

You can add Oracle assets with different Oracle OS users or groups from the same asset source into a single protection
policy.

You can add multiple Oracle assets from multiple asset sources into a single protection policy.

The Oracle assets can be associated with multiple credential types, where the supported database credential types are
Oracle, Database User, and Wallet and the supported RMAN catalog credential types are Database User and Wallet.
Use the following procedure to add or remove the credentials for the Oracle database assets.

Steps
1. In the PowerProtect Data Manager UI, select Infrastructure > Assets, and then click the Oracle tab.
2. Select one or more assets by clicking the checkbox next to each required asset name.
3. Select More Actions > Set Credential.
4. In the Set Credential dialog box, add or remove the credentials for the selected Oracle assets:
● To add the credentials for the assets, specify the required OS, Database User, or Wallet settings for Database
Credentials. When the asset is associated with an RMAN catalog, you can also specify the RMAN catalog credentials
through the Database User or Wallet settings for RMAN Catalog.
NOTE: You can specify both the database credentials and RMAN catalog credentials in the Set Credential dialog
box.
● To remove the credentials for the assets, select Remove Credentials.
5. Click Save in the Set Credential dialog box.

Results
When you save the newly added credentials in the dialog box, PowerProtect Data Manager triggers an auto-configuration job for
the credential update in the respective clients.
After you add the credentials by using this procedure, the asset-level credentials are used for the selected assets during Oracle
centralized backups, overriding the policy-level credentials.

Add a protection policy for Oracle database protection

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

Prerequisites
● 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.
● 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.
● Before you perform a backup on a weekly or monthly schedule from the protection policy, ensure that the PowerProtect
Data Manager time zone is set to the local time zone. If the PowerProtect Data Manager time zone is not set to the local
time zone, the weekly or monthly backup still runs but is triggered based on the PowerProtect Data Manager time zone.
If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection
policy. The PowerProtect Data Manager Administration and User Guide provides more information.

Steps
1. In the left navigation pane, select Protection > Protection Policies.
The Protection Policies window appears.

Managing Storage, Assets, and Protection 37

2. Click Add.
The Add Policy wizard appears.
3. On the Type page, specify the new protection policy group fields, and then click Next:
● Name—Type a descriptive name for the protection policy, for example, Oracle Prod Databases.

NOTE: The name that you specify becomes part of the Data Domain MTree entry.
● Description—Type a short description for the protection policy, for example, Oracle Prod Daily Backups.
● Type—Select Oracle.
4. On the Purpose page, select from the following options to indicate the purpose of the new protection policy group, and
then click Next:
● Centralized Protection—Select this option to use PowerProtect Data Manager to centrally manage all stages of the
protection policy.
Centralized protection means that PowerProtect Data Manager schedules the backups and manages the life cycle of the
copies.
Click Set Credentials to specify new credentials or select existing credentials from the list. Authentication requirements
on page 25 provides details about the authentication requirements for an Oracle database.
NOTE: Policy-level credentials are mandatory. Credentials that you set at the asset level and host level take
precedence over the credentials that you set at the protection policy level. Asset-level credentials have the highest
precedence.
● Self-Service Protection—Select this option to use Oracle to create local backup protection. PowerProtect Data
Manager creates a protection policy and manages extra stages.
Self-service protection means that DBAs schedule the backups but PowerProtect Data Manager discovers and manages
the life cycle of the copies.
● Exclusion—Select this option when the protection policy contains Oracle assets that you want to exclude from data
protection operations.
5. On the Assets page, select the unprotected assets that you want to add to the backup of this protection policy group. The
window enables you to filter by asset name to locate the required assets.
You can also change the assets view to display all assets discovered by PowerProtect Data Manager or a hierarchical view
with the assets in a tree structure underneath the application host. For example, a hierarchical view might be helpful when
you have added multiple Oracle databases, so that you can more easily identify which assets belong to which database.
6. Click Next.
If you selected Exclusion on the Purpose page, the Summary page appears. Proceed to Step 15.
If you selected Centralized Protection or Self-Service Protection on the Purpose page, the Objectives page appears
for creating the protection policy backup configuration.

7. On the Objectives page, select a policy-level Service Level Agreement (SLA) from the Set Policy Level SLA list, or select
Add to open the Add Policy Service Level Agreement wizard and create a new policy-level SLA.
Add a Service Level Agreement on page 42 provides instructions.
8. Complete the required steps for the specified type of protection policy group:
● For Centralized Protection:
a. Click Add under Primary Backup.
The Add Primary Backup dialog appears.
b. On the Target pane of the Add Primary Backup dialog, specify the following fields:
○ Storage Name—Select a backup destination from the list of existing DD systems, or select Add to add a system
and complete the details in the Storage Target dialog.
○ Storage Unit—Select whether this protection policy should use a New storage unit on the selected DD system,
or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for
available capacity and total capacity, for example, testvmplc-ppdm-daily-123ab (300 GB/1 TB).
When you select New, a new storage unit in the format policy name hostname unique identifier is created in the
storage system upon policy completion, for example, testvmplc-ppdm-daily-123cd.
NOTE: The Space field indicates the total amount of space, and the percentage of available space, on the
storage system.

38 Managing Storage, Assets, and Protection

 ○ Network Interface—Select a network interface from the list, if applicable.
○ Retention Lock—Move the Retention Lock slider to the right to enable retention locking for these backups on
the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that
the lock can be reverted at any time if necessary. Toggling the Retention Lock slider on or off applies to the
current backup copy only, and does not impact the retention lock setting for existing backup copies.
○ SLA—Select an existing service level agreement that you want to apply to this schedule from the list, or select
Add to create an SLA within the Add Backup Service Level Agreement wizard.
Add a Service Level Agreement on page 42 provides instructions.
c. On the Schedules pane of the Add Primary Backup dialog:
i. Specify the following fields to schedule the full backup of this protection policy:
○ Create a Full backup every—Specify how often to create a full backup.
○ Retain for—Specify the retention period for the backup.
You can extend the retention period for the latest primary backup copy by using the Extend Retention
schedule. For example, your regular schedule for daily backups can use a retention period of 30 days, but
you can apply extended retention to keep the full backups taken on Mondays for 10 weeks. Step 9 on page
40 provides instructions.
NOTE: For database backups, PowerProtect Data Manager chains the dependent backups together. For
example, the incremental or transaction log backups are chained to their base full backup. The backups do
not expire until the last backup in the chain expires. This ensures that all incremental and transaction log
backups are recoverable until they have all expired.
○ Start and End—The activity window. Specify a time of day to start the full backup, and a time of day after
which backups cannot be started.

NOTE: Any backups started before the End Time occurs continue until completion.
ii. Click Add Backup if you want to add an incremental cumulative, incremental differential, or log backup, and then
specify the following fields to schedule the backup of this protection policy:

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

○ Create a <backup_type> backup every—For <backup_type> , select Incremental Cumulative,

Incremental Differential, or Log from the drop-down list, and then specify the interval at which the backup
job runs within the window that you specify. The backup interval depends on the backup interval of the full
backup schedule:
￭ If the full backup schedule is hourly or daily, the backup interval of subsequent backup levels can be
between 1 and 12 hours or between 1 and 60 minutes.
￭ If the full backup schedule is weekly or monthly, the backup interval of subsequent backup levels can be
daily, between 1 and 12 hours, or between 1 and 60 minutes.
○ Retain for—The retention period is the time that you set for the full backup schedule in the preceding step.
○ Start and End—The activity window. Specify a time of day to start the backup, and a time of day after which
backups cannot be started.

NOTE: Any backups started before the End Time occurs continue until completion.
d. Click Save to save your changes and return to the Objectives page.
The Objectives page updates to display the name and location of the target storage system under Primary Backup.
NOTE:

After completing the backup schedule, you can change any schedule details by clicking Edit under Primary
Backup.

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 and End times, the backup runs right away, regardless of the date. If the current
time is not within the scheduled Start and End times, the backup does not start until the next time that backups
are configured to run.

Managing Storage, Assets, and Protection 39

 ● For Self-Service Protection:
a. Click Add under Primary Retention.
The Add Primary Retention dialog appears.
b. On the Target pane of the Add Primary Retention dialog, specify the following fields:
○ Storage Name—Select a backup destination from the list of existing DD systems, or select Add to add a system
and complete the details in the Storage Target dialog.
○ Storage Unit—Select whether this protection policy should use a New storage unit on the selected DD system,
or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for
available capacity and total capacity, for example, testvmplc-ppdm-daily-123ab (300 GB/1 TB).
When you select New, a new storage unit in the format policy name hostname unique identifier is created in the
storage system upon policy completion, for example, testvmplc-ppdm-daily-123cd.
NOTE: The Space field indicates the total amount of space, and the percentage of available space, on the
storage system.
○ Network Interface—Select a network interface from the list, if applicable.
○ Retention Lock—Move the Retention Lock slider to the right to enable retention locking for these backups on
the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that
the lock can be reverted at any time if necessary. Toggling the Retention Lock slider on or off applies to the
current backup copy only, and does not impact the retention lock setting for existing backup copies.
○ SLA—Select an existing service level agreement that you want to apply to this schedule from the list, or select
Add to create an SLA within the Add Backup Service Level Agreement wizard.
Add a Service Level Agreement on page 42 provides instructions.
c. On the Retentions pane of the Add Primary Retention dialog, specify the retention time in the Retain for field.
d. Click Save to save your changes and return to the Objectives page.
The Objectives page updates to display the name and location of the target storage system under Primary
Retention.
NOTE: After completing the backup retention setting, you can change the setting by clicking Edit under
Primary Retention.
9. Optionally, extend the retention period for the latest primary backup copy:
Extended retention on page 44 provides more information.
a. Click Extend Retention next to Primary Backup or Primary Retention. An entry for Extend Retention is created
below Primary Backup or Primary Retention.
b. Under Extend Retention, click Add. The Add Extended Retention dialog appears.
c. Retain the next scheduled full copy every—Specify the preferred recurrence for the extended retention backup
schedule.
d. Repeat on—Depending on the frequency of the backup schedule, specify the day of the week, the date of the month, or
the date of the year that the extended retention backup will occur.
e. Retain for—Specify the retention period for the backup. You can retain an extended retention for a maximum of 70
years.
f. Click Save to save your changes and return to the Objectives page.
10. Optionally, replicate the backups to a remote storage system:
a. Click Replicate next to Primary Backup, Primary Retention, or Extend Retention. An entry for Replicate is created
to the right of the primary or extended retention backup schedule.
NOTE: PowerProtect Data Manager supports replicating an extended retention backup only if the primary backup
already has one or more replication stages. Also, for replication of an extended retention backup, you can only select
the DDs that are used by the replication stages based on the primary stage.

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

● Replicate1 based on the primary backup is replicated to DD002

● Replicate2 based on the primary backup is replicated to DD003
● Extended retention backup is backed up to DD001
● Replicate3 based on the extended retention backup must be replicated to DD002 or DD003.

40 Managing Storage, Assets, and Protection

 b. Under Replicate, click Add. The Add Replication dialog appears.
NOTE: To enable replication, ensure that you add a remote DD system as the replication location. Add protection
storage on page 33 provides detailed instructions about adding a remote DD system.

c. Complete the schedule details in the Add Replication dialog, and then click Save to save your changes and return to the
Objectives page.
NOTE: The schedule frequency can be every day, week, month, or x hours for replication of the primary backup,
and every day, week, month, year, or x hours for replication of the extended retention backup. For daily, weekly, and
monthly schedules, the numeric value cannot be modified. For hourly, however, you can edit the numeric value. For
example, if you set Create a Full backup every 4 hours, you can set a value of 1 to 12 hours.

11. Optionally, add a cloud stage for a primary, replication, or extended retention backup schedule for the purpose of moving
backups from DD storage to cloud tier:
a. Click Cloud Tier next to Primary Backup or Extend Retention or, if adding a cloud stage for a replication schedule
that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary or
extended retention backup schedule, or below the replication schedule.
b. Under the entry for Cloud Tier, click Add.
The Add Cloud Tier Backup dialog appears, with summary schedule information for the parent node to indicate whether
you are adding this cloud tier stage for the primary backup schedule, the extended retention backup schedule, or the
replication schedule.
c. Complete the schedule details in the Add Cloud Tier Backup dialog, and then click Save to save your changes and
return to the Objectives page.
Add a cloud tier schedule to a protection policy on page 53 provides detailed instructions for adding a cloud stage for a
primary, replication, or extended retention backup schedule.
NOTE: In order to move a backup or replica to cloud tier, schedules must have a retention time of 14 days or more. Also,
discovery of a DD system configured with a cloud unit is required.

12. Click Next.

The Options page appears.
13. On the Options page, select the additional options that are required for the policy:
● Archive Logs—Select the appropriate option for the deletion of archived logs:
○ Do not delete—Select this option to prevent the deletion of archived logs during backups. To delete the archived
logs, the database administrator must run the delete command manually.
○ Delete immediately after backup—Select this option to enable the deletion of archived logs immediately after all
the backup types that are performed through the protection policy.
○ Delete older than (days)—Select this option to enable the deletion of the available archived logs that are older
than the specified number of days, for all the backup types that are performed through the protection policy. Set the
number of days after which the archived logs are deleted.
● Troubleshooting—Select this option to enable the debug logs for troubleshooting purposes.
14. Click Next.
The Summary page appears.
15. 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.
16. 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.
17. When PowerProtect Data Manager and the client are upgraded from an older version and the target Data Domain or storage
unit of the Oracle database associated protection policy is changed:
● If the objective of the protection policy includes replication, perform a replication from the Protection Policies page.
Select Protection > Protection Policies > Protect Now and select Replicate now, then change the primary target.
● For a self-service protection policy, complete the procedure for the required top-level directory changes in Performing
self-service backups of Oracle databases on page 56.

Managing Storage, Assets, and Protection 41

Add a Service Level Agreement
The SLA Compliance window in the PowerProtect Data Manager UI enables you to add a service level agreement (SLA) that
identifies your Service Level Objectives (SLOs). You use the SLOs to verify that your protected assets are meeting the Service
Level Agreements (SLAs).

About this task

NOTE: When you create an SLA for Cloud Tier, you can include only full backups in the SLA.

Steps
1. From the PowerProtect Data Manager UI, select Protection > SLA Compliance.
The SLA Compliance window displays with the following information:
● SLA Name
● Stage Type
● Policies At Risk
● Objectives Out of Compliance
● Impacted Assets
2. Select the type of asset for which you want to add the SLA, and click Add.
The Add Service Level Agreement Type window appears.
3. Select the type of SLA that you want to add, and then click Next.
● Policy. If you choose this type, go to step 4.
● Backup. If you choose this type, go to step 5.
● Extended Retention. If you choose this type, go to step 6.
● Replication. If you choose this type, go to step 7.
● Cloud Tier. If you choose this type, go to step 8.
You can select only one type of Service Level Agreement.
4. If you selected Policy, specify the following fields regarding the purpose of the new Policy SLA:
a. The SLA Name.
b. If applicable, select Minimum Copies, and specify the number of Backup and Replication copies.
c. If applicable, select Maximum Copies, and specify the number of Backup and Replication copies.
d. If applicable, select Available Location and select the applicable locations. To add a location, click Add Location.
Options include the following:
● In—Include locations of all copies in the SLO locations. Selecting this option does not require every SLO location to
have a copy.
● Must In—Include locations of all copies in the SLO locations. Selecting this option requires every SLO location to
have at least one copy.
● Exclude—Locations of all copies must be non-SLO locations.
e. Click Finish, and then go to step 9.
5. If you selected Backup, specify the following fields regarding the purpose of the new Backup SLA:
a. The SLA Name.
b. If applicable, select Recovery Point Objective (RPO), and then set the duration. The purpose of an RPO is business
continuity planning, and indicates the maximum targeted period in which data (transactions) might be lost from an IT
service due to a major incident.
NOTE: You can select only Recovery Point Objective to configure as an independent objective in the SLA, or
select both Recovery Point Objective and Compliance Window. If you select both, the RPO setting must be one
of the following:
● Greater than 24 hours or more than the Compliance window duration, in which case RPO validation occurs
independent of the Compliance Window.
● Less than or equal to the Compliance Window duration, in which case RPO validation occurs within the
Compliance Window.

c. If applicable, select Compliance Window for copy type, and then select a schedule level from the list (for example,
All, Full, Cumulative) and set the duration. Duration indicates the amount of time necessary to create the backup

42 Managing Storage, Assets, and Protection

 copy. Ensure that the Start Time and End Time of backup copy creation falls within the Compliance Window duration
specified.
This window specifies the time during which you expect the specified activity to take place. Any specified activity that
occurs outside of this Start Time and End Time triggers an alert.
d. If applicable, select the Verify expired copies are deleted option.
Verify expired copies are deleted is a compliance check to see if PowerProtect Data Manager is deleting expired
copies. This option is disabled by default.
e. If applicable, set the Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.
f. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default.
g. Click Finish, and go to step 9.
The SLA Compliance window appears with the new SLA.
6. If you selected Extended Retention, specify the following fields regarding the purpose of the new Extended Retention SLA:
a. The SLA Name.
b. If applicable, specify the Recovery Point Objective.
c. If applicable, select the Verify expired copies are deleted option.
Verify expired copies are deleted is a compliance check to see if PowerProtect Data Manager is deleting expired
copies. This option is disabled by default.
d. If applicable, set the Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.
e. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default.
f. Click Finish, and go to step 9.
The SLA Compliance window appears with the newly added SLA.
7. If you selected Replication, specify the following fields regarding the purpose of the new Replication SLA:
a. The SLA Name.
b. If applicable, select the Compliance Window, and specify the Start Time and End Time.
This window specifies the times that are permissible and during which you can expect the specified activity to occur. Any
specified activity that occurs outside of this start time and end time triggers an alert.
c. If applicable, select the Verify expired copies are deleted option.
Verify expired copies are deleted is a compliance check to see if PowerProtect Data Manager is deleting expired
copies. This option is disabled by default.
d. If applicable, set the Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.
e. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default.
f. Click Finish, and go to step 9.
The SLA Compliance window appears with the newly added SLA.
8. If you selected Cloud Tier type SLA, specify the following fields regarding the purpose of the new Cloud Tier SLA:
a. The SLA Name.
b. If applicable, select the Verify expired copies are deleted option.
This option is a compliance check to see if PowerProtect Data Manager is deleting expired copies. This option is disabled
by default.
c. If applicable, set the Retention Time Objective and specify the number of Days, Months, Weeks, or Years.
d. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default.
e. Click Finish.
9. Add the SLA to the protection policy. Select Protection > Protection Policy.
10. In the Objectives section of the Summary window, click Edit.
11. Do one of the following, and then click Next:
● Select the added Policy SLA from the Set Policy Level SLA list.
● Create and add the SLA policy from the Set Policy Level SLA list.
The Summary window appears.
12. Click Finish.
An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy.
13. Click Go to Jobs to open the Jobs window to monitor the backup and compliance results, or click OK to exit.
NOTE: Compliance checks occur automatically every day at 2 a.m. Coordinated Universal Time (UTC).

14. In the Jobs window, click next to an entry to view details on the SLA Compliance result.

Managing Storage, Assets, and Protection 43

Extended retention
You can extend the retention period for the primary backup copy for long term retention. For example, your regular schedule for
daily backups can use a retention period of 30 days, but you can extend the retention period to keep the full backups taken on
Mondays for 10 weeks.
Both centralized and self-service protection policies support weekly, monthly, and yearly recurrence schedules to meet the
demands of your compliance objectives. For example, you can retain the last full backup containing the last transaction of a
fiscal year for 10 years. When you extend the retention period of a backup in a protection policy, you can retain scheduled full
backups with a repeating pattern for a specified amount of time.
For example:
● Retain full yearly backups that are set to repeat on the first day of January for 5 years.
● Retain full monthly backups that are set to repeat on the last day of every month for 1 year.
● Retain full yearly backups that are set to repeat on the third Monday of December for 7 years.

Preferred alternatives
When you define an extended retention stage for a protection policy, you define a set of matching criteria that select preferred
backups to retain. If the matching criteria do not identify a matching backup, PowerProtect Data Manager automatically retains
the preferred alternative backup according to one of the following methods:
● Look-back—Retain the last available full backup that was taken before the matching criteria.
● Look-forward—Retain the next available full backup that was taken after the matching criteria.
For example, consider a situation where you configured a protection policy to retain the daily backup for the last day of the
month to extended retention. However, a network issue caused that backup to fail. In this case, look-back matching retains the
backup that was taken the previous day, while look-forward matching retains the backup that was taken the following day.
By default, PowerProtect Data Manager uses look-back matching to select the preferred alternative backup. A grace period
defines how far PowerProtect Data Manager can look in the configured direction for an alternative backup. If PowerProtect
Data Manager cannot find an alternative backup within the grace period, extended retention fails.
You can use the REST API to change the matching method or the grace period for look-forward matching. The API
documentation at https://developer.dellemc.com provides instructions. If there are no available backups for the defined
matching period, you can change the matching method to a different backup.
For look-forward matching, the next available backup can be an ad-hoc backup or the next scheduled backup.

Selecting backups by weekday

This section applies to centralized protection policies. Self-service protection policies have no primary backup schedule
configuration.
When you configure extended retention to match backups by weekday, PowerProtect Data Manager may identify a backup that
was taken on one weekday as being taken on a different weekday. This behavior happens where the backup window does not
align with the start of the day. PowerProtect Data Manager identifies backups according to the day on which the corresponding
backup window started, rather than the start of the backup itself.
For example, consider a backup schedule with an 8:00 p.m. to 6:00 a.m. backup window:
● Backups that start at 12:00 a.m. on Sunday and that end at 6:00 a.m. on Sunday are identified as Saturday backups, since
the backup window started on Saturday.
● Backups that start at 8:01 p.m. on Sunday and that end at 12:00 a.m. on Monday are identified as Sunday backups, since the
backup window started on Sunday.
● Backups that start at 12:00 a.m. on Monday and that end at 6:00 a.m. on Monday are identified as Sunday backups, since
the backup window started on Sunday.
In this example, when you select Sunday backups for extended retention, PowerProtect Data Manager does not retain backups
that were taken between 12:00 a.m. and 8:00 p.m. This behavior happens even though the backups occurred on Sunday.
Instead, PowerProtect Data Manager selects the first available backup that started after 8:00 p.m. on Sunday for extended
retention.
If no backups were created between 8:01 p.m. on Sunday and 6:00 a.m. on Monday, PowerProtect Data Manager retains the
next alternative to extended retention. In this example, the alternative was taken after 6:00 a.m. on Monday.

44 Managing Storage, Assets, and Protection

Extended retention backup behavior
When PowerProtect Data Manager identifies a matching backup, automatic extended retention creates a job at the beginning of
the backup window for the primary stage. This job remains queued until the end of the backup window and then starts.
The following examples describe the behavior of backups with extended retention for centralized and self-service protection.

Centralized protection
For an hourly primary backup schedule that starts on Sunday at 8:00 p.m. and ends on Monday at 6:00 p.m. with a weekly
extended retention schedule that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup
starting after 8:00 p.m. on Sunday for long-term retention.
The following diagram illustrates the behavior of backups with extended retention for a configured protection policy. In this
example, full daily backups starting at 10:00 p.m. and ending at 6:00 a.m. are kept for 1 week. Full weekly backups are set to
repeat every Sunday and are kept for 1 month.

Figure 1. Extend retention backup behavior

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

Edit the retention period for backup copies

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

About this task

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

Steps
1. Select Infrastructure > Assets.
2. From the Assets window, select the tab for the asset type for which you want to edit the retention period. If a policy has
been assigned, the table lists the assets that have been discovered, along with the associated protection policy.
3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the
backups are stored.
4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists
the backup copies.
5. Select one or more backup copies from the table, and click Edit Retention.

Managing Storage, Assets, and Protection 45

6. Select one of the following options:
● To select a calendar date as the expiration date for backups, select Retention Date.
● To define a fixed retention period in days, weeks, months, or years after the backup is performed, select Retention
Value. For example, you can specify that backups expire after 6 months.
NOTE: When you edit the retention period for copies that are retention locked, you can only extend the retention
period.

7. When satisfied with the changes, click Save.

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

Delete backup copies

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

About this task

If you no longer require a backup copy and the retention lock is not enabled, you can delete backup copies prior to their
expiration date.
Starting with PowerProtect Data Manager version 19.6, you can perform a backup copy deletion that deletes only a specified
part of a backup copy chain, without impacting the ability to restore other backup copies in the chain. When you select a
specific backup copy for deletion, only that backup copy and the backup copies that depend on the selected backup copy are
deleted:
● When you select to delete a full backup copy, any other backup copies in the chain that depend on the full backup copy are
also deleted.
● When you select to delete a cumulative backup copy, any differential backup copies that depend on the selected cumulative
backup copy are also deleted. The whole backup chain is not deleted.
● When you select to delete a differential backup copy, any other differential backup copies that depend on the selected
differential backup copy are also deleted. The whole backup chain is not deleted.
● When you select to delete a log backup copy, any other log backup copies that depend on the selected log backup copy are
also deleted. The whole backup chain is not deleted.
● When you select to delete all log backup copies without selecting any full, cumulative, or differential backup copies, the log
backup copies that the full, cumulative, and differential backup copies depend on are automatically excluded from deletion.
Regarding expired copy deletion for a backup chain, the full backup and its dependent log backups expire last. The other
cumulative, differential, and non-dependent log backups can be expired and deleted earlier:
● The full backup expires only when every other backup in the chain has expired.
● A cumulative backup expires only when all the differential backups that depend on it have expired.
● A differential backup expires when its retention time expires.
● A non-dependent log backup expires only when all the log backups that depend on it have expired.
● A dependent log backup expires only when all the full, cumulative, differential, and log backups that depend on it have
expired.

Steps
1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.
2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been
assigned, the table lists the assets that have been discovered, along with the associated protection policy.
3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the
backups are stored.
4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists
the backup copies.
5. Select one or more copies from the table that you want to delete from the DD system, and then click Delete.
A preview window opens and displays the selected backup copies and all the backup copies that depend on the selected
backup copies.

46 Managing Storage, Assets, and Protection

 NOTE: If you delete a backup copy, PowerProtect Data Manager deletes the specified backup copy and all backup
copies that depend on the specified backup copy.
6. For all asset types, you can choose to keep the latest backup copies or delete them. By default, PowerProtect Data Manager
keeps the latest backup copies. To delete the latest backup copies, clear the check box next to Include latest copies.
7. To delete the backup copies, in the preview window, click Delete.
NOTE: The delete operation may take a few minutes and cannot be undone.

An informational dialog box opens to confirm the copies are being deleted. To monitor the progress of the operation, click Go
to Jobs. To view the list of backup copies and their status, click OK.
When the job completes, the task summary provides details of each deleted backup copy, including the time that each copy
was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC.
An audit log is also generated and provides details of each deleted backup copy, including the time that each copy was
created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC. Go to
Alerts > Audit Logs to view the audit log.
8. Verify that the copies are deleted successfully from the DD system. If the deletion is successful, the deleted copies no longer
appear in the table.

Retry a failed backup copy deletion

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

Steps
1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.
2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been
assigned, the table lists the assets that have been discovered, along with the associated protection policy.
3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the
backups are stored.
4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists
the backup copies.
5. Select one or more backup copies with the Deletion Failed status from the table, and then click Delete.
You can also filter and sort the list of backup copies by status in the Copy Status column.
The system displays a warning to confirm you want to delete the selected backup copies.
6. Click OK.
An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation,
click Go to Jobs. To view the list of backup copies and their status, click OK.
7. Verify that the copies are successfully deleted from the DD system. If the deletion is successful, the deleted copies no longer
appear in the table.

Export data for deleted backup copies

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

Steps
1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.
2. From the Assets window, select the tab for the asset type for which you want to export results of deleted backup copies. If
a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.
3. Select one or more protected assets from the table and then select More Actions > Export Deleted Copies.
If you do not select an asset, PowerProtect Data Manager exports the data for deleted backup copies for all assets for the
specific asset type.
4. Specify the following fields for the export:
a. Time Range
The default is Last 24 Hours.

Managing Storage, Assets, and Protection 47

 b. Copy Status
In order to export data for deleted backup copies, the backup copies must be in one of the following states:
● Deleted—The copy is deleted successfully from the DD, and, if applicable, the agent catalog is deleted successfully
from the agent host.
● Deleting—Copy deletion is in progress.
● Deletion Failed—Copy deletion from the DD is unsuccessful.
● Deletion Failed (Agent Catalog)—The copy is deleted successfully from the DD, but is not deleted from the agent
host.
NOTE: This state is not applicable to virtual machine and Kubernetes backup copies.

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

5. Click Download.
If applicable, the navigation window appears for you to select the location to save the CSV file.
6. Save the CSV file in the desired location and click Save.

Remove backup copies from the PowerProtect Data Manager

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

About this task

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

Steps
1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.
2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been
assigned, the table lists the assets that have been discovered, along with the associated protection policy.
3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the
backups are stored.
4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists
the backup copies.
5. Select one or more backup copies with the Deletion Failed or Deletion Failed (Agent Catalog) status from the table, and
then click Remove from PowerProtect.
For backup copies with the Deletion Failed (Agent Catalog) status, click Remove from PowerProtect to remove the
information from PowerProtect Data Manager for any backup copies that were successfully deleted from the DD system but
for which the agent catalog was not deleted from the agent host.
The system displays a warning to confirm you want to delete the selected backup copies.
6. Click OK.
An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation,
click Go to Jobs. To view the list of backup copies and their status, click OK.
7. Verify that the copies are deleted from the PowerProtect Data Manager database. If the deletion is successful, the deleted
copies no longer appear in the table. The backup copies remain in the DD system.

Troubleshooting the PowerProtect RMAN operation

If a self-service backup fails with the following type of error, you must complete the required top-level directory changes:

Reason for failure: orcl failed due to error message: The backup operation failed for
the instance 'orcl' with dbid '1585115093' due to the following error: RMAN-03009:
failure of Control File and SPFILE Autobackup command on CH0 channel at 12/09/2020
13:16:52

48 Managing Storage, Assets, and Protection

 ORA-19502: write error on file "c-1585115093-20201209-06", block number 1 (block
size=16384)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
sbtwrite2:The top-level pathname must be specified in backup piece format for assets
configured with PowerProtect Data Manager.
Recovery Manager complete.

To resolve this type of error for a self-service backup, complete the procedure in Performing self-service backups of Oracle
databases on page 56.

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 <agent_service_installation_location> to represent the PowerProtect agent service installation
directory. By default, the agent service installation location is /opt/dpsapps/agentsvc on Linux. All files that are referenced
in this section are the relative paths to the agent service installation location.
The PowerProtect agent service performs the following operations:
● Addon detection—An 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.
● Discovery—The agent service discovers both stand-alone and clustered database servers (application systems), databases
and file systems (assets), and their backup copies on the application agent host. After the initial discovery, when the agent
service discovers any new application systems, assets, or copies, the agent service notifies the PowerProtect Data Manager.
● Self-service configuration—The agent service can configure the application agent for self-service operations by using
information that is provided by the PowerProtect Data Manager. When you add an asset to a protection policy for
self-service or centralized protection, or modify the protection policy, including changing the DD Boost credentials, the
PowerProtect Data Manager automatically pushes the protection configuration to the agents.
● Centralized backups—The agent service performs the centralized backups as requested by the PowerProtect Data
Manager.
● Centralized restores—The agent service performs the centralized restores as requested by the PowerProtect Data
Manager.
NOTE: In the current release, the centralized restores are only available for the File System agent, Microsoft SQL agent,
and Storage Direct agent.
● Backup deletion and catalog cleanup—The PowerProtect Data Manager deletes the backup files directly from the protection
storage when a backup expires or an explicit delete request is received and no dependent (incremental or log) backups exist.
The PowerProtect Data Manager goes through the agent service to delete the catalog entries from the database vendor's
catalog and the agent's local datastore.
NOTE: Deletion of any backup copies manually or through the command line is not recommended. PowerProtect Data
Manager deletes all the expired copies as needed.
The agent service is started during the agent installation by the installer. The agent service runs in the background as a service
and you do not interact with it directly.
The config.yml file contains the configuration information for the agent service, including several parameter settings that
you can change within the file. The config.yml file is located in the <agent_service_installation_location>
directory.

Managing Storage, Assets, and Protection 49

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 <agent_service_installation_location>/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 <agent_service_installation_location>/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
<agent_service_installation_location> directory.
● To start the agent service:

# register.sh --start

Started agent service with PID - 1234

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

# service agentsvc start

● To stop the agent service:

# register.sh --stop

Successfully stopped agent-service.

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

# service agentsvc stop

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

# register.sh --status

Agent-service is running with PID - 1234

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

# register.sh --status

Agent-service is not running.

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

# service agentsvc status

Troubleshoot the PowerProtect agent service operations

To troubleshoot the agent service operations, you can check the agent service log file OpAgentSvc-
<timestamp>.log, which is created in <agent_service_installation_location>\logs on Windows and
<agent_service_installation_location>/logs on Linux. To modify the log level and retention of temporary files,
you can modify specific parameter settings in the config.yml file.

50 Managing Storage, Assets, and Protection

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

Steps
1. Stop the agent service by using the appropriate procedure from the preceding topic.
2. Open the config.yml file in an editor.
3. Modify the log-level settings in the following parameters, as required:
NOTE: These parameters are listed in order of decreasing number of messages in the debug information output. The
default log-level is INFO.

● DEBUG
● INFO
● WARNING
● ERROR
● CRITICAL
4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.
NOTE: The agent service and application agent communicate through the temporary files, which are typically deleted
after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True
permanently, or the temporary files can use excessive space on the file system.

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

Register the PowerProtect agent service to a different server

address on Linux
The PowerProtect agent service is registered to a particular PowerProtect Data Manager server during the agent installation by
the installer. If needed, you can register the agent service to a different PowerProtect Data Manager server address. If there
are multiple agents installed on a host, all agents will be re-registered to the new PowerProtect server.
The agent service can only be registered to a single PowerProtect Data Manager server.
On Linux, perform the following steps to register the agent service to a different server address.
1. To unregister from the current PowerProtect Data Manager server, go to the /opt/dpsapps/agentsvc directory and
run the unregister.sh script.
2. In the dbs/v1 directory, rename the copies.db file to copies-backup.db.
3. To register the agent service to the different server address, go to the /opt/dpsapps/agentsvc directory, run the
register.sh script, and provide the PowerProtect Data Manager server IP address or hostname:
● The following command prompts for the new IP address or hostname:

# register.sh

Enter the PowerProtect Data Manager IP address or hostname: 10.0.0.1

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234

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

# register.sh --ppdmServer=10.0.0.1

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234

4. Verify that the agentsvc process is started.

5. Verify the agent registration status:
a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

Managing Storage, Assets, and Protection 51

 b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is
Registered.
6. To perform asset discovery for the agent:
a. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources.
The Asset Sources window appears.
b. Select the tab for your application agent or file system host.
c. Select the agent hostname and click Discover. At the confirmation prompt, click Yes.
When you select Infrastructure > Assets, the Assets window displays the discovered assets.

Recovering the PowerProtect agent service from a disaster

You can perform self-service restores of application assets by using a file system or application agent, regardless of the state of
the agent service or PowerProtect Data Manager. The information in the this section describes how to bring the agent service
to an operational state to continue if a disaster occurs and the agent service datastore is lost.
The agent service periodically creates a backup of its datastore in the
<agent_service_installation_location>/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 <agent_service_installation_location>/dbs/v1/backups repository. The subdirectories are named after the
time the operation occurred, in the format YYYY-MM-DD_HH-MM-SS_epochTime.
By default, the datastore repository is on the local disk. To ensure that the agent service datastore and its local backups are not
lost, it is recommended that you back up the datastore through file system backups. You can also change the datastore backup
location to a different location that is not local to the system. To change the datastore backup location, update the values in the
config.yml file.

Restore the PowerProtect Data Manager agent service datastore

Prerequisites

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

About this task

You can restore the datastore from the datastore backup repository. If the repository is no longer on the local disk, restore the
datastore from file system backups first.
To restore the datastore from a backup in the datastore backup repository, complete the following steps:

Steps
1. Move the files in the <agent_service_installation_location>/dbs/v1 directory to a location for safe keeping.
NOTE: Do not move or delete any <agent_service_installation_location>/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 <agent_service_installation_location>/dbs/v1
directory.
After the copy operation is complete, the <agent_service_installation_location>/dbs/v1 directory should
contain the following files:
● copies.db
● objects.db

52 Managing Storage, Assets, and Protection

 ● resources.db
● sessions.db
4. Start the agent service.

Manage the cloud tier operations with PowerProtect

Data Manager
The PowerProtect Data Manager cloud tier feature works in tandem with the Data Domain Cloud Tier feature to move
PowerProtect Data Manager backups from Data Domain systems to the cloud. This provides long-term storage of PowerProtect
Data Manager backups by seamlessly and securely tiering data to the cloud.
From the PowerProtect Data Manager UI, you configure cloud tier to move PowerProtect Data Manager backups from Data
Domain to the cloud, and you can perform seamless recovery of these backups.
Data Domain cloud storage units must be pre-configured on the Data Domain system before they are configured for cloud tier in
the PowerProtect Data Manager UI. The Data Domain Operating System Administration Guide provides more information.

Add a cloud tier schedule to a protection policy

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

Prerequisites
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
primary, replication, and extended retention stages. Schedules must have a retention time of 14 days or more.
Cloud tiering happens at 00:00 UTC each day. Depending on your time zone, this time may be within business hours and
thus cloud tiering may impact available network bandwidth. Cloud tiering applies to both centralized and self-service protection
policies.

Steps
1. Log in to PowerProtect Data Manager with administrator credentials.
2. From the PowerProtect Data Manager UI, select Protection > Protection Policies, and then click Add.
The Add Policy wizard appears.
3. On the Type page, enter a name and description, select 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 Objectives page, click Add under Primary Backup if the primary backup schedule is not already created, and fill out
the fields in the Target and Schedules panes on the Add Primary Backup dialog.
NOTE: There is no minimum recurrence required for the cloud stage. However, the cloud tier schedule requires a
minimum retention period of 14 days in the Retain for field.

7. Click Cloud Tier next to Primary Backup or Extend Retention or, if adding a cloud stage for a replication schedule that
you have added, click Cloud Tier under Replicate.
An entry for Cloud Tier is created to the right of the primary or extended retention backup schedule, or below the
replication schedule.
8. Under the entry for Cloud Tier, click Add.
The Add Cloud Tier Backup dialog appears, with summary schedule information for the parent node. This information
indicates whether you are adding this cloud tier stage for the primary backup schedule, the extended retention schedule, or
the replication schedule.
9. In the Add Cloud Tier Backup dialog box, set the following parameters and then click Save:
● Select the appropriate storage unit from the Cloud Target list.

Managing Storage, Assets, and Protection 53

 ● For Tier After, set a time of 14 days or more.
The protection policy schedule is now enabled with cloud tiering.
10. Click Next to proceed with the remaining pages of the Add Policy wizard, verify the information, and then click Finish.
A new job is created, which you can view under the Jobs tab after the job completes.

Tier the PowerProtect Data Manager backups from 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.

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

54 Managing Storage, Assets, and Protection

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

Prerequisites

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

Steps
1. Select Recovery > Assets, click Data Domain, and then select one of the available copies in the table with the location as
Cloud.
2. Click Recall, and then specify how long to keep the copy on the active tier.
A job is created to recall the backup copy from the cloud tier for the selected asset. The copy moves from the cloud tier, and
the status changes from Cloud to Local_Recalled. Then you can perform the restore from the local host.
3. To change the retention period for the recalled copy, 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 55

 4
Performing Self-Service Backups of Oracle
Databases
Topics:
• Performing self-service backups of Oracle databases
• Restore an Oracle application host

Performing self-service backups of Oracle databases

To enable self-service protection, when you create the Oracle protection policy, select Self-Service Protection.
NOTE:

For clients that are configured with a self-service protection policy, you must perform each type of data backup (full,
incremental, cumulative) in a separate RMAN session. You can perform the archived log, spfile, and controlfile backups
either with the data backups or in separate RMAN sessions.

When you perform the different types of data backups in the same RMAN session, the backups are reported incorrectly.
To perform a self-service or manual backup of an Oracle database, you must create and run an RMAN backup script. The
following example shows how to generate the backup scripts.
To identify the storage unit and Data Domain hostname, run the ddutil -s command on the Oracle client. For example, run
the following command in the $RMAN_AGENT_HOME/bin directory:

./ddutil -s

Only if the autobackup is enabled for the protected database and you have created a self-service protection policy for Oracle,
complete the required top-level directory changes:
1. Log in to the Oracle host as an Oracle user.
2. To obtain the top-level directory information, run the following command:

/home/oracle/opt/dpsapps/rmanagent/ddutil -s

Data Domain Hostname: 10.125.136.106

FC Service Name: None

FC Service Enabled: false

Storage Unit: oracle-self_plc-blrv034d018-R-df3c7

Top Level Path: PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522
PLC Name: self_plc

User: oracle-self-blrv034d018-R-df3c7
Type: PROTECTION

3. To complete the changes to the control file configuration for the Oracle database, run the following RMAN command, which
includes the top-level pathname from the ddutil -s command output:

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './

PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

4. Similarly, in the existing backup scripts that you use for backups, change the format specification accordingly. For example:

BACKUP INCREMENTAL LEVEL 0 DATABASE INCLUDE CURRENT CONTROLFILE FORMAT './

PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/OCK/Automated_data_%d_%I_%u_%p';

56 Performing Self-Service Backups of Oracle Databases

 After you complete these changes, all the database backup pieces including the autobackups will be written under the
top-level directory created in the storage unit.
NOTE:

If changing the backup scripts or the control file format is not a feasible option, then create the .disable.tlp
file under the $RMAN_AGENT_HOME/settings directory. Alternatively, add the IGNORE_TLP_SU_DIR=TRUE
environment variable setting in the ALLOCATE CHANNEL command of the existing backup scripts. In both of these
cases, the backup pieces will not be written under the top-level directory created by the protection policy.

In an Oracle RAC environment, create the .disable.tlp file on each node of the system under the
$RMAN_AGENT_HOME/settings directory.
Specify the storage unit and Data Domain hostname 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 archivelog;

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

Performing Self-Service Backups of Oracle Databases 57

To identify the storage unit and Data Domain hostname, 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 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;
recover database;

release channel c1;

release channel c2;
release channel c3;
release channel c4;
}

Restore to an alternate host

You can restore an Oracle backup of a source client for disaster recovery or for a cross-restore to an alternate client host.

About this task

Perform the following steps to complete the restore to an alternate host for disaster recovery or for a cross-restore operation.
NOTE:

To automate these steps, you can run the following script after making any required changes to the Oracle DBID and
autobackup file name. The following steps provide more details.

set DBID =1575537735;

run {

58 Performing Self-Service Backups of Oracle Databases

 startup nomount;
restore spfile from autobackup;
shutdown immediate;
startup nomount;
restore controlfile from autobackup;
alter database mount;
restore database;
recover database until sequence 495;
alter database open resetlogs;
}

Steps
1. To obtain details about the Data Domain host and storage unit that PowerProtect Data Manager has registered with the
Oracle RMAN agent, run the ddutil -s command as the root user or oracle user on the source client host.
a. SSH to the source client host as the oracle user.
b. Run the ddutil -s command from the $RMAN_AGENT_HOME/bin directory. For example:

./ddutil -s

Data Domain Hostname: 10.63.96.240

FC Service Name: None

FC Service Enabled: false

Storage Unit: PLCwlt-blrv136g140-6d974

Top Level Path: PLCTLP-43be371a-37fa-44d1-8351-30eac82e713e

User: PLCwlt-blrv136g140-6d974
Type: PROTECTION

Storage Unit: oracle-replicate_IoGJL-blrv136h018-3d069

Top Level Path: PLCTLP-1d967258-a3fd-4648-8b73-96d570b25a03

User: oracle-replic-blrv136h018-3d069
Type: PROTECTION

Record the DD system hostname or IP address, storage unit name, and DD Boost username.

2. Obtain the DD Boost storage unit password.

a. If required, obtain the PowerProtect Data Manager IP address from the agent-id.yml file in the /opt/dpsapps/
agentsvc directory.
b. Log in to the PowerProtect Data Manager, and complete the steps in View the storage unit password on page 34.
For example, the following command displays the DD Boost storage unit password:

./get_dd_mtree_credential.py rman134-os-blrv027d140-f548a

==============Data Domain MTree credential===============

Full MTree path: /data/col1/rman134-os-blrv027d140-f548a
User name : rman134-os-blrv027d140-f548a
Password : j:;Thu,lj$-2IknO{6L
=========================================================

Record the DD Boost storage unit password.

3. Install the Oracle RMAN agent on the target client.

Install and configure the Oracle RMAN agent on page 14 provides more information.
4. Register the target client lockbox to the source client storage unit.
a. SSH to the target client host as the oracle user.
b. To register the lockbox, run the ddutil -C command from the $RMAN_AGENT_HOME/bin directory. At the command
prompts, type the DD system hostname, storage unit name, and DD Boost username that you recorded from the source
client. For example:

ddutil -C

Data Domain server name: 10.63.96.240

Performing Self-Service Backups of Oracle Databases 59

 Data Domain Storage Unit name: rman134-os-blrv027d140-f548a
DD Boost username: rman134-os-blrv027d140-f548a
Password:
Re-enter password:
Successfully set the DD Boost credentials in the lockbox.

5. Obtain the database identifier (DBID) for the target database.

NOTE: To restore the spfile from the autobackup, you will need to set the DBID for the target database.

a. On the target client, to list the available backups in the storage unit, run the following command:

ddutil -f -z <DD_system>:/<storage_unit_name>

where <DD_system> and <storage_unit_name> are values that you recorded from the source client.
The following type of information appears on the console:

Type Perm Size Time Path

------------------------------------------------------------------------------
file 644 18874368 Fri Aug 7 13:06:31 2020 (1596785791) /<storage-unit-
name>/c-<dbid>-20200807-03
file 644 18874368 Fri Aug 7 13:03:19 2020 (1596785599) /<storage-unit-
name>/c-<dbid>-20200807-02
file 644 18874368 Fri Aug 7 12:47:09 2020 (1596784629) /<storage-unit-
name>/c-<dbid>-20200807-01
file 644 18874368 Fri Aug 7 12:37:39 2020 (1596784059) /<storage-unit-
name>/c-<dbid>-20200807-00
file 644 262144 Fri Aug 7 13:06:29 2020 (1596785789) /<storage-unit-
name>/Automated_spfile_ORCL_<dbid>_14v78u8g_1
file 644 262144 Fri Aug 7 12:37:38 2020 (1596784058) /<storage-unit-
name>/Automated_spfile_ORCL_<dbid>_0hv78sim_1
file 644 262144 Fri Aug 7 13:06:24 2020 (1596785784) /<storage-unit-
name>/Automated_data_ORCL_<dbid>_12v78u81_1
Because you have registered the target client to the storage unit, the backup path contains the DBID as indicated in the
example output. Record the DBID.
If you are performing a cross-restore to an alternate host, you can list the available backups from the source client
instead.

b. If you cannot obtain the DBID because the server is corrupted or because of a disaster, use the PowerProtect Data
Manager REST API.
Alternatively, check the contents of the DD Boost storage unit CIFS or NFS share.
c. If you still cannot obtain the DBID for the database, the Oracle DBA can obtain the DBID from the control file.
6. Create the required folders on the target client.
a. For a cross-restore, ensure that the folder structure on the target client is the same as on the source client.
b. Create the audit file destination at /home/oracle/app/oracle/admin/orcl/adump.
c. Create the recovery file destination at /home/oracle/app/oracle/fast_recovery_area.
d. Create the control file destination at /home/oracle/app/oracle/oradata
Ensure that each folder has the same permissions as the Oracle home path $RMAN_AGENT_HOME/bin.
7. Start the Recovery Manager on the target client.
a. Go to the /home/oracle/<version>/bin/ directory, where <version> is the installed Oracle version.
b. If you have not already done so, run the following command to set the Oracle environment variables:

. oraenv

For the ORACLE_SID variable, type orcl.

For the ORACLE_HOME variable, type /home/oracle/<version>/.

Oracle sets the required environment variables.

c. To start the Recovery Manager with default parameters, run the following command:

rman target /

60 Performing Self-Service Backups of Oracle Databases

 The following type of information appears on the console:

Recovery Manager: Release 19.0.0.0.0 - Production on Mon Aug 10 19:15:06 2020

Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN>

8. To start the Oracle instance with default parameters in the nomount mode, run the following command in Recovery
Manager:

startup nomount;

Later steps retrieve the correct parameter file from the backup.

The following type of information appears on the console:

startup failed: ORA-01078: failure in processing system parameters

LRM-00109: could not open parameter file '/home/oracle/19.3/dbs/initorcl.ora'
starting Oracle instance without parameter file for retrieval of spfile
Oracle instance started

Total System Global Area 1073737800 bytes

Fixed Size 8904776 bytes
Variable Size 276824064 bytes
Database Buffers 784334848 bytes
Redo Buffers 3674112 bytes

9. Set the DBID, and restore the spfile to the $ORACLE_HOME/dbs directory. For example:

RMAN> set DBID=1575537735;

executing command: SET DBID

RMAN> run {
2>
3> ALLOCATE CHANNEL C1 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
4>
5> ALLOCATE CHANNEL C2 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
6>
7> ALLOCATE CHANNEL C3 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
8>
9> ALLOCATE CHANNEL C4 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
10>
11> restore spfile from autobackup;
12>
13> }

using target database control file instead of recovery catalog

allocated channel: Cl
channel Cl: SID=27 device type=SBT_TAPE
channel Cl: Data Domain Boost API

allocated channel: C2
channel C2: SID=28 device type=SBT_TAPE
channel C2: Data Domain Boost API

allocated channel: C3
channel C3: SID=24 device type=SBT_TAPE
channel C3: Data Domain Boost API

Performing Self-Service Backups of Oracle Databases 61

 allocated channel: C4
channel C4: SID=25 device type=SBT_TAPE
channel C4: Data Domain Boost API

Starting restore at 10-AUG-20

channel Cl: looking for AUTOBACKUP on day: 20200810

channel C2: looking for AUTOBACKUP on day: 20200809
channel C3: looking for AUTOBACKUP on day: 20200808
channel C4: looking for AUTOBACKUP on day: 20200807
channel C4: AUTOBACKUP found: c-1575537735-20200807-03
channel C3: skipped, AUTOBACKUP already found
channel Cl: skipped, AUTOBACKUP already found
channel C2: skipped, AUTOBACKUP already found
channel C4: restoring spfile from AUTOBACKUP c-1575537735-20200807-03
channel C4: SPFILE restore from AUTOBACKUP complete
Finished restore at 10-AUG-20
released channel: Cl
released channel: C2
released channel: C3
released channel: C4

10. Verify the restored spfile in the $ORACLE-HOME/dbs directory.

a. Open a second SSH session to the target client Oracle server host as the oracle user.
b. Go to the $ORACLE-HOME/dbs directory.
c. To list the contents of the directory, run the following command:

ls -lrt

The following type of information appears on the console:

total 24
rw-r--r--. 1 oracle oracle 3079 May 14 2015 init.ora
rw-rw----. 1 oracle oracle 1544 Feb 3 2020 hc_orc119.dat
rw-rw----. 1 oracle oracle 1544 Aug 10 18:41 hc_orc119c.dat
rw-rw----. 1 oracle oracle 1544 Aug 10 18:53 hc_orc12.dat
rw-rw----. 1 oracle oracle 1544 Aug 10 19:25 hc_orcl.dat
rw-rw----. 1 oracle oracle 3584 Aug 10 20:35 spfileorcl.ora

d. Verify the contents of the spfile.

e. Close the second SSH session.
11. To shut down the Oracle instance, run the following command:

shutdown immediate;

The following type of information appears on the console:

Oracle instance shut down

12. To restart the Oracle instance with the restored spfile in the nomount mode, run the following command:

startup nomount

The following type of information appears on the console:

connected to target database (not started)

Oracle instance started

Total System Global Area 3741318336 bytes

Fixed Size 9141440 bytes
Variable Size 788529152 bytes
Database Buffers 2936012800 bytes
Redo Buffers 7634944 bytes

62 Performing Self-Service Backups of Oracle Databases

13. Restore the control file from the autobackup. For example:

RMAN> set DBID=1575537735;

executing command: SET DBID

RMAN> run {
2>
3> ALLOCATE CHANNEL C1 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
4>
5> ALLOCATE CHANNEL C2 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
6>
7> ALLOCATE CHANNEL C3 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
8>
9> ALLOCATE CHANNEL C4 TYPE SBT TRACE S PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
10>
11> restore controlfile from autobackup;
12>
13> }

allocated channel: C1
channel C1: SID=36 device type=SBT_TAPE
channel C1: Data Domain Boost API

allocated channel: C2
channel C2: SID=37 device type=SBT_TAPE
channel C2: Data Domain Boost API

allocated channel: C3
channel C3: SID=38 device type=SBT_TAPE
channel C3: Data Domain Boost API

allocated channel: C4
channel C4: SID=39 device type=SBT_TAPE
channel C4: Data Domain Boost API

Starting restore at 19-AUG-20

channel C1: looking for AUTOBACKUP on day: 20200819

channel C2: looking for AUTOBACKUP on day: 20200818
channel C3: looking for AUTOBACKUP on day: 20200817
channel C4: looking for AUTOBACKUP on day: 20200816
channel C4: AUTOBACKUP found: c-1575537735-20200816-9c
channel C3: AUTOBACKUP found: c-1575537735-20200817-Se
channel C2: skipped, AUTOBACKUP already found
channel C1: skipped, AUTOBACKUP already found
channel C4: skipped, AUTOBACKUP already found
channel C3: restoring control file from AUTOBACKUP c-1575537735-20200817-5Se
channel C3: control file restore from AUTOBACKUP complete
output file name=/home/oracle/app/oracle/oradata/ORCL/control01.ctl
output file name=/home/oracle/app/oracle/fast_recovery_area/ORCL/control02.ctl
Finished restore at 19-AUG-20
released channel: Cl
released channel: C2
released channel: C3
released channel: C4

NOTE: When autobackup is disabled, the control files and spfiles are backed up automatically as part of the database
backup. The prefix Automated_controlfile is added in the control file names and Automated_spfile is added
in the spfile names for easy identification. This feature helps with disaster recovery use cases.

Performing Self-Service Backups of Oracle Databases 63

14. To mount the database, run the following command:

RMAN> alter database mount;

The following type of information appears on the console:

Statement processed

15. To restore the database, run the restore database command in Recovery Manager. For example:

RMAN> run {
2>
3> ALLOCATE CHANNEL C1 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
4>
5> ALLOCATE CHANNEL C2 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
6>
7> ALLOCATE CHANNEL C3 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
8>
9> ALLOCATE CHANNEL C4 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
10>
11> restore database;
12>
13> }

released channel: ORA DISK 1

allocated channel: Cl
channel C1: SID=25 device type=SBT_TAPE
channel C1: Data Domain Boost API

allocated channel: C2
channel C2: SID=40 device type=SBT_TAPE
channel C2: Data Domain Boost API

allocated channel: C3
channel C3: SID=28 device type=SBT_TAPE
channel C3: Data Domain Boost API

allocated channel: C4
channel C4: SID=29 device type=SBT_TAPE
channel C4: Data Domain Boost API

Starting restore at 19-AUG-20

new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./

Automated_data_ORCL_1575537735_ndv83dg4_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_ncv83dg4_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_ngv83dgc_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_niv83dgg_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_nfv83dg4_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_nmv83dgj_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_njv83dgg_1"
new media label is "s:10.63.96.240:/rman134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_nhv83dgc_1"

64 Performing Self-Service Backups of Oracle Databases

 new media label is "s:10.63.96.240:/rmani134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_nev83dg4_1"
new media label is "s:10.63.96.240:/rmani134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_nkv83dgh_1"
new media label is "s:10.63.96.240:/rmani134-o0s-blrv027d140-f548a" for piece "./
Automated_data_ORCL_1575537735_nnv83dgj_1"
channel C1: starting datafile backup set restore
channel C1: specifying datafile(s) to restore from backup set
channel C1: restoring datafile 00006 to /home/oracle/app/oracle/oradata/ORCL/pdbseed/
sysaux01.dbf
channel Cl: reading from backup piece ./Automated_data_ORCL_1575537735_nfv83dg4_1
channel C2: starting datafile backup set restore
channel C2: specifying datafile(s) to restore from backup set
channel C2: restoring datafile 00010 to /home/oracle/app/oracle/oradata/ORCL/pdb/
sysaux01.dbf
channel C2: reading from backup piece ./Automated_data_ORCL_1575537735_nev83dg4_1
channel C3: starting datafile backup set restore
channel C3: specifying datafile(s) to restore from backup set
channel C3: restoring datafile 00001 to /home/oracle/app/oracle/oradata/ORCL/
system01.dbf
channel C3: reading from backup piece ./Automated_data_ORCL_1575537735_ndv83dg4_1
channel C4: starting datafile backup set restore
channel C4: specifying datafile(s) to restore from backup set
channel C4: restoring datafile 00004 to /home/oracle/app/oracle/oradata/ORCL/
undotbs01.dbf
channel C4: reading from backup piece ./Automated_data_ORCL_1575537735_ngv83dgc_1
channel Cl: piece handle=./Automated_data_ORCL_1575537735_nfv83dg4_1
tag=TAG20200817T141532
channel Cl: restored backup piece 1
channel Cl: restore complete, elapsed time: 00:00:07
channel Cl: starting datafile backup set restore
channel Cl: specifying datafile(s) to restore from backup set
channel C1: restoring datafile 00009 to /home/oracle/app/oracle/oradata/ORCL/pdb/
system01.dbf
channel Cl: reading from backup piece ./Automated_data_ORCL_1575537735_nhv83dgc_1
channel C3: piece handle=./Automated_data_ORCL_1575537735_nkv83dgh_1
tag=TAG20200817T141532
channel C3: restored backup piece 1
channel C3: restore complete, elapsed time: 00:00:04
channel C2: piece handle=./Automated_data_ORCL_1575537735_ncv83dg4_1
tag=TAG20200817T141532
channel C2: restored backup piece 1
channel C2: restore complete, elapsed time: 00:00:16
Finished restore at 19-AUG-20
released channel: Cl
released channel: C2
released channel: C3
released channel: C4

16. To prepare for database recovery, run the RMAN command list backup to obtain either the SCN or the log sequence
number to which the database must be restored.
For example, the following output from the list backup command shows the log sequence number 494. To complete the
database recovery, you need to restore the database to the log sequence number 494:

SPFILE Included: Modification time: 17-AUG-20

SPFILE db_unique_name: ORCL
Control File Included: Ckp SCN: 3304523 Ckp time: 17-AUG-20

BS Key Size Device Type Elapsed Time Completion Time

------ -------- ----------- ------------ ---------------
3397 256.00K SBT_TAPE 00:00:00 17-AUG-20
BP Key: 3397 Status: AVAILABLE Compressed: NO Tag: TAG20200817T141937
Handle: ./Automated_arch_ORCL_<DBID>_nrv83dnp_1 Media: S:<DD_system>:/
<storage_unit_name>/5c2914e2

List of Archived Logs in backup set 3397

Thrd Seq Low SCN Low Time Next SCN Next Time
---- ----- -------- --------- -------- ---------
1 494 3304486 17-AUG-20 3304775 17-AUG-20

Performing Self-Service Backups of Oracle Databases 65

 Record the final log sequence number.

17. To recover the database, run the recover database command in Recovery Manager.
NOTE: If you do not specify the log sequence number in the recover database command, the command output
ends with an error message, such as follows:

unable to find archived log

archived log thread=1 sequence=495
released channel: Cl
released channel: C2
released channel: C3
released channel: C4
RMAN-00571: =================================================
RMAN-00569: ========== ERROR MESSAGE STACK FOLLOWS ==========
RMAN-00571 :=================================================
RMAN-03002: failure of recover command at 08/19/2020 15:38:00
RMAN-06054: media recovery requesting unknown archived log for thread 1 with
sequence 495 and starting SCN of 3304775

In the following example, the recover database command specifies the sequence number to which the database is
restored:

RMAN> run {
2>
3> ALLOCATE CHANNEL C1 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
4>
5> ALLOCATE CHANNEL C2 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
6>
7> ALLOCATE CHANNEL C3 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
8>
9> ALLOCATE CHANNEL C4 TYPE SBT TRACE 5 PARMS 'SBT_LIBRARY=/
home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, SBT_PARMS=(RMAN_AGENT_HOME=/home/
oracle/opt/dpsapps/rmanagent/, STORAGE_UNIT=/rman134-os-blrv027d140-f548a,
BACKUP_HOST=10.63.96.240, ORACLE_HOME=/home/oracle/19.3)' ;
10>
11> recover database until sequence 495;
12>
13> }

allocated channel: C1
channel C1: SID=25 device type=SBT_TAPE
channel C1: Data Domain Boost API
allocated channel: C2
channel C2: SID=40 device type=SBT_TAPE
channel C2: Data Domain Boost API
allocated channel: C3
channel C3: SID=28 device type=SBT_TAPE
channel C3: Data Domain Boost API
allocated channel: C4
channel C4: SID=29 device type=SBT_TAPE
channel C4: Data Domain Boost API
Starting recover at 19-AUG-20

starting media recovery

media recovery complete, elapsed time: 00:00:00
Finished recover at 19-AUG-20
released channel: C1
released channel: C2
released channel: C3
released channel: C4

66 Performing Self-Service Backups of Oracle Databases

18. To create a new incarnation of the database, run the following command in Recovery Manager:

alter database open resetlogs;

19. To close the Recovery Manager, run the following command:

exit

20. To start the Recovery Manager and connect to the restored database, run the following command:

rman target /
Recovery Manager: Release 19.0.0.0.0 - Production on Mon Aug 10 19:15:06 2020
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.

connected to target database: ORCL (DBID=<DBID>)

RMAN>

Verify that the database name and DBID are correct.

Next steps
After you perform a cross-restore to an alternate host:
● Change the DBID of the restored database as described in Change the DBID of an Oracle instance on page 67.
Ensure that the DBID is unique for each data center. Multiple Oracle databases with the same DBID produce duplicate
entries in PowerProtect Data Manager.
● Optionally, to remove the access to the production backups, remove the client registration from the lockbox as described in
Remove a client registration from the lockbox on page 69.

Change the DBID of an Oracle instance

As recommended by Oracle, the Oracle DBID must be unique for each data center. After you perform a cross-restore to an
alternate host, change the DBID of the restored database according to the following instructions. You can also optionally change
the database name.

Prerequisites
Before you change the DBID of the Oracle instance, ensure that you have a recoverable whole database backup.

About this task

NOTE: For more information about the procedures for changing the Oracle DBID or database name, refer to the Oracle
Database Utilities Guide from the Oracle Help Center.

Steps
1. Ensure that the target database is mounted but not open. Ensure that the database was shut down consistently before
mounting. For example:

rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Sep 18 17:23:16 2020

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1573350876)

RMAN> shutdown immediate;

using target database control file instead of recovery catalog

database closed
database dismounted
Oracle instance shut down

Performing Self-Service Backups of Oracle Databases 67

 RMAN> startup mount

connected to target database (not started)

Oracle instance started
database mounted

Total System Global Area 2483027968 bytes

Fixed Size 8795808 bytes
Variable Size 553650528 bytes
Database Buffers 1912602624 bytes
Redo Buffers 7979008 bytes

2. To run the DBNEWID utility to change the Oracle DBID, run the nid command and include the TARGET option to specify a
valid user with SYSDBA privileges.
The DBNEWID utility performs the following operations:
a. The utility prompts for the database user password.
b. The utility performs validations in the headers of the data files and control files.
c. If the validations are successful, the utility prompts for confirmation before changing the DBID.

NOTE: If you have specified a log file, the utility does not prompt for confirmation.
d. The utility changes the DBID for each data file, including offline normal and read-only data files, and then shuts down the
database and exits.
The following examples show the outputs of the nid command:

nid

DBNEWID: Release 12.2.0.1.0 - Production on Fri Sep 18 17:27:16 2020

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.
Keyword Description (Default)

TARGET Username/Password (NONE)

DBNAME New database name (NONE)
LOGFILE Output Log (NONE)
REVERT Revert failed change NO
SETNAME Set a new database name only NO
APPEND Append to output log NO
HELP Displays these messages NO

nid TARGET=SYS

DBNEWID: Release 12.2.0.1.0 - Production on Fri Sep 18 17:27:36 2020

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.

Password:
Connected to database ORCL (DBID=1573350876)
Connected to server version 12.2.0
Control Files in database:
/home/oracle/app/oracle/oradata/orcl/control101.ctl
/home/oracle/app/oracle/fast_recovery_area/orcl/control102.ctl

Change database ID of database ORCL? (Y/[N]) => y

Proceeding with operation

Changing database ID from 1573350876 to 1579271059
Control File /home/oracle/app/oracle/oradata/orcl/control101.ctl - modified
Control File /home/oracle/app/oracle/fast_recovery_area/orcl/control102.ctl -
modified
Datafile /home/oracle/app/oracle/oradata/orcl/system01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/sysaux01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/undotbs01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/pdbseed/system01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/pdbseed/sysaux01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/users01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/pdbseed/undotbs01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/orclpdb/system01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/orclpdb/sysaux01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/orclpdb/undotbs01.db - dbid changed

68 Performing Self-Service Backups of Oracle Databases

 Datafile /home/oracle/app/oracle/oradata/orcl/orclpdb/users01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/temp01.db - dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/pdbseed/
temp012020-07-12_12-09-35-835-PM.db dbid changed
Datafile /home/oracle/app/oracle/oradata/orcl/orclpdb/temp01.db - dbid changed
Control File /home/oracle/app/oracle/oradata/orcl/control101.ctl - dbid changed
Control File /home/oracle/app/oracle/fast_recovery_area/orcl/control102.ctl - dbid
changed
Instance shut down

Database ID for database ORCL changed to 1579271059.

All previous backups and archived redo logs for this database are unusable.
Database is not aware of previous backups and archived logs in Recovery Area.
Database has been shutdown, open database with RESETLOGS option.
Successfully changed database ID.
DBNEWID - Completed successfully.

3. Mount the database, and open the database in RESETLOGS mode. For example:

rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Sep 18 17:42:26 2020

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)

RMAN> startup mount

Oracle instance started

database mounted
Total System Global Area 2483027968 bytes
Fixed Size 8795808 bytes
Variable Size 671091040 bytes
Database Buffers 1795162112 bytes
Redo Buffers 7979008 bytes

RMAN> ALTER DATABASE OPEN RESETLOGS;

using target database control file instead of recovery catalog

Statement processed

RMAN> exit

Recovery Manager complete.

At this point, you can resume normal operations with the database, which has the new DBID. For example:

rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Sep 18 18:00:30 2020

copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1579271059)

RMAN>

4. Perform a full database backup. Because the online redo logs have been reset, the previous backups and archived logs are no
longer usable in the new incarnation of the database.

Remove a client registration from the lockbox

After you perform a cross-restore to an alternate host, you can optionally remove the access to the production backups by
removing the client registration from the Oracle RMAN agent lockbox.
To remove the client registration from the lockbox, run the following command from the $RMAN_AGENT_HOME/bin directory:

./ddutil -C -d -a DD_SERVER_NAME=<server_name> -a DD_STORAGE_UNIT=<storage_unit_name>

Performing Self-Service Backups of Oracle Databases 69