Contents

Dell PowerProtect 19.12 Data Manager Oracle RMAN User Guide PDF

1 of 117
1 of 117

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

PowerProtect Data Manager 19.12 Oracle RMAN User Guide

October 2022 Rev. 01

Notes, cautions, and warnings

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

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

the problem.

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

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

Preface.........................................................................................................................................................................................6

Chapter 1: PowerProtect Data Manager for Oracle RMAN Agent Overview...................................10 PowerProtect Data Manager overview........................................................................................................................ 10 About the Oracle RMAN agent.......................................................................................................................................10 Prerequisites....................................................................................................................................................................... 10 Supported Internet Protocol versions........................................................................................................................... 11 Firewall and port considerations.....................................................................................................................................13 Role-based security........................................................................................................................................................... 14 Data-in-flight encryption.................................................................................................................................................. 14 PowerProtect Data Manager new deployment overview........................................................................................ 14 PowerProtect Data Manager existing deployment overview..................................................................................15

Chapter 2: Enabling the Oracle RMAN Agent................................................................................16 Review Oracle data protection and replication requirements................................................................................. 16

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

Install the Oracle RMAN agent................................................................................................................................. 18 Integration with PowerProtect Data Manager software...................................................................................20 Install the PowerProtect Data Manager agent..................................................................................................... 21 Uninstall the Oracle RMAN agent........................................................................................................................... 23 Uninstall the PowerProtect agent service............................................................................................................ 25 Update in an Oracle RAC environment.................................................................................................................. 26 Update the Oracle RMAN agent..............................................................................................................................26 Update the PowerProtect agent............................................................................................................................. 28 Update the application agent in the PowerProtect Data Manager UI........................................................... 30 Recommission the Oracle RMAN agent................................................................................................................. 31 How the Oracle RMAN agent communicates with PowerProtect Data Manager...................................... 32 Verify the connectivity from ddbmcon.................................................................................................................. 36 Discover the storage units........................................................................................................................................ 38

Manage the Oracle application agent...........................................................................................................................39 View application agent details..................................................................................................................................39

Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager.....................................41 Support existing Oracle RMAN agent backups with PowerProtect Data Manager....................................42

PowerProtect Data Manager support of Oracle RMAN agent with Oracle 21c................................................ 43 Enable multi-stream backups for Oracle protection policy..................................................................................... 43 Enabling app-optimization for storage unit created by Oracle protection policy.............................................. 44

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

View the storage unit password.............................................................................................................................. 46 Enable an asset source.....................................................................................................................................................47

Disable an asset source..............................................................................................................................................47

Contents

Contents 3

Delete an asset source.....................................................................................................................................................48 Discover an Oracle application host............................................................................................................................. 48 Add and remove the credentials for Oracle assets...................................................................................................49 Assign a preferred node in Oracle RAC environment...............................................................................................50 Replication triggers............................................................................................................................................................51 Add a protection policy for Oracle database protection.......................................................................................... 51 Cancel an application agent protection job.................................................................................................................58 Add a service-level agreement...................................................................................................................................... 59 Edit the retention period for backup copies................................................................................................................61 Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier)..... 62 Delete backup copies....................................................................................................................................................... 64

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

Enable the Oracle RMAN agent after hostname change........................................................................................ 66 Enable the use of an existing asset in a modified environment............................................................................. 67 Delete backup copies from RMAN catalog with ddutil command......................................................................... 68 Manage the PowerProtect agent service................................................................................................................... 70

About the PowerProtect agent service................................................................................................................. 70 Start, stop, or obtain the status of the PowerProtect agent service............................................................. 71 Register the PowerProtect agent service to a different server address on AIX or Linux..........................71 Recovering the PowerProtect agent service from a disaster.......................................................................... 72

Manage the cloud tier operations with PowerProtect Data Manager................................................................. 73 Add a cloud tier objective to a protection policy................................................................................................. 73 Tier the PowerProtect Data Manager backups from DD to the cloud...........................................................74 Restore the cloud tier backups to DD.................................................................................................................... 74

Chapter 4: Performing Self-Service Backups and Restores of Oracle Databases..........................76 Performing self-service backups of Oracle databases.............................................................................................76 Restore an Oracle application host............................................................................................................................... 78

Restore to an alternate host.....................................................................................................................................79 Change the DBID of an Oracle instance................................................................................................................ 90 Remove a client registration from the lockbox.................................................................................................... 92

Chapter 5: Performing Centralized Restores of Oracle Backups.................................................. 93 Centralized restore and recovery of Oracle backups...............................................................................................93 Considerations for centralized Oracle restore and recovery..................................................................................93 Performing centralized Oracle restore and recovery of an online database...................................................... 95 Performing centralized Oracle restore of archive logs............................................................................................ 96 Performing centralized disaster recovery of an Oracle database......................................................................... 97

Appendix A: Oracle RMAN Best Practices and Troubleshooting.................................................. 101 Troubleshooting storage units.......................................................................................................................................101 Troubleshooting backup failures when credentials include a backslash character (\)...................................102 Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname.................... 102 Troubleshooting agent registration ............................................................................................................................ 102 Troubleshooting PowerProtect agent service operations..................................................................................... 103 Troubleshooting application agent update failure in PowerProtect Data Manager UI on Linux.................. 104 Troubleshooting an asset duplication issue after downgrade...............................................................................104

4 Contents

Troubleshooting an issue with hostnames used for discoveries after a hostname change.......................... 104 Troubleshooting an issue with incorrect SID or database name in rename.config file................................... 104 Troubleshooting a self-service backup error for an unmanaged asset.............................................................. 105 Troubleshooting self-service backup error related to top-level pathname....................................................... 105 Troubleshooting self-service operations with data-in-flight encryption............................................................105 Troubleshooting Oracle self-service jobs that run indefinitely............................................................................. 106 Troubleshooting an incorrect self-service backup report for different backup types in same session..... 106 Troubleshooting an incorrect asset display after asset source deletion............................................................106 Troubleshooting a failed migration of RAC_BACKUP_NODE_IP parameter setting..................................... 106 Troubleshooting an issue with AIX RAC cluster failover........................................................................................ 107 Troubleshooting RAC cluster failure due to active node issue............................................................................. 107 Troubleshooting a missing duration value for centralized backup....................................................................... 107 Troubleshooting an issue with onboarded backup copies......................................................................................107 Troubleshooting missing Oracle version with added protection rules................................................................ 108 Troubleshooting restore failure due to FORMAT specification............................................................................108 Troubleshooting an issue on AIX with ddbmcon process not exiting................................................................. 108 Troubleshooting centralized restore issue with unchanged DBID....................................................................... 108 Troubleshooting centralized restore issue with audit file destination................................................................ 109

Appendix B: Glossary of Acronyms ........................................................................................110

Glossary......................................................................................................................................111

Contents 5

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

If a product does not function correctly or does not function as described in this document, contact Customer Support.

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

go to the Customer Support website.

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

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

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

Acronyms The acronyms used in this document might not be familiar to everyone. Although most acronyms are defined on their first use, a definition is not always provided with later uses of the acronym. For a list of all acronyms and their definitions, see the glossary at the end of the document.

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

Purpose This document describes how to configure and use the Dell 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.

6 Preface

Table 1. Revision history

Revision Date Description

01 October 25, 2022 Initial release of this document for PowerProtect Data Manager version 19.12.

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

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

Table 2. Related documentation

Title Content

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

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

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

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

PowerProtect Data Manager Security Configuration Guide Contains security information.

PowerProtect Data Manager Amazon Web Services Deployment Guide

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

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

PowerProtect Data Manager Google Cloud Platform Deployment Guide

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

PowerProtect Data Manager Cloud Disaster Recovery Administration and User Guide

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

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

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

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

PowerProtect Data Manager Microsoft Exchange Server User Guide

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

PowerProtect Data Manager Microsoft SQL Server User Guide

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

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

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

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

Preface 7

Table 2. Related documentation (continued)

Title Content

PowerProtect Data Manager Network Attached Storage User Guide

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

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

VMware Cloud Foundation Disaster Recovery With PowerProtect Data Manager

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

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

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

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

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

Table 3. Style conventions

Formatting Description

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

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

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

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

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

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

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

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

Where to find product documentation The Customer Support website The Community Network The PowerProtect Data Manager Info Hub

8 Preface

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.

Support Library The Support Library contains a knowledge base of applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Support Library:

1. Go to the Customer Support website. 2. On the Support tab, click Support Library. 3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by

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

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

1. Go to the Customer Support website. 2. On the Support tab, click Contact Support. 3. On the Contact Information page, click the relevant support, and then proceed.

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

1. Go to the Customer Support website. 2. On the Support tab, click Service Requests.

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

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

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

To review an open service request:

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

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

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

Preface 9

PowerProtect Data Manager for Oracle RMAN Agent Overview

Topics:

PowerProtect Data Manager overview About the Oracle RMAN agent Prerequisites Supported Internet Protocol versions Firewall and port considerations Role-based security Data-in-flight encryption PowerProtect Data Manager new deployment overview PowerProtect Data Manager existing deployment overview

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

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

policies are being adhered to. Manage the life cycle of backups that the application agent creates. Ensure that the backups are marked for garbage

collection, based on the rules of the retention policy.

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

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 DD host, storage unit, user, and password. Install and configure the Oracle RMAN agent provides instructions.

NOTE: PowerProtect Data Manager supports the coexistence of the Oracle RMAN agent and the File System agent on AIX

and Linux.

Software compatibility information for the PowerProtect Data Manager software and application agents is provided by the E-Lab Navigator.

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

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

application agents is provided by the E-Lab Navigator.

1

10 PowerProtect Data Manager for Oracle RMAN Agent Overview

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

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

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

Application agent 19.12 or earlier is required. License: A trial license is provided with the PowerProtect Data Manager software. Customers can contact Customer

Support for assistance with a permanent PowerProtect Data Manager license. Large environments require multiple PowerProtect Data Manager instances. Contact Champions.eCDM@emc.com for

assistance with sizing requests. The PowerProtect Data Manager 19.12 download file requires the following:

ESXi version 6.5, 6.7, or 7.0. 10 vCPUs, 24 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 24 GB of RAM for PowerProtect Data Manager Five disks with the following capacities:

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

One 1-GB NIC

Supported Internet Protocol versions PowerProtect Data Manager and its components support IPv4 and IPv6 addresses in certain configurations.

Table 4. Supported configurations

Component Internet Protocol

PowerProtect Data Manager core

IPv4 only or both IPv4 and IPv6

VM Direct and Search IPv4 only or IPv6 only NOTE: Virtual machines that are backed up must use the same protocol that VM Direct uses. Virtual machines can use both IPv4 and IPv6, even though VM Direct cannot.

Application agents integrated with PowerProtect Data Manager:

NOTE: If both IPv4 and IPv6 are configured and the PowerProtect Data Manager FQDN is used, the agent uses IPv6 for network communication.

File System IPv4, IPv6, or both

Microsoft Exchange Server IPv4 only or both IPv4 and IPv6

Microsoft SQL Server (Application Direct)

IPv4, IPv6, or both

Microsoft SQL Server (VM Direct)

IPv4 only or IPv6 only

NOTE: Only the Microsoft SQL Server agent supports VM Direct.

Oracle RMAN IPv4, IPv6, or both

SAP HANA IPv4, IPv6, or both

Storage Direct IPv4 only

Standalone application agents IPv4 only

PowerProtect Data Manager for Oracle RMAN Agent Overview 11

Table 4. Supported configurations (continued)

Component Internet Protocol

Network-attached storage (NAS)

IPv4 only

Kubernetes IPv4 only

PowerProtect Data Manager management

IPv4 or IPv6

PowerProtect DD communication

IPv4 or IPv6

Report Browser IPv4 only

SupportAssist IPv4, IPv6, or both

Syslog Log Server Gateway IPv4 or IPv6

The following limitations and considerations apply.

Communication with components

If PowerProtect Data Manager is configured to only use one protocol, all components it communicates with must also use that protocol. If some components that PowerProtect Data Manager communicates with use IPv4 and others use IPv6, PowerProtect Data Manager must be configured to use both IPv4 and IPv6.

DD systems and DDVE

If a DD system or a DDVE instance uses only IPv6, the required IPv6 interface must be manually selected when a protection policy is added or edited.

Disaster recovery

Recovering a PowerProtect Data Manager server might result in a conflict with protection-policy configurations. For instance, if the recovered server is configured to use only IPv4, a protection policy that is configured to use IPv6 cannot run.

Name resolution

Name resolution and reverse IP lookup must be configured to ensure the following:

Fully qualified domain names of PowerProtect Data Manager, its components, and DD components resolve to a valid IPv4 or IPv6 address.

If both IPv4 and IPv6 addresses are used for DD, both addresses resolve to the same FQDN. All IPv4 and IPv6 addresses are valid and reachable.

Server updates

IPv6 is only supported with new installations. Using IPv6 after updating from PowerProtect Data Manager 19.11 or earlier is unsupported.

Storage Policy Based Management

If using vCenter or ESXi 7.0u2 or earlier with only IPv6, SPBM providers must be added using their PowerProtect Data Manager FQDN.

12 PowerProtect Data Manager for Oracle RMAN Agent Overview

Service Unavailable messages with the vSphere Client PowerProtect plug-in

If vCenter uses the vSphere Client PowerProtect plug-in with IPv6 and the vCenter host is added to PowerProtect Data Manager using its IPv6 address or FQDN, Service Unavailable messages might be seen for the protected virtual machine. Backups and restores of the protected virtual machine are unaffected, and these messages can be ignored.

Uncompressed IPv6 formatting

Network interfaces that exist on a DD 7.4.x or earlier system and that are configured to use an uncompressed IPv6 format cannot be discovered. An example of an uncompressed IPv6 format is 2620:0000:0170:0597:0000:0000:0001:001a. An example of a compressed IPv6 format is 2620:0:170:597::1:1a. To use these network interfaces, reconfigure them to use either an IPv4 address or a compressed IPv6 address, and then initiate a discovery.

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

Table 5. PowerProtect Data Manager port requirements

Description Communication Port

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

22 TCP/UDP

Microsoft SQL Server, Oracle, Microsoft Exchange Server, SAP HANA, File System

Bi-directional communication between the PowerProtect Data Manager agent and the PowerProtect Data Manager appliance.

Requirement applies to Application Direct and VM Direct.

7000 TCP

REST Server Bi-directional communication between the HTTP client and the PowerProtect Data Manager appliance.

8443 TCP

RESTAPI Server - VM Direct

Bi-directional communication between the PowerProtect Data Manager agent and the PowerProtect Data Manager appliance.

Requirement applies to Microsoft SQL Server VM application- aware.

8443 TCP

UI redirect Inbound only. 80 TCP

443

LDAP Outbound only. 389 TCP/UDP

636 TCP

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

3009 TCPStorage Direct and DD system

5989 TCPSMI-S

443 TCPXtremIO

7225 TCPRecoverPoint

PowerProtect Data Manager agent

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

7000 TCP

PowerProtect Data Manager for Oracle RMAN Agent Overview 13

Table 5. PowerProtect Data Manager port requirements (continued)

Description Communication Port

This requirement applies to both Application Direct and VM Direct.

Embedded VM Direct service

Outbound. 9090 TCP

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

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

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

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

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

PowerProtect Data Manager only supports encryption in-flight for File System, Kubernetes clusters, Microsoft SQL Server, Microsoft Exchange Server, network attached storage (NAS), Oracle, and SAP HANA workloads. This is a global setting that is applicable to all supported workloads.

For File System, Microsoft SQL Server, Microsoft Exchange Server, Oracle, SAP HANA, and NAS workloads, backup and restore encryption is only supported for Application Direct hosts. For File System agents, restore encryption is supported for image-level restore only. For Microsoft SQL Server agents, restore encryption is supported for database-level restore only.

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

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

Steps

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

The account team can help with backup storage design.

2. Install PowerProtect DD Management Center.

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

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

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

3. Install PowerProtect Data Manager from the download file.

14 PowerProtect Data Manager for Oracle RMAN Agent Overview

The PowerProtect Data Manager Deployment Guide provides instructions.

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

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

5. Install the application agent on the appropriate hosts and connect them to PowerProtect Data Manager according to the instructions in the next "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.

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

Steps

1. Install PowerProtect DD Management Center.

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

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

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

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

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

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

4. Update the application agent or uninstall and then reinstall the application agent on the hosts and connect them to PowerProtect Data Manager. 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.

PowerProtect Data Manager for Oracle RMAN Agent Overview 15

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 PowerProtect Data Manager support of Oracle RMAN agent with Oracle 21c 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.

Oracle RMAN agent prerequisites

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

Verify that the environment meets the following requirements:

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

Oracle RMAN agent is provided in the E-Lab Navigator.

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. Ensure that Oracle Server is installed and configured on one of the following systems:

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

NOTE: PowerProtect Data Manager supports an Oracle database installation in a high-availabillity Data Guard

environment that includes a primary production node and standby nodes. Each node is protected as a separate asset

with a protection policy in PowerProtect Data Manager.

Additional AIX prerequisites

Ensure that IBM XL C or C++ Runtime for AIX 16.1.0.7 or later is installed.

2

16 Enabling the Oracle RMAN Agent

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

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

Install the Oracle RMAN agent provides information.

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

Manage the Oracle application agent provides information.

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

Discover an Oracle application host provides information.

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

Add a protection policy for Oracle database protection provides information.

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

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

Install the Oracle RMAN agent provides information.

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

Manage the Oracle application agent provides information.

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

Discover an Oracle application host provides information.

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

Add a protection policy for Oracle database protection 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 on DD systems with High Availability (HA) configurations.

Enabling the Oracle RMAN Agent 17

Install the Oracle RMAN agent

Learn how to install the Oracle RMAN agent on all the database servers that must access the DD 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.12 or to update 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, $USER_HOME_DIR/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.

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. Click , and then select Downloads from the System Settings menu. b. Under Oracle, select Download Agent. c. Select the Oracle RMAN agent download package:

On AIX: Select Download for AIX to download the AIX software package, ddrman1912_aixpower.tar.

On Linux: Select Download for Linux to download the Linux software package, ddrman1912_linux_x86_64.tar.

The software package is downloaded to the Oracle server host.

d. Copy the package to any user-defined directory with Oracle user ownership on the Oracle server host.

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

the authenticity and integrity of the downloaded package.

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

On AIX:

chown -R oracle:oinstall ddrman1912_aixpower.tar On Linux:

chown -R oracle:oinstall ddrman1912_linux_x86_64.tar

3. Uncompress the downloaded tar file outside of the $RMAN_AGENT_HOME directory using the oracle user by running the following command:

On AIX:

tar -xvf ddrman1912_aixpower.tar On Linux:

tar -xvf ddrman1912_linux_x86_64.tar

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

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

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

install.sh

The install.sh script displays the following type of prompt:

18 Enabling the Oracle RMAN Agent

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

NOTE: The default installation directory is /opt/dpsapps/rmanagent, which is the

default $RMAN_AGENT_HOME location.

6. At the script prompt shown in the preceding step, 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.12 installation, and must not be the ORACLE_HOME directory. The complete directory pathname must be

specified, without a slash (/) at the end.

For example, the install.sh script on Linux 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 libzmq.so.5 to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying ddutil to /home/oracle/opt/dpsapps/rmanagent/bin/. Copying pushupdate.sh 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/. Copying the configuration file to /home/oracle/opt/dpsapps/rmanagent/config/. 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 configuration file to /home/oracle/opt/dpsapps/rmanagent/config/. Copying the ddbmoim program to /home/oracle/opt/dpsapps/rmanagent/bin/. Creating the lockbox. Successfully installed the Oracle RMAN agent.

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

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

The installation script exits.

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

$RMAN_AGENT_HOME/bin/ddutil -i RMAN Agent Version: 19.12.0.0(10)

Enabling the Oracle RMAN Agent 19

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 AIX or 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 DD 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 DD 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.

Starting with release 19.9, a new Oracle database discovery method is supported, which uses the pmon process without a dependence on /etc/oratab entries. The /etc/oratab file entries have the highest precedence for the discovery of Oracle database resources on the system, which enables the PowerProtect Data Manager operations.

Perform the following steps to integrate the Oracle RMAN agent with PowerProtect Data Manager.

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.

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

4. As recommended by Oracle, ensure that all the archived redo logs in an 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 centralized backup node through one of the following settings:

Set the asset-level option More Actions > Assign Preferred Node on the Assets page in the PowerProtect Data Manager UI, as described in Assign a preferred node in Oracle RAC environment.

Set the RAC_BACKUP_NODE_IP parameter in the configuration file, as described in Configuration file requirements for connection to local databases.

NOTE: The option setting in the PowerProtect Data Manager UI takes precedence over the RAC_BACKUP_NODE_IP parameter setting in the configuration file for the same asset. The preferred node setting is only applicable for a

centralized protection policy, not for a self-service protection policy.

20 Enabling the Oracle RMAN Agent

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 appropriate command:

On AIX, run either the installp command-line program or the SMIT GUI program:

To run the command-line program, type the following command:

installp -a -d /ddrman powerprotect-agentsvc.rte

NOTE: The powerprotect-agentsvc.rte file is located in the /ddrman directory after you download and uncompress the Oracle RMAN agent software package.

For example, the command and output appears as follows:

installp -a -d /home/oracle/ddrman powerprotect-agentsvc.rte +-----------------------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------- Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------- powerprotect-agentsvc.rte 99.0.99.793 # powerprotect agent service << End of Success Section >> +-----------------------------------------------------------------------------+ BUILDDATE Verification ... +-----------------------------------------------------------------------------+ Verifying build dates...done FILESET STATISTICS ------------------ 1 Selected to be installed, of which: 1 Passed pre-installation verification ---- 1 Total to be installed +-----------------------------------------------------------------------------+ Installing Software... +-----------------------------------------------------------------------------+ installp: APPLYING software for: powerprotect-agentsvc.rte 99.0.99.793 +-----------------------------------------------------------------------------+ ** Post Installation Step ** +-----------------------------------------------------------------------------+ To configure the firewall rules, run the /opt/dpsapps/agentsvc/configfw.sh script. Finished processing all filesets. (Total time: 6 secs). +-----------------------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------------------+ Installation Summary -------------------- Name Level Part Event Result ------------------------------------------------------------------------------- powerprotect-agentsvc.rte 99.0.99.793 USR APPLY SUCCESS

Enabling the Oracle RMAN Agent 21

To run the SMIT GUI program, perform the following steps: a. Type the following command:

smitty install_latest b. In the Entry Field, type the complete pathname of the directory that contains the software installation files. c. Select the option SOFTWARE to install. d. To start the installation, perform either of the following actions:

Select default , and with the default input SOFTWARE to install, press Enter. Select F4=List, select powerprotect-agentsvc.rte, and press Enter.

To verify that the installation succeeded, type the following command:

lslpp -L all | grep -i powerprotect-agentsvc powerprotect-agentsvc.rte

If the command output includes powerprotect-agentsvc.rte, then the installation succeeded.

On Linux, run the following command:

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

NOTE: To verify the authenticity and integrity of the agent service RPM file before you run the command, follow the

instructions in the PowerProtect Data Manager Security Configuration Guide.

For example, the command on Linux displays the following command output:

rpm -ivh powerprotect-agentsvc-19.12.0.0.0-1.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:powerprotect-agentsvc-19.12.0.0.0-################################# [100%] Created symlink from /etc/systemd/system/multi-user.target.wants/agentsvc.service to /etc/systemd/system/agentsvc.service. To configure firewall rules run /opt/dpsapps/agentsvc/configfw.sh

3. To enable the PowerProtect Data Manager communication 7000 TCP port, run the /opt/dpsapps/agentsvc/ configfw.sh script as the root user.

On AIX, the command output appears as follows:

/opt/dpsapps/agentsvc/configfw.sh configuring inbound rules for AIX OS Filter rule 3 for IPv4 has been added successfully.

On Linux, the command output appears as follows:

/opt/dpsapps/agentsvc/configfw.sh firewalld service is running configuring firewall rules

NOTE: If the firewall rules are not applied, restart the firewall.

4. To complete the required addons configuration and registration with PowerProtect Data Manager, run the configureAddOn.sh script from the RMAN agent addon directory $RMAN_AGENT_HOME/addon. The following examples show the results when the retention time is set and the retention time is not set.

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

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

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.

22 Enabling the Oracle RMAN Agent

Copying the addon.cfg file. /opt/dpsapps/agentsvc/register.sh Enter the PowerProtect Data Manager server FQDN or IP address: 10.125.215.18 TMPDIR set to value /opt/dpsapps/agentsvc/tmp. Agent service (pid 29591) started successfully. Checking for PowerProtect Data Manager server Accessibility. PowerProtect Data Manager server is Accessible. Existing backups are not automatically discovered and managed by PowerProtect Data Manager by default. Follow the instructions in the PowerProtect Data Manager Oracle RMAN User Guide to discover existing bbackups. Do you want to set the retention time for retention management of existing backups by PowerProtect Data Manager? Enter "y" to specify the retention time as the number of days, or "n" to accept the default retention time of 30 days: (y or n) y Provide the 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/D2B24128_9482_44D2_8723_6D211DB49BFB directory. Copying the D2B24128_9482_44D2_8723_6D211DB49BFB.zip file. Copying the addon.cfg file. /opt/dpsapps/agentsvc/register.sh Enter the PowerProtect Data Manager server FQDN or IP address: 10.125.215.18 TMPDIR set to value /opt/dpsapps/agentsvc/tmp. Agent service (pid 31317) started successfully. Checking for PowerProtect Data Manager server Accessibility. PowerProtect Data Manager server is Accessible.

Existing backups are not automatically discovered and managed by PowerProtect Data Manager by default. Follow the instructions in the PowerProtect Data Manager Oracle RMAN User Guide to discover existing bbackups. Do you want to set the retention time for retention management of existing backups by PowerProtect Data Manager? Enter "y" to specify the retention time as the number of days, or "n" to accept the default retention time of 30 days: (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.

Uninstall the Oracle RMAN agent

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

About this task

NOTE: If the system is registered with PowerProtect Data Manager, you must first delete the host from PowerProtect

Data Manager before you uninstall the Oracle RMAN agent. To delete the host, log in to the PowerProtect Data Manager

UI, select the host in the Infrastructure > Asset Sources window, and click Delete.

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:

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.

Enabling the Oracle RMAN Agent 23

Table 6. Environment variables for uninstallation of Oracle RMAN agent

Environment variable Description Default and valid values

RMAN_AGENT_HOME Specifies the installation directory for the Oracle RMAN agent.

/ opt/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 to uninstall.

Undefined (default). NONE or noneSpecifies to

keep the Oracle RMAN agent software, and not perform the uninstallation.

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

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

NOTE: It is not necessary to uninstall the Oracle RMAN agent for an update. An existing Oracle RMAN agent is overwritten

during an update.

Perform the following steps to uninstall 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.

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. If you deleted the host from PowerProtect Data Manager before running the uninstall.sh script, then go to step 4. Otherwise, complete this step 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 $RMAN_AGENT_HOME/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:

24 Enabling the Oracle RMAN Agent

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

About this task

NOTE: If the system is registered with PowerProtect Data Manager, you must first delete the host from PowerProtect

Data Manager before you uninstall the PowerProtect agent service. To delete the host, log in to the PowerProtect Data

Manager UI, select the host in the Infrastructure > Asset Sources window, and click Delete.

Steps

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

2. If you deleted the host from PowerProtect Data Manager before uninstalling the PowerProtect agent service, then go to step 3. Otherwise, complete this step 2.

To delete the Oracle addon files in the agent service addon directory, run the unConfigureAddOn.sh script from the RMAN agent addon directory $RMAN_AGENT_HOME/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 appropriate command:

On AIX:

lslpp -L all | grep -i agent powerprotect-agentsvc.rte -19.12.0.0.0 C F powerprotect agent service

On Linux:

rpm -qa | grep agent powerprotect-agentsvc-19.12.0.0.0-1.x86_64

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

Enabling the Oracle RMAN Agent 25

NOTE: Ensure that you do not delete the agent service database that is present in the directory

$AGENT_SERVICE_INSTALL/dbs/v1.

On AIX, run either the installp command-line program or the SMIT GUI program:

To run the command-line program, type the following command:

installp -u powerprotect-agentsvc.rte To run the SMIT GUI program, perform the following steps:

a. Type the following command:

smitty remove b. To display a list of the installed software packages, select F4=List. c. Select the package to uninstall:

powerprotect-agentsvc.rte

d. Set the PREVIEW Only option to No. e. To uninstall the software, press Enter. f. Exit the SMIT GUI program.

On Linux, run the following command:

rpm -e powerprotect-agentsvc-19.12.0.0.0-1.x86_64

Update in an Oracle RAC environment

In an Oracle RAC environment, it is recommended that you update to the latest software version on each RAC node that is involved in PowerProtect Data Manager operations.

To update the software on each RAC node, you can either update the software manually or update the software in the PowerProtect Data Manager UI:

Update the software manually by completing the following steps on each RAC node:

1. Specify the SID value in the EXCLUDE_SID= parameter setting in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg on all nodes in the RAC environment.

2. Run the following command to stop the agent service:

# /opt/dpsapps/agentsvc/register.sh --stop 3. To update the Oracle RMAN agent, follow the instructions in Update the Oracle RMAN agent. 4. Run the following command to start the agent service:

# /opt/dpsapps/agentsvc/register.sh --start 5. Delete the SID value in the EXCLUDE_SID= parameter setting in the configuration file

$RMAN_AGENT_HOME/config/rman_agent.cfg on all nodes in the RAC environment.

Update the software in the PowerProtect Data Manager UI:

1. On each RAC node, specify the SID value in the EXCLUDE_SID= parameter setting in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg.

2. To update the Oracle RMAN agent, follow the instructions in Update the application agent in the PowerProtect Data Manager UI and select all the RAC nodes for the update procedure.

3. On each RAC node, delete the SID value in the EXCLUDE_SID= parameter setting in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg.

Update the Oracle RMAN agent

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

26 Enabling the Oracle RMAN Agent

About this task

NOTE: If the production host has a previous version of Oracle RMAN agent and you want to perform a disaster recovery to

another host, update the Oracle RMAN agent to the latest version on both the production host and target host. This update

prevents a natural ID collision issue.

Steps

1. Log in as an Oracle user.

2. To obtain details about the DD server hosts and storage units that PowerProtect Data Manager has registered with the Oracle RMAN agent, run the ddutil -s command on the Oracle RMAN agent client host. For example:

ddutil -s

PowerProtect DD hostname: 10.125.192.190

FC service name: None FC service enabled: false

Storage Unit: multi-asset-blrv041a118-7dab9 Top Level Path: PLCTLP-43f18cb1-fadb-4b25-ae9e-e385d5b5c401 Protection Policy Name: multi-asset

User: multi-asset-blrv041a118-7dab9 Type: PROTECTION

3. Update the Oracle RMAN agent by using either of the following methods:

Interactive update method:

To update the Oracle RMAN agent by using the interactive method that prompts for input, follow the instructions in Install the Oracle RMAN agent.

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

install.sh Do you want to install under the default installation directory /home/oracle/opt/ dpsapps/rmanagent? (y or n) y An Oracle RMAN agent already exists. Do you want to continue the installation? (y or n) y Installing the Oracle RMAN agent. Copying the lockbox libraries to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying libddobk.so to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying libDDBoost.so to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying ddutil to /home/oracle/opt/dpsapps/rmanagent/bin/. Copying the dependency libraries to /home/oracle/opt/dpsapps/rmanagent/lib/. Copying the ddbmcon program to /home/oracle/opt/dpsapps/rmanagent/bin/. Upgrading the lockbox. Import operation is not needed because the lockbox version is already updated. As a PowerProtect Data Manager user, update the existing PowerProtect DD details? (y/Y or n/N) y PowerProtect DD server name: BLRV033A205.blr.lab.emc.com PowerProtect DD storage unit name: rman Lockbox update is not needed for PowerProtect DD server 'BLRV033A205.blr.lab.emc.com'. As a PowerProtect Data Manager user, update the existing PowerProtect DD details? (y/Y or n/N) n 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 update method:

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

Enabling the Oracle RMAN Agent 27

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 update command, including the two -a command-line options that specify the DD server and storage unit credentials to be updated. If the credentials of more than one server or storage unit must be updated, specify a comma-separated list of the server names and storage unit names:

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

Update the PowerProtect agent

Complete the following steps to update a previous version of the PowerProtect agent to the current version of the PowerProtect agent.

1. Log in as the root user. 2. To update the PowerProtect agent, run the appropriate command:

On AIX, run either the installp command-line program or the SMIT GUI program:

To run the command-line program, type the following command:

installp -a -d /ddrman powerprotect-agentsvc.rte

NOTE: The powerprotect-agentsvc.rte file is located in the /ddrman directory after you download and uncompress the Oracle RMAN agent software package.

For example, the command and output appears as follows:

installp -a -d /home/oracle/ddrman powerprotect-agentsvc.rte +-----------------------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------- Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------- powerprotect-agentsvc.rte 99.0.99.793 # powerprotect agent service << End of Success Section >> +-----------------------------------------------------------------------------+ BUILDDATE Verification ... +-----------------------------------------------------------------------------+ Verifying build dates...done FILESET STATISTICS ------------------ 1 Selected to be installed, of which: 1 Passed pre-installation verification ---- 1 Total to be installed +-----------------------------------------------------------------------------+ Installing Software... +-----------------------------------------------------------------------------+ installp: APPLYING software for: powerprotect-agentsvc.rte 99.0.99.793 +-----------------------------------------------------------------------------+ ** Post Installation Step ** +-----------------------------------------------------------------------------+ To configure the firewall rules, run the /opt/dpsapps/agentsvc/configfw.sh script.

28 Enabling the Oracle RMAN Agent

Finished processing all filesets. (Total time: 6 secs). +-----------------------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------------------+ Installation Summary -------------------- Name Level Part Event Result ------------------------------------------------------------------------------- powerprotect-agentsvc.rte 99.0.99.793 USR APPLY SUCCESS

To run the SMIT GUI program, perform the following steps:

a. Type the following command:

smitty install_latest b. In the Entry Field, type the complete pathname of the directory that contains the software files. c. Select the option SOFTWARE to install. d. To start the update, perform either of the following actions:

Select default , and with the default input SOFTWARE to install, press Enter. Select F4=List, select powerprotect-agentsvc.rte, and press Enter.

To verify that the update succeeded, type the following command:

lslpp -L all | grep -i powerprotect-agentsvc powerprotect-agentsvc.rte

If the command output includes powerprotect-agentsvc.rte, then the update succeeded.

On Linux, run the following command:

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

NOTE: To verify the authenticity and integrity of the agent service RPM file before you run the command, follow the

instructions in the PowerProtect Data Manager Security Configuration Guide.

For example, the command on Linux displays the following command output:

rpm -Uvh powerprotect-agentsvc-19.12.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.12.0.0.0-################################# [ 50%] Cleaning up / removing... 2:powerprotect-agentsvc-19.10.0.0.0-################################# [100%] Created symlink from /etc/systemd/system/multi-user.target.wants/agentsvc.service to /etc/systemd/system/agentsvc.service. To configure firewall rules run /opt/dpsapps/agentsvc/configfw.sh

3. To enable the PowerProtect Data Manager communication 7000 TCP port, run the /opt/dpsapps/agentsvc/ configfw.sh script as the root user:

/opt/dpsapps/agentsvc/configfw.sh firewalld service is running configuring firewall rules

NOTE: If the firewall rules are not applied, restart the firewall.

4. To complete the required addons configuration and registration with PowerProtect Data Manager, run the configureAddOn.sh script from the RMAN agent addon directory $RMAN_AGENT_HOME/addon.

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

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

Enabling the Oracle RMAN Agent 29

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. Existing backups are not automatically discovered and managed by PowerProtect Data Manager by default. Follow the instructions in the PowerProtect Data Manager Oracle RMAN User Guide to discover existing backups. Do you want to set the retention time for retention management of existing backups by PowerProtect Data Manager? Enter "y" to specify the retention time as the number of days, or "n" to accept the default retention time of 30 days: (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 complete the update, manually approve the Oracle RMAN agent from the PowerProtect Data Manager server. Manage the Oracle application agent provides information.

Update the application agent in the PowerProtect Data Manager UI

Learn how to perform a precheck operation and update the application agent software on one or more hosts in the PowerProtect Data Manager UI.

Prerequisites

The precheck and update operations are only available for registered clients and application agent versions 19.10 and later.

Steps

To perform a precheck:

1. From the left navigation pane in the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

The Application Agents window opens.

2. Select the check box next to each application agent host to be included in the precheck. When the application agent versions on the selected hosts are 19.10 or later and the versions are earlier than the current PowerProtect Data Manager version, the More Actions button becomes enabled.

3. Click More Actions > Precheck Update.

The Precheck Update window opens.

4. On the Schedule Precheck page:

a. In the Name text box, type a name for the precheck operation. b. Select one of the following options:

Precheck nowPerforms the precheck immediately. Precheck laterSchedules the precheck to occur at a later time. If you select this option, specify the date and time

to perform the precheck.

c. Click Next.

5. On the Summary page, review the information for the selected application agent hosts, and then click OK.

The precheck verifies that the application agent hosts meet the minimum update requirements, including system memory, disk space, and version requirements. If the precheck passes, PowerProtect Data Manager downloads the update software package on each application agent host.

You can monitor the progress of the precheck operation in the System Jobs window.

To perform an update:

6. From the left navigation pane in the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

The Application Agents window opens.

30 Enabling the Oracle RMAN Agent

7. Select the check box next to each application agent host to be included in the update.

NOTE: In a cluster environment, select each host of the cluster; otherwise, any unselected hosts are automatically

selected for the update. It is recommended that each host of a cluster has the same application agent version.

When the application agent versions on the selected hosts are 19.10 or later and the versions are earlier than the current PowerProtect Data Manager version, the More Actions button becomes enabled.

8. Click More Actions > Configure Update.

The Configure Update window opens.

9. On the Schedule Updates page:

a. In the Name text box, type a name for the update operation. b. Select one of the following options:

Update nowPerforms the update immediately. Update laterSchedules the update to occur at a later time. If you select this option, specify the date and time to

perform the update.

c. Click Next.

10. On the Summary page, review the information for the selected application agent hosts, and then click OK.

On each selected host, the update performs a precheck, places the host in maintenance mode, updates the application agent, and then returns the host to normal mode.

You can monitor the progress of the update operation in the System Jobs window.

When the update is complete, the update status of each host changes to Up to date in the Application Agents window.

If the update fails:

An error is displayed, and you must manually return the hosts to normal mode. Check the agent service logs for details on how to manually restore the host system. Check the ADM logs for more information. For detailed steps to downgrade to a previous version of the application agent, run the following command:

./pushupdate.sh -r -n

Recommission the Oracle RMAN agent

You can use the procedure in this topic to onboard the decommissioned Oracle RMAN agent to the same PowerProtect Data Manager server.

NOTE:

You can run the configureAddOn.sh script to register and recommission the Oracle RMAN agent with PowerProtect

Data Manager only if you have not uninstalled the Oracle RMAN agent and PowerProtect agent service.

If you have cleaned up the installation directories and manually uninstalled both the Oracle RMAN agent and PowerProtect

agent service, then you must complete the installation procedures in Install and configure the Oracle RMAN agent.

To register and recommission the Oracle RMAN agent with PowerProtect Data Manager, run the configureAddOn.sh script from the RMAN agent addon directory $RMAN_AGENT_HOME/addon.

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

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

For example:

cd /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: An addons zip file /opt/dpsapps/agentsvc/AddOns/D2B24128_9482_44D2_8723_6D211DB49BFB/ D2B24128_9482_44D2_8723_6D211DB49BFB.zip already exists. Do you want to continue with the configuration? (y or n) y Copying the D2B24128_9482_44D2_8723_6D211DB49BFB.zip file. Copying the addon.cfg file. /opt/dpsapps/agentsvc/register.sh --enable AgentService is recommissioned.

Enabling the Oracle RMAN Agent 31

Enter the PowerProtect Data Manager IP address or hostname: 10.125.214.130 TMPDIR set to value /opt/dpsapps/agentsvc/tmp Agent service (pid 25218) started successfully. Existing backups are not automatically discovered and managed by PowerProtect Data Manager by default. Follow the instructions in the PowerProtect Data Manager Oracle RMAN User Guide to discover existing bbackups. Do you want to set the retention time for retention management of existing backups by PowerProtect Data Manager? Enter "y" to specify the retention time as the number of days, or "n" to accept the default retention time of 30 days: (y or n) y Provide the 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.

How the Oracle RMAN agent communicates with PowerProtect Data Manager

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

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

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

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

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

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

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

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

Configuration file requirements for connection to local databases

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

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

The configuration file template includes the following information.

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

32 Enabling the Oracle RMAN Agent

# Oracle RMAN agent 19.12 # # 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 # to which the parameters belong is described in the section name: SID_name. # The name here must be replaced by the SID of the database. # : # ############################################################################# [SID_name] # ORACLE_SERVICE = # ORACLE_USER = # ORACLE_OS_USER = # TNS_ADMIN = # RMAN_CATALOG_SERVICE = # RMAN_CATALOG_USER = # RAC_BACKUP_NODE_IP = # DELETE_ARCHIVE_LOGS = # FILESPERSET = # MAXOPENFILES = # SECTION_SIZE = # BLOCK_SIZE = # RAC_NODE_IP_1 = # RAC_NODE_FQDN_1 = # RAC_NODE_IP_2 = # RAC_NODE_FQDN_2 = # RAC_NODE_IP_ = # RAC_NODE_FQDN_ = # ENABLE_BROWNFIELD_DISCOVERY = # : [GENERAL] # EXCLUDE_SID = # ALLOW_BACKUP =

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

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.

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.

Enabling the Oracle RMAN Agent 33

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.

In the Oracle RAC environment, the backup operations are performed on the node specified in the RAC_BACKUP_NODE_IP parameter setting. A backup operation fails when the specified node is unavailable.

NOTE:

The backup node setting in the PowerProtect Data Manager UI takes precedence over the RAC_BACKUP_NODE_IP parameter setting in the configuration file for the same asset. Assign a preferred node in Oracle RAC environment

provides details about the backup node setting in the PowerProtect Data Manager UI.

The backup node setting is not applicable for self-service or stand-alone backups.

DELETE_ARCHIVE_LOGS is optional. Specifies whether to delete the archive logs just after performing a centralized log backup. When this parameter is set to TRUE, the archive logs are deleted after the log backup.

FILESPERSET is optional. Specifies the maximum number of files that RMAN can include in a backup set. The value must be an integer between 1 and 64, inclusive.

NOTE:

As an alternative to setting the parameters FILESPERSET, MAXOPENFILES, SECTION_SIZE, and BLOCK_SIZE in

the configuration file, you can set the options Files Per Set, Maximum Open Files, Section Size, and Block Size,

respectively, in the protection policy configuration in the PowerProtect Data Manager UI. Add a protection policy for

Oracle database protection provides details about the protection policy options.

The configuration file parameter settings take precedence over the option settings in the PowerProtect Data Manager

UI. These parameter and option settings apply only to centralized backups. The FILESPERSET and SECTION_SIZE settings apply only to full, incremental cumulative, and incremental differential backupsnot to log backups.

MAXOPENFILES is optional. Specifies the maximum number of input files that a backup or copy can have open at a given time. The value must be an integer greater than 0.

SECTION_SIZE is optional. Specifies the size in KB, MB, or GB of each backup section in a multisection backup. In the backup set, each backup piece contains the blocks from one file section. The specified value must be K or M or G, where is an integer greater than 0. K means kilobytes, M means megabytes, and G means gigabytes.

If you specify a section size that is larger than the size of the file, then RMAN does not use a multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.

BLOCK_SIZE is optional. Specifies the number of KB of data that the Oracle database reads for the backup operation. The value must be a multiple of the minimum physical block size of the Oracle database. The value must be K, where is an integer between 1 and 1024 inclusive. K means kilobytes.

RAC_NODE_IP_1, RAC_NODE_FQDN_1, RAC_NODE_IP_2, RAC_NODE_FQDN_2, RAC_NODE_IP_ , RAC_NODE_FQDN_ are optional. Specify the IP addresses and fully qualified domain names (FQDNs) of the RAC nodes. These RAC node settings are required only if the asset discoveries are not working on the RAC system and the asset report refers to the system as "Stand-alone" instead of "RAC".

ENABLE_BROWNFIELD_DISCOVERY is optional. Specifies whether to discover the database copies that were backed up before being managed by PowerProtect Data Manager. When this parameter is set to TRUE, PowerProtect Data Manager discovers the copies that the Oracle RMAN agent backed up before the asset was managed by PowerProtect Data Manager.

EXCLUDE_SID is optional. Specifies the list of Oracle SIDs to exclude from PowerProtect Data Manager discovery.

ALLOW_BACKUP is optional. Specifies the comma-separated list of Oracle SIDs to allow stand-alone Oracle backups. This parameter is only applicable for stand-alone backups.

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

34 Enabling the Oracle RMAN Agent

Authentication requirements

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

Database authentication requirements

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

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

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

NOTE: If the lockbox does not exist when you run the ddutil command, the command creates the lockbox in the

$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= and -a USERNAME= , the command prompts for the database SIDs and administrator username. The command always prompts for the administrator password.

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

ddutil -C -a USER_TYPE=DATABASE_ADMIN

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

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

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

'RMAN_AGENT_HOME' is retrieved from ddutil runtime location as '/home/oracle/opt/dpsapps/ rmanagent' Password: xxxxx Re-enter password: xxxxx Successfully set the Oracle database administrator credentials in the lockbox.

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

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

Enabling the Oracle RMAN Agent 35

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.

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/

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.

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:

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

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:

36 Enabling the Oracle RMAN Agent

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

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

Enabling the Oracle RMAN Agent 37

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

PowerProtect DD hostname: 10.125.192.190

FC service name: None FC service enabled: false

Storage Unit: multi-asset-blrv041a118-7dab9 Top Level Path: PLCTLP-43f18cb1-fadb-4b25-ae9e-e385d5b5c401 Protection Policy Name: multi-asset

User: multi-asset-blrv041a118-7dab9 Type: PROTECTION

38 Enabling the Oracle RMAN Agent

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. In the Application Agents window, click Add.

3. Select one of the following options:

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

c. Select the date until which the application agent is preapproved. d. Click Save.

If you have disabled Auto Allow List, perform the following steps:

NOTE: The Auto Allow List option is disabled by default. When Auto Allow List is enabled, all

preapproved application agents are automatically approved.

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

Approve Reject Edit, and then make the required changes. Remove

c. Click Save.

Next steps

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

View application agent details

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

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

Enabling the Oracle RMAN Agent 39

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

Agent update status displays the total number of application agents that are up-to-date, available, scheduled, in progress, or failed.

NOTE: If the update of an application agent fails for any reason, the agent host is counted as available. The host is included

in the total number of available applicant agents.

At the end of the Agent update status row, you can click the arrow to view information about scheduled updates. The Schedules table appears and displays the following information:

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

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

Table 7. Application agent information

Column Description

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

Host Name The name of the application agent host.

IP The IPv4 or IPv6 address of the application agent host.

Registration Status The registration status of the application agent: Awaiting Approval Pending Approval Registered Approved Rejected Expired Accepting Certificates Failed

OS The operating system of the application agent host.

Agent Type The application agent type.

Current Version The current version of the application agent.

Update Status The update status of the application agent host: AvailableThe PowerProtect Data Manager release is 19.12 and the application

agent release is 19.10 or 19.11. In ProgressThe update of the application agent is in progress. Up to DateThe PowerProtect Data Manager release and the application agent

release are both 19.12. ScheduledThe application agent is scheduled for an update. FailedThe update of the application agent failed. Not SupportedThe PowerProtect Data Manager release is 19.12 and application

agent release is earlier than 19.10.

Filter and sort information

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

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

40 Enabling the Oracle RMAN Agent

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

Export application agent data

To export the data that is shown in the table to a .CSV file, click Export All.

For more information about the Export All functionality, see the PowerProtect Data Manager Administration and User Guide.

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:

To enable the PowerProtect Data Manager discovery of existing stand-alone backups, you must set the

ENABLE_BROWNFIELD_DISCOVERY parameter to TRUE in the configuration file, as described in Configuration file

requirements for connection to local databases.

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 discovered 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 DD backup host and storage unit managed by PowerProtect Data Manager

With Oracle RMAN agent 19.1 or later, you can provide the DD 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.

Enabling the Oracle RMAN Agent 41

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.

Setting and reporting the retention time for existing backups

With Oracle RMAN agent, 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. 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. Update the Oracle RMAN agent on the Oracle server host.

Update the Oracle RMAN agent provides information.

2. Ensure that the ENABLE_BROWNFIELD_DISCOVERY parameter is set to TRUE in the configuration file, as described in Configuration file requirements for connection to local databases.

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

Manage the Oracle application agent 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= 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.

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

Discover an Oracle application host provides information.

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

Add a protection policy for Oracle database protection provides information.

The first backup after onboarding must be a full backup:

The first centralized backup is always 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 DD device. You can only restore from a secondary DD device.

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

42 Enabling the Oracle RMAN Agent

PowerProtect Data Manager support of Oracle RMAN agent with Oracle 21c PowerProtect Data Manager supports the Oracle RMAN agent with the following Oracle 21c features: Oracle 21c supports "read-only Oracle Home" by default. Oracle 21c supports only the multitenant container database (CDB) architecture, not the non-CDB architecture.

The following Knowledgebase article provides details about the PowerProtect Data Manager requirements for migration and protection of an Oracle database with Oracle 21c:

PowerProtect: PPDM Backup: How to continue protecting an Oracle database that is migrated from non-CDB to CDB

NOTE: The migration of a database from a non-CDB to CDB database changes the database ID. After database migration,

it is recommended that you retire the original non-CDB assets and then protect the newly discovered CDB assets going

forward.

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.

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 Stream Count. 4. Set the stream count 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 the Oracle RMAN Agent 43

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

Steps

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

44 Enabling the Oracle RMAN Agent

Managing Storage, Assets, and Protection

Topics:

Add protection storage Enable an asset source Delete an asset source Discover an Oracle application host Add and remove the credentials for Oracle assets Assign a preferred node in Oracle RAC environment Replication triggers Add a protection policy for Oracle database protection Cancel an application agent protection job Add a service-level agreement Edit the retention period for backup copies Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier) Delete backup copies Enable the Oracle RMAN agent after hostname change Enable the use of an existing asset in a modified environment Delete backup copies from RMAN catalog with ddutil command Manage the PowerProtect agent service Manage the cloud tier operations with PowerProtect Data Manager

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

Prerequisites

NOTE:

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

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

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

DD system.

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

About this task

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

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

Steps

1. From the left navigation pane, select Infrastructure > Storage.

The Storage window appears.

3

Managing Storage, Assets, and Protection 45

2. In the Protection Storage tab, click Add.

3. In the Add Storage dialog box, select a storage system (PowerProtect DD System or PowerProtect DD Management Center).

For a system pool, select DDMC.

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

5. Specify the storage system attributes:

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

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

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

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

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

9. In the Storage window, click Discover to refresh the window with any newly discovered storage systems. When a discovery completes successfully, the Status column updates to OK. If DDMC is selected, all DD systems managed by the host will be listed after discovery.

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

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

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

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

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

Results

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

View the storage unit password

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

Prerequisites

This task requires the name of the protection storage system MTree where the storage unit resides.

Steps

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

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

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

python get_dd_mtree_credential.py MTree-name For example:

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

46 Managing Storage, Assets, and Protection

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

About this task

Only the Administrator role can manage asset sources.

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

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

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

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

Steps

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

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

Results

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

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

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

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

see the PowerProtect Cloud Snapshot Manager Online Help.

Disable an asset source

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

About this task

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

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

machines, then you cannot disable the vCenter Server asset source. But if you register a vCenter server and then delete it

without creating any backups, you can disable the asset source.

Steps

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

2. Click Disable.

Results

PowerProtect Data Manager removes the tab for this asset source.

Managing Storage, Assets, and Protection 47

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

About this task

NOTE: Do not manually run the unConfigureAddOn.sh or unregister.sh command from the host. When the asset

source deletion is initiated from PowerProtect Data Manager, the unregister and unconfigure commands are run

automatically.

Only the Administrator role can manage the asset sources.

Steps

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

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

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

Results

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

Any associated assets that are protected by the protection policy are removed from the protection policy and their status is changed to deleted. These assets are removed automatically as part of daily PowerProtect Data Manager cleanup after all associated backup copies have been deleted. These assets can also be removed manually. The PowerProtect Data Manager Administration and User Guide provides details on how to remove assets from PowerProtect Data Manager.

In the PowerProtect Data Manager UI, to list the assets with the deleted status, use the appropriate filter option.

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

For an asset that was previously protected by PowerProtect Data Manager, regular compliance deletion runs until all the backup pieces are expired.

Existing backup copies that were generated before the client was added to PowerProtect Data Manager are not deleted from the PowerProtect DD storage unit. To delete the backup pieces, you must run a regular stand-alone ddutil command:

ddutil -k -b -e -R -z :/

For backup copies that PowerProtect Data Manager generates, PowerProtect Data Manager performs deletion of the copies based on the specified retention.

In the both cases, the backup administrator must perform the catalog cleanup by using the RMAN maintenance commands, such as the crosscheck and delete expired commands.

NOTE: In an Oracle RAC cluster, when the active node is down, you must use the asset source deletion option

(decommission feature) to unconfigure that particular node from the PowerProtect Data Manager. This asset source

deletion ensures that the PowerProtect Data Manager operations run automatically from the next available node.

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.

48 Managing Storage, Assets, and Protection

About this task

NOTE: Starting with release 19.9, a new Oracle database discovery method is supported, which uses the pmon process

without a dependence on /etc/oratab entries. The /etc/oratab file entries have the highest precedence for the

discovery of Oracle database resources on the system, which enables the PowerProtect Data Manager operations.

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

Discovery option.

Results

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

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

In the PowerProtect Data Manager UI, when you select Infrastructure > Assets and then click the Oracle tab, the Name

column on the Assets page lists the Oracle application assets. Each asset name in that column is an Oracle database or

instance name for a stand-alone system or a unique database name for a RAC system.

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

Managing Storage, Assets, and Protection 49

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

Assign a preferred node in Oracle RAC environment In an Oracle RAC environment, it is recommended that you assign one node to be the preferred backup node for Oracle centralized backups. You can assign the preferred backup node by setting an asset-level option in the PowerProtect Data Manager UI.

About this task

An update of PowerProtect Data Manager from a previous version automatically migrates a RAC_BACKUP_NODE_IP parameter setting in the configuration file to the preferred node setting on the Assets page in the PowerProtect Data Manager UI. If you later modify the preferred node setting in the UI, the UI setting takes precedence over the original parameter setting in the configuration file.

NOTE:

You can only set the asset-level option in the PowerProtect Data Manager UI version 19.12 or later.

The preferred node setting in the PowerProtect Data Manager UI takes precedence over a RAC_BACKUP_NODE_IP parameter setting in the configuration file for the same asset. Configuration file requirements for connection to local

databases provides details about the RAC_BACKUP_NODE_IP parameter.

In the PowerProtect Data Manager UI, when you select Infrastructure > Assets and then click the Oracle tab, the Name

column on the Assets page lists the Oracle application assets. Each asset name in that column is an Oracle database or

instance name for a stand-alone system or a unique database name for a RAC system.

Use the following procedure to assign a preferred node for centralized backups of a selected Oracle database asset in the RAC environment.

Steps

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

2. Select the required asset with the host type RAC by clicking the check box next to the asset name.

If you select more that one asset on the Assets page, the option to assign a preferred node is disabled.

3. Select More Actions > Assign Preferred Node.

4. In the Assign Preferred Node for dialog box, select the preferred node from the list in the Nodes field.

To change the Nodes field value, select a different node name from the nodes list or click Clear to delete the field value.

5. Click Save in the Assign Preferred Node for dialog box.

50 Managing Storage, Assets, and Protection

Results

After you assign the preferred RAC node by using this procedure, the node is used for backups of the selected asset during subsequent Oracle centralized backups.

Replication triggers PowerProtect Data Manager orchestrates protection policy replication objectives independently of the primary backup. When you add a replication objective to a policy, select one of the available triggers.

The default replication trigger is a schedule window that you define by setting a recurrence period plus start and end times. Replication occurs during the defined window. For example, every day between 8 p.m. and 12 a.m.

You can also trigger replication immediately after the completion of the associated primary backup, whether scheduled or manual. At the start of the primary backup, PowerProtect Data Manager generates an associated replication job that remains queued until the end of the protection job. If the backup fails or completes with exception, the associated replication job is skipped. Restarting the protection job queues the associated replication job again.

When you create a replication objective, you can specify either scheduled replication or replication after backup completion, which is applicable to both centralized and self-service protection policies.

NOTE: For replication after backup completion, PowerProtect Data Manager 19.12 or later and application agents 19.10 or

later are required. It is recommended that you update the application agents to the latest version.

Using a schedule can help you manage network traffic by replicating during off-peak hours. However, for larger backup sets, the primary backup may not finish before the start of the replication schedule, which creates a replication backlog. Replication after backup completion prevents a replication backlog from forming.

To prevent data loss, the replication after backup completion trigger replicates new backups from the primary objective and any outstanding backups that have not yet replicated.

A job status of Completed with Exceptions during replication

After a triggered replication job, you might see a job status message similar to the following:

Completed with Exceptions ABA0017: plc_linux_rac: Backup was successful for the ORACLE_DATABASE asset ORCLPP on the host blrv009d132.blr.lab.emc.com but the copy metadata information is currently unavailable.

The backup of this asset completed successfully but the copy metadata information has not yet been discovered by PowerProtect Data Manager. If the 'Replicate immediately upon backup completion' option is enabled for this protection policy, the replication job for the copy might appear in 'Unknown' or 'Cancel' state. Once the copy metadata is discovered by PowerProtect Data Manager, the copy will be replicated.

Review the backup copy details in the View Copies pane of the PowerProtect Data Manager UI Infrastructure > Assets window to determine when the discovery is complete.

If you see this message, the replication backup is not immediately available.

To correct this issue, either wait for the next automatic discovery or initiate a discovery.

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.

Managing Storage, Assets, and Protection 51

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.

NOTE: PowerProtect Data Manager does not support the automatic retention lock (ARL) setting on the DD system. The

option to create a storage unit during protection policy configuration does not support compliance mode retention locking,

only governance mode. To use compliance mode retention locking, create and configure a storage unit before you configure

an associated protection policy. If you enable retention locking and select a storage unit where the retention lock mode is

None, the retention lock defaults to governance mode. The PowerProtect Data Manager Administration and User Guide

provides more information.

Steps

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

The Protection Policies window appears.

2. In the Protection Policies window, click Add.

The Add Policy wizard appears.

3. On the Type page, specify the following fields, and then click Next:

NameType a descriptive name for the protection policy. DescriptionType a description for the policy. TypeSelect 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 ProtectionSelect this option to use PowerProtect Data Manager to centrally manage all objectives 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 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 ProtectionSelect this option to use Oracle to create local backup protection. PowerProtect Data Manager creates a protection policy and manages extra objectives.

Self-service protection means that DBAs schedule the backups but PowerProtect Data Manager discovers and manages the life cycle of the copies.

ExclusionSelect this type if there are assets within the protection policy that you plan 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 provides instructions.

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

52 Managing Storage, Assets, and Protection

For Centralized Protection:

a. Click Add under Primary Backup.

The Add Primary Backup dialog appears.

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

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

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

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

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

storage system.

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

The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.

Setting a retention lock applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

SLASelect 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 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 everySpecify how often to create a full backup. Retain forSpecify the retention period for the full backup.

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

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

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

backups are recoverable until they have all expired.

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

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

ii. 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 every For , 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 forSpecify the retention period for the backup.

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

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

point-in-time copies.

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

Managing Storage, Assets, and Protection 53

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

iii. Click Add Backup and repeat the procedure for creating full backups if you want to create additional backup copies at different intervals with different retention periods.

Within this protection policy, when a full schedule conflicts with another full backup schedule, a message appears, indicating that there is a conflict. Schedule occurrences can conflict with each other when the activity windows are identical or occur entirely within the same time range. To avoid full schedule conflicts in a policy, edit the activity windows. If you proceed with conflicting schedules, the backup of the lower priority schedule will be skipped. Schedule priority is ranked according to the following criteria:

Full schedules have a higher priority than Synthetic Full schedules. For schedules of the same backup type, the schedules that run less frequently have a higher priority than

schedules that run more frequently. For schedules with the same backup type and frequency, the schedule with the longest activity window has

the higher priority. If the activity windows are also identical, only one of these schedules will run.

NOTE: When a schedule conflict between full backups occurs, PowerProtect Data Manager retains the full

backup with the longest retention period.

d. Click Save to save the 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.

After completing the objective, you can change any details by clicking Edit next to the objective.

NOTE:

When a new asset is added to an existing policy, you must run an ad hoc full backup for the newly added asset.

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.

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 NameSelect a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.

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

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

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

storage system.

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

The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.

Setting a retention lock applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

SLASelect 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 provides instructions.

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

54 Managing Storage, Assets, and Protection

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

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

time copies.

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

When a different retention time for all backup types is set, you can create additional full backup patterns with different retention times. For example, you can add a full backup pattern Retain full backups created every week on the Monday and Tuesday for 2 months.

d. Click Save to save the 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.

After completing the objective, you can change any details by clicking Edit next to the objective.

9. Optionally, replicate the backups:

NOTE:

To enable replication, ensure that you add remote protection storage as the replication location. The PowerProtect Data

Manager Administration and User Guide provides detailed instructions about adding remote protection storage.

When creating multiple replicas for the same protection policy, it is recommended to select a different storage system

for each copy. If you select a storage unit that is the target of another objective for the same policy, the UI issues

a warning. The PowerProtect Data Manager Administration and User Guide provides information about replicating to

shared protection storage to support PowerProtect Cyber Recovery. Verify the storage targets and the use case before

you continue.

When you create a replication objective, you can specify either scheduled replication or replication after backup completion.

NOTE: For replication after backup completion, PowerProtect Data Manager 19.12 or later and application agents 19.10

or later are required. It is recommended that you update the application agents to the latest version.

For replicas of centralized backups, when you set retention periods for different backup types, any undefined types use the full backup retention period. For example, if you do not define a log backup in the primary objective, the log backup for the replication objective is also undefined. After you run a manual log backup, replicas of that log backup use the same retention period as the full backup.

a. Click Replicate next to Primary Backup or Primary Retention. An entry for Replicate is created to the right of the primary backup objective.

b. Under Replicate, click Add. The Add Replication dialog appears, with information in the left pane for each schedule that has been added for the primary backup objective of this protection policy.

NOTE: Backups for all of the listed schedules will be replicated. You cannot select individual schedules for

replication.

c. Select a storage target:

Storage NameSelect a destination from the list of protection storage. Or, select Add to add a protection storage system and complete the details in the Storage Target window.

Storage UnitSelect an existing storage unit on the protection storage system. Or, select New to automatically create a storage unit.

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

The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.

SLASelect an existing replication service level agreement that you want to apply to this schedule from the list. Or, select Add to create a replication SLA within the Add Service Level Agreement wizard.

The PowerProtect Data Manager Administration and User Guide provides more information about replication targets, such as SLAs.

d. Select when to replicate the backups:

Managing Storage, Assets, and Protection 55

Replication triggers provides more information.

To replicate after the backup finishes, move the Replicate immediately upon backup completion slider to on. For scheduled replication, move the Replicate immediately upon backup completion slider to off, and then

complete the schedule details in the Add Replication dialog.

For replication of the primary backup, the schedule frequency can be every day, week, month, or x hours.

For daily, weekly, and monthly schedules, the numeric value cannot be modified. For hourly, however, you can edit the numeric value. For example, if you set Create a Full backup every 4 hours, you can set a value of anywhere from 1 to 12 hours.

By default, all replicas of the primary backup objective inherit the retention period from the Retain For value of the synthetic full and full backup schedules.

e. To specify a different retention period for individual synthetic full and full replicas, clear Set the same retention time for all replicated copies, click Edit in the row of each schedule that you want to change, update the value in the Retain For field, and then click Save.

CAUTION: Setting a retention period for the replicas of other backup types (such as log backups,

incremental, and differential backups, where applicable) that is shorter than the retention period of the

corresponding full backup may result in being unable to recover from those replicas.

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

10. Optionally, to move backups from protection storage to Cloud Tier, add a Cloud objective for the primary or replication objective:

NOTE: To move a backup or replica to Cloud Tier, objectives must have a retention time of 14 days or more.

PowerProtect Data Manager also requires the discovery of protection storage with a configured Cloud unit.

a. Click Cloud Tier next to Primary Backup or Primary Retention. Or, if adding a Cloud objective for a replication objective that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary objective, or below the replication objective.

b. Under the entry for Cloud Tier, click Add. The Add Cloud Tier Backup dialog appears, with summary information for the parent objective to indicate whether you are adding this Cloud Tier objective for the primary objective or the replication objective.

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

Manage the cloud tier operations with PowerProtect Data Manager provides detailed instructions for adding a Cloud objective for a primary or replication objective.

11. Click Next. The Options page appears.

12. On the Options page, select the additional options that are required for the policy:

Archive LogsSelect the appropriate option for the deletion of archived logs:

Do not deleteSelect 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 backupSelect 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.

Recovery Catalog OptionOnly for centralized protection in an Oracle Data Guard environment, select the appropriate option for resynchronizing the recovery catalog with a database:

NoneBy default, the None value is selected. Select this value when the recovery catalog does not need to be automatically resynchronized with backup copies. This option is applicable to a non-Data Guard environment.

Synchronous syncSelect this option to resynchronize the recovery catalog synchronously with backup copies after each backup.

Asynchronous syncSelect this option to resynchronize the recovery catalog asynchronously with backup copies after each backup.

NOTE:

56 Managing Storage, Assets, and Protection

In the Data Guard environment, it is recommended that you use a recovery catalog to manage the RMAN metadata

for all physical databases, including both primary and standby databases. RMAN uses the recovery catalog as the

single source of truth for the Data Guard environment.

RMAN only automatically resynchronizes the recovery catalog with a database when connected to this database

as TARGET. RMAN does not automatically resynchronize every database in the Data Guard environment when

connected as TARGET to one database in the environment.

Files Per SetSpecify the maximum number of files that RMAN can include in a backup set. The value must be an integer between 1 and 64, inclusive.

NOTE:

As an alternative to setting the options Files Per Set, Maximum Open Files, Block Size, and Section Size on the

Options page, you can set the parameters FILESPERSET, MAXOPENFILES, BLOCK_SIZE, and SECTION_SIZE,

respectively, in the configuration file rman_agent.cfg. Configuration file requirements for connection to local

databases provides details about the configuration file.

The configuration file parameter settings take precedence over the option settings in the PowerProtect Data

Manager UI. These parameter and option settings apply only to centralized backups. The Files Per Set and Section

Size settings apply only to full, incremental cumulative, and incremental differential backupsnot to log backups.

Maximum Open FilesSpecify the maximum number of input files that a backup or copy can have open at a given time. The value must be an integer greater than 0.

Block SizeSpecify the number of KB of data that the Oracle database reads for the backup operation. The value must be a multiple of the minimum physical block size of the Oracle database. The value must be K, where is an integer between 1 and 1024 inclusive. K means kilobytes.

Section SizeSpecify the size in KB, MB, or GB of each backup section in a multisection backup. In the backup set, each backup piece contains the blocks from one file section. The specified value must be K or M or G, where is an integer greater than 0. K means kilobytes, M means megabytes, and G means gigabytes.

If you specify a section size that is larger than the size of the file, then RMAN does not use a multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.

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

13. Click Next. The Summary page appears.

14. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any information. When completed, click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy. When the new protection policy group is created, PowerProtect Data Manager automatically performs a full backup. Subsequent backups are performed according to the specified schedule.

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

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

NOTE:

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

When a backup fails, the backup job steps appear as canceled for the particular database. The backup job steps are

displayed on the Step Log tab in the details section of the Job ID Summary window.

16. When PowerProtect Data Manager and the client are updated from an older version and the target DD 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.

Managing Storage, Assets, and Protection 57

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

About this task

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

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

NOTE:

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

either success or failure.

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

and User Guide provides more information.

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

Steps

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

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

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

To cancel a job group:

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

A job group warning prompt appears.

b. Click OK at the prompt.

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

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

To cancel an asset job:

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

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

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

A job warning prompt appears.

c. Click OK at the prompt.

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

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

58 Managing Storage, Assets, and Protection

Add a service-level agreement SLA Compliance 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. Also, the Extended Retention

SLA applies to protection policies created in PowerProtect Data Manager 19.11 and earlier only. The Extended Retention

objective was removed in PowerProtect Data Manager 19.12. When updating to PowerProtect Data Manager 19.12 from a

previous release, any protection policies created in the earlier release with the Extended Retention SLA will continue to be

supported, however, you will not be able to edit the Extended Retention SLA in these policies.

In the SLA Compliance window, you can export compliance data by using the Export All functionality.

Steps

1. From the PowerProtect Data Manager UI, select Protection > SLA Compliance.

The SLA Compliance window appears.

2. Click Add or, if the assets that you want to apply the SLA to are listed, select these assets and then click Add.

The Add Service Level Agreement wizard 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. Replication. If you choose this type, go to step 6. Cloud Tier. If you choose this type, go to step 7.

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, Replication, and Cloud Tier copies. c. If applicable, select Maximum Copies, and specify the number of Backup, Replication, and Cloud Tier copies. d. If applicable, select Available Location and select the applicable locations. To add a location, click Add Location.

Options include the following: InInclude locations of all copies in the SLO locations. Selecting this option does not require every SLO location to

have a copy. Must InInclude locations of all copies in the SLO locations. Selecting this option requires every SLO location to

have at least one copy. ExcludeLocations of all copies must be non-SLO locations.

e. If applicable, select Allowed in Cloud through Cloud Tier/Cloud DR. f. 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 required (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 required to configure as an independent objective in the

SLA, or select both Recovery Point Objective required and Compliance Window for copy type. 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

Managing Storage, Assets, and Protection 59

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, select Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.

NOTE: For compliance validation to pass, the value set for the Retention Time Objective must match the lowest

retention value set for the backup levels of this policy's target objectives. For example, if you set the synthetic full

backup Retain For to 30 days but set the full backup Retain For to 60 days, the Retention Time Objective must be

set to the lower value, in this case, 30 days.

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 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, select Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.

NOTE: For compliance validation to pass, the value set for the Retention Time Objective must match the lowest

retention value set for the backup levels of this policy's target objectives.

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 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 determine if PowerProtect Data Manager is deleting expired copies. This option is disabled by default.

c. If applicable, select Retention Time Objective and specify the number of Days, Months, Weeks, or Years.

NOTE: For compliance validation to pass, the value set for the Retention Time Objective must match the lowest

retention value set for the backup levels of this policy's target objectives.

d. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default. e. Click Finish.

8. If the SLA has not already been applied to a protection policy:

a. Go to Protection > Protection Policies. b. Select the policy, and then click Edit.

9. In the Objectives row of the Summary window, click Edit.

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

11. Click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy.

12. Click Go to Jobs to open the Jobs window to monitor the backup and compliance results, or click OK to exit.

60 Managing Storage, Assets, and Protection

NOTE: Compliance checks occur automatically every day at 2 a.m. Coordinated Universal Time (UTC). If any objectives

are out of compliance, an alert is generated at 2 a.m. UTC. The Validate job in the System Jobs window indicates the

results of the daily compliance check.

For a backup SLA with a required RPO setting that is less than 24 hours, PowerProtect Data Manager performs real-time compliance checks. If you selected Compliance Window for copy type and set the backup level to All, the real-time compliance check occurs every 15 minutes only within the compliance window. If the backup level is not All, or if a compliance window is not specified, the real-time compliance check occurs every 15 minutes without stop.

NOTE: If the backup SLA has a required RPO setting of 24 hours or greater, compliance checks occur daily at 2 a.m.

UTC. Real-time compliance checks do not occur for backup SLAs with an RPO setting of 24 hours or greater.

Real-time compliance-check behavior

If the interval of time between the most recent backup of the asset and the compliance check is greater than the RPO requirement, then an alert indicates the RPO of the asset is out of compliance. This alert is generated once within an RPO period. If the same backup copy is missed when the next compliance check occurs, no further alerts are generated.

If the interval of time between the most recent backup of the asset and the compliance check is less than the RPO requirement, the RPO of the asset is in compliance.

If multiple assets in a policy are out of compliance at the same time when a compliance check occurs, a single alert is generated and includes information for all assets that are out of compliance in the policy. In the Alerts window, the asset count next to the alert summary indicates the number of assets that are out of compliance in the policy.

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

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

About this task

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

Steps

1. Select Infrastructure > Assets.

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

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

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

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

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

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

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

period.

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

Managing Storage, Assets, and Protection 61

Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier)

NOTE: This section applies to protection policies created in PowerProtect Data Manager 19.11 and earlier only. For

protection policies created in PowerProtect Data Manager 19.12, instead of using the Extend Retention objective to

extend the retention period of certain full copies, you can now add multiple full schedules for primary backup and replication

objectives. When updating to PowerProtect Data Manager 19.12 from a previous release, any protection policies created

in the earlier release with the Extend Retention objective will continue to be supported, however, you will not be able

to edit existing extended retention objectives, or add new extended retention objectives, in these policies. The Knowledge

Base article 000204454 at https://www.dell.com/support/ provides detailed information about specific Extend Retention

objective migration scenarios when updating to PowerProtect Data Manager 19.12.

For protection policies created in PowerProtect Data Manager 19.11 and earlier, the Extend Retention objective allows you to 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 objective for a protection policy, you define a set of matching criteria that select preferred backups to retain. If the matching criteria do not identify a matching backup, PowerProtect Data Manager automatically retains the preferred alternative backup according to one of the following methods:

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

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

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

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

For look-forward matching, the next available backup can be a manual 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 objective 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:

62 Managing Storage, Assets, and Protection

Backups that start at 12:00 a.m. on Sunday and 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 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 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.

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 objective. 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 objective 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 objective that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup that is taken between 12:00 p.m. on Sunday and 12:00 p.m. on Monday for long-term retention.

Replication of extended retention backups

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

Managing Storage, Assets, and Protection 63

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

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

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

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

About this task

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

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

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

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.

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.

64 Managing Storage, Assets, and Protection

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

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

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

appears as Completed with Exceptions.

When the job completes, the task summary provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time are 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 are shown in UTC. Go to Alerts > Audit Logs to view the audit log.

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

Retry a failed backup copy deletion

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

Steps

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

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

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

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

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

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 that you want to delete the selected backup copies.

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

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

Export data for deleted backup copies

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

Steps

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

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

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

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

4. Specify the following fields for the export:

a. Time Range

The default is Last 24 Hours.

b. Copy Status

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

Managing Storage, Assets, and Protection 65

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

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

from the agent host.

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

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

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

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

Remove backup copies from the PowerProtect Data Manager database

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

About this task

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

Steps

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

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

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

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

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

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

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

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

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

Enable the Oracle RMAN agent after hostname change After the hostname of the Oracle RMAN agent host is changed, you must delete and re-create the lockbox files and re-register the Oracle RMAN agent.

About this task

Perform the following steps to enable the Oracle RMAN agent operations after the hostname is changed.

66 Managing Storage, Assets, and Protection

Steps

1. Unregister the Oracle RMAN agent from the PowerProtect Data Manager server by running the dpsapps/agentsvc/ unregister.sh script.

2. Change the fully-qualified domain name (FQDN) of the Oracle host:

a. Shut down the Oracle database, and stop the listener. b. Run the following command to set the hostname:

hostnamectl set-hostname c. Edit the hostname in the tnsnames.ora, listener.ora, and hosts files.

d. Start the Oracle database and listener.

3. Delete the following existing lockbox files:

ddboost.config* files in the $RMAN_AGENT_HOME/config directory

agents.clb* files in the dpsapps/agentsvc/config directory

4. Obtain the updated hostname of the client system by running the uname -n command.

5. Create the new lockbox files on the client by running the ddutil command:

ddutil -H "hostnames "

Replace with the hostname obtained in the previous step.

6. Re-register the Oracle RMAN agent with PowerProtect Data Manager by running the register.sh script from the agent service directory dpsapps/agentsvc.

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

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

Enable the use of an existing asset in a modified environment When the Oracle environment is modified, you can follow the procedures in this topic to continue using an existing asset from an existing protection policy with PowerProtect Data Manager.

When you change the SID of the stand-alone database or the database name of the RAC database of an Oracle asset, the asset is treated as a new Oracle asset. If the asset is not automatically added to the protection policy using a protection rule, you must modify the protection policy. However, you have the option to continue to protect the original Oracle asset, even after changing the SID of the stand-alone database or the database name of the RAC database.

You can continue using an existing asset that was configured in the current version of PowerProtect Data Manager even after changing the SID of the stand-alone database or the database name of the RAC database. To continue using the existing asset, you must provide the previous SID of the stand-alone database or the database name of the RAC database in a configuration file, as described in the following procedures.

Enable the use of an existing asset when the SID is changed

For example, the DBID of the database is 1630741966, and the SID will be changed from orcl1 (previous SID) to orcl2 (new SID).

Complete the following steps to enable the continued use of the existing asset when the SID is changed:

1. Before you change the SID value, specify the new SID value in the parameter setting EXCLUDE_SID= in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg.

For example, add the following parameter setting in the configuration file:

EXCLUDE_SID=orcl2 2. Create a new configuration file, $RMAN_AGENT_HOME/settings/rename.config, which will contain the current DBID

and both previous and new SID values. 3. Edit the rename.config file, and add the following two lines in the file:

Managing Storage, Assets, and Protection 67

[ : ]

PREVIOUS_SID=

For example:

[1630741966:orcl2]

PREVIOUS_SID=orcl1 4. Set the rename.config file access permissions to 666, as with the following command:

chmod 666 rename.config 5. Ensure that the SID value of the database is changed to the new value. 6. Delete the parameter setting EXCLUDE_SID= in the configuration file $RMAN_AGENT_HOME/config/

rman_agent.cfg.

Enable the use of an existing asset when the database name is changed

For example, the DBID of the database is 1630741966, and the database name will be changed from orcl1 (previous database name) to orcl2 (new database name).

Complete the following steps to enable the continued use of the existing asset when the database name is changed:

1. Before you change the database name, specify the SID of the database in the parameter setting EXCLUDE_SID= in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg on all nodes in the RAC environment.

2. Create a new configuration file, $RMAN_AGENT_HOME/settings/rename.config, which will contain the current DBID and both previous and new database names.

3. Edit the rename.config file, and add the following two lines in the file:

[ : ]

PREVIOUS_DBNAME=

For example:

[1630741966:orcl2]

PREVIOUS_DBNAME=orcl1 4. Set the rename.config file access permissions to 666, as with the following command:

chmod 666 rename.config 5. Ensure that the database name is changed to the new name. 6. Delete the parameter setting EXCLUDE_SID= in the configuration file $RMAN_AGENT_HOME/config/

rman_agent.cfg on all nodes in the RAC environment.

Delete backup copies from RMAN catalog with ddutil command You can use the ddutil -r command with specific command options to delete the backup copies with certain tag IDs or certain time ranges from the RMAN catalog. The -a DRY_RUN option specifies to only report which backup copies will be deleted, and not perform any backup copy deletion.

NOTE:

You must run the ddutil -r command as the root user.

Starting with version 19.12, all Oracle backups are assigned a unique tag ID. By default, the ddutil -r command deletes

the RMAN catalog entries for the latest tagged backup copies.

68 Managing Storage, Assets, and Protection

Dry run of ddutil command reports backup copies to be deleted

When you run the ddutil -r command with the -a DRY_RUN option, the command does not perform any backup copy deletion from the RMAN catalog, but only reports the backup copies to be deleted:

ddutil -r -a SID= -a DRY_RUN=TRUE [-b ] -e [-a TAG_NAME= -a CONNECTION_TYPE={OS|DB|WALLET} -a TNS_SERVICE= ]

Other than the -a DRY_RUN option, the only mandatory options are -a SID= and -e . The other listed options are optional.

For example, the following command reports the backup copies to be deleted from the RMAN catalog for the specified SID, time, tag ID, and database authentication connection:

ddutil -r -a SID=orcl -a DRY_RUN=TRUE -e "Thu Jul 29 16:00:13 IST 2022" -a TAG_NAME=23d20a24 -a CONNECTION_TYPE=DB -a TNS_SERVICE=orcl RMAN instance: Oracle system ID: orcl Following backup pieces will be deleted from catalog: ./PLCTLP-d2394afd-08d6-4093-bf18-32d17418fa3b/Automated_data_ORCL_1630219917_gn13r70f_1 ./PLCTLP-d2394afd-08d6-4093-bf18-32d17418fa3b/Automated_data_ORCL_1630219917_gm13r70f_1 ./PLCTLP-d2394afd-08d6-4093-bf18-32d17418fa3b/Automated_data_ORCL_1630219917_go13r70j_1 :

Delete all backups with a specified asset tag

To delete all the backups from the RMAN catalog with a specified asset tag, run the ddutil -r command with the -a TAG_NAME= option.

For example:

OS Authentication: ddutil -r -a SID=orcl -a TAG_NAME=d617af34 -e "Thu Jul 29 16:00:13 IST 2022" Database Authentication: ddutil -r -a SID=orcl -a TAG_NAME=d617af34 -e "Thu Jul 29 16:00:13 IST 2022" -a CONNECTION_TYPE=DB -a TNS_SERVICE=orcl Wallet Authentication: ddutil -r -a SID=orcl -a TAG_NAME=d617af34 -e "Thu Jul 29 16:00:13 IST 2022" -a CONNECTION_TYPE=WALLET -a TNS_SERVICE=orcl

Delete all backups for a specified time range

To delete all the backups from the RMAN catalog for a specified time range, run the ddutil -r command with the -b (optional) and -e options.

For example:

OS Authentication: ddutil -r -a SID=orcl -b "Fri Jul 1 16:00:00 IST 2022" -e "Thu Jul 29 16:00:13 IST 2022" Database Authentication: ddutil -r -a SID=orcl -b "Fri Jul 1 16:00:00 IST 2022" -e "Thu Jul 29 16:00:13 IST 2022" -a CONNECTION_TYPE=DB -a TNS_SERVICE=orcl Wallet Authentication: ddutil -r -a SID=orcl -b "Fri Jul 1 16:00:00 IST 2022" -e "Thu Jul 29 16:00:13 IST 2022" -a CONNECTION_TYPE=WALLET -a TNS_SERVICE=orcl

Managing Storage, Assets, and Protection 69

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

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

About the PowerProtect agent service

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

This section uses to represent the PowerProtect agent service installation directory. By default, the agent service installation location is /opt/dpsapps/agentsvc on AIX or Linux. All files that are referenced in this section are the relative paths to the agent service installation location.

The PowerProtect agent service performs the following operations:

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

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

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

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

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

NOTE: In the current release, the centralized restores are only available for the File System agent, Microsoft SQL agent,

and Storage Direct agent.

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

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

Manager deletes all the expired copies as needed.

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

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

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

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

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

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

70 Managing Storage, Assets, and Protection

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

location in the config.yml file.

Start, stop, or obtain the status of the PowerProtect agent service

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

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

To start the agent service:

# register.sh --start

Started agent service with PID - 1234

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

# service agentsvc start To stop the agent service:

# register.sh --stop

Successfully stopped agent-service.

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

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

# register.sh --status

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

# register.sh --status

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

running:

# service agentsvc status

Register the PowerProtect agent service to a different server address on AIX or Linux

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

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

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

1. Perform the required steps, depending on whether the registered PowerProtect Data Manager is available:

If the registered PowerProtect Data Manager is available, delete the host from PowerProtect Data Manager. Log in to the PowerProtect Data Manager UI, select the host in the Infrastructure > Asset Sources window, and click Delete.

If the registered PowerProtect Data Manager is unavailable:

Managing Storage, Assets, and Protection 71

a. Unconfigure the Oracle RMAN agent by logging in as the root user on the Oracle RMAN host and running the / home/oracle/opt/dpsapps/rmanagent/addon/unConfigureAddOn.sh script.

b. Unregister the Oracle RMAN agent by running the /opt/dpsapps/agentsvc/unregister.sh script.

2. Delete the /ssl folder and /dbs/v1/objects.db.

3. Rename the copies.db file in the dbs/v1/ folder to copies-backup.db.

4. Complete the required addons configuration and registration with PowerProtect Data Manager. Run the configureAddOn.sh script from the RMAN agent addon directory $RMAN_AGENT_HOME/addon and specify the new PowerProtect Data Manager IP for registration. Step 4 provides more information.

5. Verify that the agentsvc process is started.

6. Verify the agent registration status:

a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is Registered.

7. 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 this section describes how to bring the agent service to an operational state to continue if a disaster occurs and the agent service datastore is lost.

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

By default, the agent service backs up consistent copies of its datastore files to the local disk every hour and keeps the copies for 7 days. Each time the agent service backs up the contents of the datastore, it creates a subdirectory under the /dbs/v1/backups repository. The subdirectories are named after the time the operation occurred, in the format YYYY-MM-DD_HH-MM-SS_epochTime.

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

Restore the PowerProtect Data Manager agent service datastore

Prerequisites

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

About this task

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

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

72 Managing Storage, Assets, and Protection

Steps

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

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

2. Select the most recent datastore backup.

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

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

4. Start the agent service.

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

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

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

Add a cloud tier objective to a protection policy

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

Prerequisites

Ensure that a DD 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 objective from primary and replication objectives. Objectives 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 objective is not already created, and fill out the fields in the Target and Schedules panes on the Add Primary Backup dialog.

Managing Storage, Assets, and Protection 73

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

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

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

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

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. For Tier After, set a time of 14 days or more.

The protection policy is now enabled with cloud tiering.

10. Click Next to proceed with the remaining pages of the Add Policy wizard, verify the information, and then click Finish. A new job is created, which you can view under the Jobs tab after the job completes.

Tier the PowerProtect Data Manager backups from DD to the cloud

Once you add the Oracle database assets to a protection policy that contains a cloud tier objective, 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 DD 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 DD system.

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

# data-movement policy show

Mtree Target(Tier/Unit Name) Policy Value ----------------------------------------- ---------------------- ----------- ------- /data/col1/rman137-blrv136g140-840dd Cloud/ecs-unit app-managed enabled /data/col1/rman134-copy-blrv136g138-61900 Cloud/ecs-unit app-managed enabled /data/col1/rman-11-blrv136h010-7014f Cloud/ecs-unit app-managed enabled

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

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

After 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 DDOS Administration Guide provides more details about cloud tier data movement.

Restore the cloud tier backups to DD

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

The PowerProtect Data Manager software recalls a copy of the backup from the cloud to the local (active) tier of the DD system, and then performs a restore of the backup from the active tier to the client. The status appears as Cloud. After the

74 Managing Storage, Assets, and Protection

restore, the backup copy is removed from the cloud tier, and is stored on the active tier of the DD system for a minimum of 14 days, after which the backup may be returned to the cloud, depending on the protection policy.

Recall and 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 DD system and restore this backup.

About this task

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

Steps

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

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

3. Click PowerProtect DD, and then select one of the available copies in the table with the location as Cloud.

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

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

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

Managing Storage, Assets, and Protection 75

Performing Self-Service Backups and Restores 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.

Considerations for self-service backups in a Data Guard environment

In an Oracle Data Guard environment, you must run the self-service backups without connecting to the recovery catalog. Synchronize the recovery catalog in separate RMAN sessions at regular intervals. This operation updates the recovery catalog with the current metadata from the target database control file. You can run the resync catalog command to initiate a full resynchronization of the recovery catalog.

To enable the self-service backups for an Oracle RAC Data Guard configuration, you must add the DB_UNIQUE_NAME parameter setting explicitly in the ALLOCATE CHANNEL line in the RMAN script. For example:

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=/PLC-RAC-DG-blrv136g138-e8e4e, BACKUP_HOST=10.125.208.242, ORACLE_HOME=/u02/software, DB_UNIQUE_NAME=DGUARD)';

Considerations for all self-service backups

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 control file backups

either with the data backups or in separate RMAN sessions. To perform the archived log, spfile, and control file backups in

the same RMAN session, add the archived log backup command after the data backups command.

When you perform the different types of data backups in the same RMAN session, the backups are reported incorrectly.

The following example RMAN scripts in this topic perform a database backup and archived log backup by using separate

backup commands.

RMAN sessions must be exited for every backup and restore operation. Otherwise, the self-service job that monitors the

progress will continue to run indefinitely or until the session exits.

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

4

76 Performing Self-Service Backups and Restores of Oracle Databases

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:

$RMAN_AGENT_HOME/bin/ddutil -s

PowerProtect DD hostname: 10.125.136.106

FC service name: None FC service enabled: false

Storage Unit: oracle-self_policy-blrv034d018-R-df3c7 Top Level Path: PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522 Protection Policy Name: self_policy

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

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, top-level pathname, and DD 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 in separate statements:

connect target username/password;

run { configure controlfile autobackup on; set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

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 './ PLCTLP-4eb04bd9-b825-4e72- b668-14e9aacaa522/%F';

backup archivelog all delete input format './ PLCTLP-4eb04bd9-b825-4e72- b668-14e9aacaa522/%F';

release channel c1; }

Performing Self-Service Backups and Restores of Oracle Databases 77

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 { set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

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 './ PLCTLP-4eb04bd9-b825-4e72- b668-14e9aacaa522/%F';

backup archivelog all delete input format './ PLCTLP-4eb04bd9-b825-4e72- b668-14e9aacaa522/%F';

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.

To identify the storage unit and DD 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, top-level pathname, and DD 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 { set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

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

78 Performing Self-Service Backups and Restores of Oracle Databases

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 { set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

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.

To automate these steps, you can run the following RMAN script after making any required changes to the Oracle DBID and autobackup file name. This sample RMAN script is used to restore to a different host with the same file structure as the source host. The following steps provide more details.

set DBID =1575537735; run { set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F'; 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. In the mandatory parameter setting EXCLUDE_SID= , specify the Oracle production database SID (instance name).

Performing Self-Service Backups and Restores of Oracle Databases 79

To obtain the instance name, run the following command in the SQLPlus utility as an Oracle user in the production database. For example:

SQL> SELECT INSTANCE_NAME FROM V$INSTANCE;

INSTANCE_NAME ------------- orcl

Specify the INSTANCE_NAME value in the EXCLUDE_SID= parameter setting in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg. This setting prevents any duplicate discovery during an Oracle redirected restore. Configuration file requirements for connection to local databases provides details about the parameter settings in the configuration file.

2. To obtain details about the DD 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

PowerProtect DD hostname: 10.63.96.240

FC service name: None FC service enabled: false

Storage Unit: POLICYwlt-blrv136g140-6d974 Top Level Path: PLCTLP-43be371a-37fa-44d1-8351-30eac82e713e

User: POLICYwlt-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, top-level pathname, and DD Boost username.

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

For example, the following command displays the DD Boost storage unit password:

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

Record the DD Boost storage unit password.

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

Install and configure the Oracle RMAN agent provides more information.

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

80 Performing Self-Service Backups and Restores of Oracle Databases

PowerProtect DD server name: 10.125.198.116 PowerProtect DD storage unit name: ppdm-1910-blrv034d018-75914 DD Boost username: ppdm-1910-blrv034d018-75914 Password: Re-enter password: Successfully set the DD Boost credentials in the lockbox. Press y or Y to add more storage unit details. Press n or N to exit:

6. 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 :/

where and 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) / name>/c- -20200807-03 file 644 18874368 Fri Aug 7 13:03:19 2020 (1596785599) / name>/c- -20200807-02 file 644 18874368 Fri Aug 7 12:47:09 2020 (1596784629) / name>/c- -20200807-01 file 644 18874368 Fri Aug 7 12:37:39 2020 (1596784059) / name>/c- -20200807-00 file 644 262144 Fri Aug 7 13:06:29 2020 (1596785789) / name>/Automated_spfile_ORCL_ _14v78u8g_1 file 644 262144 Fri Aug 7 12:37:38 2020 (1596784058) / name>/Automated_spfile_ORCL_ _0hv78sim_1 file 644 262144 Fri Aug 7 13:06:24 2020 (1596785784) / name>/Automated_data_ORCL_ _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.

7. Create the required folders on the target client. The following example shows the creation of audit, recovery, and control file destination folders that are the same as on the source client:

Create the audit file destination folder /home/oracle/app/oracle/admin/orcl/adump.

Create the recovery file destination folder /home/oracle/app/oracle/fast_recovery_area.

Create the control file destination folder /home/oracle/app/oracle/oradata.

Ensure that each folder has the same permissions as the Oracle home path $RMAN_AGENT_HOME/bin. NOTE: If you must perform the restore to a target host that has a different directory file structure than the source

host, then you can create the pfile from the spfile, to update the file directory structure in the pfile.

8. Start the Recovery Manager on the target client.

a. Go to the /home/oracle/ /bin/ directory, where 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/ / .

Performing Self-Service Backups and Restores of Oracle Databases 81

Oracle sets the required environment variables. c. To start the Recovery Manager with default parameters, run the following command:

rman target /

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>

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

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

NOTE:

If the restore is performed to a different directory file structure, add the command create pfile from spfile; in

the following RMAN script. You can edit the pfile manually to update the new directory file structure.

You can specify the different file paths and file names to restore the spfile and pfile. For example:

restore spfile to '/u01/oracle/19.3/dbs/spnewdb.ora' from autobackup; create pfile from spfile='/u01/oracle/19.3/dbs/spnewdb.ora';

RMAN> set DBID=1575537735; executing command: SET DBID

RMAN> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/%F'; executing command: SET CONTROLFILE AUTOBACKUP FORMAT

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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 8>

82 Performing Self-Service Backups and Restores of Oracle Databases

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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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: PowerProtect DD Boost API

allocated channel: C2 channel C2: SID=28 device type=SBT_TAPE channel C2: PowerProtect DD Boost API

allocated channel: C3 channel C3: SID=24 device type=SBT_TAPE channel C3: PowerProtect DD Boost API

allocated channel: C4 channel C4: SID=25 device type=SBT_TAPE channel C4: PowerProtect DD Boost API

Starting restore at 07-JAN-22

channel C1: looking for AUTOBACKUP on day: 20220107 channel C1: AUTOBACKUP found: ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ c-1617195089-20220107-05 channel C2: looking for AUTOBACKUP on day: 20220107 channel C2: skipped, AUTOBACKUP already found channel C3: looking for AUTOBACKUP on day: 20220107 channel C3: skipped, AUTOBACKUP already found channel C4: looking for AUTOBACKUP on day: 20220107 channel C4: skipped, AUTOBACKUP already found channel C1: restoring spfile from AUTOBACKUP ./PLCTLP-d0af4f59-d810-4b6b- aef1-1f7a8709ca47/c-1617195089-20220107-05 channel C1: SPFILE restore from AUTOBACKUP complete Finished restore at 07-JAN-22 released channel: C1 released channel: C2 released channel: C3 released channel: C4

11. 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. If the pfile creation command is added in the RMAN script in the preceding step 10, then verify the newly created pfile in

the $ORACLE_HOME/dbs directory.

Performing Self-Service Backups and Restores of Oracle Databases 83

The following type of information appears on the console:

rw-rw----. 1 oracle oracle 3584 Aug 10 20:35 spfileorcl.ora rw-r--r--. 1 oracle oracle 1111 Aug 10 20:35 initorcl.ora

Verify the contents of the pfile, and update the new directory file structure for audit, recovery, and control file destination folders.

f. Close the second SSH session.

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

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

startup nomount;

To restart the Oracle instance with the newly created pfile in the nomount mode, run the following command:

startup nomount pfile='$ORACLE_HOME/dbs/initorcl.ora';

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

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

RMAN> set DBID=1575537735; executing command: SET DBID

RMAN> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/%F'; executing command: SET CONTROLFILE AUTOBACKUP FORMAT

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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 10> 11> restore controlfile from autobackup;

84 Performing Self-Service Backups and Restores of Oracle Databases

12> 13> }

allocated channel: C1 channel C1: SID=36 device type=SBT_TAPE channel C1: PowerProtect DD Boost API

allocated channel: C2 channel C2: SID=37 device type=SBT_TAPE channel C2: PowerProtect DD Boost API

allocated channel: C3 channel C3: SID=38 device type=SBT_TAPE channel C3: PowerProtect DD Boost API

allocated channel: C4 channel C4: SID=39 device type=SBT_TAPE channel C4: PowerProtect DD Boost API

Starting restore at 07-JAN-22

channel C1: looking for AUTOBACKUP on day: 20220107 channel C1: AUTOBACKUP found: ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ c-1617195089-20220107-05 channel C2: looking for AUTOBACKUP on day: 20220107 channel C2: skipped, AUTOBACKUP already found channel C3: looking for AUTOBACKUP on day: 20220107 channel C3: skipped, AUTOBACKUP already found channel C4: looking for AUTOBACKUP on day: 20220107 channel C4: skipped, AUTOBACKUP already found channel C1: restoring control file from AUTOBACKUP ./PLCTLP-d0af4f59-d810-4b6b- aef1-1f7a8709ca47/c-1617195089-20220107-05 channel C1: control file restore from AUTOBACKUP complete output file name=/home/oracle/app/oracle/product/12.2.0/dbhome_1/dbs/cntrlorcl.dbf Finished restore at 07-JAN-22 released channel: C1 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.

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

RMAN> alter database mount;

The following type of information appears on the console:

Statement processed

16. 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)';

Performing Self-Service Backups and Restores of Oracle Databases 85

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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 10> 11> restore database; 12> 13> }

released channel: ORA DISK 1 allocated channel: Cl channel C1: SID=25 device type=SBT_TAPE channel C1: PowerProtect DD Boost API

allocated channel: C2 channel C2: SID=40 device type=SBT_TAPE channel C2: PowerProtect DD Boost API

allocated channel: C3 channel C3: SID=28 device type=SBT_TAPE channel C3: PowerProtect DD Boost API

allocated channel: C4 channel C4: SID=29 device type=SBT_TAPE channel C4: PowerProtect DD Boost API

Starting restore at 07-JAN-22

new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_jb0illk6_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_ja0illk6_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_ji0illkr_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_jj0illkr_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_je0illkl_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_jc0illk6_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_jh0illkq_1" new media label is "s:10.125.214.227:/PLC82-blrv136h019-2882b" for piece "./PLCTLP- d0af4f59-d810-4b6b-aef1-1f7a8709ca47/Automated_data_ORCL_1617195089_jk0illks_1" channel C1: starting datafile backup set restore channel C1: specifying datafile(s) to restore from backup set channel C1: restoring datafile 00010 to /home/oracle/app/oracle/oradata/orcl/orclpdb/ sysaux01.dbf channel C1: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jc0illk6_1 channel C2: starting datafile backup set restore channel C2: specifying datafile(s) to restore from backup set channel C2: restoring datafile 00001 to /home/oracle/app/oracle/oradata/orcl/ system01.dbf channel C2: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jb0illk6_1 channel C3: starting datafile backup set restore channel C3: specifying datafile(s) to restore from backup set channel C3: restoring datafile 00009 to /home/oracle/app/oracle/oradata/orcl/orclpdb/ system01.dbf channel C3: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_je0illkl_1 channel C4: starting datafile backup set restore channel C4: specifying datafile(s) to restore from backup set channel C4: restoring datafile 00007 to /home/oracle/app/oracle/oradata/orcl/ users01.dbf channel C4: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jj0illkr_1 channel C4: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jj0illkr_1 tag=TAG20220107T054749 channel C4: restored backup piece 1 channel C4: restore complete, elapsed time: 00:00:01

86 Performing Self-Service Backups and Restores of Oracle Databases

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 ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_ji0illkr_1 channel C4: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_ji0illkr_1 tag=TAG20220107T054749 channel C4: restored backup piece 1 channel C4: restore complete, elapsed time: 00:00:07 channel C4: starting datafile backup set restore channel C4: specifying datafile(s) to restore from backup set channel C4: restoring datafile 00011 to /home/oracle/app/oracle/oradata/orcl/orclpdb/ undotbs01.dbf channel C4: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jh0illkq_1 channel C3: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_je0illkl_1 tag=TAG20220107T054749 channel C3: restored backup piece 1 channel C3: restore complete, elapsed time: 00:00:09 channel C3: starting datafile backup set restore channel C3: specifying datafile(s) to restore from backup set channel C3: restoring datafile 00012 to /home/oracle/app/oracle/oradata/orcl/orclpdb/ users01.dbf channel C3: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jk0illks_1 channel C3: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jk0illks_1 tag=TAG20220107T054749 channel C3: restored backup piece 1 channel C3: restore complete, elapsed time: 00:00:01 channel C3: starting datafile backup set restore channel C3: specifying datafile(s) to restore from backup set channel C3: restoring datafile 00003 to /home/oracle/app/oracle/oradata/orcl/ sysaux01.dbf channel C3: reading from backup piece ./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_ja0illk6_1 channel C4: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jh0illkq_1 tag=TAG20220107T054749 channel C4: restored backup piece 1 channel C4: restore complete, elapsed time: 00:00:06 channel C1: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jc0illk6_1 tag=TAG20220107T054749 channel C1: restored backup piece 1 channel C1: restore complete, elapsed time: 00:00:18 channel C2: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_jb0illk6_1 tag=TAG20220107T054749 channel C2: restored backup piece 1 channel C2: restore complete, elapsed time: 00:00:26 channel C3: piece handle=./PLCTLP-d0af4f59-d810-4b6b-aef1-1f7a8709ca47/ Automated_data_ORCL_1617195089_ja0illk6_1 tag=TAG20220107T054749 channel C3: restored backup piece 1 channel C3: restore complete, elapsed time: 00:00:25 Finished restore at 07-JAN-22 released channel: C1 released channel: C2 released channel: C3 released channel: C4

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

Use SET UNTIL to specify the target time, restore point, SCN, or log sequence number for database point-in-time recovery. If specifying a time, then use the date format specified in the NLS_LANG and NLS_DATE_FORMAT environment variables.

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

Performing Self-Service Backups and Restores of Oracle Databases 87

------ -------- ----------- ------------ --------------- 3397 256.00K SBT_TAPE 00:00:00 17-AUG-20 BP Key: 3397 Status: AVAILABLE Compressed: NO Tag: TAG20200817T141937 Handle: ./Automated_arch_ORCL_ _nrv83dnp_1 Media: S: :/ /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

Record the final log sequence number.

You can also use time expressions, restore points, or log sequence numbers to specify the SET UNTIL time. For example:

SET UNTIL TIME 'Nov 15 2021 09:00:00'; SET UNTIL SEQUENCE 9923; SET UNTIL SCN 1000; SET UNTIL RESTORE POINT before_update;

NOTE: For more information about the procedures for restoring and recovering Oracle databases, refer to the Oracle

Database Backup and Recovery User's Guide from the Oracle Help Center.

18. To recover the database, run the recover database command in Recovery Manager.

NOTE: If you do not specify the log sequence number, SCN, or time expressions 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 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=/PLC82-blrv136h019-2882b, BACKUP_HOST=10.125.214.227, ORACLE_HOME= /home/oracle/app/oracle/product/12.2.0/dbhome_1)'; 10> 11> recover database until sequence 495; 12> 13> }

allocated channel: C1

88 Performing Self-Service Backups and Restores of Oracle Databases

channel C1: SID=25 device type=SBT_TAPE channel C1: PowerProtect DD Boost API allocated channel: C2 channel C2: SID=40 device type=SBT_TAPE channel C2: PowerProtect DD Boost API allocated channel: C3 channel C3: SID=28 device type=SBT_TAPE channel C3: PowerProtect DD Boost API allocated channel: C4 channel C4: SID=29 device type=SBT_TAPE channel C4: PowerProtect DD Boost API Starting recover at 07-JAN-22

starting media recovery media recovery complete, elapsed time: 00:00:00 Finished recover at 07-JAN-22 released channel: C1 released channel: C2 released channel: C3 released channel: C4

If the operation completes without errors, then your database point-in-time recovery has succeeded. You can open the database as mentioned in the next step. However, if the operation completes with errors, you may have chosen the wrong target SCN or sequence. In that case, investigate the issue and determine a new target SCN or sequence, then repeat the database point-in-time recovery process.

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

alter database open resetlogs;

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

exit

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

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.

Ensure that the DBID is unique for each data center. Multiple Oracle databases with the same DBID cause a DBID collision.

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.

After you have changed the DBID of the restored database, ensure that the Oracle SID value is removed from the parameter setting EXCLUDE_SID= in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg.

Performing Self-Service Backups and Restores of Oracle Databases 89

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.

The DBNEWID utility can change only the database name (DBNAME), not the instance name (SID).

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

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.

90 Performing Self-Service Backups and Restores of Oracle Databases

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

Performing Self-Service Backups and Restores of Oracle Databases 91

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= -a DD_STORAGE_UNIT=

92 Performing Self-Service Backups and Restores of Oracle Databases

Performing Centralized Restores of Oracle Backups

Topics:

Centralized restore and recovery of Oracle backups Considerations for centralized Oracle restore and recovery Performing centralized Oracle restore and recovery of an online database Performing centralized Oracle restore of archive logs Performing centralized disaster recovery of an Oracle database

Centralized restore and recovery of Oracle backups When Oracle Server data is backed up as part of a protection policy in PowerProtect Data Manager, you can restore and recover the Oracle Server backups by using the centralized restore and recovery functionality in the PowerProtect Data Manager UI.

A centralized Oracle restore and recovery includes the following limitations:

You cannot perform a cross-OS platform restore. You cannot perform a quick recovery. You cannot perform a centralized restore of an Oracle backup performed by a stand-alone Oracle RMAN agent before the

agent was registered with PowerProtect Data Manager.

You can perform the following types of centralized restore and recovery of Oracle Server backups:

Centralized restore and recovery of a full online database without restore of the control file. Centralized restore of only archive logs without restore of the control file. Centralized disaster recovery of an entire database, including the spfile and control file.

Using a centralized restore from the PowerProtect Data Manager UI, you can restore the Oracle database or archive logs for a single asset. You can perform the centralized restore to either the original Oracle Server host or an alternate host with the following requirements:

The Oracle RMAN agent software must be installed and configured on the alternate host. The alternate host must be an Oracle Server host that is a discovered asset of PowerProtect Data Manager.

Optionally, you can select to perform a dry run of any centralized restore and recovery operation to either the original host or an alternate host. The dry run option creates the required RMAN restore scripts, but does not perform an actual restore or recovery. You can use the RMAN restore scripts that the dry run creates to perform a self-service restore as required.

You must perform all centralized restore and recovery operations from the Restore > Assets > Oracle window in the PowerProtect Data Manager UI. You can perform a centralized restore and recovery to a specified Oracle Server host.

The following topics describe the considerations, prerequisites, and procedures for the supported types of centralized restore and recovery of Oracle backups.

Considerations for centralized Oracle restore and recovery Ensure that you review the following information before you perform a centralized restore and recovery of Oracle backups by using the PowerProtect Data Manager.

A centralized restore and recovery of an online Oracle database supports the following features:

Restore and recovery to the original Oracle host.

5

Performing Centralized Restores of Oracle Backups 93

Restore and recovery to an alternate Oracle host. Point-in-time restore and recovery, based on time, SCN, or log sequence. Dry run of the database restore and recovery.

NOTE: A centralized restore and recovery of an Oracle database is allowed only when the backup copies location is listed as

LOCAL or Local_Recalled in the Location column in the PowerProtect Data Manager UI. (To see the Location column, go

to Infrastructure > Assets, select the asset on the Oracle tab, click View Copies, and then click the storage icon on the

left.) To recall a cloud tier backup before you perform a centralized restore, follow the procedure in Restore the cloud tier

backups to DD.

For any centralized restore to an alternate host, ensure that the alternate host is an Oracle Server host that is a discovered asset of PowerProtect Data Manager.

NOTE: If the alternate host is not included in the list of available hosts, follow the instructions to install and configure the

Oracle RMAN agent on the alternate host. Ensure that the Oracle Server host is registered to the same PowerProtect Data

Manager server.

A centralized restore of only Oracle archive logs supports the following features:

Restore to the original Oracle host. Restore to an alternate Oracle host. Restore of a specific range of archive logs, based on time, SCN, or log sequence. Dry run of the archive log restore.

A centralized Oracle disaster recovery supports the following features:

Restore to the original Oracle host. Restore to an alternate Oracle host.

NOTE: You can use the disaster recovery for Oracle testing and development purposes, for example, to validate the

Oracle backups on an alternate host.

Change of the database ID (DBID) of the restored database after disaster recovery. Relocation of the Oracle data files. Customization of Oracle startup parameter settings in the spfile of the Oracle database. Point-in-time restore and recovery, based on time, SCN, or log sequence. Dry run of the disaster recovery.

PowerProtect Data Manager applies the following concurrency rules for jobs associated with a centralized restore, including any backup, restore, and manual agent installation jobs that you run on the same host:

If an asset backup is in progress, the Oracle Server restore against the same asset is queued. If an Oracle Server restore against an asset is in progress, the backup against the same asset is queued. If an archive log restore is in progress, a backup request is not queued. If a restore is in progress for 48 hours or less, a manual or scheduled delete job is not started.

NOTE: If a restore runs for more than 48 hours, a scheduled delete job is started.

Application agent manual installation and configuration

When you want to restore to a host that is not part of a protection policy, you must manually install and configure the Oracle RMAN agent on the target host of the restore.

Ensure that the target host meets the following prerequisites:

An AIX or Linux OS is running. The Oracle Server is installed and running. The Oracle DBA account has the same security configuration as required for backup. The network ports are configured as required for backup.

94 Performing Centralized Restores of Oracle Backups

Performing centralized Oracle restore and recovery of an online database You can use the PowerProtect Data Manager UI to perform a centralized restore and recovery of a full Oracle database backup without the control file.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the Oracle tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the filter icon in the column heading Name, Status, Protection Policy, Host/Cluster/Group Name, Host Type, OS Type, Application Name, Last Copy, or Network:

The Name and Application Name columns list the Oracle database asset names. The Status column lists the status as Available, Deleted, or Not Detected. The Protection Policy column lists the names of the protection policies for the assets. The Host/Cluster/Group Name column lists the hostnames. The Host Type column lists the host types as RAC or STANDALONE. The OS Type column lists the operating system as AIX or LINUX. The Last Copy column lists the dates and times of the backup copies within the specified date and time range. The Network column lists the networks that are available under the selected host or cluster.

NOTE: The listed assets are the assets that have at least one copy discovered by PowerProtect Data Manager. You can

select only one asset for one Oracle host.

2. Select the check box next to the Oracle Server database asset for restore, and click Restore.

The restore wizard opens the Oracle Restore and Recovery window.

3. On the Scope page, select Online database recovery, then select Full database recovery, and then click Next.

This option restores and recovers the full database without the control file. The database must be in the mount state.

4. On the Storage Unit Selection page page, type the name of the storage unit that contains the backup in the Storage unit field, or select the storage unit from the menu, and then click Next.

5. On the Location page, select the preferred type of restore, and then click Next:

Restore to original hostSpecifies to restore to the original host with the displayed hostname.

If the original host is part of a RAC cluster, select the available node hostname from the list.

Restore to alternate hostSpecifies to restore to an alternate host.

Select the alternate hostname from the list, and then select the required instance name.

6. On the Credentials page, select one of the following options, and then click Next:

Use the credentials set at asset level or policy level for restore

NOTE: Credentials at the asset level take precedence over credentials at the protection policy level.

Select existing credentials or create new credentials for restore

Click Set Credentials, complete the fields in the Set Credential dialog, and then click Save.

7. On the Database Recovery Options page, select the required options, and then click Next:

Restore ToSelect Current time or Point in time.

The Current time is the latest backup time in the control file.

For Point in time, select one of the following options from the menu:

System Change NumberType the System Change Number (SCN) in the text box. TimestampType the date and time in the text box, or click the icon to display a calendar and select the date and

time. Log SequenceType the log sequence in the text box.

Database OptionsSelect Dry Run if you do not want to run an actual restore and recovery.

Performing Centralized Restores of Oracle Backups 95

The dry run option enables a job that creates the required RMAN restore scripts in the $RMAN_AGENT_HOME/tmp directory on the selected target host. The dry run procedure does not perform an actual restore or recovery. You can use the scripts that the dry run creates to perform a self-service restore as required.

8. On the More Options page, specify the required options, and then click Next:

Set Stream CountType an integer stream count in the text box, if required. The default stream count is 4. The maximum stream count is 255.

Compressed RestoreTo enable restore compression and reduce the impact on the network bandwidth, select Use PowerProtect DD Boost compressed restore.

TroubleshootingTo enable troubleshooting, select Enable debug log.

9. On the Summary page:

a. To ensure that the restore settings are correct, review the information about the Scope, Storage unit, Location, Credentials, Database Recovery Options, and More Options.

To change any settings, you can click Edit beside an information section. As an alternative, you can click Back to access a specific page and change the settings as needed.

b. To start the centralized restore and recovery operation for the Oracle database, click Restore.

A status message appears with a link to the Protection Jobs page where you can monitor the restore and recovery job.

Performing centralized Oracle restore of archive logs You can use the PowerProtect Data Manager UI to perform a centralized restore of an Oracle archive logs backup without the control file.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the Oracle tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the filter icon in the column heading Name, Status, Protection Policy, Host/Cluster/Group Name, Host Type, OS Type, Application Name, Last Copy, or Network:

The Name and Application Name columns list the Oracle database asset names. The Status column lists the status as Available, Deleted, or Not Detected. The Protection Policy column lists the names of the protection policies for the assets. The Host/Cluster/Group Name column lists the hostnames. The Host Type column lists the host types as RAC or STANDALONE. The OS Type column lists the operating system as AIX or LINUX. The Last Copy column lists the dates and times of the backup copies within the specified date and time range. The Network column lists the networks that are available under the selected host or cluster.

NOTE: The listed assets are the assets that have at least one copy discovered by PowerProtect Data Manager. You can

select only one asset for one Oracle host.

2. Select the check box next to the Oracle Server database asset for restore, and click Restore.

The restore wizard opens the Oracle Restore and Recovery window.

3. On the Scope page, select Online database recovery, then select Archive log only restore, and then click Next.

This option restores only the archive logs without the control file. The database can be in either the mount state or open state.

4. On the Storage Unit Selection page page, type the name of the storage unit that contains the backup in the Storage unit field, or select the storage unit from the menu, and then click Next.

5. On the Location page, select the preferred type of restore, and then click Next:

Restore to original hostSpecifies to restore to the original host with the displayed hostname.

If the original host is part of a RAC cluster, select the available node hostname from the list.

Restore to alternate hostSpecifies to restore to an alternate host.

Select the alternate hostname from the list, and then select the required instance name.

6. On the Credentials page, select one of the following options, and then click Next:

96 Performing Centralized Restores of Oracle Backups

Use the credentials set at asset level or policy level for restore

NOTE: Credentials at the asset level take precedence over credentials at the protection policy level.

Select existing credentials or create new credentials for restore

Click Set Credentials, complete the fields in the Set Credential dialog, and then click Save.

7. On the Archive Log Options page, select the required options, and then click Next:

Restore ToSelect one of the following options:

AllSpecifies to restore all the archive logs of the database asset. System Change NumberSpecifies to restore the archive logs for the SCN range. Type the SCN start and end

values in the text boxes. TimestampSpecifies to restore the archive logs for the timestamp range. Type or select the timestamp start and

end values in the text boxes. Log SequenceSpecifies to restore the archive logs for the log sequence range. Type the log sequence start and

end values in the text boxes. Database OptionsSelect Dry Run if you do not want to run an actual restore.

The dry run option enables a job that creates the required RMAN restore scripts in the $RMAN_AGENT_HOME/tmp directory on the selected target host. The dry run procedure does not perform an actual restore or recovery. You can use the scripts that the dry run creates to perform a self-service restore as required.

8. On the More Options page, specify the required options, and then click Next:

Set Stream CountType an integer stream count in the text box, if required. The default stream count is 4. The maximum stream count is 255.

Compressed RestoreTo enable restore compression and reduce the impact on the network bandwidth, select Use PowerProtect DD Boost compressed restore.

TroubleshootingTo enable troubleshooting, select Enable debug log.

9. On the Summary page:

a. To ensure that the restore settings are correct, review the information about the Scope, Storage unit, Location, Credentials, Archive Log Options, and More Options.

To change any settings, you can click Edit beside an information section. As an alternative, you can click Back to access a specific page and change the settings as needed.

b. To start the centralized restore operation for the Oracle database, click Restore.

A status message appears with a link to the Protection Jobs page where you can monitor the restore job.

Performing centralized disaster recovery of an Oracle database You can use the PowerProtect Data Manager UI to perform a centralized disaster recovery of an Oracle database including the spfile and control file.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the Oracle tab.

The Restore window displays all the databases that are available for disaster recovery.

To filter the displayed list of assets if needed, you can click the filter icon in the column heading Name, Status, Protection Policy, Host/Cluster/Group Name, Host Type, OS Type, Application Name, Last Copy, or Network:

The Name and Application Name columns list the Oracle database asset names. The Status column lists the status as Available, Deleted, or Not Detected. The Protection Policy column lists the names of the protection policies for the assets. The Host/Cluster/Group Name column lists the hostnames. The Host Type column lists the host types as RAC or STANDALONE. The OS Type column lists the operating system as AIX or LINUX. The Last Copy column lists the dates and times of the backup copies within the specified date and time range. The Network column lists the networks that are available under the selected host or cluster.

Performing Centralized Restores of Oracle Backups 97

NOTE:

The listed assets are the assets that have at least one copy discovered by PowerProtect Data Manager. You can select

only one asset for one Oracle host.

Oracle software installed on the alternate host must be compatible with the source Oracle Server, as recommended by

Oracle.

2. Select the check box next to the Oracle Server database asset for restore, and click Restore.

The restore wizard opens the Oracle Restore and Recovery window.

3. On the Scope page, select Disaster recovery, and then click Next.

This option restores and recovers the entire database, including the spfile and control file.

You can use this option to restore the Oracle database to the original host or to an alternate host with a different database ID (DBID) than the original production host. The restore to the alternate host is usually used for test and development purposes.

4. On the Copy Selection page, select the backup copy to be restored from the list, and then click Next.

To filter the displayed list of backup copies if needed, you can click the filter icon in the column heading Created Time, Copy Type, Location, Copy Status, or Storage Unit:

The Created Time column lists the dates and times when the backup copies were created. The Copy Type column lists the backup copy types as Differential, Full, or Cumulative. The Location column lists the backup copy locations as LOCAL or Local_Recalled. The Copy Status column lists the backup copy status as Available, Deleting, Deletion Failed, Deletion Failed (Agent

Catalog), Cloud Tiering, Cloud Recalling, Replicating, Restoring, or Ready for Cloud Tiering. The Storage Unit column lists the storage units of the backup copies.

5. On the Location page, select the preferred type of restore, and then click Next:

Restore to original hostSpecifies to restore to the original host with the displayed hostname.

If the original host is part of a RAC cluster, select the available node hostname from the list.

Restore to alternate hostSpecifies to restore to an alternate host.

Select the alternate hostname from the list.

6. On the Folder Location page, select one of the following options, and then click Next:

Restore to original folder

CAUTION: When you select to restore the Oracle data files to the original location, the original database is

overwritten.

Restore to alternate folder

To specify an alternate location, select Archive log, Control file, Datafiles, Fast recovery area, or Redo log from the menu, and then type the alternate location in the text box. For each additional alternate location, click the + icon, select the file type from the menu, and type the alternate location in the text box.

NOTE:

You must specify at least one alternate location if selected. For the control file, specify the full pathname, such

as /u01/app/oracle/fast_recovery_area/sourcemay1/control01.ctl. You can specify a maximum of

31 archive log locations, five control file locations, one data file location, one fast recovery area location, and five

redo log locations.

To ensure successful restores, the folders specified for the alternate folder locations must exist with the required

permissions.

7. On the Instance Details page, specify the required settings, and then click Next:

Oracle SIDType the Oracle instance system ID (SID) in the text box.

Oracle HomeType the valid Oracle home pathname in the text box.

NOTE: The Oracle home pathname must not include a final space or slash (/).

CredentialsSelect one of the following options:

98 Performing Centralized Restores of Oracle Backups

Use the credentials set at asset level or policy level for restore

NOTE: Credentials at the asset level take precedence over credentials at the protection policy level.

Select existing credentials or create new credentials for restore

Click Set Credentials, complete the fields in the Set Credential dialog, and then click Save.

8. On the SPFILE Options page, specify the required settings, and then click Next:

SPFILE OptionsSelect this option to specify the restore of the spfile during the disaster recovery. This option is selected by default when the selected copy contains the spfile.

NOTE:

If you do not select this option to restore the spfile, you must create the spfile manually and start the database

instance in no mount mode.

This option is disabled by default when the selected copy does not have an spfile backup. In this case, a warning

message is displayed:

Warning: The spfile is not found in the selected backup copy. Create the spfile or pfile manually and start the database instance in no mount mode.

In some cases, the restore job from the UI might be reported as failed when pre-19.11 backup copies are selected.

A known limitation exists in identifying specific backup pieces, such as an spfile and control file. The identification is

required for a successful restore that is started from the UI.

When the spfile option is cleared, only the Datafiles folder locations are used during the restore operation. Other

added locations are ignored.

Configure SPFILE Parameters (optional)To change a default spfile parameter setting, type the parameter name in the Parameter text box and the parameter value setting in the Value text box. For each additional parameter setting that you want to change, click the + icon and then type the parameter name and value in the new blank text boxes.

For example, to specify the memory parameter settings sga_target=3000m and pga_aggregate_target=694m, type the following values in the text boxes:

Parameter: sga_target, Value: 3000m Parameter: pga_aggregate_target, Value: 694m

NOTE: The Oracle database audit folder must exist with the required permissions on the target host system,

similar to the source host system. If the folder location is different from the source location, then specify the

audit_file_dest parameter setting.

9. On the Database Recovery Options page, select the required options, and then click Next:

Restore ToSelect Backup time (backup end time of selected backup copy) or Point in time.

For Point in time, select one of the following options from the menu:

System Change NumberType the System Change Number (SCN) in the text box. TimestampType the date and time in the text box, or click the icon to display a calendar and select the date and

time. Log SequenceType the log sequence in the text box.

Data GuardSelect the required option for a database restore in a Data Guard environment:

NOTE: Ensure that the standby database is in sync with the primary database. You can restore a standby database

backup to the primary database, or restore a primary database backup to the standby database.

NoneBy default, the None value is selected, which specifies to restore the database in a non-Data Guard configuration.

PrimarySelect this option to restore the database as a primary database in a Data Guard configuration to a specified point in time.

StandbySelect this option to restore the database as a standby database in a Data Guard configuration to a specified point in time.

Database OptionsSelect any required options from the list:

Open database after recovery

Performing Centralized Restores of Oracle Backups 99

This option opens the database after the recovery. If the database is a container database (CDB), all the pluggable databases are opened.

Change DBID after recovery

This option changes the DBID after the recovery. Select this option only when you also select to open the database after the recovery. When the database is unopened, the DBID cannot be changed.

NOTE:

When you select the Change DBID after recovery option, the asset is discovered automatically in

PowerProtect Data Manager after a successful restore with the DBID change. When you do not select this

option, the restored asset is not discovered automatically.

Remove the SID entry from the EXCLUDE_SID parameter setting in the $RMAN_AGENT_HOME/config/ rman_agent.cfg file.

Dry run

This option enables a job that creates the required RMAN restore scripts in the $RMAN_AGENT_HOME/tmp directory on the selected target host. The dry run procedure does not run an actual disaster recovery. You can use the scripts that the dry run creates to perform a self-service disaster recovery as required.

10. On the More Options page, specify the required options, and then click Next:

Set Stream CountType an integer stream count in the text box, if required. The default stream count is 4. The maximum stream count is 255.

Compressed RestoreTo enable restore compression and reduce the impact on the network bandwidth, select Use PowerProtect DD Boost compressed restore.

TroubleshootingTo enable troubleshooting, select Enable debug log.

11. On the Summary page:

a. To ensure that the recovery settings are correct, review the information about the Scope, Location, Folder Location, Oracle Instance Details, SPFILE Restore Option, Database Recovery Options, and More Options.

To change any settings, you can click Edit beside an information section. As an alternative, you can click Back to access a specific page and change the settings as needed.

b. To start the centralized disaster recovery operation for the Oracle database, click Restore.

A status message appears with a link to the Protection Jobs page where you can monitor the restore and recovery job.

100 Performing Centralized Restores of Oracle Backups

Oracle RMAN Best Practices and Troubleshooting

Topics:

Troubleshooting storage units Troubleshooting backup failures when credentials include a backslash character (\) Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname Troubleshooting agent registration Troubleshooting PowerProtect agent service operations Troubleshooting application agent update failure in PowerProtect Data Manager UI on Linux Troubleshooting an asset duplication issue after downgrade Troubleshooting an issue with hostnames used for discoveries after a hostname change Troubleshooting an issue with incorrect SID or database name in rename.config file Troubleshooting a self-service backup error for an unmanaged asset Troubleshooting self-service backup error related to top-level pathname Troubleshooting self-service operations with data-in-flight encryption Troubleshooting Oracle self-service jobs that run indefinitely Troubleshooting an incorrect self-service backup report for different backup types in same session Troubleshooting an incorrect asset display after asset source deletion Troubleshooting a failed migration of RAC_BACKUP_NODE_IP parameter setting Troubleshooting an issue with AIX RAC cluster failover Troubleshooting RAC cluster failure due to active node issue Troubleshooting a missing duration value for centralized backup Troubleshooting an issue with onboarded backup copies Troubleshooting missing Oracle version with added protection rules Troubleshooting restore failure due to FORMAT specification Troubleshooting an issue on AIX with ddbmcon process not exiting Troubleshooting centralized restore issue with unchanged DBID Troubleshooting centralized restore issue with audit file destination

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

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

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

To determine storage unit capacity, use DDVE instead.

A

Oracle RMAN Best Practices and Troubleshooting 101

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

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

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

Troubleshooting backup failures when credentials include a backslash character (\) When you enter credentials that include a backslash character (\) for an application agent in the PowerProtect Data Manager UI, the backups fail.

For example, when you enter a password for the operating system or database user that includes the backslash character, subsequent backups fail with the following error message:

systemErr: Unable to log in. This error might occur when updating the password for a storage unit.

To resolve this issue, type \\ (double backslash) instead of \ (single backslash) when you enter the credentials for an application agent in the PowerProtect Data Manager UI.

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

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

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

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

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

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

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

1. If the ping command is blocked in the environment, the agent registration can still complete successfully. Review the agent service logs at INSTALL_DIR\DPSAPPS\AgentService\logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI. 2. If the ping command is not blocked in the environment, the agent registration

102 Oracle RMAN Best Practices and Troubleshooting

might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

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

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

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

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

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

Wait 10 to 15 seconds.

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

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

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

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

About this task

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

Steps

1. Stop the agent service by using the appropriate procedure from the preceding topic.

2. Open the config.yml file in an editor.

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

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

default log-level is INFO.

DEBUG INFO WARNING ERROR CRITICAL

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

Oracle RMAN Best Practices and Troubleshooting 103

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

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

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

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

Troubleshooting application agent update failure in PowerProtect Data Manager UI on Linux On a Linux OS that uses /etc/init.d instead of systemd to start the OS services, an update of a previous application agent version in the PowerProtect Data Manager UI might fail with the following error message:

Upgrade operation failed with error 'tuple' object has no attribute 'lower', errorcode: .

As a workaround, update the application agent by using the appropriate update commands and command-line procedure as described in this guide.

Troubleshooting an asset duplication issue after downgrade When you downgrade the Oracle RMAN agent to an earlier version and register the agent with the same PowerProtect Data Manager server, the downgrade creates duplicate asset entries in the PowerProtect Data Manager UI.

In the PowerProtect Data Manager UI, you can view the duplicate asset entries by selecting Infrastructure > Assets and then clicking the Oracle tab.

The downgrade of the Oracle RMAN agent is not supported.

Troubleshooting an issue with hostnames used for discoveries after a hostname change After the Oracle RMAN hostname is changed, a scheduled discovery might run with the new hostname and a manual discovery might run with the old hostname. The PowerProtect Data Manager UI displays the different hostnames that are used for the scheduled and manual discovery operations.

As a workaround, complete the procedure in Enable the Oracle RMAN agent after hostname change.

Troubleshooting an issue with incorrect SID or database name in rename.config file After you change the SID of a stand-alone database or the database name of a RAC database, you can continue using an existing asset from an existing protection policy with PowerProtect Data Manager. You need to provide the previous SID of the stand-alone database or previous database name of the RAC database in the rename.config file. If the SID or database name in the rename.config file is incorrect, the following error appears during a backup:

Some of the assets have the new natural ID status. Please reconfigure the PLC.

Use the following steps to resolve the issue:

1. Make any required corrections of the SIDs or database names in the rename.config file. Enable the use of an existing asset in a modified environment provides more details about updating the rename.config file to enable the continued use of an existing asset.

2. Reconfigure the PowerProtect Data Manager protection policy:

104 Oracle RMAN Best Practices and Troubleshooting

a. In the PowerProtect Data Manager UI, select Protection > Protection Policies. b. On the Protection Policies page, select the existing protection policy in the list and click Set Lockbox, which starts

the configuration.

NOTE: Use of Set Lockbox is required only when a previous SID or database name was incorrectly specified and

then later corrected.

Troubleshooting a self-service backup error for an unmanaged asset When two assets on a host have the same DBID and only one asset is managed by PowerProtect Data Manager, a backup of the asset that is not managed by PowerProtect Data Manager might fail with the following error message:

sbtbackup: Unable to find the asset in the settings file. for a dataguard instance, make sure to specify DBUNIQUE_NAME parameter in rman script.

To resolve this issue, set the ALLOW_BACKUP parameter in the $RMAN_AGENT_HOME/config/rman_agent.cfg file to the SID of the asset that is not managed by PowerProtect Data Manager. For example:

ALLOW_BACKUP = orcl2

Troubleshooting self-service backup error related to top-level pathname 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 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.

Troubleshooting self-service operations with data-in- flight encryption PowerProtect Data Manager supports in-flight encryption for both centralized and self-service Oracle backup and restore operations. The /opt/dpsapps/agentsvc/Addons/global_config.json file on the Oracle client contains option settings that affect the in-flight encryption during self-service operations.

NOTE:

The /opt/dpsapps/agentsvc/Addons/global_config.json file is created automatically. You cannot edit the

contents of the file.

Centralized settings take precedence over settings in the /opt/dpsapps/agentsvc/Addons/global_config.json file. Stand-alone self-service operations without PowerProtect Data Manager do not support in-flight encryption.

The status of in-flight encryption during self-service operations depends on the following settings:

Oracle RMAN Best Practices and Troubleshooting 105

If the encryptionOverTheWire option setting in the /opt/dpsapps/agentsvc/Addons/global_config.json file is TRUE, then in-flight encryption is enabled.

If the encryptionOverTheWire option setting in the /opt/dpsapps/agentsvc/Addons/global_config.json file is FALSE, then in-flight encryption is disabled.

If the /opt/dpsapps/agentsvc/Addons/global_config.json file does not exist or is corrupted, then in-flight encryption is disabled. Applicable information is recorded in the operational logs.

Data-in-flight encryption provides more information about the PowerProtect Data Manager support of in-flight encryption.

Troubleshooting Oracle self-service jobs that run indefinitely When you perform an Oracle self-service backup or restore, the backup or restore job continues to run indefinitely and the job status appears as In Progress in the PowerProtect Data Manager UI.

As a workaround, always exit from the RMAN session after each backup or restore job. Then the job status changes to Successful or Failed in the PowerProtect Data Manager UI, depending on the RMAN session output.

Troubleshooting an incorrect self-service backup report for different backup types in same session When you perform different types of self-service data backups such as full and incremental backups with archive log backups in the same RMAN session, the backups job can be reported incorrectly in the PowerProtect Data Manager UI.

For example, you might run the following backup command to perform the full and incremental backups with archive log backups in the same RMAN session:

backup incremental level=0 database plus archivelog delete input tag='oracle-L0'

In this case, the Oracle self-service backups job name and subtype can be reported as LOG instead of FULL or INCREMENTAL in the PowerProtect Data Manager UI.

To prevent this issue, perform a self-service data backup and archived log backup by using separate backup commands. Performing self-service backups of Oracle databases provides examples of RMAN backup scripts that perform a full backup of a database and its archive logs in separate statements.

Troubleshooting an incorrect asset display after asset source deletion If an asset source is deleted, the associated assets sometimes appear as Available rather than Deleted. This issue can occur when using PowerProtect Data Manager version 19.9 or later with an older version of the Oracle RMAN agent.

To resolve this issue, contact Customer Support.

Troubleshooting a failed migration of RAC_BACKUP_NODE_IP parameter setting When the RAC_BACKUP_NODE_IP parameter in the configuration file is set to an FQDN (rather than IP address), an update of the PowerProtect Data Manager fails to migrate this parameter setting to the preferred node setting on the Assets page in the PowerProtect Data Manager UI.

The preferred node setting in an Oracle RAC environment is only applicable for a centralized protection policy, not for a self-service protection policy.

106 Oracle RMAN Best Practices and Troubleshooting

As a workaround, ensure that the RAC_BACKUP_NODE_IP parameter in the configuration file is set to the required IP address prior to updating the PowerProtect Data Manager from a previous version. Then the PowerProtect Data Manager update automatically migrates the RAC_BACKUP_NODE_IP parameter setting to the preferred node setting on the Assets page in the PowerProtect Data Manager UI.

Assign a preferred node in Oracle RAC environment provides details on the preferred node setting in an Oracle RAC environment.

NOTE: If you later modify the preferred node setting in the UI, the RAC_BACKUP_NODE_IP parameter setting remains

unchanged in the configuration file. The preferred node setting in the UI takes precedence over the parameter setting in the

configuration file.

Troubleshooting an issue with AIX RAC cluster failover After shutting down the first node of an AIX RAC cluster, backups do not start from the second node. Automatic failover does not work in this situation.

To resolve this issue, perform one of the following actions and then restart the agent service:

Bring back up the first node of the cluster. Change the Preferred Node parameter of the RAC system to use the second node.

Troubleshooting RAC cluster failure due to active node issue In an Oracle RAC cluster, if the active node database service is stopped or the active node is down, then any configure, backup, or delete requests cause PowerProtect Data Manager to continually report a failure.

To resolve this issue, perform one of the following actions:

If it is stopped, start the active node database service. If it is down, bring up the active node. Remove the active node from the Oracle RAC cluster. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources and delete the related asset source.

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

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

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

Troubleshooting an issue with onboarded backup copies You might encounter an issue with onboarded Oracle backup copies.

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

Oracle RMAN Best Practices and Troubleshooting 107

Troubleshooting missing Oracle version with added protection rules When you add protection rules for unprotected Oracle assets in the PowerProtect Data Manager UI, no information appears in the Oracle Version column.

To resolve this issue, manually obtain the Oracle version from the RMAN /SQL Utility.

Troubleshooting restore failure due to FORMAT specification An RMAN restore of the following types of backups might fail when the FORMAT specification contains a dot or period (.) character as a prefix: Self-service Oracle RMAN agent backup performed with the RMAN BACKUP command.

Centralized Oracle RMAN agent backup through a PowerProtect Data Manager protection policy with a control file autobackup.

To prevent this issue, do not start the FORMAT specification with a dot or period (.) character.

Troubleshooting an issue on AIX with ddbmcon process not exiting On AIX, due to an Oracle OCI library issue, the ddbmcon process does not exit after completing all operations, which can cause different types of symptoms. The following symptoms can occur: 1. The ddbmcon process has a child process.

2. The process ID is 1 for the parent process of the ddbmcon process.

3. The process ID is not 1 for the parent process of the ddbmcon process and the debug log shows that the ddbmcon process finished all operations. However, the ddbmcon process does not exit.

These symptoms are caused by the Oracle bug 34372439, "OCI APPLICATION LOADING DLLS DYNAMICALLY HANGS".

As a workaround, contact Oracle to obtain the latest patch.

Troubleshooting centralized restore issue with unchanged DBID When you perform a centralized Oracle restore and select the option to change the database ID (DBID), the centralized restore might display the following error message:

Unable to complete changeDbid command: NID-00137: All datafiles that are not dropped should be readable.

In this case, the DBID is not changed after the restore. To change the DBID manually, use the instructions on the following Oracle site:

NID-00137 In Multitenant Database 12c (12.1.2) (Doc ID 2418171.1)

108 Oracle RMAN Best Practices and Troubleshooting

Troubleshooting centralized restore issue with audit file destination When you perform a centralized Oracle restore, the restore job might fail with the following error message:

RMAN-04014: startup failed: ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 2: No such file or directory

To resolve this issue, complete either of the following actions:

Create an Oracle database audit folder on the target host system, similar to the audit folder on the source host system. Specify the audit_file_dest parameter setting in the Configure SPFILE Parameters (optional) option in the

PowerProtect Data Manager UI, as described in step 8 in Performing centralized disaster recovery of an Oracle database. For example, specify the Parameter and Value field settings in the UI as follows:

Parameter: audit_file_dest Value: /u01/app/oracle/admin/source/adump

Oracle RMAN Best Practices and Troubleshooting 109

Glossary of Acronyms This glossary provides definitions of acronyms used in the PowerProtect Data Manager documentation.

B

110 Glossary of Acronyms

A

AAG: Always On availability group

ACL: access control list

AD: Active Directory

AKS: Azure Kubernetes Service

API: application programming interface

ARM: Azure Resource Manager

AVS: Azure VMware Solution

AWS: Amazon Web Services

AZ: availability zone

B

BBB: block-based backup

C

CA: certificate authority

CBT: Changed Block Tracking

CDC: change data capture

CIFS: Common Internet File System

CLI: command-line interface

CLR: Common Language Runtime

CN: common name

CPU: central processing unit

CR: custom resource

CRD: custom resource definition

CSI: container storage interface

CSV: Cluster Shared Volume

D

DA: database administrator

DAG: database availability group

Glossary

Glossary 111

DBID: database identifier

DDMC: DD Management Center

DDOS: DD Operating System

DDVE: DD Virtual Edition

DFC: DD Boost over Fibre Channel

DNS: Domain Name System

DPC: Data Protection Central

DR: disaster recovery

DRS: Distributed Resource Scheduler

DSA: Dell security advisory

E

EBS: Elastic Block Store

EC2: Elastic Compute Cloud

eCDM: Enterprise Copy Data Management

ECS: Elastic Cloud Storage

EFI: Extensible Firmware Interface

EKS: Elastic Kubernetes Service

ENI: Elastic Network Interface

EULA: end-user license agreement

F

FC: Fibre Channel

FCD: first class disk

FCI: failover cluster instance

FETB: front-end protected capacity by terabyte

FLR: file-level restore

FQDN: fully qualified domain name

FTP: File Transfer Protocol

G

GB: gigabyte At Dell, this is 230 bytes.

Gb/s: gigabits per second At Dell, this is 230 bits per second.

112 Glossary

GCP: Google Cloud Platform

GCVE: Google Cloud Virtual Edition

GID: group identifier

GLR: granular-level restore

GUI: graphical user interface

GUID: globally unique identifier

H

HA: High Availability

HANA: high-performance analytic appliance

HTML: Hypertext Markup Language

HTTP: Hypertext Transfer Protocol

HTTPS: Hypertext Transfer Protocol Secure

I

IAM: identity and access management

IDE: Integrated Device Electronics

IP: Internet Protocol

IPv4: Internet Protocol version 4

IPv6: Internet Protocol version 6

K

KB: kilobyte At Dell, this is 210 bytes.

L

LAC: License Authorization Code

LAN: local area network

M

MB: megabyte At Dell, this is 220 bytes.

ms: millisecond

MTU: maximum transmission unit

Glossary 113

N

NAS: network-attached storage

NBD: network block device

NBDSSL: network block device over SSL

NDMP: Network Data Management Protocol

NFC: Network File Copy

NFS: Network File System

NIC: network interface card

NTFS: New Technology File System

NTP: Network Time Protocol

O

OS: operating system

OSS: open-source software

OVA: Open Virtualization Appliance

P

PCS: Protection Copy Set

PDF: Portable Document Format

PEM: Privacy-enhanced Electronic Mail

PIN: personal identification number

PIT: point in time

PKCS: Public Key Cryptography Standards

PSC: Platform Service Controller

PVC (cloud computing): private virtual cloud

PVC (Kubernetes): Persistent Volume Claim

R

RAC: Real Application Clusters

RAM: random-access memory

RBAC: role-based access control

ReFS: Resilient File System

REST API: representational-state transfer API

RHEL: RedHat Enterprise Linux

114 Glossary

RMAN: Recovery Manager

RPO: recovery-point objective

RSA: Rivest-Shamir-Adleman

S

S3: Simple Storage Services

SaaS: software as a service

SAP: System Analysis Program Development From the SAP website (2022), "the name is an initialism of the company's original German name: Systemanalyse Programmentwicklung, which translates to System Analysis Program Development. Today the company's legal corporate name is SAP SE - SE stands for societas Europaea, a public company registered in accordance with the European Union corporate law.

SCSI: Small Computer System Interface

SDDC: software-defined data center

SELinux: Security-Enhanced Linux

SFTP: Secure File Transfer Protocol

SLA: service-level agreement

SLES: SuSE Linux Enterprise Server

SLO: service-level objective

SPBM: Storage Policy Based Management

SQL: Structured Query Language

SRS: Secure Remote Services

SSD: solid-state drive

SSH: Secure Shell

SSL: Secure Sockets Layer

SSMS: SQL Server Management Studio

SSVs: System Stable Values

T

TB: terabyte At Dell, this is 240 bytes.

TCP: Transmission Control Protocol

TDE: Transparent Data Encryption

TLS: Transport Layer Security

TPM: Trusted Platform Module

TSDM: Transparent Snapshot Data Mover

T-SQL: Transact-SQL

Glossary 115

U

UAC: user account control

UDP: User Datagram Protocol

UI: user interface

UID: user identifier

UTC: Coordinated Universal Time From Wikipedia (2022), "this abbreviation comes as a result of the International Telecommunication Union and the International Astronomical Union wanting to use the same abbreviation in all languages. English speakers originally proposed CUT (for 'coordinated universal time'), while French speakers proposed TUC (for 'temps universel coordonn')."

V

VADP: VMware vStorage APIs for Storage Awareness

VBS: virtualization-based security

VCF: VMware Cloud Foundation

vCLS: vSphere Cluster Service

vCSA: vCenter Server Appliance

VCSA: vCenter Server Appliance

VDI: Virtual Device Interface

vDisk: virtual disk

vDS: virtual distributed switch

vFRC: Virtual Flash Read Cache

VGT: Virtual Guest Tagging

VIB: vSphere Installation Bundle

VLAN: virtual LAN

VM: virtual machine

VMC: VMware Cloud

VMDK: virtual machine disk

VNet: virtual network

VPC: virtual private cloud

vRSLCM: vRealize Suite Lifecycle Manager

VST: Virtual Switch Tagging

vTPM: Virtual Trusted Platform Module

VVD: VMware Validated Design

vVol: virtual volume

116 Glossary

W

WAN: wide area network

Glos

Manualsnet FAQs

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

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

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

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

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

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

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