Dell EMC PowerProtect Oracle RMAN Agent 19.3 ... · Dell EMC PowerProtect Oracle RMAN Agent Version...

Dell EMC PowerProtect Oracle RMANAgentVersion 19.3

Administration GuideREV 01

December 2019

Copyright © 2012-2019 Dell Inc. or its subsidiaries. All rights reserved.

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

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

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

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

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

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

of their respective owners. Published in the USA.

Dell EMCHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.DellEMC.com

2 Dell EMC PowerProtect Oracle RMAN Agent Administration Guide

7

9

11

Introducing the Oracle RMAN Agent 15Overview of Oracle RMAN agent.......................................................................16Supported configurations.................................................................................. 17

DD Boost Features 19Distributed segment processing........................................................................20Advanced load balancing and link failover......................................................... 22

Configuration restrictions.................................................................... 23DD Boost-over-Fibre Channel transport............................................................24DD Boost-over-Fibre Channel path management..............................................26

Initial path selection............................................................................. 27Client path failover............................................................................... 27Dynamic re-balancing...........................................................................28Queue-depth constraints..................................................................... 28

Encrypted managed file replication................................................................... 28DD Boost and high availability........................................................................... 29

DD Boost, HA, and failover...................................................................29Partial HA configurations .................................................................... 30

Low-bandwidth optimization.............................................................................30Client access validation..................................................................................... 31In-flight encryption............................................................................................31Marker support .................................................................................................31

Configuring the Data Domain System for Stand-alone Oracle RMANAgent Deployments 33Oracle RMAN agent and DD OS upgrades........................................................ 34Firewalls and ports............................................................................................ 34Enabling DD Boost on a Data Domain system....................................................34Enabling Oracle optimized deduplication...........................................................35Configuring the DD Boost server...................................................................... 36

Creating storage units..........................................................................36Configuring distributed segment processing........................................ 36Configuring advanced load balancing and link failover.......................... 37Enabling low-bandwidth optimization ..................................................38Enabling encrypted file replication....................................................... 38Configuring client access validation..................................................... 39

Configuring DD Boost-over-FC service.............................................................40Sizing DD Boost-over-FC device-set................................................... 42Sizing calculation................................................................................. 43

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

CONTENTS

Dell EMC PowerProtect Oracle RMAN Agent Administration Guide 3

Configuring the SCSI device driver for AIX clients............................... 45Configuring the SCSI generic device driver for Solaris clients..............45

Configuring the Oracle RMAN Agent for Stand-alone Deployment49Installing and configuring the Oracle RMAN agent on AIX, Linux, and Solarissystems............................................................................................................ 50

Installing the Oracle RMAN agent on database servers........................50Installing the Oracle RMAN agent on Linux and UNIX.......................... 52Uninstalling the Oracle RMAN agent on database servers................... 56Uninstalling the Oracle RMAN agent on Linux and UNIX...................... 57Configuring the software on Linux and UNIX systems..........................57

Installing and configuring the Oracle RMAN agent on Windows systems..........58Installing the Oracle RMAN agent on database servers........................58Installing the Oracle RMAN agent on Windows systems...................... 59Uninstalling the Oracle RMAN agent on Windows systems.................. 62Configuring the software on Windows systems................................... 62

Registering each Data Domain system.............................................................. 62Registering a standard Data Domain system........................................ 63Registering a Data Domain system with DD Boost over Fibre Channel....65Registering a Data Domain system for shared lockbox access..............67

Migrating an Oracle configuration from the database application agent........... 69Updating the RMAN scripts for Oracle RMAN agent operations.......... 70Using the correct RMAN script for restore, crosscheck, and deleteoperations............................................................................................ 72Updating the data movement policy for cloud tier operations.............. 73

Performing backups of a clustered environment to Data Domain...................... 74Data Domain replication.................................................................................... 75

Performing managed file replication (MFR)......................................... 75Restoring from MTree replicated backups........................................... 79

Specifying subdirectories for Oracle RMAN agent backups..............................80Performing backups and restores of Oracle CDBs and PDBs............................ 82Performing DD Boost compressed restores...................................................... 83Display and deletion of backups........................................................................ 83

Using the ddutil command to display and delete backups.....................84Using the ddutil command to display backup information.....................87Using the ddutil command to delete backups.......................................90Using the ddutil command to prune backups based on age.................. 90

Oracle Incremental Merge operations................................................................91Overview of Oracle Incremental Merge features..................................92Installation requirements for Oracle Incremental Merge.......................93Configuration requirements for Oracle Incremental Merge.................. 94Performing the Oracle Incremental Merge operations........................ 103

Configuring the use of Data Domain Cloud Tier for data movement to the cloud..131

Setting up the data movement to the cloud........................................ 131Performing the data recall from the cloud.......................................... 132RMAN crosscheck and deletion of backup data in the cloud...............133

Usage limits on Data Domain resources........................................................... 133Oracle RMAN agent operations with Data Domain usage limits oncapacity.............................................................................................. 134Oracle RMAN agent operations with Data Domain usage limits onstreams...............................................................................................134Configuring usage limits on Data Domain resources............................134

Chapter 4

Contents


Estimating the Data Domain resource usage on Oracle systems......... 135

Data Domain System Administration 137Restricting DD Boost access to specific database servers...............................138File replication version compatibility................................................................ 138Modifying an interface group...........................................................................139

Removing the advanced load balancing and link failover configuration....139

Troubleshooting 141Troubleshooting overview................................................................................142Investigating problems.....................................................................................142Oracle limitations.............................................................................................142Reporting problems......................................................................................... 142Data Domain system settings for file replication.............................................. 143Lockbox troubleshooting information.............................................................. 143Failure to load the media management library..................................................144

Using DD Boost Commands 147DD Boost command summary..........................................................................148The ddboost command options........................................................................148

access................................................................................................ 148clients................................................................................................. 149destroy............................................................................................... 149disable................................................................................................ 149enable.................................................................................................150fc........................................................................................................150file-replication.................................................................................... 150ifgroup................................................................................................ 154option................................................................................................. 156reset................................................................................................... 157set user-name.....................................................................................157show................................................................................................... 157status................................................................................................. 159storage-unit........................................................................................159

Installation and Configuration Checklist 161Configure the Data Domain system................................................................. 162Download and install the Oracle RMAN agent................................................. 162Configure RMAN for the environment............................................................. 162Test the installation by using sbttest (optional) ..............................................163Backup examples............................................................................................. 163

Performing a Backup with Oracle Enterprise Manager 165Example screens..............................................................................................166

Installing and Configuring the Oracle RMAN Agent 169Installation and configuration examples........................................................... 170

Chapter 5

Chapter 6

Chapter 7

Appendix A

Appendix B

Appendix C

Contents


Contents


Oracle RMAN agent configuration..................................................................................... 16High-level data flow with distributed segment processing disabled................................... 21High-level data flow with distributed segment processing enabled................................... 22Example of advanced load balancing and link failover configuration.................................. 23DD Boost-over-IP transport.............................................................................................. 24SCSI commands between media server and Data Domain system.....................................25Fibre Channel communication path................................................................................... 25DD Boost-over-FC path management scenario................................................................. 26Login window...................................................................................................................166Database instance page...................................................................................................166Processing page.............................................................................................................. 166Schedule Customized Backup: Options page................................................................... 167Schedule Customized Backup: Schedule page................................................................. 167Schedule Customized Backup: Review page.................................................................... 167Execution page................................................................................................................ 168

123456789101112131415

FIGURES


Figures


Revision history..................................................................................................................11Style conventions.............................................................................................................. 12Environment variables for installation or upgrade of Oracle RMAN agent..........................51Software package names on UNIX and Linux.................................................................... 52Product software components on Linux or UNIX.............................................................. 54Environment variables for uninstallation of Oracle RMAN agent....................................... 56Product software components on Windows......................................................................60The ddutil command options for backup display and deletion............................................85Oracle RMAN agent version 19.3 compatibility matrix for Oracle Incremental Merge........ 91Configuration file parameters for Oracle Incremental Merge.............................................97The ddbmoim command options for Oracle Incremental Merge operations..................... 104Summary of DD Boost commands................................................................................... 148Inbound and outbound file transfer.................................................................................. 152Inbound and outbound data transfer................................................................................153Output definitions for DD Boost histogram......................................................................158

123456789101112131415

TABLES


Tables


Preface

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

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

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

Purpose

This document describes how to install, configure, and use the PowerProtect Oracle RMAN agentversion 19.3 software.

In earlier versions of the product, the Oracle RMAN agent was known as Data Domain Boost (DDBoost) for Oracle Recovery Manager (RMAN) or the RMAN plug-in. In version 4.0, the productname changed to Oracle RMAN agent.

Note: The Oracle RMAN agent uses Application Direct workflows, known in previous releasesas DD Boost workflows.

Audience

This guide is for system administrators who are familiar with Oracle backup applications andgeneral backup administration.

Revision history

The following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

01 December 17, 2019 Initial release of this document for Oracle RMANagent 19.3.

Related documentation

The following publications provide additional information:

l PowerProtect Oracle RMAN Agent Release Notes

l DDBEA section of the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection

l Data Domain Operating System documentation

l Data Domain system installation and setup guide for each supported platform, for exampleDD890, DD670, and so on

l PowerProtect Data Manager Administration and User Guide

l PowerProtect Data Manager Deployment Guide

l PowerProtect Data Manager Security Configuration Guide

l PowerProtect X400 Administration and User Guide


https://www.dell.com/support

https://elabnavigator.emc.com/eln/modernHomeDataProtection


l PowerProtect X400 Deployment Guide

l PowerProtect X400 Security Configuration Guide

RMAN Documentation

Oracle 18c: From the Oracle Database Documentation library at https://docs.oracle.com/en/database/oracle/oracle-database/18/, select Administration and select a guide under Backup andRecovery:

l Database Backup and Recovery Reference

l Database Backup and Recovery User’s Guide

Oracle 12c Release 2: From the Oracle Database Documentation library at https://docs.oracle.com/en/database/oracle/oracle-database/12.2/index.html, select Administration andselect a guide under Backup and Recovery:

l Database Backup and Recovery Reference

l Database Backup and Recovery User’s Guide

Oracle 12c Release 1: From the Oracle Database Documentation library at http://docs.oracle.com/database/121/index.htm, select Database Administration and select a guide under Backup andRecovery:

l Backup and Recovery User’s Guide

l Backup and Recovery Reference

Oracle 11g Release 2: From the Oracle Database Documentation library at www.oracle.com/pls/db112/homepage, select Database Administration and select a guide under Backup and Recovery:

l Backup and Recovery User’s Guide


Oracle 10g Release 2: From the Oracle Database Documentation library at www.oracle.com/pls/db102/homepage, select Administration and select a guide under Backup and Recovery:


l Backup and Recovery Advanced User’s Guide

Special notice conventions that are used in this document

The following conventions are used for special notices:

NOTICE Identifies content that warns of potential business or data loss.

Note: Contains information that is incidental, but not essential, to the topic.

Typographical conventions

The following type style conventions are used in this document:

Table 2 Style conventions

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

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

Monospace Used for:

l System code

Preface


https://docs.oracle.com/en/database/oracle/oracle-database/18/

https://docs.oracle.com/en/database/oracle/oracle-database/18/

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/index.html

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/index.html

http://docs.oracle.com/database/121/index.htm

http://docs.oracle.com/database/121/index.htm

http://www.oracle.com/pls/db112/homepage




Table 2 Style conventions (continued)

l System output, such as an error message or script

l Pathnames, file names, file name extensions, prompts, andsyntax

l Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means orfor 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 theexample.

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

Where to find product documentation

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

l https://community.emc.com

Where to get support

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

To access a product-specific page:

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

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

Knowledgebase

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

To search the Knowledgebase:


2. On the Support tab, click Knowledge Base.

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

Live chat

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


2. On the Support tab, click Contact Support.

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

Preface



https://community.emc.com





Service requests

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


2. On the Support tab, click Service Requests.

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

To review an open service request:


2. On the Support tab, click Service Requests.

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

Online communities

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

How to provide feedback

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

Preface




https://community.emc.com

mailto:[email protected]

CHAPTER 1

Introducing the Oracle RMAN Agent

This chapter contains the following topics:

l Overview of Oracle RMAN agent........................................................................................... 16l Supported configurations.......................................................................................................17


Overview of Oracle RMAN agentThe Oracle RMAN agent enables database servers to communicate with Data Domain andPowerProtect X400 systems in an optimized way, without the need to use a backup application.

Note:

l In earlier versions of the product, the Oracle RMAN agent was known as Data DomainBoost (DD Boost) for Oracle Recovery Manager (RMAN) or the RMAN plug-in. In version4.0, the product name changed to Oracle RMAN agent.

l The Oracle RMAN agent uses Application Direct workflows, known in previous releases asDD Boost workflows.

l Self-service backups and restores are backups and restores that you perform throughRMAN or Oracle Enterprise Manager (OEM).

The use of the Oracle RMAN agent improves performance while reducing the amount of data thatis transferred over the LAN. In the context of Oracle RMAN, the software has two components:

l An RMAN agent that you install on each database server. This RMAN agent includes the DDBoost libraries for communicating with the DD Boost server that runs on the Data Domainsystem.

l The DD Boost server that runs on the Data Domain systems.

RMAN sets policies that control when backups and replications occur. Administrators managebackup, replication, and restore from a single console and can use all the features of DD Boost,including WAN-efficient replicator software. RMAN manages all the files (collections of data) inthe catalog, even those created by the Data Domain system.

The Data Domain or PowerProtect X400 system exposes pre-made disk volumes called storageunits to a DD Boost enabled database server. Multiple database servers, each with the OracleRMAN agent, can use the same storage unit on a Data Domain system as a storage server. Eachdatabase server can run a different operating system, provided that it is supported by DataDomain.

The following figure shows an example configuration of the Oracle RMAN agent with Data Domainsystems.

Figure 1 Oracle RMAN agent configuration



Supported configurationsThe Oracle RMAN agent supports DD Boost on the following Data Domain and PowerProtect X400systems:

l Data Domain systems DD1xx, DD5xx, DD6xx, DD8xx, DD9xx

l Data Domain Extended Retention (formerly Archiver) systems

l PowerProtect X400 systems

The Oracle RMAN agent version must be compatible with the Data Domain or PowerProtect X400system and RMAN configurations. Data Domain and PowerProtect X400 do not supportcombinations other than those detailed in the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection. The information about Oracle RMANagent is available in the DDBEA section of the eLab Navigator. Check that information before youupgrade either the Oracle RMAN agent or the Data Domain or PowerProtect X400 system.





CHAPTER 2

DD Boost Features


l Distributed segment processing............................................................................................ 20l Advanced load balancing and link failover.............................................................................. 22l DD Boost-over-Fibre Channel transport................................................................................ 24l DD Boost-over-Fibre Channel path management.................................................................. 26l Encrypted managed file replication....................................................................................... 28l DD Boost and high availability................................................................................................29l Low-bandwidth optimization................................................................................................. 30l Client access validation..........................................................................................................31l In-flight encryption................................................................................................................ 31l Marker support ..................................................................................................................... 31


Distributed segment processingDistributed segment processing enables parts of the deduplication process to be performed by theOracle RMAN agent, which prevents the sending of duplicate data to the Data Domain orPowerProtect X400 system that is configured as a storage server. The option to distribute theprocessing is enabled or disabled on the Data Domain or PowerProtect X400 system. The OracleRMAN agent negotiates with the Data Domain or PowerProtect X400 system for the currentsetting of the option and behaves appropriately. The Oracle RMAN agent offers two modes ofoperation for sending backup data to a Data Domain or PowerProtect X400 system, one withdistributed segment processing enabled and the other with distributed segment processingdisabled.

Distributed segment processing provides the following benefits:

l Higher throughput is possible because the Oracle RMAN agent sends only unique data to aData Domain or PowerProtect X400 system, instead of sending all the data over the LAN.Throughput improvements depend on the redundant nature of the data being backed up, theoverall workload on the database server, and the capability of the database server. In general,greater throughput is attained with higher redundancy, greater database server workload, anddatabase server capability.

l The network bandwidth requirements are significantly reduced because only the unique data issent over the LAN to the Data Domain or PowerProtect X400 system.

l Recovery from failed backups can potentially proceed much faster. If a large backup fails in themiddle or towards the end, when it is restarted by RMAN, the data already sent to the DataDomain or PowerProtect X400 system does not have to be resent. This results in fastercompletion of the backup on retry.

The Data Domain Operating System Administration Guide provides more information about localcompression and its configuration.

You manage distributed segment processing through the ddboost option commands only witha Data Domain system. Data Domain recommends that you use distributed segment processing ifyour network connection is 1 Gb Ethernet. Configuring distributed segment processing on page36 provides details.

Distributed segment processing disabled

In this mode, the Oracle RMAN agent sends the data directly to the Data Domain or PowerProtectX400 system over the LAN. The Data Domain or PowerProtect X400 system then segments,deduplicates, and compresses the data before it is written to the disk. The Oracle RMAN agentruns on the database server.

Note: Distributed segment processing cannot be disabled on an Extended Retention DataDomain or PowerProtect X400 system.

The following figure shows a high-level data flow scenario for a single-system Data Domain systemwith distributed segment processing disabled.

DD Boost Features


Figure 2 High-level data flow with distributed segment processing disabled

Distributed segment processing enabled

In this mode, the deduplication process is distributed between the Oracle RMAN agent and theData Domain or PowerProtect X400 system. The Oracle RMAN agent runs on the database server.Parts of the deduplication process are run on the Oracle RMAN agent so that only unique data issent to a Data Domain or PowerProtect X400 system over the LAN.

The Oracle RMAN agent segments the data, computes IDs for the segments, checks with the DataDomain or PowerProtect X400 system for duplicate segments, compresses unique segments thatare not found on the Data Domain or PowerProtect X400 system, and sends the compressed datato the Data Domain or PowerProtect X400 system. The Data Domain or PowerProtect X400system then writes the unique data to disk.

The Oracle RMAN agent’s handling of data is transparent to RMAN, and the agent does not storeany data on the database server.

The following figure shows a high-level data flow scenario for a single-system Data Domain systemwith distributed segment processing enabled.

DD Boost Features


Figure 3 High-level data flow with distributed segment processing enabled

Advanced load balancing and link failoverNote: PowerProtect X400 systems do not support the advanced load balancing and linkfailover feature. This topic applies only to Data Domain systems.

The advanced load balancing and link failover feature enables the combination of multiple Ethernetlinks into a group. Only one of the interfaces on the Data Domain system is registered with RMAN.The Oracle RMAN agent negotiates with the Data Domain system on the interface registered withRMAN to obtain an interface to send the data. The load balancing provides higher physicalthroughput to the Data Domain system compared to configuring the interfaces into a virtualinterface using Ethernet level aggregation.

The Data Domain system load balances the connections coming in from multiple database serverson all the interfaces in the group. The load balancing is transparent to RMAN. Because advancedload balancing and link failover works at the software layer of the Oracle RMAN agent, it isseamless to the underlying network connectivity and supports both physical and virtual interfaces.

The data transfer is load balanced based on the number of connections outstanding on theinterfaces. Only connections for backup and restore jobs are load balanced.

Note:

l The file replication connection between the Data Domain systems is not part of the loadbalancing. A single IP address is used for the target Data Domain system.

l It is recommended that you exclude one interface from the interface group (ifgroup) andreserve it for the file replication path between the source and target Data Domain systems.Every Oracle RMAN agent must be able to connect to every interface that is a member ofthe interface group on the Data Domain system.

The following figure shows an example high-level configuration diagram. The interface marked inred is registered with RMAN.

DD Boost Features


Figure 4 Example of advanced load balancing and link failover configuration

The advanced load balancing and link failover feature can be used with other network layeraggregation and failover technologies. The sample configuration in the preceding figure shows onesuch possibility. The links connecting the database servers and the switch that connects to DataDomain system are put in an aggregated failover mode. This configuration provides end-to-endnetwork failover functionality. Any of the available aggregation technologies can be used betweenthe database server and the switch.

The advanced load balancing and link failover functionality also works with other network layerfunctionality on the Data Domain systems, including VLAN tagging and IP aliasing. Thisfunctionality enables additional flexibility in segregating traffic into multiple virtual networks, all ofwhich run over the same physical links on the Data Domain system.

Note: The Data Domain Operating System Administration Guide provides more information abouthow to configure VLAN tagging and IP aliasing on a Data Domain system.

Advanced load balancing and link failover provides the following benefits:

l Eliminates the need to register multiple storage servers (one for each interface) with RMAN,which can potentially simplify installation management.

l If one of the interfaces in the group goes down while the Data Domain system is stilloperational, the subsequent incoming backup jobs are routed to the available interfaces.

l The backup and restore jobs are automatically load balanced on multiple interfaces in thegroup, which can potentially result in higher utilization of the links.

l All in-flight jobs to the failed interface are failed over transparently to healthy operational links.From the point of view of RMAN, the jobs continue uninterrupted.

Configuring advanced load balancing and link failover on page 37 provides more details.

Configuration restrictionsl Interfaces can be added only to the group by using an IP address.

DD Boost Features


l Although the advanced load balancing and link failover feature works with mixed 1 GbEinterfaces and 10 GbE interfaces in a group, this is not a recommended setup. It isrecommended to have interfaces with the same link speed in a group.

l Prior to DD OS 5.2, only one interface group was supported on a Data Domain system. Thismeant that, to connect more than one database server, a switch was needed in the middle. DDOS 5.2 and later support multiple interface groups, so this restriction no longer applies.

DD Boost-over-Fibre Channel transportNote: Data Domain Virtual Edition and PowerProtect X400 systems do not support the FibreChannel transport.

Prior to DD OS release 5.3, all communication between the DD Boost library and any Data Domainsystem was performed by using IP networking. The application specified the Data Domain systemby using its hostname or IP address, and the DD Boost Library used TCP/IP connections totransmit requests to, and receive responses from, the Data Domain system, as shown in thefollowing figure.

Figure 5 DD Boost-over-IP transport

DD OS release 5.3 introduced Fibre Channel as an alternative transport mechanism forcommunication between the DD Boost library and the Data Domain system.

Certain installations prefer or require the use of Fibre Channel as the media for data transferbetween media servers and storage systems. The DD Boost-over-Fibre Channel transport (DDBoost-over-FC) enables such installations to access the features provided by the DD Boosttechnology.

Although Fibre Channel is specified as a general-purpose data transport mechanism, in practiceFibre Channel is used solely as a transport for SCSI device access. In standard host operatingsystems, such as Windows and Linux, Fibre Channel hardware and drivers reside solely within theSCSI protocol stacks. Therefore, the DD Boost-over-FC transport must use SCSI commands for allcommunication.

In the DD Boost-over-FC solution, the Data Domain system advertises one or more SCSI devicesof type Processor. The media server operating system discovers these devices, and makes themavailable to applications through a generic SCSI mechanism (Linux: SCSI Generic driver; Windows:SCSI Pass-Through Interface).

To request access to a Data Domain system by using the DD Boost-over-FC transport, theapplication specifies the Data Domain system by using the special string DFC-<dfc-server-name>,where dfc-server-name is the DD Boost-over-FC server name configured for the Data Domainsystem. The DD Boost-over-FC transport logic within the DD Boost library examines the set of

DD Boost Features


generic SCSI devices available on the media server and uses SCSI commands to identify a catalogof devices, which are paths to the specified Data Domain system.

Referencing this catalog, the DD Boost-over-FC transport logic issues SCSI commands to theidentified generic SCSI devices, to transfer DD Boost protocol requests and responses betweenthe library and the Data Domain system.

Figure 6 SCSI commands between media server and Data Domain system

Most DD Boost features are independent of the transport. One notable exception is the DD Boost-over-IP advanced load balancing and link failover feature, and its associated ifgroups. This featureis specific to the IP transport. For the DD Boost-over-FC transport, load balancing and link-levelhigh availability is achieved through different means.

The DD Boost-over-FC communication path applies only between the media server/DD Boostlibrary and the Data Domain system, and does not apply to communication between two DataDomain systems. For example, the managed file replication section of this document describesefficient replication of data from one Data Domain system to another, possibly over a WAN. Asshown in the following figure, such communication is always over a TCP/IP network, regardless ofthe communication path between the media server and the Data Domain systems.

Figure 7 Fibre Channel communication path

DD Boost Features


DD Boost-over-Fibre Channel path managementNote: Data Domain Virtual Edition and PowerProtect X400 systems do not support the FibreChannel transport.

The Dynamic Interface Group (DIG)-based mechanism is based on Ethernet interfaces and is notapplicable to the Fibre Channel transport. Instead, a different path mechanism is provided for theDD Boost-over-FC solution.

The Data Domain system advertises one or more SCSI processor-type devices to the backupserver, over one or more physical paths. The operating system discovers all devices through allavailable paths, and creates a generic SCSI device for each discovered device and path.

For example, consider the following case:

l Backup server has 2 initiator HBA ports (A and B)

l Data Domain System has 2 FC target endpoints (C and D)

l Fibre Channel Fabric zoning is configured such that both initiator HBA ports can access bothFC target endpoints

l Data Domain system is configured with a SCSI target access group that contains:

n Both FC target endpoints on the Data Domain System

n Both initiator HBA ports

n 4 devices (0, 1, 2, and 3)

Figure 8 DD Boost-over-FC path management scenario

1. Four devices2. Backup Server3. HBA Initiator A4. HBA Initiator B5. Data Domain System6. Fibre Channel Endpoint C7. Fibre Channel Endpoint D

In this case, the backup server operating system may discover up to 16 generic SCSI devices, onefor each combination of initiator, target endpoint, and device number:

l /dev/sg11: (A, C, 0)

l /dev/sg12: (A, C, 1)

l /dev/sg13: (A, C, 2)

l /dev/sg14: (A, C, 3)

DD Boost Features


l /dev/sg15: (A, D, 0)

l /dev/sg16: (A, D, 1)

l /dev/sg17: (A, D, 2)

l /dev/sg18: (A, D, 3)

l /dev/sg19: (B, C, 0)

l /dev/sg20: (B, C, 1)

l /dev/sg21: (B, C, 2)

l /dev/sg22: (B, C, 3)

l /dev/sg23: (B, D, 0)

l /dev/sg24: (B, D, 1)

l /dev/sg25: (B, D, 2)

l /dev/sg26: (B, D, 3)

When the application requests that the DD Boost library establish a connection to the server, theDD Boost-over-FC transport logic within the DD Boost library uses SCSI requests to build acatalog of these 16 generic SCSI devices, which are paths to access the DD Boost-over-FC serviceon the required Data Domain system. As part of establishing the connection to the server, the DDBoost-over-FC transport logic provides to the server this catalog of paths.

Initial path selectionThe server maintains statistics on the DD Boost-over-FC traffic over the various target endpointsand known initiators. During the connection setup procedure, path management logic in the serverconsults these statistics, and selects the path to be used for this connection, based upon thefollowing criteria:

l For queue-depth constrained clients (see below), evenly distribute the connections acrossdifferent paths.

l Choose the least-busy target endpoint.

l Choose the least-busy initiator from among paths to the selected target endpoint.

Client path failoverThe client may start using a different path because it is directed to do so by the server dynamic re-balancing logic. However, the client may also decide, on its own, to start using a different availablepath. This happens if the client receives errors when using the connection's current path.

For example, assume the path catalog for a connection consists of eight paths:

/dev/sg21: (A, C, 0)

/dev/sg22: (A, C, 1)

/dev/sg23: (A, D, 0)

/dev/sg24: (A, D, 1)

/dev/sg25: (B, C, 0)

/dev/sg26: (B, C, 1)

/dev/sg27: (B, D, 0)

/dev/sg28: (B, D, 1)

The server selects the (A, C, 0) path during initial path selection. The DFC transport logic in theDD Boost library starts sending and receiving data for the connection, using SCSI commandsto /dev/sg21.

DD Boost Features


Later, the link from target endpoint C to its switch becomes unavailable, due to cable pull or somehardware failure. Any subsequent SCSI request submitted by the DFC transport logic to /dev/sg21 fails with an error code indicating that the SCSI request could not be delivered to the device.

In this case, the DFC transport logic looks in the catalog of devices, for a path with a differentphysical component; that is, a different combination of initiator and target endpoint. The SCSIrequest is retried on the selected path, and the process is repeated until a path is discovered overwhich the SCSI request can be successfully completed.

Dynamic re-balancingThe server periodically performs dynamic re-balancing. This involves consulting the statistics tolook for situations where:

l For queue-depth constrained clients (see below), connections are distributed unequally acrossavailable paths.

l Workload across target endpoints is out of balance.

l Workload across initiators is out of balance.

If such a situation is discovered, the server can mark one or more connections for server-directedpath migration. This is achieved by having the server request, during a future data transferoperation, that the DD Boost library start using a different available path from the catalog forsubsequent operations.

Queue-depth constraintsFor the purposes of the DD Boost-over-FC solution, the specific SCSI device over which a requestis received is irrelevant. All SCSI devices are identical, destination objects for SCSI commands asrequired by the SCSI protocol. When processing a SCSI request, the server logic gives noconsideration to the specific device on which the SCSI request arrived.

Why bother to allow for more than one device? Because certain client-side operating systemsimpose a restriction on the number of outstanding I/O requests that can be conductedsimultaneously over a given generic SCSI device. For example, the Windows SCSI Pass-ThroughInterface mechanism will only conduct one SCSI request at a time through each of its generic SCSIdevices. This impacts the performance of the DD Boost-over FC solution, if multiple connections(such as backup jobs) try to use the same generic SCSI device.

Additionally, the Data Domain system also imposes a limit on the number of outstanding I/Orequests per advertised SCSI device. For performance reasons with larger workloads, multipleSCSI devices may need to be advertised on the Data Domain system.

The term queue-depth describes the system-imposed limit on the number of simultaneous SCSIrequests on a single device. Client systems, such as Windows, whose queue depth is so low as toimpact performance are considered queue-depth constrained.

Refer to Sizing DD Boost-over-FC device-set on page 42 for guidance on how many devices toconfigure based on the workload, type of Data Domain system, and whether or not the clientsystem is queue-depth constrained.

Encrypted managed file replicationNote: If you have a PowerProtect X400 system, refer to the PowerProtect X400documentation for information on how to enable encryption of managed file replication. Thistopic applies only to Data Domain systems.

By default, file replication jobs are set up between two Data Domain systems without encryptionafter being authenticated by using the preconfigured DD Boost username and password. If theencrypted file replication feature is enabled, the session between the source and destination Data

DD Boost Features


Domain systems is encrypted by using Secure Sockets Layer (SSL), which ensures that all theimage data and metadata is sent encrypted over the WAN.

Enabling this option on the Data Domain system is transparent to RMAN. When RMAN requeststhe Data Domain system to perform a file replication job, the source and destination systemsnegotiate automatically to perform encryption without the knowledge of RMAN. Encrypted filereplication uses the ADH-AES256-SHA cipher suite. There is no ability to configure a differentsuite in the DD OS.

Encrypted file replication is available to a Data Domain system with an installed Replicator license,and applies to all the file replication jobs on that system. Both the source and the destination DataDomain systems that are participating in file replication jobs must have this option enabled.Otherwise, replication fails.

Encrypted file replication can be used with the encryption of data-at-rest feature that is availableon the DD OS with the optional Encryption license. When encrypted file replication is used with theencryption of data-at-rest feature, the encrypted backup image data is encrypted again by usingSSL for sending over a WAN.

Note:

l Both the source and the destination Data Domain systems must run DD OS 5.0 or later touse this feature.

l Enabling this feature does not require restarting the file system on a Data Domain system.

l The low-bandwidth optimization and the encryption options can be used with each other.

Enabling encrypted file replication on page 38 and the Data Domain Operating SystemAdministration Guide provide more information about this topic.

DD Boost and high availabilityNote: If you have a PowerProtect X400 system, refer to the PowerProtect X400documentation for information on the high availability options provided by PowerProtect X400systems. This topic applies only to Data Domain systems.

Starting with DD OS 5.7.1, Data Domain systems with DD Boost can accommodate high availability(HA) configurations.

During normal operations, DD Boost on the active node sends to the standby node any DD Boostdata and state information necessary to continue the DD Boost operations on the standby node if afailure should occur.

Note: DD Boost currently supports only active-standby configurations.

DD Boost performs periodic operations to force the user data to disk on the server. DD Boost onthe client buffers all the user data between these periodic synchronize-to-disk operations so that ifa DD server fails, the data can be resent.

This method also applies to virtual writes. You can mix standard write operations with syntheticwrite operations.

DD Boost, HA, and failoverWhen a Data Domain system with HA enabled fails, recovery occurs in less than ten minutes. Oncethe failed system recovers, DD Boost recovery begins and applications that use DD Boostautomatically recover without failing or receiving an error. DD Boost recovery might take longerthan ten minutes because DD Boost recovery cannot start until the failover of the DD system iscomplete.

DD Boost Features


No changes are necessary to allow applications to take advantage of DD Boost HA capabilities.With DD Boost 3.2.1 and DD OS 5.7.1 on HA configurations, applications automatically recover if afailover occurs. No action is required from the application.

Partial HA configurationsManaged file replication (MFR) is supported between any two Data Domain systems that runcompatible versions of DD OS, regardless of whether one or both of the DD systems is enabled forHA.

MFR between two HA systems succeeds in the event of failure of either system because bothsystems support HA. An MFR in progress recovers seamlessly if either the source HA system orthe destination HA system fails.

MFR between an HA system and a non-HA system succeeds if the HA system fails, but does notsucceed if the non-HA system fails.

MFR to HA enabled systemsA single-node Data Domain system that runs DD OS 5.7 or later and performs MFR to an HAsystem recovers seamlessly if the HA system fails. The MFR does not recover seamlessly if thesingle-node Data Domain source system fails.

MFR from HA enabled systemsAn MFR from an HA system to a single-node Data Domain system that runs DD OS 5.7 or laterrecovers seamlessly if the source HA system fails. However, the MFR does not recover seamlesslyif the single-node Data Domain destination system fails.

In all cases that involve partial HA configurations, the non-HA system must run DD OS 5.7 toenable an MFR to continue seamlessly when a failure occurs. In partial HA configurations wherethe non-HA system runs a DD OS version earlier than 5.7, the MFR does not recover seamlesslyfrom a failure of either system.

In all cases, the application must use DD HA Boost 3.2.1 libraries to enable the seamless recoveryof the MFR.

Low-bandwidth optimizationNote: If you have a PowerProtect X400 system, refer to the PowerProtect X400documentation for information on the replication options. This topic applies only to DataDomain systems.

The low-bandwidth Replicator option reduces the WAN bandwidth utilization. This option is usefulif file replication is performed over a low-bandwidth network (WAN) link. This option providesadditional compression during data transfer and is recommended only for file replication jobs thatoccur over WAN links that have fewer than 6 Mb/s of available bandwidth.

The low-bandwidth optimization option is available to Data Domain systems with an installedReplicator license. The option is enabled on a Data Domain system and applies to all the filereplication jobs on that system.

Enabling this option on Data Domain system is transparent to RMAN. When RMAN requests a DataDomain system to perform a file replication job, the source and destination systems automaticallyperform the additional compression without involving RMAN.

Each Data Domain system that participates in managed file replication must have this optionenabled.

Enabling low-bandwidth optimization on page 38 and the Data Domain Operating SystemAdministration Guide provide more information about this topic.

DD Boost Features


Client access validationConfiguring client access validation for DD Boost limits the access to the Data Domain system forDD Boost clients by requiring DD Boost authentication per connection for:

l The initial connection to the Data Domain system

l Each restart of DD Boost (Enable/Disable)

l Each file system restart

l Each Data Domain system reboot

The list of clients can be updated at any time without a restart requirement, which eliminates theaccess validation impact on jobs in progress.

In-flight encryptionNote: PowerProtect X400 systems do not support the in-flight encryption feature. This topicapplies only to Data Domain systems.

In-flight encryption enables applications to encrypt in-flight backup or restore data over the LANfrom the Data Domain system. This feature was introduced to offer a more secure data transportcapability.

When configured, the client is able to use TLS to encrypt the session between the client and theData Domain system. The specific cipher suite used is either ADH-AES256-SHA, if the HIGHencryption option is selected, or ADH-AES128-SHA, if the MEDIUM encryption option is selected.

Marker supportThe default marker support setting is auto marker handling. If any marker is encountered in thefirst 512 KB of a write stream, support is enabled for that stream. Users can toggle the markersettings on a protection system. The DD OS Administration Guide provides details.

DD Boost Features


DD Boost Features


CHAPTER 3

Configuring the Data Domain System for Stand-alone Oracle RMAN Agent Deployments

Note: When the Oracle RMAN agent is deployed with PowerProtect Data Manager orPowerProtect X400, refer to the PowerProtect Data Manager or PowerProtect X400documentation for information about the protection target configuration.


l Oracle RMAN agent and DD OS upgrades............................................................................. 34l Firewalls and ports................................................................................................................ 34l Enabling DD Boost on a Data Domain system........................................................................ 34l Enabling Oracle optimized deduplication............................................................................... 35l Configuring the DD Boost server...........................................................................................36l Configuring DD Boost-over-FC service................................................................................. 40


Oracle RMAN agent and DD OS upgradesThe Oracle RMAN agent and DD OS maintenance compatibility is defined in the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection. The information about OracleRMAN agent is available in the DDBEA section of the eLab Navigator. Consult that publicationbefore you upgrade either the Oracle RMAN agent or the DD OS.

Firewalls and portsThe Data Domain system as it is initially configured does not work through a firewall (a databaseserver to a Data Domain system, or from one Data Domain system to another). If you need theData Domain system to work in the presence of a firewall, contact your network support provider.

The following ports must be open in a firewall to enable the DD Boost backups and file replication:

l TCP 2049 (NFS)

l TCP 2051 (Replication)

l TCP 111 (NFS portmapper)

l TCP xxx (Select a port for NFS mountd. The default MOUNTD port is 2052.)

Enabling DD Boost on a Data Domain systemAbout this task

Every Data Domain system that is enabled for DD Boost must have a unique name. You can use theData Domain system’s DNS name, which is always unique.

Procedure

1. On the Data Domain system, log in as an administrative user.

2. Verify that the file system is enabled and running:

# filesys status

The file system is enabled and running.

If disabled, enable the file system:

# filesys enable

3. Verify that the DD Boost license is enabled:

# license show

Feature licenses:

## License Key Feature-- -------------------- --------1 ABCD-EFGH-IJKL-MNOP DDBOOST-- -------------------- --------




If disabled, enter the license key that is provided:

# license add <license-key>

License “ABCE-BCDA-CDAB-DABC” added.

4. Establish the DD Boost username and password for the Data Domain system.

Note: The username and password are case-sensitive, and must match the usernameand password provided in Registering each Data Domain system on page 62.

# user add <username> password <password># ddboost user assign <username>

Note: If the username is changed or deleted, the change in access rights does not affectany current operations. For example, deleting the current clients from the DD Boostaccess list by using the ddboost clients del <client-list> command does not stopa file backup that is already in progress. All operations in progress continue. The changein access rights does not cause existing operations to fail. It is recommended to changeaccess rights only when no RMAN operations are in progress. The ddboost disablecommand can be used to prevent operations while access is changed. Disabling DDBoost terminates any existing operations, so be careful that no RMAN operations are inprogress when you disable DD Boost. After changing access, ddboost enable re-enables DD Boost and enables RMAN operations that are then subject to the changedaccess rights.

5. Enable DD Boost:

# ddboost enable

DD Boost enabled

Enabling Oracle optimized deduplicationAbout this task

For Oracle RMAN agent operations, ensure that you have enabled the Oracle optimizeddeduplication feature at the MTree level in the Data Domain system by running the followingcommand:

# mtree option set app-optimized-compression oracle1 mtree <mtree_path>

In the following command output, the MTrees with the value of oracle1 have the Oracle optimizeddeduplication enabled:

# mtree option show

Name Option Value--------------------- ------------------------- ------------------/data/col1/db2west app-optimized-compression global (none)



/data/col1/nfswest app-optimized-compression oracle1/data/col1/oracleoldf app-optimized-compression global (none)/data/col1/oraclevlab app-optimized-compression oracle1/data/col1/pool-test app-optimized-compression global (none)/data/col1/tdeoracle app-optimized-compression oracle1

Refer to the online white paper, Dell EMC Data Domain Oracle Optimized Deduplication, for moredetails on when to enable the Oracle optimized deduplication feature.

Configuring the DD Boost serverUse the tasks in this section to configure the DD Boost server.

Creating storage unitsAbout this task

Create one or more storage units on each Data Domain system that will be used with RMAN. Eachstorage unit name on a single Data Domain system must be unique. However, you can use thesame storage unit name on more than one Data Domain system. You must provide the storage unitname when you perform the RMAN backup and restore operations.

Storage unit names are case-sensitive.

Configuring the software on Linux and UNIX systems on page 57 and Configuring the software onWindows systems on page 62 provide more information.

Procedure

1. On the Data Domain system, enter the following command:

# ddboost storage-unit create <storage_unit_name> user <username>

2. Repeat step 1 for each storage unit that you want to create. Create at least one storage uniton each Data Domain system that you will use with RMAN. You can share a storage unit on aData Domain system with more than one RMAN client system.

Configuring distributed segment processingThe distributed segment processing option is configured on the Data Domain system and applies toall the database servers and the Oracle RMAN agents that are installed on them.

If distributed segment processing is disabled on the Data Domain system, then the data flow fromthe database servers is as shown in Figure 2 on page 21. If distributed segment processing isenabled, then the data flow is as shown in Figure 3 on page 22.

To configure the option, run the following command:

# ddboost option set distributed-segment-processing {enabled | disabled}

Note: Enabling or disabling the distributed segment processing option does not require arestart of the Data Domain file system.

Distributed segment processing is supported with the Oracle RMAN agent 1.0 or latercommunicating with a Data Domain system that runs DD OS 5.0 or later.



https://www.emc.com/collateral/white-papers/h15389-data-domain-oracle-optimized-deduplication.pdf

Distributed segment processing is enabled by default on a system initially installed with DD OS 5.2.If a system is upgraded from DD OS 5.0.x or 5.1.x to DD OS 5.2, distributed segment processing isleft in its previous state.

Configuring advanced load balancing and link failoverAbout this task

If an interface group is configured, when the Data Domain system receives data from the databaseserver clients, the data transfer is load balanced and distributed as separate jobs on the privatenetwork, providing higher throughput, especially for customers who use multiple 1 GbEconnections. Advanced load balancing and link failover on page 22 provides details.

Create an interface group on the Data Domain system by adding existing interfaces to the groupand registering the Data Domain system with RMAN, as described in the following steps.

Procedure

1. Add the interfaces into the group (the interfaces must have been created already with thenet command):

# ifgroup add default interface 192.168.1.1# ifgroup add default interface 192.168.1.2# ifgroup add default interface 192.168.1.3# ifgroup add default interface 192.168.1.4

Note: This example assumes that no additional named interface groups have beencreated and uses the default interface group. To see help for the net command, enterthe command with no arguments at the DD OS prompt.

2. Select one interface on the Data Domain system to register with RMAN. It is recommendedthat you create a failover aggregated interface and register that interface with RMAN.

Note: It is not mandatory to use an interface in the ifgroup to register with RMAN. Aninterface that is not part of the ifgroup can also be used to register with RMAN. It isrecommended that the interface be registered with a resolvable name using DNS or anyother name resolution mechanism.

3. Enable the feature on the Data Domain system:

# ifgroup enable default

Verify the configuration:

# ifgroup show config default interfaces

Group Name Status Interface------------------ ------------ default enabled 192.168.1.1 default enabled 192.168.1.2 default enabled 192.168.1.3 default enabled 192.168.1.4

After the interface group is set up, you can add or delete interfaces from the group. Modifying an interface group on page 139 provides details.



Note:You can manage the advanced load balancing and link failover through either of thefollowing methods:

l Run the ddboost ifgroup command, as described in ifgroup on page 154.

l Use the Data Domain System Manager (DD System Manager) Data Management >

DD Boost page, as described in the Data Domain Operating System AdministrationGuide.

Enabling low-bandwidth optimizationTo enable the low-bandwidth option, run the following command:

# ddboost file-replication option set low-bw-optim enabled

Low bandwidth optimization for file-replication set to “enabled”.

Note: Enabling or disabling the low-bandwidth optimization option does not require a restart ofthe Data Domain file system. However, after low-bandwidth optimization is enabled, a fullcleaning cycle on the Data Domain system is needed for effective operation.

You can monitor and manage the low-bandwidth optimization through either of the followingmethods:

l Run the ddboost file-replication command, as described in file-replication on page150.

l Use the DD System Manager Data Management > DD Boost page, as described in the DataDomain Operating System Administration Guide.

No configuration changes are required on the database server as this feature is transparent toRMAN.

Note:

l Enabling this feature takes additional resources of CPU and memory on the Data Domainsystem, so it is recommended that this option be used only when file replication is beingdone over low-bandwidth networks with less than 6 Mbps aggregate bandwidth.

l The Data Domain Operating System Administration Guide provides more information aboutthis feature.

Enabling encrypted file replicationTo enable the encrypted file replication option, run the following command:

# ddboost file-replication option set encryption enabled

The output indicates that the encryption you requested was enabled.

file-replication on page 150 provides more details about how to monitor and manage theencryption option for file replication.

Turning on this feature takes additional resources of CPU and memory on the Data Domainsystem.



Note: Enabling or disabling the encrypted file replication option does not require a restart ofthe Data Domain file system. For more information on this feature, see the discussion aboutthis topic in the Data Domain Operating System Administration Guide.

Encrypted file replication must be enabled on both of the Data Domain systems involved in thereplication. If either system does not have encryption file replication enabled, encryption will notbe used during replication between the two Data Domain systems.

Configuring client access validationConfiguring the client access control for DD Boost limits the access to the Data Domain system forDD Boost clients and removes the dependency on the DNS. By default, if no clients are added tothe clients list when DD Boost is enabled, all clients are automatically included in the clients list. Bydefault, a * wildcard is used.

To restrict access, remove the * wildcard from the list and then add the new clients.

The backup server client list may contain both fully qualified domain names or short names. Thebackup host's fully qualified domain name needs to be correctly configured for reverse lookup inDNS.

To delete all the clients from the DD Boost clients list, run the following command:

# ddboost clients del <client-list>

Optionally, to delete all the clients previously added and reset the DD Boost clients list, run thefollowing command:

# ddboost client reset

Clients can be added as both fully qualified domain names and short names. To add clients to theDD Boost clients list, run the following command:

# ddboost clients add <client-list> [encryption-strength {medium | high} authentication-mode {one-way | two-way | two-way-password | anonymous}] | [authentication-mode kerberos]

For example:

# ddboost clients add ddboost-dl.emc.com ddboost-dlddboost-dl.emc.com

: Addedddboost-dl : Added

To view the DD Boost clients list, run the following command:

# ddboost clients show config

Client Encryption Strength Authentication Mode----------------------- ------------------- -------------------* none none*.corp.emc.com medium anonymousrtp-ost-ms02.domain high anonymousrtp-ost-ms02.domain.com high anonymous

During access validation, the following search order is used to restrict access:



l Wild card * followed by partial, for example, *.emc.com followed by *.coml Perfect match of sent client name, for example, ddboost-dl.emc.comIf the search does not find a matching entry for the client, the client will be denied access.

Enabling in-flight encryptionTo enable in-flight encryption for backup and restore operations over a LAN, run the followingcommand:

# ddboost clients add <client-list> [encryption-strength {medium | high} authentication-mode {one-way | two-way | anonymous}]

This command can enable encryption for a single client or for a set of clients. The authentication-mode option is used to configure the minimum authentication requirement. A client trying toconnect by using a weaker authentication setting will be blocked. Both one-way and two-wayauthentication require the client to be knowledgeable about certificates.

One-Way Authentication

The DD Boost client requests authentication from the Data Domain server, and the DataDomain server sends the appropriate certificate to the DD Boost client. The DD Boost clientverifies the certificate. The communication channel between the DD Boost client and the DataDomain server is encrypted.

Two-Way Authentication

The DD Boost client requests authentication from the Data Domain server using the servercertificate. The Data Domain server also requests authentication from the DD Boost clientusing the client certificate. After authentication through an SSL handshake, thecommunication channel between the DD Boost client and the Data Domain server isencrypted.

Anonymous Authentication

No certificates are exchanged, but information is exchanged. After the SSL handshake, thecommunication channel between the DD Boost client and the Data Domain server isencrypted.

Note: This option does not apply to DD Boost-over-Fibre Channel (FC). If both IP and FC arein use, encryption can be enabled on IP connections.

Configuring DD Boost-over-FC serviceAbout this task

To enable the DD Boost-over-FC service, install the supported Fibre Channel Target HBAs into thesystem. The Data Domain Operating System Command Reference Guide and Administration Guideprovide information about scsitarget as a related command that may be helpful in managing theSCSI target subsystem.

The following additional configuration steps are also required.

Procedure

1. Enable the DD Boost-over-FC service:

# ddboost option set fc enabled



2. Optionally set the DFC-server-name:

# ddboost fc dfc-server-name set <server-name>

Or accept the default, which is the base hostname of the Data Domain system. A valid dfc-server-name consists of one or more of the following characters:

l lower-case letters (“a”–“z”)

l upper-case letters (“A”–“Z”)

l digits (“0”–“9”)

l underscore (“_”)

l dash (“–”)

Note:

l The dot or period character (“.”) is not valid within a dfc-server-name; thisprecludes using the fully-qualified domain name of a Data Domain system as its dfc-server-name.

l Similar to IP hostnames, the dfc-server-name is not case-sensitive. Multiple DataDomain sytems accessible by the same clients using DDBoost-over-FC should beconfigured without case-sensitive dfc-server-name.

3. Create a SCSI target access group:

# ddboost fc group create <group-name>

For example:

# ddboost fc group create lab_group

4. To display the available list of scitarget endpoint:

# scsitarget endpoint show list

Endpoint System Address Transport Enabled Status------------- -------------- ------------ ------- ------endpoint-fc-0 6a FibreChannel Yes Onlineendpoint-fc-1 6b FibreChannel Yes Online------------- -------------- ------------ ------- ------

5. Configure the device set of the SCSI target access group for one of the endpoint:

# ddboost fc group modify <group-name> device-set count <count> endpoint <endpoint-list>

For example:

# ddboost fc group modify lab_group device-set count 8 endpoint 6a



6. Add initiators to the SCSI target access group:

# ddboost fc group add <group-name> initiator <initiator-spec>

For example:

# ddboost fc group add lab_group initiator "initiator-15,initiator-16"

Sizing DD Boost-over-FC device-setThe Data Domain system advertises one or more "DFC devices" of type Processor, which the DDBoost library uses to communicate with the DD Boost-over-FC service. On the Data Domainsystem, access to these DFC devices is granted to one or more initiators by adding the initiators toa ddboost-type scsitarget access group:

# ddboost fc group add lab_group initiator "initiator-15,initiator-16"

The number of DFC devices advertised to the initiator is controlled by configuring the device-setof the scsitarget access group:

# ddboost fc group modify lab_group device-set count 4

The maximum number of supported DFC devices per Data Domain system is 64. You can have thesame devices in multiple groups, but each group is limited to 64 devices.

Note: AIX DDdfc drivers support 128 devices. However, if you use the disk option with theddboost fc add command, this limitation is removed.

Because the DFC client sees each path to the Data Domain system as a separate device, morepaths and more DFC devices mean better performance for constrained clients such as AIX,Windows, and Solaris.

So, how many DFC devices should be advertised to initiators on a given backup server? Theanswer depends upon several factors:

1. Is the backup server queue-depth constrained?Windows platforms are considered “queue-depth constrained,” because the Windows SCSIPass-Through Interface mechanism will only conduct 1 SCSI request at a time through each ofits generic SCSI devices. This impacts the performance of the DD Boost-over FC solution, ifmultiple connections (for example, backup jobs) are trying to use the same generic SCSIdevice. So, for Windows platforms running more than one job, it is useful to advertise multipleDFC devices.

Contrast this with the behavior of the Linux SCSI Generic driver, which imposes no suchrestriction. Linux is not considered “queue-depth constrained,” so it is sufficient to simplyadvertise one DFC device to initiators on Linux systems.

2. Number of physical paths between backup server and Data Domain systemFor each advertised DFC device, the backup server operating system will create n genericSCSI devices, one for each physical path through which the backup server OS can access thedevice.

For example, if:



l Backup server has 2 initiator HBA ports (A and B)l Data Domain System has 2 FC target endpoints (C and D)l Fibre Channel Fabric zoning is configured such that both initiator HBA ports can access

both FC target endpoints

then the backup server OS will see each device through four physical paths:

A -> CA -> DB -> CB -> D

and will create 4 generic SCSI devices for each advertised DFC device.

For a Windows backup server (with its queue-depth=1 limitation), this allows up to 4simultaneous SCSI requests to the Data Domain system, even with only one DFC deviceadvertised.

Sizing calculationThe following calculation may be used to determine the number of DFC devices to advertise on theData Domain system and to the initiators on a specified media server. It is recommended that thesame number of DFC devices be advertised to all initiators on the same media server.

On the Data Domain system

The Data Domain system imposes a limit on the number of simultaneous requests to a single DFCSCSI device. Because of this limit, the number of devices advertised needs to be tuned dependingon the maximum number of simultaneous jobs to the system at any given time. In general, thelarger the number of jobs expected from media servers using DD Boost over FC, the higher thenumber of devices advertised.

Let J be the maximum number of simultaneous jobs running using DFC, to the Data Domain systemat any given time.

Let C be the maximum number of connections per job:

l 3 for DD Extended Retention systemsl 1 for other types of Data Domain systems

Calculate:

l Maximum simultaneous connections to the Data Domain system, using DFC, from all backupservers:

n S = J * Cn DFC device count D = minimum(64, 2*(S/128)), round upn All DFC access groups must be configured with "D" devices.

Example

Assume:

l 8 backup servers, DD Extended Retention systems, each server running a maximum of 30 jobsat any given time.

l Here, J = 8 * 30 = 240, C = 3 (DD Extended Retention systems), S = J * C = 720, D = 2 *720 / 128 = 11.25, round up to 12.

l As a result, all DFC groups on the Data Domain system must be configured with 12 devices.

Linux backup servers

The number of DFC devices advertised on the Data Domain system using the calculations listedunder On the Data Domain system on page 43 is sufficient for Linux backup servers. No additional



configuration is required. Linux backup servers are not queue-depth constrained, so manyconnections can share the same DFC generic SCSI device with no performance impact.

Windows backup servers

The Data Domain server path management logic spreads out connections across available logicalpaths (Initiator, Target Endpoint, DFC Device). Enough DFC devices must be configured so thateach connection uses its own generic SCSI device (logical path) on the backup server, with amaximum DFC device count of 64.

Let X be the number of DFC devices configured on the Data Domain system (from On the DataDomain system on page 43).

Let P be the number of physical paths between backup server and Data Domain system.

Let J be the maximum number of simultaneous jobs.

Let C be the maximum number of connections per job:

l 3 for DD Extended Retention systemsl 1 for other types of Data Domain systems

Calculate, assuming the following:

l 4 physical paths between the backup server and Data Domain system, 30 maximum jobs, DDExtended Retention system

l In this case, X = 25, P = 4, J = 30, and C = 3l Maximum simultaneous connections from backup server S = (J * C) = 90l DFC device count D = (90/4, 25) = 25

As a result, the Data Domain system should be configured to advertise 25 devices to each initiatoron the backup server.

Assume:

l 2 physical paths between the backup server and Data Domain system, 50 maximum jobs, singleData Domain system

l In this case, X=18, P = 2, J = 40, C = 1l Maximum simultaneous connections from backup server S = (J * C) = 40l DFC device count D = maximum(40/2, 18) = 20

As a result, the Data Domain system should be configured to advertise 20 devices to each initiatoron the backup server.

Because the value of D (20) is greater than the value of X (18), it is sufficient to configure twodevices only for the DFC access group with Windows clients.

AIX backup servers

For AIX, the proprietary device entries are exclusively locked on a per-process basis—one and onlyone process can use a device entry. Calculations are based on application instance usage. If anapplication spawns multiple processes, each process exclusively locks at least one device entry.Multi-threaded applications lock one device per thread. For these reasons, you should configurethe Data Domain system to advertise as many DFC devices as possible (up to the maximum of128). A Device Busy error can result if there are not enough devices accessible to the AIXclients.

Note: If you are using the proprietary device driver, the total number of streams in a policyshould not exceed the number of AIX DFC devices available; otherwise, the backup job mightfail.

Solaris backup servers

For Solaris, device entries are exclusively locked on a per-process basis—one and only oneprocess can use a device entry. Calculations are based on application instance usage. If an



application spawns multiple processes, each process exclusively locks at least one device entry.Multi-threaded applications lock one device per thread. For these reasons, configure the DataDomain system to advertise as many DFC devices as possible to avoid "in use" errors from thesgen device driver. A Device Busy error can result if there are not enough devices accessible tothe Solaris clients.

The number of sgen devices is the number of Fibre Channel ports accessible to the Solarisinstance times the number of different paths to the Data Domain system endpoints times thenumber of LUNs in the access group.

Configuring the SCSI device driver for AIX clientsDD Boost-over-FC is supported on clients that run the supported AIX versions on IBM Powerhardware. DFC for AIX uses the SCSI generic device driver, which is included in the AIXinstallation.

By default, the Oracle RMAN agent uses the SCSI generic device driver, which does not requirethe installation of any drivers.

To check for the SCSI generic device driver, you can run the lsdev command and review thecommand output. The command output for this device driver includes the device names ashdisk* and the type as Other FC SCSI Disk Drive. For example:

lsdev

hdisk1 Available 05-00-01 Other FC SCSI Disk Drivehdisk2 Available 05-00-01 Other FC SCSI Disk Drivehdisk3 Available 05-00-01 Other FC SCSI Disk Drive

Note: To discover the DD Boost devices that are added to the DD Boost FC group in DataDomain system, run the cfgmgr command on the client. You might need to run the cfgmgrcommand if the lsdev command cannot show all the devices.

To complete the configuration and integration of the device driver on an AIX system, perform thefollowing steps.

1. Follow the required instructions in the Data Domain Fibre Channel Configuration and Integrationwith Data Domain Boost for Enterprise Applications Database Application Agent Technical Notes.Follow the instructions on configuration of an AIX DFC setup without DFC drivers by addingdisk type devices. The document is available on the Support website at https://support.emc.com.

2. To ensure that the DBA can perform backup and restore operations as a non-root user, followthe configuration instructions in the section "AIX with SCSI generic disk driver" in thefollowing Knowledgebase article:

Fibre Channel Devices with Products using DD Boost in Linux/UNIX Environment (Article Number000182275)

The article is available on the Support website at https://support.emc.com.

Configuring the SCSI generic device driver for Solaris clientsAbout this task

DD Boost-over-FC is supported on clients that run Solaris 10 and 11 on SPARC and x86 hardware.DFC for Solaris uses the SCSI generic device driver (sgen), which is included in the Solarisinstallation. Use the following procedure to ensure that sgen successfully identifies the processordevices at startup.



HTTPS://SUPPORT.EMC.COM/



Procedure

1. Add the following line in the forceload section of /etc/system:

forceload: drv/sgen

This step should resolve issues with sgen not properly loading during startup and keep thesgen driver loaded.

2. To check for existing usage of sgen, run the command grep sgen /etc/driver_aliases.

Note: The existence of a /dev/scsi, /dev/scsi/processor, or /dev/scsi/*directory does not necessarily mean that sgen is currently configured. There could bedangling files.

3. If there is no existing use of sgen, or if sgen is used only for "scsiclass,03", perform thefollowing steps:

a. Run the command rem_drv sgen.

b. Run the command add_drv –m '* 0600 root sys' –i '"scsiclass,03"' sgen.

Note: It is critical that you use single and double quotes exactly as shown.

This command should return to the prompt with no errors or warnings. Checkconnectivity to the Data Domain system. There should be at least one file in /dev/scsi/processor.

c. To confirm at least one entry for three configuration files, run the command grepsgen /etc/minor_perm /etc/name_to_major and /etc/driver_aliases.

Example results of this command are as follows:

/etc/minor_perm:sgen * 0600 root sys/etc/name_to_major:sgen 151/etc/driver_aliases:sgen "scsiclass,03"

Note: The name_to_major number will likely be different than this example.

4. If the sgen device is already used for other devices, perform the following steps:

a. Run the command rem_drv sgen.

b. Run the command add_drv –m '* 0600 root sys' –i '"scsiclass,03""scsiclass,XX"' sgen.

Note: XX would be the device type from a previously run command grepsgen /etc/driver_aliases. It is critical that you use single and double quotesexactly as shown.

An example of this command is as follows: add_drv –m '* 0600 root sys' –i'"scsiclass,03" "scsiclass,06"' sgen.

This command should return to the prompt with no errors or warnings. Checkconnectivity to the Data Domain system. There should be at least one file in /dev/scsi/processor.

c. To confirm at least one entry for three configuration files, run the command grepsgen /etc/minor_perm /etc/name_to_major and /etc/driver_aliases.



d. Open the /kernel/drv/sgen.conf file. If the device-type-config-list isuncommented, add “processor” to the list to ensure that the driver is recognized. Forexample, if the device-type-config-list is uncommented as in this example:

device-type-config-list="direct", "sequential", "worm", "rodirect", "optical", "changer";

Change the entry to:

device-type-config-list="direct", "sequential", "worm", "rodirect", "optical", "changer", "processor";



CHAPTER 4

Configuring the Oracle RMAN Agent for Stand-alone Deployment

Note: This chapter applies only to configuration of stand-alone deployments on Data Domainsystems, not PowerProtect Data Manager or PowerProtect X400 systems.


l Installing and configuring the Oracle RMAN agent on AIX, Linux, and Solaris systems..........50l Installing and configuring the Oracle RMAN agent on Windows systems.............................. 58l Registering each Data Domain system.................................................................................. 62l Migrating an Oracle configuration from the database application agent................................69l Performing backups of a clustered environment to Data Domain...........................................74l Data Domain replication.........................................................................................................75l Specifying subdirectories for Oracle RMAN agent backups.................................................. 80l Performing backups and restores of Oracle CDBs and PDBs.................................................82l Performing DD Boost compressed restores...........................................................................83l Display and deletion of backups.............................................................................................83l Oracle Incremental Merge operations.................................................................................... 91l Configuring the use of Data Domain Cloud Tier for data movement to the cloud..................131l Usage limits on Data Domain resources................................................................................133


Installing and configuring the Oracle RMAN agent on AIX,Linux, and Solaris systems

Installing the Oracle RMAN agent on database serversInstall the Oracle RMAN agent on all the database servers that must access the Data Domainsystem.

The pre-4.0 versions of Oracle RMAN agent are installed under the ORACLE_HOME directory.Starting with Oracle RMAN agent version 4.0, the software must be installed in a directory otherthan the ORACLE_HOME directory.

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

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

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

To upgrade from a pre-4.0 version, use either of the following methods:

l Run the uninstallation script, uninstall.sh, to uninstall the pre-4.0 software and then installthe Oracle RMAN agent 19.3. Uninstalling the Oracle RMAN agent on database servers onpage 56 describes how to use the uninstallation script.

l Run the installation script to install the version 19.3 software and at the same time remove orupdate the pre-4.0 Oracle RMAN agent settings.

For an upgrade, if you want to continue using a pre-4.0 RMAN script without any changes, it isrecommended that you run the installer script for each ORACLE_HOME. If you do not want toreuse the RMAN script, run the installer script once and then modify the RMAN script for OracleRMAN agent 19.3.

You can run the install.sh script manually or automatically (silently). To enable the automaticoperation, you must set the environment variables as listed in Table 3 on page 51:

l When the variables are not set, the script runs manually and prompts you for the requiredvalues.

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

To perform an automatic (silent) upgrade to Oracle RMAN agent 19.3:

1. Run the following commands to set the required environment variables:

# export DD_CREDENTIALS_UPDATE=FALSE# export RMAN_AGENT_HOME=<$RMAN_AGENT_HOME># export RMAN_AGENT_INSTALL_OPTIONS=OVERWRITE

2. Run the install.sh script without any command-line options, as described in Installingthe Oracle RMAN agent on Linux and UNIX on page 52.

Note: ORACLE_HOME is an Oracle environment variable. The other variables are the OracleRMAN agent environment variables.



Table 3 Environment variables for installation or upgrade of Oracle RMAN agent

Environment variable Description Default and valid values

DD_CREDENTIALS_UPDATE Required for an automatic (silent)upgrade.

Specifies the type of upgrade, based onwhether the Oracle RMAN agent isintegrated with PowerProtect DataManager.

l Undefined (default).

l FALSE—Specifies an automaticupgrade when Oracle RMAN agent isnot integrated with PowerProtectData Manager.

l TRUE—Specifies an automaticupgrade when Oracle RMAN agent isintegrated with PowerProtect DataManager. In this case, you must runthe install.sh script with

appropriate command-line options,as described in the PowerProtectData Manager Administration and UserGuide.

ORACLE_HOME Required for an upgrade of pre-4.0Oracle RMAN agent.

Specifies the installation location of thepre-4.0 Oracle RMAN agent.


l Valid value of the ORACLE_HOMEdirectory under which the pre-4.0Oracle RMAN agent is installed.

RMAN_AGENT_HOME Required for an automatic (silent)upgrade.

Specifies the installation directory forthe Oracle RMAN agent 19.3.

l $HOME/opt/dpsapps/rmanagent(default).

l Valid complete pathname of thedirectory for the Oracle RMANagent 19.3 installation.

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

RMAN_AGENT_INSTALL_OPTIONS

Required only when Oracle RMAN agentalready exists in the installationdirectory.

Specifies whether to bypass the version19.3 installation or continue andoverwrite the existing installation.

Note: For an upgrade from version4.0 or later, set this variable to theOVERWRITE or overwrite value.


l BYPASS or bypass—Specifies tobypass the version 19.3 installation.

l OVERWRITE or overwrite—Specifies to continue the version19.3 installation and overwrite theexisting installation in the destinationdirectory.

RMAN_AGENT_UPGRADE_OPTIONS

Required only if a pre-4.0 Oracle RMANagent is installed.

Specifies whether to keep or remove thepre-4.0 installation, and whether toupdate the Oracle settings to enable thereuse of pre-4.0 RMAN scripts withoutany script changes.

Note: For an upgrade from thepre-4.0 agent, it is recommended


l KEEP or keep—Specifies to keepthe pre-4.0 installation.

l UNINSTALL or uninstall—Specifiesto uninstall the pre-4.0 installation.

l UPGRADE or upgrade—Specifies touninstall the pre-4.0 installation andalso update the Oracle settings sothat the pre-4.0 RMAN scripts can



Table 3 Environment variables for installation or upgrade of Oracle RMAN agent (continued)


that you set this variable to theUPGRADE or upgrade value.

be reused without any scriptchanges.

Perform the download and installation steps for the environment as described in the followingtopic.

Installing the Oracle RMAN agent on Linux and UNIXAbout this task

Procedure

1. Ensure that no backups are running. Stop the RMAN processes before you install the OracleRMAN agent.

Note: If you use AIX and you experience copy failures, you might need torun /usr/bin/slibclean as the root user after you stop the RMAN processes.

2. Download the Oracle RMAN agent as the software package for the operating system fromthe Support website at https://support.emc.com.

The following table shows the software package names for the supported operatingsystems.

Table 4 Software package names on UNIX and Linux

Operating system Software package name

AIX (64-bit) ddrman193_aixpower.tar

Linux x64 (64-bit) ddrman193_linux_x86_64.tar

Solaris AMD (64-bit) ddrman193_solaris_x86_64.tar

Solaris SPARC (64-bit) ddrman193_solaris64.tar

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

# chown -R oracle:oinstall <file_name>

Uncompress the downloaded tar file using the oracle user by running the followingcommand:

# tar -vxf <file_name>

4. If you want the installation script to run automatically, ensure that you set the multipleenvironment variables that are described in Installing the Oracle RMAN agent on databaseservers on page 50.

For example, you want to run an automatic installation that overwrites an existing OracleRMAN agent 19.3 in the default directory and uninstalls a pre-4.0 installation under




ORACLE_HOME without any prompts. In this case, run the following commands to set therequired environment variables before you run the installation script:

# export DD_CREDENTIALS_UPDATE=FALSE# export ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1/# export RMAN_AGENT_INSTALL_OPTIONS=overwrite# export RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent/# export RMAN_AGENT_UPGRADE_OPTIONS=uninstall

For an automatic upgrade from Oracle RMAN agent version 4.0 or later to version 19.3,ensure that you run the following commands:

# export DD_CREDENTIALS_UPDATE=FALSE# export RMAN_AGENT_HOME=<$RMAN_AGENT_HOME># export RMAN_AGENT_INSTALL_OPTIONS=OVERWRITE

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

# echo $RMAN_AGENT_HOME

/home/oracle/opt/dpsapps/rmanagent

5. As an Oracle user, run the install.sh script:

./install.sh

Note: When you set the required environment variables for an automatic (silent) installor upgrade, the install.sh script runs without displaying prompts. Otherwise, thescript displays specific prompts, described as follows.

If RMAN_AGENT_HOME is not set, the script displays the following prompt:

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

Type the appropriate value:

l To install to the default directory, type y.

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

The script prompts you to enter the installation directory pathname:

A directory outside of the ORACLE_HOME directory must have been created specifically for this installation. Enter the full pathname of the installation destination:

Type the pathname of an already created installation directory.

6. If a previous version of the Oracle RMAN agent is installed:

Note: The following prompts for detailed entries are displayed only when you do not runthe export command to set the environment variables as described in step 4.



a. The installer prompts for an existing Data Domain server and storage unit name:

As a PowerProtect Data Manager user, update the existing Data Domain details? (y or n) yData Domain server name: 10.31.140.205Data Domain storage unit name: rman

b. The installer prompts whether to uninstall pre-4.0 software. Type the appropriate value:

l To uninstall the pre-4.0 software, type y.

l To keep and use the pre-4.0 software, type n. You can later run the uninstallationscript if required to uninstall the pre-4.0 software, as described in Uninstalling theOracle RMAN agent on Linux and UNIX on page 57.

c. If you selected to uninstall pre-4.0 software in the preceding step, the installer promptswhether to update the Oracle settings under $ORACLE_HOME. The updated settings willenable the reuse of RMAN scripts from the previous version without any script changes.Type the appropriate value:

l To enable the reuse of the pre-4.0 RMAN scripts without script changes, type y.

l To prevent updates of the Oracle settings, type n. Then, to make any pre-4.0 RMANscript usable with the Oracle RMAN agent 19.3, you must change the following itemsin the script:

n Set SBT_LIBRARY to $RMAN_AGENT_HOME/lib/libddobk.so.

n Replace the ORACLE_HOME setting with the RMAN_AGENT_HOME setting.

The Oracle RMAN agent 19.3 files are installed in the following directories on a Linux orUNIX system.

Table 5 Product software components on Linux or UNIX

Software components Installation directory

DD Boost library files:

libddobk.so

libDDBoost.so

$RMAN_AGENT_HOME/lib

Configuration validation library file forPowerProtect integration (Linux only):

libddboravalidate.so


Lockbox library files on AIX, Linux, Solaris:

libLockbox.so

libEnshroud-OpenSSL.so

libcrypto.so.1.0.0

libddvdisk.so

libssl.so.1.0.0


Lockbox files:

ddboost.config

ddboost.config.bak

$RMAN_AGENT_HOME/configNote: If lockbox files exist that werecreated by a pre-4.0 installation and nonew lockbox files are created by the



Table 5 Product software components on Linux or UNIX (continued)


ddboost.config.FCD

ddboost.config.bak.FCD

version 19.3 software, the pre-4.0 lockboxfiles are upgraded to this location.

adm-agent-19.3.0.rpm (Linux only) $RMAN_AGENT_HOME/bin

ddbmcon (Linux only) $RMAN_AGENT_HOME/bin

ddbmoim binary (Linux only) $RMAN_AGENT_HOME/bin

ddbmoim log files (Linux only) $RMAN_AGENT_HOME/logs

ddutil binary $RMAN_AGENT_HOME/bin

ddutil log files $RMAN_AGENT_HOME/logs

rman_agent.cfg (Linux only)

rman_agent_oim.cfg (Linux only)

rman_options.cfg (Linux only)

$RMAN_AGENT_HOME/config

rman_agent_home.cfgNote: This configuration file is createdduring an update from a pre-4.0installation.

$ORACLE_HOME/config

Installation and configuration examples on page 170 provides examples.

7. After the software installation, if you want to use an existing lockbox in a non-defaultdirectory, upgrade the lockbox through either of the following procedures:

l Run the following ddutil -U command to upgrade the lockbox and then copy theexisting lockbox files to the default directory, $RMAN_AGENT_HOME/config. Thecommand must include the complete pathname of the non-default directory. Forexample:

ddutil -U -a LOCKBOX_IMPORT=TRUE -a LOCKBOX_PATH=<non-default_lockbox_directory_pathname>cp <non-default_lockbox_directory_pathname>/ddboost.config* $RMAN_AGENT_HOME/config

l Copy the existing lockbox files from the non-default directory to the default directory,$RMAN_AGENT_HOME/config, and then run the following ddutil -U command toupgrade the lockbox:

ddutil -U -a LOCKBOX_IMPORT=TRUE

NOTICE If you do not run the appropriate ddutil -U command to upgrade the existinglockbox, any subsequent backup, restore, and query operations will fail with an errormessage.



Uninstalling the Oracle RMAN agent on database serversRun the uninstall.sh script to uninstall the Oracle RMAN agent 19.3. You can also run thescript to uninstall a previous version of the Oracle RMAN agent.

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

You can run the uninstall.sh script manually or automatically. To enable the automaticoperation, you must set the appropriate environment variables as listed in Table 6 on page 56:

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

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

Note: ORACLE_HOME is an Oracle environment variable. The other variables are the OracleRMAN agent environment variables.

Table 6 Environment variables for uninstallation of Oracle RMAN agent


ORACLE_HOME Specifies the installation location of apre-4.0 Oracle RMAN agent.


l Valid value of the ORACLE_HOMEdirectory under which the pre-4.0Oracle RMAN agent is installed.

RMAN_AGENT_HOME Specifies the installation directory forthe Oracle RMAN agent 4.0 or later.

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

l Valid complete pathname of thedirectory for installation of OracleRMAN agent 4.0 or later.

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

RMAN_AGENT_UNINSTALL_OPTIONS

Required only for an uninstallation ofOracle RMAN agent 4.0 or later.Specifies the software components touninstall.


l NONE or none—Specifies to keepthe version 4.0 or later software,and not perform the uninstallation.

l BINARY or binary—Specifies touninstall the version 4.0 or latersoftware, but not the lockbox.

l FULL or full—Specifies to uninstallboth the version 4.0 or latersoftware and the lockbox.

RMAN_AGENT_UNINSTALL_PRE40_OPTIONS

Required only for an uninstallation ofpre-4.0 Oracle RMAN agent software.Specifies the components to uninstall forthe pre-4.0 software.


l NONE or none—Specifies to keepthe pre-4.0 software, and notperform the uninstallation.

l BINARY or binary—Specifies touninstall the pre-4.0 software, butnot the lockbox.



Table 6 Environment variables for uninstallation of Oracle RMAN agent (continued)


l FULL or full—Specifies to uninstallboth the pre-4.0 software and thelockbox.

Perform the uninstallation steps as described in the following topic.

Uninstalling the Oracle RMAN agent on Linux and UNIXAbout this task

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

Procedure

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

2. If you want the uninstallation script to run automatically, ensure that the requiredenvironment variables are set as described in Uninstalling the Oracle RMAN agent ondatabase servers on page 56. To verify the value of an environment variable, run the echocommand. For example:

# echo $RMAN_AGENT_HOME

/home/oracle/opt/dpsapps/rmanagent

To set the RMAN_AGENT_HOME environment variable, run the export command. Forexample:

# export RMAN_AGENT_HOME=/opt/dpsapps/rmanagent

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

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

# ./uninstall.sh

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

When prompted for a directory pathname for the uninstallation, you can specify thepathname of the Oracle RMAN agent that is installed. Type the complete pathname withouta slash (/) at the end.

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

Configuring the software on Linux and UNIX systemsFrom within RMAN, configure a channel.



Note:The storage unit specified in the following command must already exist on the Data Domainsystem.

The same storage unit must be used for both manual and scheduled backups. The latestPowerProtect Data Manager or PowerProtect X400 documentation provides details on how toset up and perform scheduled backups.

The following example shows the command syntax for configuring a channel in a Linux or UNIXenvironment.

RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' TRACE <trace-level> PARMS 'BLKSIZE=1048576, SBT_LIBRARY=<path-to-$RMAN_AGENT_HOME>/lib/libddobk.so, ENV=(STORAGE_UNIT=<storage-unit-on-Data-Domain-system>, BACKUP_HOST=<hostname-of-Data-Domain-system>, RMAN_AGENT_HOME=<path-to-$RMAN_AGENT_HOME>)';

The configuration that you specify is also displayed in the Media Management Settings field ofOracle Enterprise Manager (OEM).

Installing and configuring the Oracle RMAN agent on Windowssystems

Installing the Oracle RMAN agent on database serversInstall the Oracle RMAN agent on all the database servers that must access the Data Domainsystem. The installation can be performed by an administrator or an Oracle user.

The pre-4.0 versions of Oracle RMAN agent are installed under the ORACLE_HOME directory.Starting with Oracle RMAN agent version 4.0, the software must be installed in a directory otherthan the ORACLE_HOME directory.

Before you install the Oracle RMAN agent, ensure that all the Oracle and RMAN processes arestopped and no RMAN backup or restore processes are running.

During an upgrade of a preexisting Windows Oracle RMAN agent, the installation might fail unlessall the Oracle instances are stopped. Stop all the Oracle instances before you perform a Windowsinstallation.

The user that performs the Oracle RMAN agent installation must have permissions to install theMicrosoft Installer (MSI) technology binaries. If the local users do not have such permissions, theadministrator must perform the installation on behalf of the local users.

For each user that performs the installation, a set of Oracle RMAN agent files is installed. Bydefault, the software files are installed under the user profile directory. If you want a single copy ofthe software files to be installed per computer, specify a non-default shared directory for theinstallation and manually set the appropriate read and write permissions on the directory.

An installation of the Oracle RMAN agent requires at least 50 MB of available disk space in theinstallation user profile directory.

Perform the download and installation steps for the environment as described in the followingtopic.



Installing the Oracle RMAN agent on Windows systemsAbout this task

Note: During an upgrade of Oracle RMAN agent on Windows, you do not need to uninstall theprevious-version software. An existing Oracle RMAN agent is overwritten during an upgrade.

Procedure

1. Download the Oracle RMAN agent as the Windows software package from the Supportwebsite at https://support.emc.com/.

The Windows software package name is ddrman193_ntx64.zip.

2. Install the Oracle RMAN agent by using either of the following methods:

l Interactive method with the installation wizard:

a. Double-click Oracle RMAN agent.exe to launch the installation wizard.

The Welcome to the Setup Wizard page appears.

Note: Run only one instance of the installation wizard at a time. If you try to runmore than one instance, the wizard operation terminates with an error.

b. Read the terms of the Software License and Support Services Agreement, select IAgree, and then click Next to continue.

c. The Change Install Location page displays the default destination directory for theinstallation as %LOCALAPPDATA%\RMANAgent, for example, C:\Users\Administrator\AppData\Local\RMANAgent. The Oracle RMAN agentcomponents will be installed in subdirectories in this destination directory.

Accept or change the installation directory:

n To accept the displayed directory for the installation, click Install.

n To change the displayed directory, click Change and browse to select a differentdirectory. When the correct directory is displayed, click Install.

d. If any previous versions of Oracle RMAN agent are installed, an Upgrade Optionspage displays a list of the previous installations. Select to keep or remove theprevious installations as required:

n To uninstall all the previous installations, select Remove all the previous OracleRMAN agent installations.

n To copy the pre-4.0 lockbox files from one of the displayed installations to the%RMAN_AGENT_HOME%\config directory:

– Select Copy a legacy lockbox into the new installation directory (selectonly one item).

– Select only one of the displayed pre-4.0 installations in the list.

Note: The uninstallation of previous versions is irreversible. Pre-4.0 lockboxfiles are not removed by the version 19.3 installation.

When you have completed the selections on the Upgrade Options page, click Installand respond to any displayed prompts.

Note: The upgrade of Oracle RMAN agent from a previous version includes anautomatic upgrade of the lockbox.

e. The Installation Progress window displays a progress bar. To cancel the installationat any time, click Cancel.



https://support.emc.com/

f. When the installation completes, the Complete the Setup window displaysinformation about the log, any errors, and the software installation status. ClickFinish to exit the wizard.

l Silent installation method:

Run the Oracle RMAN agent.exe command with the appropriate command options:

Oracle RMAN agent.exe <installation_options>

where <installation_options> includes the following options:

n /s /qn are the only mandatory options, to suppress the GUI output. Without theseoptions, the Windows installer GUI is launched to perform the installation.

n ProductInstallPath <pathname> specifies the installation directory for theOracle RMAN agent files. Enclose <pathname> in double quotes if it includes a space.The default directory is %LOCALAPPDATA%\RMANAgent, for example, C:\Users\Administrator\AppData\Local\RMANAgent. Use this option to specify a non-default installation directory.

n RemoveOldVersions=1 specifies to uninstall all pre-4.0 versions of Oracle RMANagent that are installed on the Windows system. The uninstallation is irreversible, anddoes not display any prompts for confirmation.

n CopyLockboxBinaries <pathname> specifies to copy the pre-4.0 lockbox filesfrom the <pathname> directory to the %RMAN_AGENT_HOME%\config directory.The Oracle RMAN 19.3 installation directory is %RMAN_AGENT_HOME%.

Note: You can use the CopyLockboxBinaries option only whenRemoveOldVersions=1 appears in the same command. The command can copythe lockbox files from only one pre-4.0 directory. Pre-4.0 lockbox files are notremoved by a version 19.3 installation.

For example, the following command silently installs the Oracle RMAN agent 19.3software in the directory C:\Program Files\RMANAgent, and uninstalls all pre-4.0versions of the software. The command also copies the pre-4.0 lockbox files fromC:\app\oracle\product\12.1.0\dbhome_2\config to %RMAN_AGENT_HOME%\config:

"Oracle RMAN agent.exe" /s /qn ProductInstallPath="C:\Program Files\RMANAgent" RemoveOldVersions=1 CopyLockboxBinaries="C:\app\oracle\product\12.1.0\dbhome_2"

Note: The upgrade of Oracle RMAN agent from a previous version includes anautomatic upgrade of the lockbox.

The Oracle RMAN agent 19.3 files are installed in the following directories on a Windowssystem.

Table 7 Product software components on Windows


DD Boost library files:

libddobk.dll

libDDBoost.dll

%RMAN_AGENT_HOME%\BIN



Table 7 Product software components on Windows (continued)


libDataDomainoncrpc.dll

libDataDomainpthread.dll

Lockbox library files:

Lockbox.dll

Enshroud-OpenSSL.dll

%RMAN_AGENT_HOME%\cst

Other library files:

msvcr80.dll

msvcr100.dll

%RMAN_AGENT_HOME%\BIN

Lockbox files:

ddboost.config

ddboost.config.bak

ddboost.config.FCD

ddboost.config.bak.FCD

%RMAN_AGENT_HOME%\config

ddutil.exe binary %RMAN_AGENT_HOME%\BIN

ddutil.exe log files %RMAN_AGENT_HOME%\logs

3. After the software installation, if you want to use an existing lockbox in a non-defaultdirectory, upgrade the lockbox through either of the following procedures:

l Run the following ddutil -U command to upgrade the lockbox and then copy theexisting lockbox files to the default directory, %RMAN_AGENT_HOME%\config. Thecommand must include the complete pathname of the non-default directory. Forexample:

ddutil -U -a LOCKBOX_IMPORT=TRUE -a LOCKBOX_PATH=<non-default_lockbox_directory_pathname>cp <non-default_lockbox_directory_pathname>\ddboost.config* %RMAN_AGENT_HOME%\config

l Copy the existing lockbox files from the non-default directory to the default directory,%RMAN_AGENT_HOME%\config, and then run the following ddutil -U command toupgrade the lockbox:


NOTICE If you do not run the appropriate ddutil -U command to upgrade the existinglockbox, any subsequent backup, restore, and query operations will fail with an errormessage.



Uninstalling the Oracle RMAN agent on Windows systemsAbout this task

Note: During an upgrade of Oracle RMAN agent on Windows, you do not need to uninstall theprevious-version software. An existing Oracle RMAN agent is overwritten during an upgrade.

Procedure

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

2. Uninstall the Oracle RMAN agent by using the uninstall/change program feature in theWindows Control Panel, as used to uninstall a typical Windows program. Be careful to selectand uninstall the correct item for the Oracle RMAN agent.

Open the Windows Control Panel, and then select Program and Features.

3. In the Uninstall or change a program window, select Oracle RMAN agent and then clickUninstall.

4. In the Install Modification window, select the Remove radio button and then click Remove.

Note: The Change option is not supported for the Oracle RMAN agent. The Repairoption can be selected to restore the installation to its original state without affectingany user-generated files or configuration files.

The Uninstallation Progress window displays a progress bar. The software files areuninstalled without removing any user-generated files or configuration files.

5. When the uninstallation completes, the Complete the Setup window displays informationabout the log, any errors, and the software uninstallation status. Click Finish to exit thewizard.

Configuring the software on Windows systemsFrom within RMAN, configure a channel.

Note: The storage unit specified in the following command must already exist on the DataDomain system.

The following example shows the Oracle RMAN command syntax for configuring a channel in aWindows environment:

RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' TRACE <trace-level> PARMS 'BLKSIZE=1048576, SBT_LIBRARY=<path-to-%RMAN_AGENT_HOME%>\bin\libDDobk.dll, ENV=(STORAGE_UNIT=<storage-unit-on-Data-Domain-system>, BACKUP_HOST=<hostname-of-Data-Domain-system>, RMAN_AGENT_HOME=<path-to-%RMAN_AGENT_HOME%>)';

The configuration that you specify is also displayed in the Media Management Settings field ofOracle Enterprise Manager (OEM).

Registering each Data Domain systemNote: The registration step is not required when you deploy the Oracle RMAN agent withPowerProtect Data Manager or PowerProtect X400 because those systems automaticallycomplete the Data Domain registration to the agents. The manual registration step is only



required when you restore from an alternate host that is not part of the same PowerProtectprotection policies.

To connect to a Data Domain system, you must first register the Data Domain system with theOracle RMAN agent. This registration provides the Oracle RMAN agent with the necessaryusername and password for connecting to the Data Domain system. The Oracle RMAN agentstores the username and password securely in an encrypted lockbox file and retrieves the valueswhen connecting to a Data Domain system.

Note: The Oracle RMAN agent 19.3 introduced support for using multiple storage units perData Domain system associated with the same Oracle database host. To use more than onestorage unit with the same Oracle host and Data Domain system, you must register theusername and password for each storage unit separately.

When a Data Domain system is registered for the first time, the encrypted lockbox file is created inthe $RMAN_AGENT_HOME/config directory (Linux or UNIX) or in the %RMAN_AGENT_HOME%\config directory (Windows). For security purposes, the lockbox file is typically created so thatit can only be accessed by the host system that creates it. If another host system tries to accessthe lockbox, the access is denied. This prevents other systems from connecting to the DataDomain system. Typically, these other systems have their own Oracle instance and Oracle homedirectory with RMAN installed and therefore will have their own lockbox file.

NOTICE By default, the lockbox file on UNIX and Linux is created with the rw-rw----permissions, so that the file owner and group user can read from the file and write to the file.To implement a higher security level on the lockbox file, you can change the file permissions torw-r-----, so that group users cannot write to the lockbox file. Run the chmod g-wddboost.config command to change the permissions.

In a typical case, a single Oracle host system is in use, or multiple host systems exist and each hasits own Oracle instance and its own Oracle home directory. In this typical case, register the DataDomain systems as described in Registering a standard Data Domain system on page 63. Eachclient system has its own lockbox file, accessible only to that system.

When a Data Domain system has DD Boost over Fibre Channel, register the Data Domain systemas described in Registering a Data Domain system with DD Boost over Fibre Channel on page 65.

In some cases, such as in an Oracle RAC environment, multiple system nodes share an Oraclehome directory and thus share a lockbox file. In these cases, create a lockbox file that can beaccessed by multiple systems as described in Registering a Data Domain system for sharedlockbox access on page 67.

Registering a standard Data Domain system

Note: The registration step is not required when you deploy the Oracle RMAN agent withPowerProtect Data Manager or PowerProtect X400 because those systems automaticallycomplete the Data Domain registration to the agents. The manual registration step is onlyrequired when you restore from an alternate host that is not part of the same PowerProtectprotection policies.

Register each standard Data Domain system by using the ddutil command with the -C option orby using an RMAN command within a script. Use the instructions in one of the following subtopics:

l Using a ddutil -C command to register a standard Data Domain system on page 64

l Using an RMAN command to register a standard Data Domain system on page 65

After you register a Data Domain system in the lockbox, you can perform backups and restoreswith the Data Domain system by using 'device type sbt_tape'. If you want all the backups



to go to the Data Domain system, configure SBT_TAPE as the default device by using thefollowing command:

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

Using a ddutil -C command to register a standard Data Domain system

To register a Data Domain system so that RMAN can connect to it for backup operations, you canuse the ddutil command with the -C option. This registration task is required only once for eachseparate storage unit to be used on the same Data Domain system. Do not run the registrationcommand for each backup. Perform the registration before you perform any backups.

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

The -C option has four optional -a arguments, DD_SERVER_NAME, DD_STORAGE_UNIT,USERNAME, and VERIFY_CREDENTIAL. To register a Data Domain system, run the ddutil -Ccommand for each storage unit to be used on the Data Domain system and enter the promptedvalues:

l When you omit the -a arguments, the command prompts for the Data Domain server name,storage unit name, DD Boost username, and password:

ddutil -C

Data Domain server name: <server_name>Data Domain Storage Unit name: <storage_unit_name>DD Boost username: <username>Password: <password>Re-enter password: <password>Successfully set the DD Boost credentials in the lockbox.

l When you include the -a arguments, the command prompts only for the password:

ddutil -C -a DD_SERVER_NAME=<server_name> -a DD_STORAGE_UNIT=<storage_unit_name> -a USERNAME=<username> -a VERIFY_CREDENTIAL=TRUE

Password: <password>Re-enter password: <password>

When you specify the -a VERIFY_CREDENTIAL=TRUE argument, the ddutil commandverifies the DD Boost user credential with the specified Data Domain server before saving thecredential in the lockbox. If the credential verification fails, the command prints an error message,stating that it cannot connect to the Data Domain system, and does not save the credential. Whenyou do not specify the -a VERIFY_CREDENTIAL=TRUE argument, the program saves the DDBoost user credential directly in the lockbox without performing any credential verification.

Ensure that you specify the correct values in the command and at the prompts:

l The <server_name> value is the name of the Data Domain server exactly as specified by theBACKUP_HOST value in the CONFIGURE CHANNEL command. The <server_name> value iscase-sensitive, and the same form of the name must be specified with the ddutil -Ccommand as with the CONFIGURE CHANNEL command.

For example, if server1.domain.com was used when configuring the channel, you must also useserver1.domain.com here. Do not use SERVER1.domain.com or server1. An IP address can beused, if that same IP address was used in the CONFIGURE CHANNEL command. You canregister multiple forms of the server name. For example, you can register both server1 andserver1.domain.com and use either of those names in CONFIGURE CHANNEL commands.



l The <storage_unit_name> value is the name of a storage unit on the Data Domain server thatwill be used for backup operations with the Oracle RMAN agent.

l The <username> value is the DD Boost username that you set with the user add commandand ddboost user assign command when you enable DD Boost on the Data Domainsystem. The username is case-sensitive, and must match exactly the value set on the DataDomain system.

l The <password> value is the password that you set up with the DD OS CLI user commandwhen you enable DD Boost on the Data Domain system. The password is case-sensitive, andmust match exactly the value set on the Data Domain system.

Using an RMAN command to register a standard Data Domain system

To register a Data Domain system so that RMAN can connect to it for backup operations, you canuse an RMAN command as shown in the following example. Edit the command for yourenvironment. This registration task is required only once for each separate storage unit to be usedon the same Data Domain system. Do not include the registration command in each backup script.Perform the registration before you perform any backups.

RUN {ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE' TRACE 5 PARMS 'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(BACKUP_HOST=bu-ddbea-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';send 'set username q_ost password 1X3quest servernamebu-ddbea-lin-16.lss.emc.com storageunit rman_cloud';RELEASE CHANNEL C1;}

Ensure that you specify the correct values in the RMAN command:

l The username is the DD Boost username that you set with the user add command andddboost user assign command when you enable DD Boost on the Data Domain system.The username is case-sensitive, and must match exactly the value set on the Data Domainsystem.

l The password is the password that you set up with the DD OS CLI user command when youenable DD Boost on the Data Domain system. The password is case-sensitive, and must matchexactly the value set on the Data Domain system.

l The servername value is the name of the Data Domain server exactly as specified by theBACKUP_HOST value in the CONFIGURE CHANNEL command. The servername value is case-sensitive, and the same form of the name must be used in this command as in the CONFIGURECHANNEL command.

For example, if server1.domain.com was used when configuring the channel, you must also useserver1.domain.com here. Do not use SERVER1.domain.com or server1. An IP address can beused, if that same IP address was used in the CONFIGURE CHANNEL command. You canregister multiple forms of the server name. For example, you can register both server1 andserver1.domain.com and use either of those names in CONFIGURE CHANNEL commands.

l The storageunit value is the name of a storage unit on the Data Domain server that will beused for backup operations with the Oracle RMAN agent.

Registering a Data Domain system with DD Boost over Fibre Channel

Note: This registration topic does not apply to PowerProtect Data Manager or PowerProtectX400 deployments.

Registering a Data Domain system with DD Boost over Fibre Channel is almost the same asregistering a standard Data Domain system, but with one important difference. For the DataDomain server name, you must specify the configured Fibre Channel server name.



Register each Data Domain system with DD Boost over Fibre Channel by using the ddutilcommand with the -C option or by using an RMAN command within a script. Use the instructionsin one of the following subtopics:

l Using a ddutil -C command to register a Data Domain system with DD Boost over FibreChannel on page 66

l Using an RMAN command to register a Data Domain system with DD Boost over Fibre Channelon page 67

Specify the configured Fibre Channel server name for the BACKUP_HOST parameter:

RUN {CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'BLKSIZE=1048576, SBT_LIBRARY=/home/oracle1/ddboost_home/lib/libddobk.so,ENV=(STORAGE_UNIT=<storage_unit>,BACKUP_HOST=<DFC_server_name>,RMAN_AGENT_HOME=/home/oracle1/ddboost_home)' FORMAT '%d_%U_%t';}

After you register a Data Domain system in the lockbox, you can perform backups and restoreswith the Data Domain system by using 'device type sbt_tape'. If you want all the backupsto go to the Data Domain system, configure SBT_TAPE as the default device by using thefollowing command:

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

Using a ddutil -C command to register a Data Domain system with DD Boost over FibreChannel

To register a Data Domain system with DD Boost over Fibre Channel, you can specify the FibreChannel server name in the ddutil -C command or when prompted by the command. Using addutil -C command to register a standard Data Domain system on page 64 provides moreinformation about running the ddutil -C command.

For example, you can specify the Fibre Channel server name with the -aDD_SERVER_NAME=<DFC_server_name> argument in the command:

ddutil -C -a DD_SERVER_NAME=<DFC_server_name> -a DD_STORAGE_UNIT=<storage_unit_name> -a USERNAME=<DD_Boost_username> -a VERIFY_CREDENTIAL=TRUE

Password: <password>Re-enter password: <password>

The <DFC_server_name> value is the Fibre Channel server name exactly as specified by theBACKUP_HOST value in the CONFIGURE CHANNEL command. The <DFC_server_name> value iscase-sensitive, and the same form of the name must be specified with the ddutil -C commandas with the CONFIGURE CHANNEL command.

For example, run the following command to determine the Fibre Channel server name:

ddboost fc dfc-server-name show

DDBoost dfc-server-name: ddavamarfourConfigure clients to use "DFC-ddavamarfour" for DDBoost FC.



Then, to register the Data Domain system with DD Boost over Fibre Channel, run the followingcommand with the Fibre Channel server name in the proper form, preceded by DFC-:

ddutil -C -a DD_SERVER_NAME=DFC-ddavamarfour -a DD_STORAGE_UNIT=<storage_unit_name> -a USERNAME=<DD_Boost_username> -a VERIFY_CREDENTIAL=TRUE

Using an RMAN command to register a Data Domain system with DD Boost over FibreChannel

To register a Data Domain system with DD Boost over Fibre Channel, you can specify the FibreChannel server name in the RMAN send command in the RMAN script. The registration task isrequired once for each separate storage unit to be used on the same Data Domain system. Forexample:

RUN {ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE' TRACE 5 PARMS 'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(BACKUP_HOST=bu-dfc-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';send 'set username q_ost password 1X3quest servernamebu-dfc-lin-16.lss.emc.com storageunit rman_cloud';RELEASE CHANNEL C1;}

The servername value is the Fibre Channel server name exactly as specified by theBACKUP_HOST value in the CONFIGURE CHANNEL command. The Fibre Channel server name iscase-sensitive, and the same form of the name must be specified in the RMAN script as in theCONFIGURE CHANNEL command.

Registering a Data Domain system for shared lockbox access

Note: This registration step is not required when you deploy the Oracle RMAN agent withPowerProtect Data Manager or PowerProtect X400 because those systems automaticallycomplete the Data Domain registration to all the nodes in the cluster.

In some cases, such as in an Oracle RAC environment, multiple system nodes share an Oraclehome directory and thus share a lockbox file. In these cases, it is necessary to create a lockbox filethat can be accessed by multiple systems.

If multiple database host systems must use the same lockbox file, the procedure for creating thelockbox file includes an additional step. This step is required so that host database systems otherthan the one that created the lockbox can also access the lockbox. Perform this step before anyData Domain systems are registered. After this step is performed, each Data Domain system canbe registered.

Users of RMAN versions prior to RMAN 1.2 who want to share lockbox files among multiple clientsystems must delete the existing lockbox files and create new lockbox files by using RMAN 1.2 andthe instructions in this topic. It is not possible to upgrade a lockbox that was created with earlierversions of RMAN so that it can be accessed by multiple client database systems.

Note: A lockbox file created with RMAN 1.0 or 1.1 continues to work with RMAN 1.2 whenaccessed from the client database system that created it. It is not necessary to modify thelockbox file.

Register a Data Domain system for shared lockbox access by using the ddutil command with the-H option or by using an RMAN command within a script. Use the instructions in one of thefollowing subtopics:



l Using a ddutil -H command to register a Data Domain system for shared lockbox access onpage 68

l Using an RMAN command to register a Data Domain system for shared lockbox access on page68

Using a ddutil -H command to register a Data Domain system for shared lockbox access

The following ddutil -H command specifies all the hosts that must access the lockbox file:

ddutil -H "hostnames <hostname-1> <hostname-2> ... <hostname-n>"

When you run this command to create the lockbox, all the hosts that you specify in the commandare given access to the lockbox.

You run the ddutil -H command only once, to create the lockbox. All the hosts that shareaccess to the lockbox must be specified in a single ddutil -H command. It is not possible togrant additional hosts access to the lockbox later. In that case, you must delete the existinglockbox file and then create a new lockbox file with all the hostnames.

Run the ddutil -H command before you run the registration command. All the hosts that willaccess the shared lockbox file must be listed in the <hostname-1> ... <hostname-n> list. Specifyeach <hostname> value as a fully qualified hostname, for example, test1.datadomain.com.

For example, the following command creates a lockbox that can be shared by three database clienthost systems:

ddutil -H "hostnames dbclient1.datadomain.com dbclient2.datadomain.com dbclient3.datadomain.com"

When the Oracle RMAN agent receives the ddutil -H command, the Oracle RMAN agentchecks if a lockbox file already exists. If so, an error is reported, and a message (logged in theRMAN trace file) reports this and instructs the user to delete the lockbox file if preferred andrepeat the command. The Oracle RMAN agent does not delete an existing lockbox file.

If no lockbox file exists, the Oracle RMAN agent creates a lockbox file, and all the specified hostsare granted access to the new lockbox. The lockbox can then be used and shared by all thesehosts. Next, register each Data Domain system that these hosts will access. You can registeradditional Data Domain systems at any time after the lockbox is created. Register each DataDomain system as described in Registering a standard Data Domain system on page 63. Becauseall the specified hosts have access to the lockbox, you can register the Data Domain systems onany of the listed host systems. Each Data Domain system must be registered only once.

It is not possible to add additional hostnames after the ddutil -H command has been run. Theonly way to add additional hostnames is to delete the current lockbox file and then re-create thefile by running the ddutil -H command again, this time with all the required hostnames.However, the lockbox contents are lost, and all the Data Domain systems must be re-registered.

Using an RMAN command to register a Data Domain system for shared lockbox access

The RMAN hostnames command specifies all the hosts that must access the lockbox file. Whenyou run the hostnames command to create the lockbox, all the hosts that you specify in thecommand are given access to the lockbox.

You run the hostnames command only once, to create the lockbox. All the hosts that shareaccess to the lockbox must be specified in a single hostnames command. It is not possible togrant additional hosts access to the lockbox later. In that case, you must delete the existinglockbox file and then create a new lockbox file with all the hostnames.



The hostnames command format is as follows:

RUN { ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS 'SBT_LIBRARY=<path-to-$RMAN_AGENT_HOME>/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=<path-to-$RMAN_AGENT_HOME>)'; send 'hostnames <hostname-1> <hostname-2> ... <hostname-n>'; RELEASE CHANNEL C1; }

Run this command as the first RMAN command, before the registration command. All the hoststhat will access the shared lockbox file must be listed in the <hostname-1> ... <hostname-n> list.Specify each <hostname> value as a fully qualified hostname, for example, test1.datadomain.com.

For example, the following RMAN command creates a lockbox that can be shared by threedatabase client host systems:

RUN { ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS 'SBT_LIBRARY=<path-to-$RMAN_AGENT_HOME>/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=<path-to-$RMAN_AGENT_HOME>)'; send 'hostnames dbclient1.datadomain.com dbclient2.datadomain.com dbclient3.datadomain.com'; RELEASE CHANNEL C1; }

When the Oracle RMAN agent receives the hostnames command, the Oracle RMAN agentchecks if a lockbox file already exists. If so, an error is reported, and a message (logged in theRMAN trace file) reports this and instructs the user to delete the lockbox file if preferred andrepeat the command. The Oracle RMAN agent does not delete an existing lockbox file.

If no lockbox file exists, the Oracle RMAN agent creates a lockbox file, and all the specified hostsare granted access to the new lockbox. The lockbox can then be used and shared by all thesehosts. Next, register each Data Domain system that these hosts will access. You can registeradditional Data Domain systems at any time after the lockbox is created. Register each DataDomain system as described in Registering a standard Data Domain system on page 63. Becauseall the specified hosts have access to the lockbox, you can register the Data Domain systems onany of the listed host systems. Each Data Domain system must be registered only once.

It is not possible to add additional hostnames after the hostnames command has been run. Theonly way to add additional hostnames is to delete the current lockbox file and then re-create thefile by running the hostnames command again, this time with all the required hostnames.However, the lockbox contents are lost, and all the Data Domain systems must be re-registered.

Migrating an Oracle configuration from the databaseapplication agent

Complete the following steps to migrate an Oracle configuration from the database applicationagent on the Oracle database server host to the Oracle RMAN agent.

Procedure

1. Discontinue all the Oracle backups that are performed with the database application agent.

2. Install the Oracle RMAN agent according to the appropriate instructions:

l Installing and configuring the Oracle RMAN agent on AIX, Linux, and Solaris systems onpage 50

l Installing and configuring the Oracle RMAN agent on Windows systems on page 58



Note: The Oracle RMAN agent installation does not modify any of the databaseapplication agent files on the same system.

3. Create the required lockbox for the Oracle RMAN agent operations by using the appropriateddutil -C command as described in Registering each Data Domain system on page 62.

4. Update the RMAN scripts as described in Updating the RMAN scripts for Oracle RMANagent operations on page 70.

5. Use the correct type of RMAN script for restore, crosscheck, and delete operations asdescribed in Using the correct RMAN script for restore, crosscheck, and delete operationson page 72.

Note: You must allocate channels for both the database application agent and OracleRMAN agent, for the restore, crosscheck, and delete operations on any unexpiredOracle backups that were previously performed with the database application agent.You can maintain the database application agent software on the Oracle database serverhost as long as needed.

6. To enable the cloud tier operations with the Oracle RMAN agent, update the required datamovement policies as described in Updating the data movement policy for cloud tieroperations on page 73.

Updating the RMAN scripts for Oracle RMAN agent operationsTo restore the Oracle backups that were performed with the Oracle RMAN agent, you must use anRMAN script created for these restores, not an RMAN script created for the database applicationagent for Oracle restores.

The RMAN scripts used for database application agent operations will not work for Oracle RMANagent operations because the scripts refer to the database application agent SBT library and donot include the required parameter settings. You must update the RMAN scripts for the OracleRMAN agent operations.

For example, the following RMAN command includes the correct SBT_LIBRARY setting for theOracle RMAN agent:

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS 'BLKSIZE=1048576,SBT_LIBRARY=libddobk.so, ENV=(STORAGE_UNIT=rman_su, BACKUP_HOST=blrv071a091.lss.emc.com,RMAN_AGENT_HOME=/opt/dpsapps/rmanagent/)';

As described in Using the correct RMAN script for restore, crosscheck, and delete operations onpage 72, you must allocate channels for both the database application agent and Oracle RMANagent, for the restore, crosscheck, and delete operations on any unexpired Oracle backups thatwere previously performed with the database application agent. You can maintain the databaseapplication agent software on the Oracle database server host as long as needed.

The following topics provide details about performing backups with the Oracle RMAN agent:

l Specifying subdirectories for Oracle RMAN agent backups on page 80

l Oracle RMAN agent channel configuration and backup on page 172

Identifying the types of backups

To ensure that you update the RMAN scripts properly for operations with the correct agent,identify whether the backups were performed with the database application agent or the OracleRMAN agent. To determine which agent performed the backups, you can run either the RMANcommand LIST BACKUP or the RMAN command RESTORE...PREVIEW:



l In the LIST BACKUP command output, the database application agent backups are indicatedby a media handle (after the label Media:) as either Database Application Agent/<storage_unit> or (for database application agent 2.5) database app agent/<storage_unit>. The Oracle RMAN agent backups are indicated by a media handle of only<device_path>.

For example, the following output from the LIST BACKUP command shows the two types ofmedia handles:

RMAN>LIST BACKUP;…BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------34 Full 670.00M SBT_TAPE 00:00:04 13-FEB-19 BP Key: 27 Status: AVAILABLE Compressed: NO Tag: TAG20190213T021252 Handle: ./testdir/0vtpo8d4_1 Media: s:blrv071a091.lss.emc.com:/rman_su List of Datafiles in backup set 27 Container ID: 3, PDB Name: PDBORCLBS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------27 Full 670.00M SBT_TAPE 00:00:03 20-FEB-19 BP Key: 34 Status: AVAILABLE Compressed: NO Tag: TAG20190220T041617 Handle: ORCL_17tqau8i_1_1 Media: Database Application Agent/ddbea_su List of Datafiles in backup set 34 Container ID: 3, PDB Name: PDBORCL File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 8 Full 1969272 04-FEB-19 /u01/app/oracle/oradata/orcl/pdborcl/system01.dbf 9 Full 1969272 04-FEB-19 /u01/app/oracle/oradata/orcl/pdborcl/sysaux01.dbf 10 Full 1969272 04-FEB-19 /u01/app/oracle/oradata/orcl/pdborcl/SAMPLE_SCHEMA_users01.dbf 11 Full 1969272 04-FEB-19 /u01/app/oracle/oradata/orcl/pdborcl/example01.dbf

l The RMAN command RESTORE...PREVIEW shows which product performed the backup andthe backup pieces required for the restore. In the RESTORE...PREVIEW command output, thedatabase application agent backups are indicated by a media handle (after the label Media:)as Database Application Agent/<device_path>. The Oracle RMAN agent backupsare indicated by a media handle of only <device_path>.

For example, the following output from the RESTORE...PREVIEW command shows the twotypes of media handles:

List of Backup Sets===================BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------27 Incr 0 751.50M SBT_TAPE 00:00:08 18-JUN-19 BP Key: 27 Status: AVAILABLE Compressed: NO Tag: TAG20190618T224918 Handle: DDBEA_BACKUP_ORCL_1au4el7e_1_1 Media: Database Application Agent/ddbea_su List of Datafiles in backup set 27 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 0 Incr 3099340 18-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_system_gjncgq81_.dbf 4 0 Incr 3099340 18-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_gjncgqch_.dbf

BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------37 Incr 1 19.25M SBT_TAPE 00:00:02 18-JUN-19 BP Key: 37 Status: AVAILABLE Compressed: NO Tag: TAG20190618T234336 Handle: DDBEA_BACKUP_ORCL_1ju4eod8_1_1 Media: Database Application Agent/ddbea_su



List of Datafiles in backup set 37 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 1 Incr 3104875 18-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_system_gjncgq81_.dbf 4 1 Incr 3104875 18-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_gjncgqch_.dbf

BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------42 Incr 1 25.00M SBT_TAPE 00:00:01 19-JUN-19 BP Key: 42 Status: AVAILABLE Compressed: NO Tag: TAG20190619T051822 Handle: RMAN_BACKUP_ORCL_1vu4fc0u_1_1 Media: blrv071a091.lss.emc.com:/rman_su List of Datafiles in backup set 42 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 1 Incr 3123880 19-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_system_gjncgq81_.dbf 4 1 Incr 3123880 19-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_gjncgqch_.dbf

BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------48 Incr 1 1.00M SBT_TAPE 00:00:01 19-JUN-19 BP Key: 48 Status: AVAILABLE Compressed: NO Tag: TAG20190619T052357 Handle: RMAN_BACKUP_ORCL_28u4fcbd_1_1 Media: blrv071a091.lss.emc.com:/rman_su List of Datafiles in backup set 48 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 1 Incr 3124118 19-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_system_gjncgq81_.dbf 4 1 Incr 3124118 19-JUN-19 NO /u01/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_gjncgqch_.dbf

Using the correct RMAN script for restore, crosscheck, and delete operationsYou must allocate channels for both the database application agent and Oracle RMAN agent, forthe restore, crosscheck, and delete operations on any unexpired Oracle backups that werepreviously performed with the database application agent. You can maintain the databaseapplication agent software on the Oracle database server host as long as needed.

For the database application agent operations, you must modify the RMAN scripts to allocate therequired channels and include the correct commands. The latest version of the DatabaseApplication Agent Installation and Administration Guide provides details on the RMAN scripts to usewith the database application agent.

For example, the following RMAN commands include the correct SBT_LIBRARY settings for thedatabase application agent:

l On UNIX or Linux:

ALLOCATE CHANNEL DDBEA1 TYPE SBT_TAPE PARMS ‘BLKSIZE=1048576, SBT_LIBRARY= SBT_LIBRARY=/opt/dpsapps/dbappagent/lib/lib64/libddboostora.so,ENV=(CONFIG_FILE=/orasnb/oracle_ddbda.cfg)’;

l On Windows:

ALLOCATE CHANNEL DDBEA1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=C:\PROGRA~1\DPSAPPS\DBAPPAGENT\bin\libddboostora.dll, SBT_PARMS=(CONFIG_FILE=D:\orasnb\oracle_ddbda.cfg)' FORMAT '%d_%U';

To identify whether a backup was performed with the database application agent or Oracle RMANagent, follow the instructions in Identifying the types of backups on page 70.



You must use the database application agent in the RMAN crosscheck and delete scripts to deletethe database application agent backups when they become expired according to the RMANretention policy.

Note: Use the database application agent software for the recover, crosscheck, and deleteoperations until all the database application agent backups have expired.

The following sample RMAN script restores a database after allocating the required channels forboth the Oracle RMAN agent and database application agent:

connect target *RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS 'BLKSIZE=1048576, SBT_LIBRARY=libddobk.so, ENV=(STORAGE_UNIT=rman_su, BACKUP_HOST=blrv071a091.lss.emc.com, RMAN_AGENT_HOME=/opt/dpsapps/rmanagent/)';ALLOCATE CHANNEL DDBEA1 TYPE SBT_TAPE PARMS ‘BLKSIZE=1048576, SBT_LIBRARY= SBT_LIBRARY=/opt/dpsapps/dbappagent/lib/lib64/libddboostora.so,ENV=(CONFIG_FILE=/orasnb/oracle_ddbda.cfg)’RESTORE DATABASE;RECOVER DATABASERELEASE CHANNEL CH1;RELEASE CHANNEL DDBEA1;}

Updating the data movement policy for cloud tier operationsA DD Cloud Tier policy, also known as a data movement policy, is required for each MTree orstorage unit that the Oracle RMAN agent uses for data movement to the cloud. The databaseapplication agent supports an application-based data movement policy while the Oracle RMANagent supports an age-based data movement policy.

After you migrate an Oracle configuration from the database application agent to the OracleRMAN agent, you must update the data movement policy from an application-based policy to anage-based policy for cloud tiering.

For example, you can run the following command to verify the policy configurations:

data-movement policy show

Mtree Target(Tier/Unit Name) Policy Value------------------------- ---------------------- ------------- -------/data/col1/rman Cloud/ecs_1 age-threshold 14 days/data/col1/exchange Cloud/ecs_1 app-managed enabled/data/col1/DDBEA_ORACLE Cloud/ecs_1 app-managed enabled------------------------- ---------------------- ------------- -------

After the data is moved to the cloud, complete the following steps to update the data movementpolicy from the application-based policy to the age-based policy.

1. Disable the application-based policy. For example:

data-movement policy set app-managed disabled to-tier cloud cloud-unit ecs_1 mtrees /data/col1/DDBEA_ORACLE

The data-movement app-managed policy for Mtree(s) "/data/col1/DDBEA_ORACLE" is reset to "none".



2. Set the age-based policy for the Oracle RMAN agent. For example:

data-movement policy set age-threshold 14 to-tier cloud cloud-unit ecs_1 mtrees /data/col1/DDBEA_ORACLE

The data-movement age-threshold policy is set to "14" days for the following Mtree(s):/data/col1/DDBEA_ORACLE

Run the following command again to verify the policy configurations:

data-movement policy show

Mtree Target(Tier/Unit Name) Policy Value------------------------- ---------------------- ------------- -------/data/col1/rman Cloud/ecs_1 age-threshold 14 days/data/col1/exchange Cloud/ecs_1 app-managed enabled/data/col1/DDBEA_ORACLE Cloud/ecs_1 age-threshold 14 days------------------------- ---------------------- ------------- -------

Use the correct type of RMAN script for data recall and restore operations as described in Performing the data recall from the cloud on page 132.

Performing backups of a clustered environment to DataDomain

The following examples provide the procedures in different lockbox scenarios for Oracle RMANagent backups and restores with Oracle RAC nodes in a clustered environment.

Scenario 1 - Lockbox in a shared location

1. Mount an NFS/CIFS path on both of the Oracle RAC nodes to be used for backups andrestores.

2. Install the Oracle RMAN agent on the NSF-mounted path.

3. Run the following command to create a shared lockbox that includes the RAC node hostnamesin the cluster:

send 'hostnames <hostname-1> <hostname-2> ... <hostname-n>';

4. Back up the database on node 1.

5. Restore the database backup on node 2.

Scenario 2 - Using a lockbox copy

1. Install the Oracle RMAN agent on both of the Oracle RAC nodes separately.

2. Create a lockbox, and add both of the node hostnames to the lockbox on node 1.

3. Copy the lockbox files from node 1 to node 2.



Note: As an alternative, you can back up the database on node 2 and then restore thebackup on node 1.



Scenario 3 - Without a shared lockbox

1. Install the Oracle RMAN agent on both of the Oracle RAC nodes separately.

2. Register the lockbox separately on each node, node 1 and node 2.



Data Domain replicationThe Data Domain Replicator provides automated encrypted replication for disaster recovery andmultisite backup and archive consolidation. The Data Domain Replicator software asynchronouslyreplicates only compressed, deduplicated data over a wide area network (WAN).

You can use one of two methods to replicate the Oracle backups. Oracle RMAN agent does notsupport the use of both methods together:

l Managed file replication (MFR)

MFR can be used to create multiple copies of a backup while the backup is running. As eachRMAN file is created on the primary Data Domain system during a backup, network-efficientreplication automatically begins to copy the unique and compressed file segments to theremote Data Domain system. When the RMAN backup to the local Data Domain system as wellas replication to the remote Data Domain system are complete, the RMAN catalog is updatedwith information about both the local and remote backup copies. Performing managed filereplication (MFR) on page 75 provides details about setting up MFR in the Oracle RMANagent and restoring from a backup copy.

l MTree replication

MTree replication can be used to create a copy or copies of a backup independently from theRMAN backup process. You use the Oracle RMAN agent to create the backup on a primaryData Domain system, and the Data Domain administrator performs the MTree replication fromthe primary system to the secondary system. The Oracle RMAN agent does not initiate ormonitor the MTree replication. However, the product can restore from the replicated copy on asecondary Data Domain system. Restoring from MTree replicated backups on page 79provides details about the restore process.

The Data Domain Operating System Administration Guide provides more information about thelicense requirement for Data Domain Replicator and the compatibility between the source DD OSand destination DD OS. The guide includes detailed steps to perform and manage the MTreereplication.

Performing managed file replication (MFR)File replication enables you to make multiple copies of an RMAN backup. With the Oracle RMANagent, you can make two, three, or four copies of a backup by specifying COPIES <n> in thebackup command, where <n> is 2, 3, or 4.

NOTICEIf the Oracle RMAN agent is integrated with PowerProtect, the following self-servicereplication and cloud tiering operations are disabled:

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

l Automatic recall of the backup data during restore, when the backup file is in the cloudtier. The PowerProtect administrator must explicitly recall the backup copy before it canbe restored by the DBA.

The PowerProtect Administration and User Guide provides more details about these limitations.



To perform file replication, use a command similar to the one shown as follows. Edit the scriptcommand for your environment, specifying the Data Domain system that is the destination systemfor the file replication. Specifying COPIES <n> requires an installed Replicator license on both thesource and destination Data Domain systems. Performing a backup by specifying COPIES <n>requires Oracle Enterprise Edition.

For example, specifying COPIES 2 instructs the Oracle RMAN agent to perform managed filereplication (MFR) to the second Data Domain system. The second Data Domain system name isspecified as part of the file name of the second copy, as <destination-system> in the followingcommand.

The two file names specified in this command must be identical except for the inclusion of<destination-system> in the second name. The Oracle RMAN agent requires that the file names ofthe two copies are identical. The underscore character (_) is also required. Omitting theunderscore in the file names results in an error, and the backup fails. Any changes made to the filename formats shown must meet both of the following requirements:

l The file name formats include the underscore character.

l The file names are identical, except for <destination-system> in the name for the second copy.

The use of Oracle formats such as %U and %c is not supported, as these Oracle formats includethe copy number in the generated file name. As a result, the file name generated for the secondcopy is different from the file name generated for the first copy.

backup copies 2 database filesperset=1 format '%u_%p', '<destination-system>/%u_%p';

Note: Use the lowercase u in '%u_%p'. An uppercase U, while a valid Oracle format, is invalidfor the Oracle RMAN agent and causes the replication to fail.

To use COPIES 2, the value of BACKUP_TAPE_IO_SLAVES must be TRUE, which you canconfigure as follows:

SQL> show parameter backup_tape

NAME TYPE VALUE------------------------------------ ----------- ------------------------------backup_tape_io_slaves boolean FALSESQL>

SQL> alter system set backup_tape_io_slaves = true scope=spfile;

System altered.

bounce the oracle instance( shutdown and startup) the database

SQL> show parameter backup_tape

NAME TYPE VALUE------------------------------------ ----------- ------------------------------backup_tape_io_slaves boolean TRUESQL>

The only difference from performing a second backup to a different BACKUP_HOST is that thedata flow for managed file replication is between the two Data Domain systems. A typical backupsends data between the backup server and a Data Domain system.



To make three or four copies, use a backup command with COPIES 3 or COPIES 4 instead ofCOPIES 2. The format of the backup command is as follows:

backup copies <n> database filesperset=1 format '%u_%p', '<destination-system2>/%u_%p', '<destination-system3>/%u_%p', '<destination-system4>/%u_%p'

Specifying two, three, or four copies creates the additional copies on the second, third, and fourthdestination systems, respectively. All the formats must be identical except for the initial DataDomain system name so that all the file copies are created with the same file names. Each DataDomain system specified must have a storage unit with the name specified by the STORAGE_UNITvalue.

File replication must be performed to a destination storage unit with the same name as the sourcestorage unit. The target Data Domain systems must have a storage unit that has the same name asthe storage unit on the source Data Domain system containing the file being replicated. The file isreplicated to the identically named storage unit on the destination Data Domain systems.

File replication using RMAN requires that both the source Data Domain system and the destinationData Domain systems are connected to, and accessible from, the RMAN system that performs thebackups. The network configuration must enable backups to the source Data Domain system andto all the destination Data Domain systems. The destination systems must all be accessible fromthe source system. When more than two copies are made, the destination systems do not need tobe accessible to each other, only to the source system. Replication does not succeed inconfigurations where the destination Data Domain system is only connected to the source DataDomain system through a private network or link.

The following example shows the output of the RMAN list command, which displays thedestination and the storage unit associated with COPIES 2.

RMAN> list backupset 52;

List of Backup Sets===================

BS Key Type LV Size------- ---- -- ----------52 Full 1.62G List of Datafiles in backup set 52 File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 1 Full 4614599 09-MAY-12 /u02/app/oracle/oradata/Demo/system01.dbf 2 Full 4614599 09-MAY-12 /u02/app/oracle/oradata/Demo/sysaux01.dbf 3 Full 4614599 09-MAY-12 /u02/app/oracle/oradata/Demo/undotbs01.dbf 4 Full 4614599 09-MAY-12 /u02/app/oracle/oradata/Demo/users01.dbf 5 Full 4614599 09-MAY-12 /u02/app/oracle/oradata/Demo/example01.dbf

Backup Set Copy #2 of backup set 52 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ --------------- ---------- --- SBT_TAPE 00:00:34 09-MAY-12 NO TAG20120509T101338

List of Backup Pieces for backup set 52 Copy #2 BP Key Pc# Status Media Piece Name ------- --- ----------- ----------------------- ---------- 78 1 AVAILABLE Demo dd670-ostqa06.datadomain.com/20nahpei_1

Backup Set Copy #1 of backup set 52 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ --------------- ---------- --- SBT_TAPE 00:00:34 09-MAY-12 NO TAG20120509T101338



List of Backup Pieces for backup set 52 Copy #1 BP Key Pc# Status Media Piece Name ------- --- ----------- ----------------------- ---------- 77 1 AVAILABLE Demo 20nahpei_1

RMAN>

Restoring from multiple backup copiesIf there are multiple copies of a backup that are generated through MFR, you can perform arestore from any Data Domain system that contains a copy of the backup. Typically, you perform arestore from the source (local) Data Domain system. In this case, specify this Data Domain systemas the backup host in the restore command.

If this source Data Domain system is unavailable for any reason, you can restore the backup fromany of the other available Data Domain systems. To do this, determine which Data Domain systemsare accessible over the network. If COPIES 2 was used, there is only one other system that canperform the restore, so it must be available. If COPIES 3 or COPIES 4 was used, any currentlyavailable system can perform the restore. If more than one system with the required backup isavailable, select a system based on the following factors:

l Available bandwidth

l Speed of the connection

l Other performance or logistical considerations

Specify the preferred system as the backup host in the restore command.

In some cases, it is possible that a backup file is unavailable on the specified backup host. In such acase, if another available Data Domain system has a copy of the backup, RMAN tries to retrievethe file from the other system. This retrieval attempt occurs although this system was notspecified as the backup host.

For example, three copies of a backup were made to ddr-host-1, ddr-host-2, and ddr-host-3. Whena restore is required, ddr-host-1 is down, but both ddr-host-2 and ddr-host-3 are available. If youspecify ddr-host-2 as the backup host in the restore command, RMAN retrieves the backup filesfrom ddr-host-2. If a file cannot be found on ddr-host-2, RMAN tries to retrieve the file from ddr-host-3. If that retrieval does not succeed, the restore fails.

If you select ddr-host-3 as the backup host, RMAN tries to restore the backup files from ddr-host-3. If a file cannot be found on ddr-host-3, RMAN tries to retrieve the file from ddr-host-2.

Note: If ddr-host-2 is down but ddr-host-1 and ddr-host-3 are available, specifying ddr-host-3as the backup host causes the restore to be performed from ddr-host-3. However, if a file isnot found on ddr-host-3, RMAN does not try to find the missing file on ddr-host-1.

The system specified as the backup host must always be available. If the system specified as thebackup host is unavailable, the restore always fails, even if the backup is available from othercopies.



Restoring from MTree replicated backupsTo enable the restore of an MTree replicated backup, you must register the secondary DataDomain system in the lockbox. Use an RMAN command as shown in the following example, andedit the command for the environment.

Note: The registration of the secondary Data Domain system is required only once. Do notinclude the registration command in each restore script. Perform this registration before youperform any restores from the secondary Data Domain system.

RUN {ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE' TRACE 5 PARMS 'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(BACKUP_HOST=bu-ddbealin-17.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';send 'set username q_ost password 1X3quest servernamebu-ddbealin-17.lss.emc.com storageunit rman_su';RELEASE CHANNEL C1;}

Ensure that you specify the correct values in the RMAN send command for the registration:

l The username value is the DD Boost username on the secondary Data Domain system. Theusername is case-sensitive, and must match exactly the value that is set on the secondaryData Domain system.

l The password value is the password that you set for the username. The password is case-sensitive, and must match exactly the value that is set on the secondary Data Domain system.

l The servername value is the case-sensitive name of the secondary Data Domain system.Specify the same form of the name in this command as in the RMAN restore script, shown asfollows. For example, if you use server1.domain.com in the RMAN restore script, you must alsouse server1.domain.com in the send command. Do not use SERVER1.domain.com or server1.

You can specify an IP address if the same IP address is used in the RMAN restore script. Youcan register multiple forms of the server name. For example, you can register both server1 andserver1.domain.com, and use either of these names in the RMAN restore script.

l The storageunit value is the destination storage unit of the MTree replication on thesecondary Data Domain system. The value is case-sensitive, and must match exactly the valuethat is set on the secondary Data Domain system.

After the registration is complete, you can perform restores from the secondary Data Domainsystem. Use an RMAN restore script as shown in the following example, and edit the command forthe environment:

RUN {ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE' TRACE 5 PARMS 'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(STORAGE_UNIT=rman_su, BACKUP_HOST=bu-ddbealin-17.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';restore database;RELEASE CHANNEL C1;}

Ensure that you specify the correct values in the RMAN restore script:

l The STORAGE_UNIT value is the destination storage unit of the MTree replication on thesecondary Data Domain system. The value is case-sensitive, and must match exactly the valuethat is set on the secondary Data Domain system.

l The BACKUP_HOST value is the case-sensitive name of the secondary Data Domain system.Specify the same form of the name in this script as in the RMAN registration command. For



example, if you use server1.domain.com in the RMAN registration command, you must also useserver1.domain.com in the restore script. Do not use SERVER1.domain.com or server1.

You can specify an IP address if the same IP address is used in the RMAN registrationcommand.

Note: For MTree replication, the destination storage unit name on the secondary Data Domainsystem can be the same as or different than the source storage unit name on the source DataDomain system.

Specifying subdirectories for Oracle RMAN agent backupsYou can specify one or more subdirectories in the pathname that Oracle RMAN agent uses as thelocation to store the backup pieces created during a backup. You must specify the subdirectoriesin the FORMAT specification in the RMAN backup script. If the specified subdirectories do not yetexist when the backup starts, the Oracle RMAN agent automatically creates the subdirectoriesduring the backup to the Data Domain system.

Note: When you perform a restore, crosscheck, or delete operation, you do not need to specifyany subdirectories in the RMAN script. The pathname is recorded as part of the backup piecename in the Oracle catalog. When you perform the operation, Oracle provides the requiredpathname to the Oracle RMAN agent.

You must use the correct subdirectory naming in the FORMAT specification, depending onwhether the backup is performed to a local or remote Data Domain system:

l For a backup to a local system, use the following types of FORMAT specification:

n When the pathname includes a single subdirectory:

FORMAT './<directory-name>/%u_%p';

n When the pathname includes multiple subdirectories:

FORMAT './<directory-name-1>/<directory-name-2>/.../<directory-name-n>/%u_%p';

l For a backup to a remote system, use the following types of FORMAT specification:

n When the pathname includes a single subdirectory:

FORMAT './<directory-name>/%u_%p', '<destination-system>/./<directory-name>/%u_%p';

n When the pathname includes multiple subdirectories:

FORMAT './<directory-name-1>/<directory-name-2>/.../<directory-name-n>/%u_%p', '<destination-system>/./<directory-name-1>/<directory-name-2>/.../<directory-name-n>/%u_%p';

Note: When you specify any subdirectories in a single BACKUP command that is used for adatabase plus archive log backup, you must use the FORMAT specification twice: once for thedatabase backup pieces and once for the archive log backup pieces. The following RMANscript examples include a database plus archive log backup.

The following examples provide sample RMAN scripts with the correct subdirectory naming in theFORMAT specification for local and remote backups.



Example 1 Specifying a single subdirectory in the FORMAT specification for a local backup

The following sample RMAN script for a local backup includes a FORMAT specificationwith a single subdirectory in the backup pathname:

RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(STORAGE_UNIT=rman_cloud,BACKUP_HOST=bu-ddbea-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';BACKUP DATABASE FORMAT './testdir/%u_%p';RELEASE CHANNEL CH1;}

Example 2 Specifying a subdirectory in the FORMAT specification for a local backup of database plusarchive log

The following sample RMAN script for a local backup includes a FORMAT specificationwith a single subdirectory in the backup pathname. Because the BACKUP commandincludes both the database and archivelog options, you must specify theFORMAT twice in this case:

RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(STORAGE_UNIT=rman_cloud,BACKUP_HOST=bu-ddbea-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';BACKUP FORMAT './testdir/%u_%p' DATABASE PLUS ARCHIVELOG DELETE INPUT FORMAT './testdir/%u_%p';RELEASE CHANNEL CH1;}

Example 3 Specifying multiple subdirectories in the FORMAT specification for a local backup

The following sample RMAN script for a local backup includes a FORMAT specificationwith multiple subdirectories in the backup pathname:

RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(STORAGE_UNIT=rman_cloud,BACKUP_HOST=bu-ddbea-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';BACKUP TABLESPACE PSAPCERUSR FORMAT './testdir1/testdir2/.../testdir<n>/%u_%p';RELEASE CHANNEL CH1;}

Example 4 Specifying a single subdirectory in the FORMAT specification for a remote backup



Example 4 Specifying a single subdirectory in the FORMAT specification for a remotebackup (continued)

The following sample RMAN script for a backup to a remote Data Domain systemincludes a FORMAT specification with a single subdirectory in the backup pathname.The two file names specified in the BACKUP COPIES 2 command must be identicalexcept for the inclusion of <destination-system> in the second name. The underscorecharacter (_) is also required:

RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(STORAGE_UNIT=rman_cloud,BACKUP_HOST=bu-ddbea-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';BACKUP COPIES 2 DATABASE FORMAT './testdir1/%u_%p', '<destination-system>/./testdir1/%u_%p';RELEASE CHANNEL CH1;}

Example 5 Specifying multiple subdirectories in the FORMAT specification for a remote backup

The following sample RMAN script for a backup to a remote Data Domain systemincludes a FORMAT specification with multiple subdirectories in the backup pathname.The two file names specified in the BACKUP COPIES 2 command must be identicalexcept for the inclusion of <destination-system> in the second name. The underscorecharacter (_) is also required:

RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS'BLKSIZE=1048576,SBT_LIBRARY=/home/oracle1/rman_agent_home/lib/libddobk.so,ENV=(STORAGE_UNIT=rman_cloud,BACKUP_HOST=bu-ddbea-lin-16.lss.emc.com,RMAN_AGENT_HOME=/home/oracle1/rman_agent_home)';BACKUP COPIES 2 DATABASE FORMAT './testdir1/testdir2/.../testdir<n>/%u_%p', '<destination-system>/./testdir1/testdir2/.../testdir<n>/%u_%p';RELEASE CHANNEL CH1;}

Performing backups and restores of Oracle CDBs and PDBsOracle 12c introduced support for a multitenant database that allows a single container database(CDB) to include multiple user-created pluggable databases (PDBs). You can perform backups andrestores of a whole CDB or individual PDBs. No additional configuration steps are needed in theOracle RMAN agent to support the environment.

It is recommended that you perform regular backups of the whole CDB to ensure that all PDBs andarchived logs are backed up. You can recover the whole CDB or individual PDBs to any point-in-time from a CDB backup. The Oracle documentation provides details.



Performing DD Boost compressed restoresOracle RMAN agent 4.5 introduced support of DD Boost compressed restores. A compressedrestore uses less bandwidth by restoring the backed-up data in a compressed form from the DataDomain system to the application host.

A compressed restore can be beneficial in a constrained bandwidth environment or a cloudenvironment, but can impact the restore performance due to the usage of compression resourceson the Data Domain system and application host. By default, the compression of restores isdisabled.

Configure a compressed restore of an Oracle RMAN agent backup by setting theDDBOOST_COMPRESSED_RESTORE parameter to the value TRUE in the SBT_PARMS or ENVsection of the RMAN restore script.

For example, the following RMAN restore script includes the parameter setting:

RUN {ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS'BLKSIZE=1048576,SBT_LIBRARY=C:\Users\Administrator\AppData\Local\RMANAgent\bin\libDDobk.dll,ENV=(STORAGE_UNIT=ddbea,BACKUP_HOST=bu-dbe4500.lss.emc.com,RMAN_AGENT_HOME=C:\Users\Administrator\AppData\Local\RMANAgent,DDBOOST_COMPRESSED_RESTORE=TRUE)';RESTORE DATABASE;RECOVER DATABASE;RELEASE CHANNEL CH1;}

Note:When the DDBOOST_COMPRESSED_RESTORE parameter is not set to TRUE, the Oracle RMANagent performs an uncompressed restore of the backed-up data from the Data Domainsystem.

Display and deletion of backupsWhen the Oracle catalog records are removed for some backups that were performed with theOracle RMAN agent but the backups still remain on the Data Domain system, those backupsbecome orphaned backups. You can delete such orphaned backups with the ddutil program thatis installed with the Oracle RMAN agent software.

Note:The ddutil program deletes backup files on the Data Domain system but does not delete anyinformation on the database server. Backups are normally deleted by using the RMAN DELETEcommand, which deletes both the backup on the Data Domain system and the correspondingRMAN catalog record.

The ddutil program user must have permissions to the lockbox as described in Registeringeach Data Domain system on page 62. The program uses the DD Boost library for operations,and does not require you to mount the storage unit.

The ddutil program is installed in the bin directory, created by the Oracle RMAN agent installer.The program performs deletions of individual backup files or groups of backup files, as specified.

You can perform any of the following operations, based on the ddutil command and options thatyou specify on the command line:

l Display information about backup files at the individual file level, directory level, or storage unitlevel.



l Delete the backup files at the individual file level or directory level.l Prune (delete) backup files that were created or modified during a specified time interval.

You must run the ddutil command on the command line with the required options. The -z<hostname>:<storage_unit> option is the only mandatory option, and specifies the credentialsthat the Oracle RMAN agent requires for lockbox access during the display, delete, and pruneoperations.

Note: You must run the ddutil command from the original installation location or set theRMAN_AGENT_HOME environment variable to enable the dependent libraries and lockbox tobe found.

The following topics provide details about how to use the ddutil command and options toperform the display, delete, and prune operations.

Using the ddutil command to display and delete backupsAn Oracle DBA user can run the ddutil command with the appropriate options to perform thefollowing operations:

l Display information about the installed version of the Oracle RMAN agent:

ddutil -i

For example:

ddutil -iRMAN Agent Version: 19.1.0.0(14)

l Display information about the specified backup files and directories:

ddutil [-f] -z <hostname>:<storage_unit> [-F {asce|desc} | -T {asce|desc}] [-b <start_time>] [-e <end_time>] [-R] [-t] [-D <debug_level>] [<pathname1> [<pathname2>]...[<pathname><n>]]

Note: The default operation of the ddutil command is the display of backup information.If you run the ddutil command with no options other than the mandatory -z option, thecommand displays all the backup files that are located directly under the storage unit.

Using the ddutil command to display backup information on page 87 provides details.l Delete the specified backup files and directories:

ddutil -d -z <hostname>:<storage_unit> [-c] [-x] [-D <debug_level>] [<pathname1> [<pathname2>]...[<pathname><n>]]

Using the ddutil command to delete backups on page 90 provides details.l Prune (delete) the backup files and directories within a save time range:

ddutil -k -z <hostname>:<storage_unit> [-b <start_time>] [-e <end_time>] [-c] [-R] [-x] [-D <debug_level>] [<pathname1> [<pathname2>]...[<pathname><n>]]

Using the ddutil command to prune backups based on age on page 90 provides details.

Options enclosed in brackets ([ ]) are optional. The following table describes the ddutilcommand options.



Table 8 The ddutil command options for backup display and deletion

Option Description

-b <start_time> Optional. Specifies the start of a time range, in a date and time format. Date andtime format used with the ddutil command options on page 87 provides detailsabout the supported date and time formats for <start_time>.

Without this option, the earliest backup time is used by default for the start of thetime range.

Note: The operation terminates with an error if the <start_time> value is laterthan the <end_time> value that is specified with the -e option.

-c Optional. Specifies to suppress prompting during a delete or prune operation. Withthis option, the program proceeds to delete or prune the specified backup fileswithout issuing any user prompts.

-d Required for a delete operation. Specifies to delete the specified backup files anddirectories from the Data Domain system.

-D <debug_level> Optional. Generates debugging information during the operation, where<debug_level> is an integer from 0 to 9. This option is used to troubleshootoperational issues.

This option causes the ddutil command to print the debugging information to

stderr and to the operational log file. The higher the integer value, the more loginformation is produced. The operational log file also contains the normal operationalmessages that are printed to stdout.

The operational log file, ddutil_<timestamp>.log, resides in the logsubdirectory of the installation location. For example, the operational log file namehas the format ddutil_Wed May 17 21:49:08 2017.log.

-e <end_time> Optional. Specifies the end of a time range, in a date and time format. Date and timeformat used with the ddutil command options on page 87 provides details aboutthe supported date and time formats for <end_time>.

The option setting -e now specifies the current time, which is the default time

value.

Note: The operation terminates with an error if the <end_time> value is earlierthan the <start_time> value that is specified with the -b option.

-f Optional. Specifies to display information about the specified backup files anddirectories that were created or modified within the specified time range on theData Domain system. This display operation is the default operation of the ddutilcommand.

-F {asce|desc} Optional. Specifies to list the backup files in either ascending or descendingalphabetical order:

l The -F asce option displays the files in ascending alphabetical order, based on

the file pathnames.

l The -F desc option displays the files in descending alphabetical order, based

on the file pathnames.

You must specify the -f and -z options with the -F asce or -F desc option. You

can optionally specify the -b, -e, -R, -t, and <pathname><n> options with the -Fasce or -F desc option.



Table 8 The ddutil command options for backup display and deletion (continued)

Option Description

Note: The -F and -T options are mutually exclusive. You can use either option

but not both in the same ddutil command.

-k Required for a prune operation. Specifies to prune (delete) the specified backupfiles that were created or modified within the specified time range on the DataDomain system.

-R Optional. Specifies to perform the operation on the backup files in everysubdirectory.

-t Optional. Specifies to include the cloud tier information in the backup file anddirectory information that a display operation produces.

-T {asce|desc} Optional. Specifies to list the backup files in either ascending or descending timeorder:

l The -T asce option displays the files in ascending time order, from the oldest

backup to the newest backup.

l The -T desc option displays the files in descending time order, from the

newest backup to the oldest backup.

You must specify the -f and -z options with the -T asce or -T desc option. You

can optionally specify the -b, -e, -R, -t, and <pathname><n> options with the -Tasce or -T desc option.

Note: The -T and -F options are mutually exclusive. You can use either option

but not both in the same ddutil command.

-x Optional. Specifies to delete all the empty directories during a delete or pruneoperation.

-z<hostname>:<storage_unit>

Mandatory. Specifies the hostname of the Data Domain system, followed by a colon,a forward slash (/), and the storage unit name. For example:

-z dd_host1:/dd_storage_unit1

Note: The hostname can be a DFC server name if you must run the ddutilcommand over Fibre Channel.

<pathname1><pathname2>...<pathname><n>

Optional. Specifies the pathnames of the files or directories for display or deletion.For each specified directory, the operation is performed on all the files in thedirectory. When -R is included, the operation processes all the subdirectories of

each directory. Without -R, the operation does not process any subdirectories.

The following guidelines apply to the pathnames in a ddutil command:

l The pathnames must be the last options on the command line. No other typesof options, such as -R or -c, can appear after the pathnames.

l When no pathnames are specified, the operation occurs only at the level of thestorage unit root directory.

l When a pathname starts with a forward slash (/), the storage unit name mustappear after the slash.

l When a pathname does not start with a slash (/), the pathname is assumed tobe located directly under the storage unit.



Table 8 The ddutil command options for backup display and deletion (continued)

Option Description

For example, when the storage unit is named su1, the pathnames /su1/dir1 and

dir1 both specify the directory dir1 under the storage unit.

The wildcard character * is supported in pathnames, and represents any number ofunspecified characters.

Date and time format used with the ddutil command optionsYou can use specific date and time formats with the options -b <start_time> and -e <end_time>in the ddutil command. The following date and time formats are valid:

l Time of day—A time of day is in the form hh[:mm[:ss]] (or hhmm) [meridian] [zone]. If you donot specify a meridian (am or pm), a 24-hour clock is used. You can specify a time of day asjust hh followed by a meridian. If you do not specify a timezone (for example, GMT), then thecurrent timezone is used, as determined by the second parameter, now.

l Date—A date is a specific month and day, and possibly a year. The acceptable formats aremm/dd[/yy] and month_name dd[, yy]. If omitted, the year defaults to the current year. If youspecify a year as a number in the range 70 and 99, 1900 is added. If a year is in the range 00and 30, 2000 is added. The treatment of other years less than 100 is undefined. If a number isnot followed by a day or relative time unit, the number is interpreted as a year if a time_of_day,month_name, and dd have already been specified; otherwise, it will be treated as atime_of_day.

l Day—A day of the week can be specified. The current day is used if appropriate. A day can bepreceded by a number, indicating which instance of that day is preferred; the default is 1.Negative numbers indicate times past. Some symbolic numbers are accepted: last, next, andthe ordinals first through twelfth (second is ambiguous, and is not accepted as an ordinalnumber). The symbolic number next is equivalent to 2; thus, next monday does not refer to thecoming Monday, but refers to the one a week later.

l relative time—Specifications relative to the current time can be used. The format is [number]unit. Acceptable units are decade, year, quarter, month, fortnight, week, day, hour, minute,and second.

Most common abbreviations for days, months, and so on are acceptable, including an uppercase orlowercase first letter and three-letter abbreviations, with or without a trailing period. Units, suchas weeks, can be specified as singular or plural. Timezone and meridian values can be uppercase orlowercase, with or without periods.

The actual date is formed as follows. First, any absolute date and/or time is processed andconverted. Using that time as the base, day-of-week specifications are added. Last, relativespecifications are used. If a date or day is specified, and no absolute or relative time is given,midnight is used. Finally, a correction is applied so that the correct hour of the day is producedafter allowing for daylight savings time differences.

Using the ddutil command to display backup informationYou can run the following ddutil command to display information about the backup files anddirectories:

ddutil [-f] -z <hostname>:<storage_unit> [-F {asce|desc} | -T {asce|desc}] [-b <start_time>] [-e <end_time>] [-R] [-t] [-D <debug_level>] [<pathname1> [<pathname2>]...[<pathname><n>]]



Table 8 on page 85 provides details about the command options.

Typically, you run this operation to prepare for a delete or prune operation with the ddutilcommand. You can compare the displayed backup information with details in the database backupcatalog and determine which backup files to delete or prune.

The ddutil -f <options> command output includes one row for each backup file anddirectory that was found, where the row contains the file or directory name and the backup sizeand time.

The default operation of the ddutil command is the display of backup information. If you run thecommand with no pathnames and no options other than the -z option, the command displays allthe backup files that are located directly under the storage unit. The following commands displaythe same output:

ddutil -z <hostname>:<storage_unit>ddutil -f -z <hostname>:<storage_unit>

The ddutil command ignores all subdirectories unless you specify the -R option. For example,the following command displays all the backup files and directories on the storage unit su1,including the files in all the subdirectories:

ddutil -f -z host1:/su1 -R

Type Perm Size Time Path---------------------------------------------------------------------------------dir 777 489 Wed May 3 12:15:12 2017 (1493828112) /su1file 644 682098688 Wed May 3 12:12:47 2017 (1493827967) /su1/6rs3aer4_1file 644 3181641728 Wed May 3 12:14:35 2017 (1493828075) /su1/6ts3aet5_1_1file 644 775946240 Wed May 3 12:14:53 2017 (1493828093) /su1/6us3aev7_1_1file 644 690225152 Wed May 3 12:15:07 2017 (1493828107) /su1/6vs3aevm_1_1file 644 18350080 Wed May 3 12:12:56 2017 (1493827976) /su1/c-4088691966-20170503-00file 644 18350080 Wed May 3 12:15:12 2017 (1493828112) /su1/c-4088691966-20170503-01

To display the backup files in specific directories, include the directory pathnames on thecommand line. For example, the following command displays the backup files in thedirectories /su1/dir1 and /su1/dir2:

ddutil -f -z host1:/su1 dir1 dir2

To display the backup files that were created after March 1, use the -b Mar 1 option. Forexample:

ddutil -f -z host1:/su1 -b Mar 1 -R

To display the backup files in ascending alphabetical order according to the file pathnames, use the-F asce option. For example, the following command displays the backup files in the /xapprmanstorage unit in ascending alphabetical order:

ddutil -f -F asce -z blrv033a154.lss.emc.com:/xapprman

Type Perm Size Time Path-----------------------------------------------------------------------------------------dir 777 1118 Mon Feb 25 15:52:51 2019 (1551090171) /xapprmanfile 644 1213988864 Mon Feb 18 16:27:42 2019 (1550487462) /xapprman/02tq68jn_1_1



file 644 601620480 Mon Feb 18 16:27:55 2019 (1550487475) /xapprman/03tq68kh_1_1dir 744 101 Tue Feb 12 14:36:43 2019 (1549962403) /xapprman/ABCfile 644 11534336 Mon Feb 25 15:52:20 2019 (1551090140) /xapprman/c-1944822367-20190225-01dir 744 219 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/ecdmdir 744 489 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/shradsdir 755 101 Thu Nov 22 16:35:00 2018 (1542884700) /xapprman/xyz

To display the backup files in descending alphabetical order according to the file pathnames, usethe -F desc option. For example, the following command displays the backup files in the /xapprman storage unit in descending alphabetical order:

ddutil -f -F desc -z blrv033a154.lss.emc.com:/xapprman

Type Perm Size Time Path-----------------------------------------------------------------------------------------dir 755 101 Thu Nov 22 16:35:00 2018 (1542884700) /xapprman/xyzdir 744 489 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/shradsdir 744 219 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/ecdmfile 644 11534336 Mon Feb 25 15:52:20 2019 (1551090140) /xapprman/c-1944822367-20190225-01dir 744 101 Tue Feb 12 14:36:43 2019 (1549962403) /xapprman/ABCfile 644 601620480 Mon Feb 18 16:27:55 2019 (1550487475) /xapprman/03tq68kh_1_1file 644 1213988864 Mon Feb 18 16:27:42 2019 (1550487462) /xapprman/02tq68jn_1_1dir 777 1118 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman

To display the backup files in ascending time order, use the -T asce option. For example, thefollowing command displays the backup files in the /xapprman storage unit in ascending timeorder, from the oldest backup to the newest backup:

ddutil -f -T asce -z blrv033a154.lss.emc.com:/xapprman

Type Perm Size Time Path-----------------------------------------------------------------------------------------dir 755 101 Thu Nov 22 16:35:00 2018 (1542884700) /xapprman/xyzdir 744 101 Tue Feb 12 14:36:43 2019 (1549962403) /xapprman/ABCfile 644 1213988864 Mon Feb 18 16:27:42 2019 (1550487462) /xapprman/02tq68jn_1_1file 644 601620480 Mon Feb 18 16:27:55 2019 (1550487475) /xapprman/03tq68kh_1_1file 644 11534336 Mon Feb 25 15:52:20 2019 (1551090140) /xapprman/c-1944822367-20190225-01dir 777 1118 Mon Feb 25 15:52:51 2019 (1551090171) /xapprmandir 744 219 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/ecdmdir 744 489 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/shrads

To display the backup files in descending time order, use the -T desc option. For example, thefollowing command displays the backup files in the /xapprman storage unit in descending timeorder, from the newest backup ot the oldest backup:

ddutil -f -T desc -z blrv033a154.lss.emc.com:/xapprman

Type Perm Size Time Path-----------------------------------------------------------------------------------------dir 777 1118 Mon Feb 25 15:52:51 2019 (1551090171) /xapprmandir 744 219 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/ecdmdir 744 489 Mon Feb 25 15:52:51 2019 (1551090171) /xapprman/shradsfile 644 11534336 Mon Feb 25 15:52:20 2019 (1551090140) /xapprman/c-1944822367-20190225-01file 644 601620480 Mon Feb 18 16:27:55 2019 (1550487475) /xapprman/03tq68kh_1_1file 644 1213988864 Mon Feb 18 16:27:42 2019 (1550487462) /xapprman/02tq68jn_1_1



dir 744 101 Tue Feb 12 14:36:43 2019 (1549962403) /xapprman/ABCdir 755 101 Thu Nov 22 16:35:00 2018 (1542884700) /xapprman/xyz

Using the ddutil command to delete backupsYou can run the following ddutil command to delete the specified backup files and directories:

ddutil -d -z <hostname>:<storage_unit> [-c] [-x] [-D <debug_level>] [<pathname1> [<pathname2>]...[<pathname><n>]]


The -d option specifies to delete from the Data Domain system any backup files and directoriesthat are specified on the command line. When you specify a directory, the command also deletesany subdirectories in that directory.

By default, the ddutil -d <options> command prompts you before deleting any files ordirectories. The -c option specifies to perform the deletions without prompting.

When the -x option is specified, the ddutil command also deletes any empty directories that itfinds. Without the -x option, the directories are not deleted.

NOTICE Use the ddutil -d <options> command with caution. The deletion of backupfiles and directories cannot be undone.

To delete specific backup files, run the following command:

ddutil -d -z <hostame>:/<storage_unit> <file_pathname1> <file_pathname2> ...

To delete specific backup directories, run the following command:

ddutil -d -x -z <hostame>:/<storage_unit> <directory_pathname1> <directory_pathname2> ...

To delete both backup files and directories, run the following command:

ddutil -d -x -z <hostame>:/<storage_unit> <file_pathname1> <file_pathname2> ... <directory_pathname1> <directory_pathname2> ...

Using the ddutil command to prune backups based on ageRun the following ddutil command to prune (delete) the backup files in the specified pathnamesthat were created (or later modified) during the time range specified by the -b and -e options:

ddutil -k -z <hostname>:<storage_unit> [-b <start_time>] [-e <end_time>] [-c] [-R] [-x] [-D <debug_level>] [<pathname1> [<pathname2>]...[<pathname><n>]]


The -k option specifies to delete from the Data Domain system the backup files based on theirage:

l If a specified pathname is a file, the file is deleted if it meets the time criteria.

l If a specified pathname is a directory, all the files in the directory are deleted if they meet thetime criteria.



l If the -b and -e options are omitted, the files in the specified pathnames are deleted, withoutconsidering a time range.

NOTICEUse the ddutil -k <options> command with caution. After you delete certain backupfiles, you might be unable to restore data from a backup. Therefore, improper file deletion withthe ddutil command can lead to failed restores and data loss.

The deletion of backup files and directories cannot be undone.

When the -x option is specified, the ddutil command also deletes any empty directories that itfinds. Without the -x option, the directories are not deleted.

By default, the ddutil command prompts you before deleting any files. The command promptsfor every file to be deleted, but does not prompt for the removal of empty directories. The -coption specifies to perform the deletions without prompting.

The ddutil command ignores all subdirectories unless you specify the -R option. Without the -Roption, empty subdirectories are not deleted; only the current directory is deleted if it is empty ofall files and subdirectories after the prune operation.

Both of the following example commands prune all the backup files and empty directories that areolder than 30 days under dir1/subdir1 on the storage unit su1. The commands also prune thedirectory dir1/subdir1 itself:

ddutil -k -z host1:/su1 -e "-30 days" -R -x dir1/subdir1

ddutil -k -z host1:/su1 -e "now-30 days" -R -x dir1/subdir1

Oracle Incremental Merge operationsOracle RMAN agent 19.2 introduced support for Oracle Incremental Merge on Linux for bothstand-alone and Oracle RAC systems, leveraging the RMAN feature known as Oracle incrementallyupdated backups. Oracle incrementally updated backups enable you to create a full image copybackup of a database every day for the cost of an incremental backup, while providing therecovery benefits of image copy backups.

Note: Oracle Incremental Merge is the Dell EMC term for the group of Oracle RMAN agentfeatures that are implemented around Oracle incrementally updated backups.

The following table outlines the Oracle database versions, Data Domain versions, Linux operatingsystems, and Oracle cluster configurations that Oracle RMAN agent 19.3 supports for OracleIncremental Merge operations.

Table 9 Oracle RMAN agent version 19.3 compatibility matrix for Oracle Incremental Merge

Oracle databaseversions

Operatingsystems

Oracle clusterconfigurations

Data Domainsupport

Oracle 11gR2,12cR1, 12cR2, 18c,19c

Linux RHEL 7 Active-passive

Oracle RAC on all cluster filesystems supported by Oracle

BoostFS 1.3

DD Boost 7.0.1.0

DD OS 6.1, 6.2, 7.0

Oracle 11gR2,12cR1, 12cR2, 18c,19c

Linux SLES 12 Active-passive

Oracle RAC on all cluster filesystems supported by Oracle

BoostFS 1.3

DD Boost 7.0.1.0



Table 9 Oracle RMAN agent version 19.3 compatibility matrix for Oracle IncrementalMerge (continued)

Oracle databaseversions

Operatingsystems

Oracle clusterconfigurations

Data Domainsupport

DD OS 6.1, 6.2, 7.0

The following topics describe the supported Oracle Incremental Merge features, the requiredinstallation and configuration procedures, and how to perform the backups, restores, and othersupported operations with the Oracle RMAN agent.

Overview of Oracle Incremental Merge featuresWhen you first run an Oracle Incremental Merge backup of a database to a Data Domain storageunit, a full image copy backup is performed to begin the cycle of incremental updates. The secondand subsequent runs produce level 1 incremental backups of the database. After each incrementalbackup, the changed blocks are applied to the existing full backup to create an up-to-datesynthetic full backup. Being an image copy, the synthetic full backup is easier to restore than atraditional RMAN backup.

Traditional RMAN backups, as performed by Oracle RMAN agent prior to version 19.2, use theOracle SBT library to create backup sets. Oracle Incremental Merge backups use file system callsto create the Oracle image backups as exact copies of datafiles, which can be restored andbrought online quickly.

Oracle Incremental Merge operations with the Oracle RMAN agent provide the following benefits:

l Preservation of past backups

On a Data Domain storage unit, copies of files can be created almost instantly, and the copiesuse little space because they are deduplicated. The Oracle RMAN agent performs the followingsteps during an Oracle Incremental Merge backup:

1. Performs an Oracle incrementally updated backup.

2. Fast copies the backup from an MTree or directory to a new location on the same DataDomain system.

Note: Because the fast copy operation does not include any physical data movement,the operation is completed in minutes regardless of the size of the file, MTree, ordirectory.

3. Catalogs the backup in Oracle RMAN.

The next subsequent backup overwrites the backup in the original location on the storage unitbut not the backup copy in the new location. Therefore, a copy of the previous backup ispreserved, registered in RMAN and ready to restore.

l Automated mount and unmount of Data Domain storage units

Before an Oracle Incremental Merge backup or restore, the Oracle RMAN agent canautomatically mount the Data Domain storage unit. The Oracle RMAN agent can alsoautomatically unmount the storage unit after the operation. Limiting the mount times duringbackups and restores can reduce the risk of backup data theft or attack.

l Setting of retention locks

Oracle Incremental Merge operations leverage the Data Domain retention lock feature. Aretention lock prevents the backup files on a storage unit from being deleted or modified until aspecified retention period has passed. Retention locks protect the backups from the sameexternal threats as automated mount and unmount operations, and also prevent the damage of



backup files locally. Before you can delete or modify the backup files, you must remove theretention lock.

Note: You must not set any type of Oracle retention policy on Oracle Incremental Mergebackups, such as a redundancy based or recovery window based policy.

Oracle Incremental Merge operations require the installation of Data Domain BoostFS on theapplication host, to provide a standard file system mount point to the application. With directaccess to the BoostFS mount point, the application can leverage the storage and networkefficiencies of the DD Boost protocol for backups and restores.

Note: An Oracle Incremental Merge backup of a pfile based Oracle database is not supported.You can create an spfile from the pfile and then perform the Oracle Incremental Mergebackup.

Oracle Incremental Merge supports the following operations:

l Full backups—A full backup creates a full copy of the database plus archive logs, and storesthe copy on the Data Domain storage unit. The full copy is used with an incremental backup tocreate a new synthetic full backup. Backups are protected by a Data Domain retention lock.

l Incremental backups—An incremental backup backs up the changed data blocks, which areapplied to the previous full backup to create a new synthetic full backup. This synthetic fullbackup is stored in a new location and then cataloged and protected by a Data Domainretention lock.

l Archive log backups—The Oracle database archive logs are backed up during the full andincremental backups. The Oracle Incremental Merge feature provides an option to back up onlythe archive logs. The archive log backups are protected by a Data Domain retention lock.

l Control file backups—The control file is backed up with the full, incremental, and archive logbackups. The Oracle Incremental Merge feature provides an option to back up only the controlfile. The control file backups are protected by a Data Domain retention lock.

l Cleanup operations—The Oracle Incremental Merge feature provides an option to perform acleanup operation that removes the copies of any failed backups to free up space on the DataDomain system.

l Restore operations—You can restore the RMAN backups through RMAN scripts that you runthrough the Oracle Incremental Merge binary.

l Mount operations—An Oracle Incremental Merge backup performs open and write operationsto a local disk or NFS mount. The storage unit is mounted by using a Data Domain BoostFSFUSE mount operation, and backups are performed on the mounted storage unit.

l Unmount operations—An Oracle Incremental Merge operation unmounts the storage unit fromthe local mount path by using a Data Domain BoostFS FUSE mount operation.

l Live mount operations—A live mount operation is a live migration of the database by using theimage-based backup copies.

l Proxy restore operations—A proxy restore operation restores a backup to a new host by usingthe image-based backup copies.

Installation requirements for Oracle Incremental MergeEnsure that you complete the following installation procedures and then the configurationprocedures in the next topic before you perform any Oracle Incremental Merge operations.

Procedure

1. Ensure that you have completed the installation of the Oracle RMAN agent software onLinux according to the procedures outlined in this chapter.

The following Oracle RMAN agent files are installed for the Oracle Incremental Mergeoperations:



l ddbmoim binary in directory $RMAN_AGENT_HOME/binl rman_agent_oim.cfg configuration file template in directory $RMAN_AGENT_HOME/

config

2. Ensure that you meet the Data Domain BoostFS requirements as described in the latestversion of the Dell EMC Data Domain BoostFS Configuration Guide, available on the Supportwebsite at https://support.emc.com.

3. Download the Data Domain BoostFS software package from the Support website at https://support.emc.com to a temporary local directory.

4. Uncompress the downloaded software file by running the following command:

$ tar -vxf <BoostFS_package_name>.tar

5. Install the Data Domain BoostFS software by running the following command as the rootuser:

# rpm -ivh <BoostFS_package_name>.rpm

6. Create a storage unit on the Data Domain system to be used for Oracle Incremental Mergebackups.

Note: Before you run the Oracle Incremental Merge backups for the first time, ensurethat you create a Data Domain storage unit.

7. Create a mount point on the Oracle host, and assign valid permissions similar to an Oracleuser on the host.

8. Enable the retention lock feature on the Data Domain storage unit by running the followingtype of command as the root user. This example command sets a maximum retention periodof 90 days for the MTree /data/col1/oim:

# mtree retention-lock set max-retention-period 90days mtree /data/col1/oim

9. Verify that the retention lock is enabled by running the following type of command as theroot user:

# mtree list /data/col1/oim

Configuration requirements for Oracle Incremental MergeBefore you perform any Oracle Incremental Merge operations, complete the configurationprocedures as described in the following topics. You must set the required parameters for OracleIncremental Merge operations, either through the ddbmoim command options or through theparameter settings in the configuration file. You must also register the Data Domain Boostcredentials and Data Domain BoostFS credentials in the lockbox.

Note: Prior to performing the configuration procedures, ensure that you have met theinstallation requirements as described in the preceding topic.






Setting the configuration file parametersTo meet the configuration requirements, you can set the parameters in the Oracle IncrementalMerge configuration file. Customize the parameter settings in the configuration file templaterman_agent_oim.cfg, which is stored in the $RMAN_AGENT_HOME/config directory by theOracle RMAN agent installation on Linux.

The uninstall of the product software removes the original configuration file template. To createthe Oracle Incremental Merge configuration file, it is recommended that you copy and rename theconfiguration file template, either in the same directory or a different directory.

Note:Each parameter in the configuration file corresponds to a command-line option of theddbmoim command. You run the ddbmoim command to perform many of the OracleIncremental Merge operations. The command-line options take precedence over theconfiguration file parameters.

As an alternative to setting the parameters in the configuration file, you can specify theappropriate command-line options when you run the ddbmoim command. Performing theOracle Incremental Merge operations on page 103 provides details about the ddbmoimcommand and its options.

The Oracle Incremental Merge configuration file contains two types of sections in which you setthe parameters, the general section and the database-specific sections:

l The general section of the configuration file begins with the [GENERAL] heading. You can setthe following parameters in the general section:

BOOSTFS_INSTALL_DIRCLIENTDEBUG_LEVELRMAN_AGENT_HOME

Note: Instead of setting these parameters in the general section of the configuration file,you can specify the corresponding command-line options when you run the ddbmoimcommand. Performing the Oracle Incremental Merge operations on page 103 providesdetails about the ddbmoim command and its options.

For example, the following general section of the configuration file shows the parametersettings. Table 10 on page 97 provides details about the parameters that you can set in theconfiguration file.

############################################################################### General Parameters##############################################################################[GENERAL]BOOSTFS_INSTALL_DIR = /opt/emc/boostfs/CLIENT = ClientHostNameDEBUG_LEVEL = 3RMAN_AGENT_HOME = /home/oracle/opt/dpsapps/rmanagent/

l Each database-specific section of the configuration begins with the [SID_<name>] heading.You must add a separate database-specific section in the configuration file for each database.Replace <name> in SID_<name> with the Oracle SID of the database. In an Oracle RACenvironment, replace <name> with the local instance name of the database. After the



[SID_<name>] heading, add the settings for the following parameters as needed for theparticular database:

BACKUP_HOSTBACKUP_PATHDELETE_ARCHIVELOGDELETE_ARCHIVELOG_NUM_DAYSFORCE_LIVEMOUNT_CLEANUPMOUNT_PATHNFS_MOUNTOIM_TAGOPERATIONORACLE_BASE_PATHORACLE_HOMEORACLE_VERSION_11GPARALLELISMRETENTIONRMAN_CATALOG_SERVICERMAN_CATALOG_USERSCRIPT_PATHSTORAGE_UNITSYSBACKUPTEMP_DATABASE_PATHTEMP_SNAPSHOT_PATHTNS_ADMIN

Note: Instead of setting these parameters in the database-specific section of theconfiguration file, you can specify the corresponding command-line options when you runthe ddbmoim command. Performing the Oracle Incremental Merge operations on page 103provides details about the ddbmoim command and its options.

For example, the following database-specific section of the configuration file shows theparameter settings for the database with Oracle SID orcl. Table 10 on page 97 providesdetails about the parameters that you can set in the configuration file.

############################################################################### 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.# For RAC systems, the name should be the local instance name of the# database.##############################################################################[SID_orcl]BACKUP_HOST = DataDomainServerNameDELETE_ARCHIVELOG = TRUEDELETE_ARCHIVELOG_NUM_DAYS = 3MOUNT_PATH = /MountPathOIM_TAG = INCR_MERGEOPERATION = fullORACLE_HOME = /oracle/product/12.2.0.1/db_1PARALLELISM = 4RETENTION = 10 day# RMAN_CATALOG_SERVICE =# RMAN_CATALOG_USER =# SCRIPT_PATH =STORAGE_UNIT = StorageUnitSYSBACKUP = FALSE# TNS_ADMIN =

The following table describes all the configuration parameters that you can set in the OracleIncremental Merge configuration file. To set a parameter in the configuration file, such as



BACKUP_HOST, remove the # symbol at the start of the parameter line and add the parametervalue after the equal sign (=).

Table 10 Configuration file parameters for Oracle Incremental Merge

Parameter Description Default and valid values

BACKUP_HOST Mandatory in [SID_<name>] section.

Specifies the hostname of the DataDomain server to use for backups.


l Valid hostname of the Data Domainserver.

BACKUP_PATH Mandatory in [SID_<name>] section fora live mount or proxy restore operationthat uses the ddbmoim command.

Specifies the directory pathname of theincremental or full backup to berestored.


l Valid directory pathname of theincremental or full backup.

BOOSTFS_INSTALL_DIR Mandatory in [GENERAL] section.

Specifies the installation directory ofthe Data Domain BoostFS plug-in.


l Valid complete pathname of theData Domain BoostFS installationdirectory.

CLIENT Mandatory in [GENERAL] section.

Specifies the hostname of the localclient to use to store the backups onthe Data Domain system.

Note: Set this parameter to thesame value for each node in anOracle RAC environment.


l Valid hostname of the local client.

DEBUG_LEVEL Optional in [GENERAL] section.

Specifies the level of debug messagesthat the Oracle Incremental Mergeoperation generates.

l 0 (default) = Debug messages arenot generated.

l 1 to 9 = Debug messages arewritten to the debug log file. Thelevel of detail in the generateddebug messages increases with thedebug level. The debug log filename isddbmoim_<operation_type>.*.*.log, for example,ddbmoim_full.14928.1567760357.log.

DELETE_ARCHIVELOG Optional in [SID_<name>] section.

Specifies whether to delete the archivelog after it is backed up.

l FALSE (default) = The archive logis not deleted.

l TRUE = The archive log is deleted.

DELETE_ARCHIVELOG_NUM_DAYS

Optional in [SID_<name>] section. l Undefined (default). The archivelog is not deleted, unlessDELETE_ARCHIVELOG is set to

TRUE.



Table 10 Configuration file parameters for Oracle Incremental Merge (continued)


Specifies to delete the archive log whenit is older than the specified number ofdays.

l Integer number of days. Thearchive log is deleted after thenumber of days.

FORCE_LIVEMOUNT_CLEANUP

Optional in [SID_<name>] section.

Specifies whether to perform a forcecleanup operation to remove a livemounted database after a live mountrestore that uses the ddbmoimcommand.

You can perform this force cleanupafter a previous live mount cleanup(performed without this setting) failedto remove a live mounted database.

l FALSE (default) = A force cleanupoperation is not performed.

l TRUE = A force cleanup operationis performed.

MOUNT_PATH Mandatory in [SID_<name>] section.

Specifies the Data Domain BoostFSmount path on which the MTree ismounted.

Note: The Oracle user must havepermissions for the read, write, andexecute operations on the mountpath. The mount path must be thesame for all operations. Do notchange the mount path once it isset.


l Valid mount path of Data DomainBoostFS.

NFS_MOUNT Mandatory in [SID_<name>] section fora live mount restore that uses theddbmoim command and an NSF mount.

Specifies whether to use a BoostFSmount or NSF mount for the live mountrestore with the ddbmoim command.

l FALSE (default) = Use a BoostFSmount for the live mount restore.

l TRUE = Use an NFS mount for thelive mount restore.

OIM_TAG Mandatory in [SID_<name>] section.

Specifies the tag that is applied to thebackup copies.

Note: The backup tag is used whenthe incrementally updated backupsare applied to full backups, toidentify which incremental backupsapply to which working imagecopies. The backup tag must be thesame for the full and incrementalbackups.


l Tag that is applied to the backupcopies, for example,INCR_MERGE.





OPERATION Mandatory in [SID_<name>] section.

Specifies the type of OracleIncremental Merge operation that isperformed.

l full = Creates a full backup copy ofthe database, archive logs, andcontrol file.

l arch = Backs up the archive logsand control file.

l cleanup = Removes the copies ofany failed backups.

l ctl = Backs up the control file only.

l incr = Backs up the changed datablocks, archive logs, and controlfile.

l livemount = Performs a live mountrestore that uses the ddbmoimcommand.

l livemount-cleanup = Removes thelive mounted database after a livemount restore that uses theddbmoim command.

l mount = Mounts the Data Domainstorage unit on the mount pathspecified by MOUNT_PATH by using

a BoostFS FUSE mount operation.

l proxy-restore = Performs a proxyrestore that uses the ddbmoimcommand.

l restore = Restores the backup byusing the RMAN restore scriptspecified by SCRIPT_PATH.

l unmount = Unmounts the DataDomain storage unit by using aBoostFS FUSE mount operation.

ORACLE_BASE_PATH Mandatory in [SID_<name>] section fora live mount or proxy restore operationthat uses the ddbmoim command.

Specifies the base pathname of theOracle installation directory.


l Valid base pathname of the Oracleinstallation directory.

ORACLE_HOME Mandatory in [SID_<name>] section.

Specifies the pathname of the Oracleinstallation directory.


l Valid complete pathname of theOracle installation directory.

ORACLE_VERSION_11G Mandatory in [SID_<name>] sectionwhen the Oracle database is version 11.

l FALSE (default) = Oracle databaseis not version 11.





Specifies whether the Oracle databaseis version 11.

Note: Ensure that this parameter isset to TRUE before you perform anOracle Incremental Mergeoperation with an Oracle 11database.

l TRUE = Oracle database is version11.

PARALLELISM Optional in [SID_<name>] section.

Specifies the number of channels thatRMAN allocates in parallel for thebackup.

l 4 (default).

l Integer number of channels.

RETENTION Optional in [SID_<name>] section.

Specifies the retention policy as thelength of time that RMAN retains thebackup copies.

A retention lock is applied for a backupwhen the storage unit is retentionenabled and this parameter is set.

Note: Do not set any type of Oracleretention policy, such as aredundancy based or recoverywindow based policy. You must usethe ddutil commands for backup

deletion, as described in Using theddutil command to list and deletethe backups on page 114.


l Integer number and one of thefollowing values, surrounded bydouble quotes:

n decade

n year

n quarter

n month

n fortnight

n week

n day

n hour

n minute

n min

n seconds

n sec

For example: RETENTION = "4 month".Note: The minimum setting is "12hour". The maximum setting is "70year".

RMAN_AGENT_HOME Mandatory in [GENERAL] section.

Specifies the installation directory ofthe Oracle RMAN agent.

l $HOME/opt/dpsapps/rmanagent(default).

l Valid complete pathname of theOracle RMAN agent installationdirectory.

RMAN_CATALOG_SERVICE Optional in [SID_<name>] section. l Undefined (default).





Specifies the Net service or EasyConnect name of the RMAN catalogdatabase.

To ensure that the specified name iscorrect, run the following command atthe command line:

rman catalog <RMAN_catalog_username>/<password>@<RMAN_catalog_service_name>

l Valid Net service or Easy Connectname of the RMAN catalogdatabase.

RMAN_CATALOG_USER Mandatory in [SID_<name>] sectionwhen the RMAN catalog database isused and RMAN_CATALOG_SERVICE is

set.

Specifies the username of the RMANcatalog database.


l Valid username of the RMANcatalog database.

SCRIPT_PATH Mandatory in [SID_<name>] section fora restore operation.

Specifies the pathname of the restorescript.


l Valid complete pathname of therestore script.

STORAGE_UNIT Mandatory in [SID_<name>] section.

Specifies the name of the storage unitor a top-level directory within thestorage unit on the Data Domainsystem.


l Valid directory name of the storageunit on the Data Domain system,without the /data/col1 prefix.

The specified name is case-sensitive.

SYSBACKUP Optional in [SID_<name>] section.

Specifies whether to use SYSBACKUPor SYSDBA for the RMAN connection.

l FALSE (default) = RMAN isconnected by using SYSDBA.

l TRUE = RMAN is connected byusing SYSBACKUP.

TEMP_DATABASE_PATH Mandatory in [SID_<name>] section fora live mount or proxy restore operationthat uses the ddbmoim command.

Specifies the pathname of a temporarydirectory that will be used during thelive mount or proxy restore.


l Valid pathname of a temporarydirectory.

TEMP_SNAPSHOT_PATH Mandatory in [SID_<name>] section fora force cleanup operation to beperformed after a live mount restorethat uses the ddbmoim command.


l Valid pathname of the temporarysnapshot directory that was usedduring the live mount restore.





Specifies the pathname of thetemporary snapshot directory that wasused during the live mount restore.

TNS_ADMIN Optional in [SID_<name>] section.

Specifies the directory pathname of theOracle Net configuration files.


l Valid complete pathname of thedirectory that contains the OracleNet configuration files. This valuemust the same as the Oracleparameter TNS_ADMIN setting.

Registering the lockbox credentialsTo meet the configuration requirements, you must also run the ddutil -C command to registerthe Data Domain Boost credentials in the BoostFS lockbox. This registration task is required onlyonce for each separate storage unit to be used on the same Data Domain system. Do not run theregistration command for each backup.

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

The type of ddutil -C command that you must run depends on whether you have previouslyregistered the Data Domain Boost credentials in the lockbox:

l If you have not previously registered the Data Domain Boost credentials for the Data Domainsystem, run either of the following commands:

n To specify the Data Domain server, storage unit, and DD Boost user on the command line,run the following command. The command prompts for only the user password:

ddutil -C -a USER_TYPE=DD_BOOST_USER -a BOOSTFS=TRUE -a DD_SERVER_NAME=<Data_Domain_server_name> -a DD_STORAGE_UNIT=<storage_unit_name> -a USERNAME=<username> -a VERIFY_CREDENTIAL=TRUE

Password: <password>Re-enter password: <password>Successfully set the DD Boost FS credentials in the lockbox.Successfully set the DD Boost credentials in the lockbox.

n To specify the minimum options on the command line, run the following command. Thecommand prompts for the Data Domain server, storage unit, DD Boost user, and password:

ddutil -C -a USER_TYPE=DD_BOOST_USER -a BOOSTFS=TRUE

Data Domain server name: <Data_Domain_server_name>Data Domain Storage Unit name: <storage_unit_name>DD Boost username: <username>Password: <password>Re-enter password: <password>



Successfully set the DD Boost FS credentials in the lockbox.Successfully set the DD Boost credentials in the lockbox.

l If you have previously registered the Data Domain Boost credentials for the Data Domainsystem, run either of the following commands:

n To specify the Data Domain server and storage unit on the command line, run the followingcommand:

ddutil -C -a USER_TYPE=DD_BOOST_USER -a BOOSTFS=TRUE -a BOOSTFS_LOCKBOX_UPDATE=TRUE -a DD_SERVER_NAME=<Data_Domain_server_name> -a DD_STORAGE_UNIT=<storage_unit_name> -a VERIFY_CREDENTIAL=TRUE

Successfully set the DD Boost FS credentials in the lockbox.Successfully set the DD Boost credentials in the lockbox.

n To specify the minimum options on the command line, run the following command. Thecommand prompts for the Data Domain server and storage unit:

ddutil -C -a USER_TYPE=DD_BOOST_USER -a BOOSTFS=TRUE -a BOOSTFS_LOCKBOX_UPDATE=TRUE

Data Domain server name: <Data_Domain_server_name>Data Domain Storage Unit name: <storage_unit_name>Successfully set the DD Boost FS credentials in the lockbox.Successfully set the DD Boost credentials in the lockbox.

l If the RMAN catalog is configured, run the following command to register the catalog user andpassword in the lockbox:

ddutil -C -a USER_TYPE=DATABASE_ADMIN -a DATABASE_SIDS=<RMAN_catalog_service_name> -a USERNAME=<RMAN_catalog_username>

For example:

ddutil -C -a USER_TYPE=DATABASE_ADMIN -a DATABASE_SIDS=SHC -a USERNAME=sysPassword:Re-enter password:Successfully set the Oracle database administrator credentials in the lockbox.

Performing the Oracle Incremental Merge operationsYou can run the ddbmoim command to perform the Oracle Incremental Merge mount, unmount,backup, restore, and cleanup operations. In an Oracle RAC environment, you can run the commandon any Oracle database RAC node. You must run the ddutil command to list and delete thebackups. You can run the live mount and proxy restore operations by using either the ddbmoimcommand or other commands.

Using the ddbmoim command for mount, unmount, backup, cleanup, and restore operationsYou must run the ddbmoim command with appropriate options as the Oracle user on Linux. Theonly mandatory option is --dbname <database_name>, where <database_name> is the Oracle SIDof the database. In an Oracle RAC environment, replace <database_name> with the local instancename of the database.

If you set any parameters in the Oracle Incremental Merge configuration file, you must include the-z <configuration_file_path> option on the ddbmoim command line; otherwise, you can omit the -z <configuration_file_path> option. For every other option, you can either specify the option on



the command line or set the corresponding parameter setting in the Oracle Incremental Mergeconfiguration file.

Note: The command-line options take precedence over the parameter settings in theconfiguration file. Setting the configuration file parameters on page 95 provides details aboutthe configuration file parameters.

The ddbmoim command options in curly braces ({ }) are mandatory. The command options inbrackets ([]) are optional:

ddbmoim --dbname <database_name> [-c <client_hostname>] [-d <Data_Domain_server_name>] [-D <debug_level>] [-m <mount_path>] [-o {full|incr|arch|ctl|livemount|livemount-cleanup|mount|unmount|proxy-restore|restore|cleanup}] [-s <storage_unit_name>] [-t <backup_tag>] [-z <configuration_file_path>] [-a BACKUP_PATH=<dir_path>] [-a BOOSTFS_INSTALL_DIR=<dir_path>] [-a DELETE_ARCHIVELOG={FALSE|TRUE}] [-a DELETE_ARCHIVELOG_NUM_DAYS=<number_of_days>] [-a FORCE_LIVEMOUNT_CLEANUP={FALSE|TRUE}] [-a NFS_MOUNT={FALSE|TRUE}] [-a ORACLE_BASE_PATH=<dir_path>] [-a ORACLE_HOME=<pathname>] [-a ORACLE_VERSION_11G={FALSE|TRUE}] [-a PARALLELISM=<number>] [-a RETENTION=<value>] [-a RMAN_AGENT_HOME=<dir_path>] [-a RMAN_CATALOG_SERVICE=<service_name>] [-a RMAN_CATALOG_USER=<username>] [-a SCRIPT_PATH=<script_path>] [-a SYSBACKUP={FALSE|TRUE}] [-a TEMP_DATABASE_PATH=<dir_path>] [-a TEMP_SNAPSHOT_PATH=<dir_path>] [-a TNS_ADMIN=<dir_path>]

The following table describes the ddbmoim command options and the corresponding parametersthat you can set in the configuration file. To obtain a list of all the available command options, runthe command ddbmoim --help or ddbmoim -h.

Examples of ddbmoim commands for Oracle Incremental Merge operations on page 112 providesmore information about ddbmoim commands for the supported Oracle Incremental Mergeoperations.

Table 11 The ddbmoim command options for Oracle Incremental Merge operations

Command option Description Default and valid values

-c <client_hostname> Mandatory if you do not set theCLIENT parameter in the

configuration file.

Specifies the hostname of the localclient to use to store the backups onthe Data Domain system.

Note: Use the same client namesetting for each node in anOracle RAC environment.

CLIENT is the corresponding

parameter in the configuration file.

Values of <client_hostname>:


l Valid hostname of the localclient.

-d <Data_Domain_server_name> Mandatory if you do not set theBACKUP_HOST parameter in the

configuration file.

Specifies the hostname of the DataDomain server to use for backups.

BACKUP_HOST is the corresponding


Values of<Data_Domain_server_hostname>:


l Valid hostname of the DataDomain server.

-D <debug_level> Optional. Values of <debug_level>:



Table 11 The ddbmoim command options for Oracle Incremental Merge operations (continued)


Specifies the level of debugmessages that the OracleIncremental Merge operationgenerates.

DEBUG_LEVEL is the corresponding


l 0 (default) = Debug messagesare not generated.

l 1 to 9 = Debug messages arewritten to the debug log file. Thelevel of detail in the generateddebug messages increases withthe debug level. The debug logfile name isddbmoim_<operation_type>.*.*.log, for example,ddbmoim_full.14928.1567760357.log.

-m <mount_path> Mandatory if you do not set theMOUNT_PATH parameter in the

configuration file.

Specifies the Data Domain BoostFSmount path on which the MTree ismounted.

Note: The Oracle user must havepermissions for the read, write,and execute operations on themount path. The mount pathmust be the same for alloperations. Do not change themount path once it is set.

MOUNT_PATH is the corresponding


Values of <mount_path>:


l Valid mount path of Data DomainBoostFS.

-o [full|incr|arch|ctl|

livemount|livemount-cleanup|

mount|unmount|proxy-restore|

restore|cleanup]

Mandatory if you do not set theOPERATION parameter in the

configuration file.

Specifies the type of OracleIncremental Merge operation that isperformed.

OPERATION is the corresponding


l full = Creates a full backup copyof the database, archive logs,and control file.

l arch = Backs up the archive logsand control file.

l cleanup = Removes the copies ofany failed backups.

l ctl = Backs up the control fileonly.

l incr = Backs up the changed datablocks, archive logs, and controlfile.

l livemount = Performs a livemount restore that uses theddbmoim command.

l livemount-cleanup = Removesthe live mounted database after





a live mount restore that usesthe ddbmoim command.

l mount = Mounts the DataDomain storage unit on themount path specified by the -moption or MOUNT_PATHparameter, by using a BoostFSFUSE mount operation.

l proxy-restore = Performs aproxy restore that uses theddbmoim command.

l restore = Restores the backup byusing the RMAN restore scriptspecified by the -aSCRIPT_PATH option or

SCRIPT_PATH parameter.

l unmount = Unmounts the DataDomain storage unit by using aBoostFS FUSE mount operation.

-s <storage_unit_name> Mandatory if you do not set theSTORAGE_UNIT parameter in the

configuration file.

Specifies the name of the storageunit or a top-level directory withinthe storage unit on the Data Domainsystem.

STORAGE_UNIT is the corresponding


Values of <storage_unit_name>:


l Valid directory name of thestorage unit on the Data Domainsystem, without the /data/col1 prefix. The name is case-

sensitive.

-t <backup_tag> Mandatory if you do not set theOIM_TAG parameter in the

configuration file.

Specifies the tag that is applied tothe backup copies.

Note: The backup tag is usedwhen the incrementally updatedbackups are applied to fullbackups, to identify whichincremental backups apply towhich working image copies. Thebackup tag must be the same forthe full and incremental backups.

OIM_TAG is the corresponding


Values of <backup_tag>:


l Tag that is applied to the backupcopies, for example,INCR_MERGE.





-z <configuration_file_path> Mandatory if you set any parametersin the configuration file as describedin Setting the configuration fileparameters on page 95.

Specifies the pathname of theconfiguration file that contains theparameter settings for the OracleIncremental Merge operations.

Note: If you do not set anyparameters in a configuration file,you can omit this option.

Values of <configuration_file_path>:


l Valid complete pathname of theOracle Incremental Mergeconfiguration file.

-a BACKUP_PATH=<dir_path> Mandatory if you do not set theBACKUP_PATH parameter in the

configuration file for a live mount orproxy restore that uses the ddbmoimcommand.

Specifies the directory pathname ofthe incremental or full backup to berestored.

BACKUP_PATH is the corresponding


Values of <dir_path>:


l Valid directory pathname of theincremental or full backup.

-a BOOSTFS_INSTALL_DIR=<dir_path>

Mandatory if you do not set theBOOSTFS_INSTALL_DIR parameter

in the configuration file.

Specifies the installation directory ofthe Data Domain BoostFS plug-in.

BOOSTFS_INSTALL_DIR is the

corresponding parameter in theconfiguration file.



l Valid complete pathname of theData Domain BoostFS installationdirectory.

-a DELETE_ARCHIVELOG={FALSE|

TRUE}

Optional.

Specifies whether to delete thearchive log after it is backed up.

DELETE_ARCHIVELOG is the


l FALSE (default) = The archivelog is not deleted.

l TRUE = The archive log isdeleted.

-aDELETE_ARCHIVELOG_NUM_DAYS=<number_of_days>

Optional.

Specifies to delete the archive logwhen it is older than the specifiednumber of days.

Values of <number_of_days>:

l Undefined (default). The archivelog is not deleted, unless the -aDELETE_ARCHIVELOG option orDELETE_ARCHIVELOG_NUM_DAYS parameter is set to TRUE.





DELETE_ARCHIVELOG_NUM_DAYSis the corresponding parameter in theconfiguration file.

l Integer number of days. Thearchive log is deleted after thenumber of days.

-a FORCE_LIVEMOUNT_CLEANUP={FALSE|TRUE}

Optional.

Specifies whether to perform a forcecleanup operation to remove a livemounted database after a live mountrestore that uses the ddbmoimcommand.

You can perform this force cleanupafter a previous live mount cleanup(performed without this setting)failed to remove a live mounteddatabase.

FORCE_LIVEMOUNT_CLEANUP is the


l FALSE (default) = A forcecleanup operation is notperformed.

l TRUE = A force cleanupoperation is performed.

-a NFS_MOUNT={FALSE|TRUE} Mandatory if you do not set theNSF_MOUNT parameter to TRUE in

the configuration file for a live mountrestore that uses the ddbmoimcommand and an NSF mount.

Specifies whether to use a BoostFSmount or NSF mount for the livemount restore with the ddbmoimcommand.

NSF_MOUNT is the corresponding


l FALSE (default) = Use aBoostFS mount for the livemount restore.

l TRUE = Use an NFS mount forthe live mount restore.

-a ORACLE_BASE_PATH=<dir_path>

Mandatory if you do not set theORACLE_BASE_PATH parameter in

the configuration file for a live mountor proxy restore that uses theddbmoim command.

Specifies the base pathname of theOracle installation directory.

ORACLE_BASE_PATH is the




l Valid base pathname of theOracle installation directory.

-a ORACLE_HOME=<pathname> Mandatory if you do not set theORACLE_HOME parameter in the

configuration file.

Values of <pathname>:


l Valid complete pathname of theOracle installation directory.





Specifies the pathname of the Oracleinstallation directory.

ORACLE_HOME is the corresponding


-a ORACLE_VERSION_11G={FALSE|TRUE}

Mandatory if you do not setORACLE_VERSION_11G to TRUE in

the configuration file when theOracle database is version 11.

Specifies whether the Oracledatabase is version 11.

Note: Ensure that this option isset to TRUE before you performan Oracle Incremental Mergeoperation with an Oracle 11database.

ORACLE_BASE_PATH is the


l FALSE (default) = Oracledatabase is not version 11.

l TRUE = Oracle database isversion 11.

-a PARALLELISM=<number> Optional.

Specifies the number of channelsthat RMAN allocates in parallel forthe backup.

PARALLELISM is the corresponding


Values of <number>:

l 4 (default).

l Integer number of channels.

-a RETENTION=<value> Optional.

Specifies the retention policy as thelength of time that RMAN retains thebackup copies.

A retention lock is applied for abackup when the storage unit isretention enabled and this option isspecified.

Note: Do not set any type ofOracle retention policy, such asredundancy based or recoverywindow based. You must use theddutil commands for backup

deletion, as described in Usingthe ddutil command to list anddelete the backups on page 114.

RETENTION is the corresponding


Values of <value>:


l Integer number plus one of thefollowing values, surrounded bydouble quotes:

n decade

n year

n quarter

n month

n fortnight

n week

n day

n hour

n minute

n min





n seconds

n sec

For example: -a RETENTION="4month".

Note: The minimum setting is "12hour". The maximum setting is"70 year".

-a RMAN_AGENT_HOME=<dir_path> Mandatory if you do not set theRMAN_AGENT_HOME parameter in

the configuration file.

Specifies the installation directory ofthe Oracle RMAN agent.

RMAN_AGENT_HOME is the



l $HOME/opt/dpsapps/rmanagent (default).

l Valid complete pathname of theOracle RMAN agent installationdirectory.

-a RMAN_CATALOG_SERVICE=<service_name>

Optional.

Specifies the Net service or EasyConnect name of the RMAN catalogdatabase.

To ensure that the specified name iscorrect, run the following commandat the command line:

rman catalog <RMAN_catalog_username>/<password>@<RMAN_catalog_service_name>

RMAN_CATALOG_SERVICE is the


Values of <service_name>:


l Valid Net service or EasyConnect name of the RMANcatalog database.

-a RMAN_CATALOG_USER=<username>

Mandatory if you do not set theRMAN_CATALOG_USER parameter

but the RMAN catalog database isused and either the -aRMAN_CATALOG_SERVICE option is

specified or theRMAN_CATALOG_SERVICEparameter is set.

Specifies the username of the RMANcatalog database.

Values of <username>:


l Valid username of the RMANcatalog database.





RMAN_CATALOG_USER is the


-a SCRIPT_PATH=<script_path> Mandatory for a restore if you do notset the SCRIPT_PATH parameter in

the configuration file.

Specifies the pathname of therestore script.

SCRIPT_PATH is the corresponding


Values of <script_path>:


l Valid complete pathname of therestore script.

-a SYSBACKUP={FALSE|TRUE} Optional. Specifies whether to useSYSBACKUP or SYSDBA for theRMAN connection.

SYSBACKUP is the corresponding


l FALSE (default) = RMAN isconnected by using SYSDBA.

l TRUE = RMAN is connected byusing SYSBACKUP.

-a TEMP_DATABASE_PATH=<dir_path>

Mandatory if you do not setTEMP_DATABASE_PATH in the

configuration file for a live mount orproxy restore operation that uses theddbmoim command.

Specifies the pathname of atemporary directory that will be usedduring the live mount or proxyrestore.

TEMP_DATABASE_PATH is the




l Valid pathname of a temporarydirectory.

-a TEMP_SNAPSHOT_PATH=<dir_path>

Mandatory if you do not setTEMP_SNAPSHOT_PATH in the

configuration file for a force cleanupoperation to be performed after a livemount restore that uses theddbmoim command.

Specifies the pathname of thetemporary snapshot directory thatwas used during the live mountrestore.

TEMP_SNAPSHOT_PATH is the




l Valid pathname of the temporarysnapshot directory that was usedduring the live mount restore.

-a TNS_ADMIN=<dir_path> Optional. Values of <dir_path>:





Specifies the directory pathname ofthe Oracle Net configuration files.

TNS_ADMIN is the corresponding



l Valid complete pathname of thedirectory that contains theOracle Net configuration files.This value must the same as theOracle parameter TNS_ADMINsetting.

Examples of ddbmoim commands for Oracle Incremental Merge operationsThis topic includes examples of the ddbmoim commands for the mount, unmount, backup,cleanup, and restore operations.

Note:For every ddbmoim command option except --dbname <database_name> and -z<configuration_file_path>, you can set the corresponding parameter in the configuration fileinstead of specifying the option on the command line. For example, if you use all the possibleparameter settings instead of command options, then you can run the following minimalcommand:

ddbmoim --dbname <database_name> -z <configuration_file_path>

The following topics provide examples of ddbmoim commands for the live mount restores and therestores to a proxy host:

l Performing an automated live mount restore by using a BoostFS mount on page 118

l Performing an automated live mount restore by using an NFS mount on page 119

l Performing an automated proxy host restore by using a BoostFS mount on page 127

l Performing an automated proxy host restore by using an NFS mount on page 128

Review the following information about ddbmoim commands for Oracle Incremental Mergeoperations:

l Mount operation—The following example ddbmoim command performs a mount operation:

ddbmoim --dbname orcl -o mount -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE

l Unmount operation—The following example ddbmoim command performs an unmountoperation:

ddbmoim --dbname orcl -o unmount -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit

l Full backup—You must create a full backup before any other type of backup. A full backupcreates a full copy of the database in the working directory, /<mount_path>/<hostname>/



<database_SID>/full/datafile on the Data Domain storage unit. This working copy is backed upand cataloged in the directory /<mount_path>/<hostname>/<database_SID>/full/datafile.OIM_TAG<timestamp>. The backup is retention locked as required, and the status isupdated in the tag file. Every full backup cleans up the working directory and creates a freshcopy of the datafiles.

The following example ddbmoim command performs a full backup:

ddbmoim --dbname orcl -o full -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RETENTION="10 day" -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE

l Incremental backup—You can only perform an incremental backup after a successful fullbackup. Incremental backup pieces are copied to the directory /<mount_path>/<hostname>/<database_SID>/incr on the Data Domain storage unit. These pieces are applied to the fullbackup in the working directory, and a backup of the working directory is created in thedirectory /<mount_path>/<hostname>/<database_SID>/full/datafile.OIM_TAG<timestamp>.The backup is retention locked as required, and the status is updated in the tag file.

The following example ddbmoim command performs an incremental backup:

ddbmoim --dbname orcl -o incr -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RETENTION="10 day" -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE

l Archive log backup—An archive log backup is stored in the directory /<mount_path>/<hostname>/<database_SID>/archivelogs on the Data Domain storage unit. The backup copyof the archive log is retention locked as required.

The following example ddbmoim command performs an archive log backup:

ddbmoim --dbname orcl -o arch -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RETENTION="10 day" -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE

l Control file backup—A control file backup is stored in the directory /<mount_path>/<hostname>/<database_SID>/controlfile on the Data Domain storage unit. The backup copyof the control file is retention locked as required.

The following example ddbmoim command performs a control file backup:

ddbmoim --dbname orcl -o ctl -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RETENTION="10 day" -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE

l Cleanup operation—The following example ddbmoim command performs a cleanup operation:

ddbmoim --dbname orcl -o cleanup -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE



l The following example ddbmoim command performs a restore operation:

ddbmoim --dbname orcl -o restore -m /MountPath -a BOOSTFS_INSTALL_DIR=/opt/emc/boostfs -a ORACLE_HOME=/oracle/product/12.2.0.1/db_1 -a RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent -a SCRIPT_PATH=/opt/restore/oim_restore_script -c ClientName -d DataDomainServerName -s StorageUnit -t INCR_MERGE

An Oracle Incremental Merge restore operation involves a sequence of procedural steps asdescribed in Performing the restore operations with RMAN scripts on page 116.

Using the ddutil command to list and delete the backupsYou must run the ddutil command with the appropriate command options to list and delete theOracle Incremental Merge backups.

The following ddutil command lists the information about the full, archive log, or control filebackups that are stored on the specified Data Domain storage unit:

ddutil -O oim -n {full|arch|ctl|tagfile} [-b "<start_time>"] [-e "<end_time>"] -f [-l] -z <Data_Domain_hostname_or_IP>:/<storage_unit> <Oracle_host>/<database_ID>

Note: The -l option lists the details of the available files.

For example:

l The following example ddutil command lists the available full backups:

ddutil -O oim -n full -f -z 10.31.140.154:/xapprman orcl/1542418608

mount: Mounting 10.31.140.154:xapprman on /home/oracle/opt/dpsapps/rmanagent/tmp/1567997099Type Perm Size Time Path--------------------------------------------------------------------------------------------------------------------dir 770 827 Tue Sep 3 20:05:51 2019 (1567521351) /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019131727dir 770 827 Tue Sep 3 20:00:42 2019 (1567521042) /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019131217dir 770 827 Tue Sep 3 14:41:24 2019 (1567501884) /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019075300dir 770 827 Tue Sep 3 14:28:29 2019 (1567501109) /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019074006

l The following example ddutil command lists the details of the available files in the fullbackups:

ddutil -O oim -n full -f -l -z 10.31.140.154:/xapprman orcl/1542418608

mount: Mounting 10.31.140.154:xapprman on /home/oracle/opt/dpsapps/rmanagent/tmp/1567997130

NAME : INCR_MERGE09032019131727DBID : 1542418608MOUNT PATH : /boostfsEXPIRATION : Wed Sep 4 13:18:11 2019CONTROL FILE : /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019131727/CONTROL_FILE.ctlSP FILE : /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019131727/SP_FILE.spfile



Type Perm Size Time Path--------------------------------------------------------------------------------------------------------------------dir 770 827 Tue Sep 3 20:05:51 2019 (1567521351) /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019131727file 640 5251072 Tue Sep 3 20:05:15 2019 (1567521315) /xapprman/orcl/1542418608/full/datafile.INCR_MERGE09032019131727/data_D-ORCL_I-1542418608_TSUSERS_FNO-7_49uaqkra_20190903 : :

l The following example ddutil command lists the full backups in the specified time range:

ddutil -O oim -n full -b "Sep 11" -e "Sep 13" -f -z 10.31.140.154:/xapprman orcl/1542915199

l The following example ddutil command lists the available archive log backups:

ddutil -O oim -n arch -f -z 10.31.140.154:/xapprman orcl/1542418608

l The following example ddutil command lists the archive log backups in the specified timerange:

ddutil -O oim -n arch -b "Sep 3 14:25:28 2019" -e "Sep 3 20:05:50 2019" -f -z 10.31.140.154:/xapprman orcl/1542418608

l The following example ddutil command lists the available control file backups:

ddutil -O oim -n ctl -c -z 10.31.140.154:/xapprman orcl/1542418608

l The following example ddutil command lists the available full backup summary:

ddutil -O oim -n tagfile -f -z 10.31.140.154:/xapprman orcl/1542418608

The following ddutil command deletes the full or archive log backups that are stored on thespecified Data Domain storage unit:

ddutil -O oim -n {full|arch} [-b "<start_time>"] [-e "<end_time>"] [-c] -d -z <Data_Domain_hostname_or_IP>:/<storage_unit> <Oracle_host>/<database_ID>

Note:Use only the ddutil command to delete the Oracle Incremental Merge backups. Do not usethe RMAN delete command or crosscheck command with Oracle Incremental Mergebackups.

Use the -c option for a forced deletion. If you do not use the -c option, the delete operationprompts for confirmation before deleting the backups.

For example:

l The following example ddutil command deletes the full backups:

ddutil -O oim -n full -d -z 10.31.140.154:/xapprman orcl/1542418608



l The following example ddutil command deletes the full backups in the specified time range:

ddutil -O oim -n full -b "Sep 11" -e "Sep 13" -d -z 10.31.140.154:/xapprman orcl/1542915199

l The following example ddutil command deletes the archive log backups:

ddutil -O oim -n arch -c -d -z 10.31.140.154:/xapprman orcl/1542418608

l The following example ddutil command deletes the archive log backups in the specified timerange:

ddutil -O oim -n arch -b "Sep 11" -e "Sep 13" -c -d -z 10.31.140.154:/xapprman orcl/1542915199

Performing the restore operations with RMAN scriptsTo enable an Oracle Incremental Merge restore of a database backup, create separate RMANscripts to restore the control file and database. After ensuring that the required configurations arecompleted, run the appropriate ddbmoim commands with the RMAN scripts to restore the controlfile and then restore the database.

Perform the following steps to complete an Oracle Incremental Merge restore of a databasebackup.

1. Log in to RMAN on the host where you will restore the control file and datafiles of thedatabase. To determine the control file from the RMAN catalog, run the following type ofcommand:

RMAN> LIST COPY OF CONTROLFILE TAG TESTDB09192019150043;

List of Control File Copies===========================Key S Completion Time Ckp SCN Ckp Time---- - --------------- ------- ---------------2402 A 19-SEP-19 3768293 19-SEP-19Name: /oraclemount/testdb_30/2800932625/full/datafile.testdb09192019150043/CONTROL_FILE.ctlTag: TESTDB09192019150043

2. Start the database in the nomount state:

RMAN> startup nomount;

3. Create an RMAN script to restore the control file. An example RMAN script is as follows:

connect target "/";set dbid=2800932625;run{ ALLOCATE CHANNEL CH0 DEVICE TYPE DISK;restore controlfile from "/oraclemount/testdb_30/2800932625/full/datafile.testdb09192019150043/CONTROL_FILE.ctl";RELEASE CHANNEL CH0;}



4. Ensure that the required configurations are completed, as described in the preceding topics.For example, include the following parameter settings in the configuration file:

OPERATION = restoreSCRIPT_PATH = <restore_script_pathname>

5. Run the appropriate ddbmoim command to perform the control file restore. For example, withall the parameters set in the configuration file, run the following command:

ddbmoim --dbname orcl -z /home/oracle/opt/dpsapps/rmanagent/config/rman_agent_oim.cfg

6. Determine the latest SCN of the datafiles. For example:

RMAN> select current_scn from v$database;

CURRENT_SCN

-----------

35127547. Create an RMAN script to restore the database. An example RMAN script is as follows:

connect target /run {ALLOCATE CHANNEL CH0 DEVICE TYPE DISK;ALLOCATE CHANNEL CH1 DEVICE TYPE DISK;ALLOCATE CHANNEL CH2 DEVICE TYPE DISK;ALLOCATE CHANNEL CH3 DEVICE TYPE DISK;set until scn 3512754;restore database;recover database;}alter database open resetlogs;

8. Ensure that the required configurations are completed. For example, include the followingparameter settings in the configuration file:

OPERATION = restoreSCRIPT_PATH = <restore_script_pathname>

9. Run the appropriate ddbmoim command to perform the database restore. For example, with allthe parameters set in the configuration file, run the following command:

ddbmoim --dbname orcl -z /home/oracle/opt/dpsapps/rmanagent/config/rman_agent_oim.cfg

Performing the live mount restore operationsYou can perform a live mount restore through either an automated method that uses the ddbmoimcommand or a manual method that uses a series of manual steps (without the ddbmoimcommand). Oracle RMAN agent 19.3 introduced the automated method with the ddbmoimcommand. Both the automated and manual methods can use either a BoostFS mount or an NFSmount.

The following topics describe all the supported methods of live mount restores.

Note:For a live mount restore, ensure that the Oracle username, group ID, and user ID are the sameon both the production host and the new host.



A live mount restore with the ddbmoim command applies only to the same-named database. Amanual live mount operation, as introduced with Oracle RMAN agent 19.2, applies to either thesame-named database or a different-named database.

When you perform a live mount restore with ASM enabled source database backups, therestored database is converted to a stand-alone database that is created using a pfile of thedatabase instance.

Performing an automated live mount restore by using a BoostFS mount

You can perform the following steps for an automated live mount restore that uses the ddbmoimcommand with a BoostFS mount.

1. Ensure that the target system (where the database will be live mounted) does not have thesame database name or database ID as the source database backups.

2. Specify the required parameter settings for the automated live mount restore through either ofthe following methods:

l Set the parameters in the configuration file, as described in Setting the configuration fileparameters on page 95.

or

l Set the parameters with the ddbmoim command-line options, as described in Using theddbmoim command for mount, unmount, backup, cleanup, and restore operations on page103.

You run the ddbmoim command in step 3.

For example, the configuration file includes the following parameter settings for the automatedlive mount restore, where orcl is the Oracle SID of the database. The NFS_MOUNT setting ofFALSE specifies a BoostFS mount:

[SID_orcl]BACKUP_HOST = 10.31.140.154DELETE_ARCHIVELOG = TRUEDELETE_ARCHIVELOG_NUM_DAYS = 1MOUNT_PATH = /oraclemountSTORAGE_UNIT = oimOIM_TAG = TEST_2OPERATION = livemountORACLE_HOME = /u01/app/oracle/product/19.0.0/dbhome_1# PARALLELISM =# RETENTION =# RMAN_CATALOG_SERVICE =# RMAN_CATALOG_USER =# SCRIPT_PATH =# SYSBACKUP =# TNS_ADMIN =NFS_MOUNT = FALSEBACKUP_PATH = /oim/orcl_streams/1269163748/full/datafile.stream11122019151615TEMP_DATABASE_PATH = /home/oracle/test1ORACLE_BASE_PATH = /u01/app/oracle# TEMP_SNAPSHOT_PATH =# FORCE_LIVEMOUNT_CLEANUP =# ORACLE_VERSION_11G =

3. To perform the automated live mount restore, run the ddbmoim command with theappropriate command options. For example:

ddbmoim --dbname orcl -z /opt/dpsapps/rmanagent/config/rman_agent_oim.cfg

Performing Oracle Incremental Merge operation.Starting BoostFS mount operation.Running the mount command. Mountpath: /oraclemount



BoostFS mount operation completed successfully.Creating a temp livemount directory '/oim/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557' of backup directory '/oim/orcl_streams/1269163748/full/datafile.stream11122019151615'.Building the livemount repository in temp path completed successfully.Live mount restore directory creation completed successfullyStarting PFile restore from SPFile '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557/SP_FILE.spfile'.PFile restored successfully to '/home/oracle/test1/orcl/initorcl.ora'.Starting control file restore /oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557/CONTROL_FILE.ctl.Control file '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557/CONTROL_FILE.ctl' restored successfully.Database 'orcl' Mounted successfully.Starting database 'orcl' open operationDatabase 'orcl' opened successfully.LiveMount of database 'orcl' done successfully.Oracle Incremental Merge operation completed successfully.

4. When the database is open, export the particular table from the temporary live mounteddatabase and then import it to the required database. For example, export TEST_TABLE fromthe orcl database and import to the BOOST database:

l Export command:

ORACLE_SID=orcl exp file=test.dmp tables=test_table rows=y

l Import command:

ORACLE_SID=BOOST imp file=test.dmp full=y

5. To remove the live mounted database, perform a cleanup operation with the ddbmoimcommand as described in Performing a cleanup of the live mount restored database on page121.

Performing an automated live mount restore by using an NFS mount

You can perform the following steps for an automated live mount restore that uses the ddbmoimcommand with an NFS mount.

1. Ensure that the target system (where the database will be live mounted) does not have thesame database name or database ID as the source database backups.

2. Specify the required parameter settings for the automated live mount restore through either ofthe following methods:


or



For example, the configuration file includes the following parameter settings for the automatedlive mount restore, where orcl is the Oracle SID of the database. The NFS_MOUNT setting ofTRUE specifies an NFS mount:

[SID_orcl]BACKUP_HOST = 10.31.140.154DELETE_ARCHIVELOG = TRUEDELETE_ARCHIVELOG_NUM_DAYS = 1



MOUNT_PATH = /oraclemountSTORAGE_UNIT = oimOIM_TAG = TEST_2OPERATION = livemountORACLE_HOME = /u01/app/oracle/product/19.0.0/dbhome_1# PARALLELISM =# RETENTION =# RMAN_CATALOG_SERVICE =# RMAN_CATALOG_USER =# SCRIPT_PATH =# SYSBACKUP =# TNS_ADMIN =NFS_MOUNT = TRUEBACKUP_PATH = /oim/orcl_streams/1269163748/full/datafile.stream11122019151615TEMP_DATABASE_PATH = /home/oracle/test1ORACLE_BASE_PATH = /u01/app/oracle# TEMP_SNAPSHOT_PATH =# FORCE_LIVEMOUNT_CLEANUP =# ORACLE_VERSION_11G =

3. Create an NFS share for the Data Domain storage unit.

Note: An NFS share will be created automatically if it does not exist. Ensure that the DataDomain user has limited administrative access.

4. Edit the /etc/fstab file, and add the appropriate entry. For example:

10.31.140.154:/data/col1/harboostfs /home/oracle/boostfs nfs rw,user,noauto 0 0

In this example, the values in the entry are as follows:

l 10.31.140.154 is the Data Domain IP address.

l /data/col1/harboostfs is the Data Domain storage unit pathname.

l /home/oracle/boostfs is the mount path on which the storage unit must be mounted.

l nfs is the file system type.

l rw,user,noauto are the mount options.

5. To perform the automated live mount restore, run the ddbmoim command with theappropriate command options. For example:


Performing Oracle Incremental Merge operation.NFS mount of backup device is in progressNFS mount of backup device is completeRunning the mount command. Mountpath: /oraclemountBoostFS mount operation completed successfully.Creating a temp livemount directory '/oim/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557' of backup directory '/oim/orcl_streams/1269163748/full/datafile.stream11122019151615'.Building the livemount repository in temp path completed successfully.Live mount restore directory creation completed successfullyStarting PFile restore from SPFile '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557/SP_FILE.spfile'.PFile restored successfully to '/home/oracle/test1/orcl/initorcl.ora'.Starting control file restore /oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557/CONTROL_FILE.ctl.Control file '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11132019141557/CONTROL_FILE.ctl' restored successfully.Database 'orcl' Mounted successfully.Starting database 'orcl' open operationDatabase 'orcl' opened successfully.



LiveMount of database 'orcl' done successfully.Oracle Incremental Merge operation completed successfully.

6. When the database is open, export the particular table from the temporary live mounteddatabase and then import it to the required database. For example, export TEST_TABLE fromthe orcl database and import to the BOOST database:

l Export command:

ORACLE_SID=orcl exp file=test.dmp tables=test_table rows=y

l Import command:

ORACLE_SID=BOOST imp file=test.dmp full=y

7. To remove the live mounted database, perform a cleanup operation with the ddbmoimcommand as described in Performing a cleanup of the live mount restored database on page121.

Performing a cleanup of the live mount restored database

You can perform the following steps for a cleanup operation with the ddbmoim command, whichremoves the live mounted database after an automated live mount restore.

1. Specify the same parameter settings as described in the preceding topics for the automatedlive mount restores, except change the operation type. Set the operation type through eitherthe OPERATION=livemount-cleanup parameter setting or the -o livemount-cleanupoption of the ddbmoim command.

2. To perform the cleanup, run the ddbmoim command with the appropriate command options.For example:

ddbmoim --dbname orcl -o livemount-cleanup -z /opt/dpsapps/rmanagent/config/rman_agent_oim.cfg

Performing Oracle Incremental Merge operation.Shutting down temp database for cleanup orcl.Temp database orcl shut down successfully.Starting the BoostFS unmount operation.BoostFS unmount operation completed successfully.Oracle Incremental Merge operation completed successfully.

3. If the cleanup operation in step 2 fails, you can perform a force cleanup operation:

a. Keep the same parameter settings as used for the cleanup in step 2, but specify the forcecleanup by adding either the FORCE_LIVEMOUNT_CLEANUP=TRUE parameter setting orthe -a FORCE_LIVEMOUNT_CLEANUP=TRUE option of the ddbmoim command.

b. Run the ddbmoim command with the appropriate command options. For example:

ddbmoim --dbname orcl -o livemount-cleanup -a FORCE_LIVEMOUNT_CLEANUP=TRUE -z /opt/dpsapps/rmanagent/config/rman_agent_oim.cfg

Performing a manual live mount restore by using a BoostFS mount

You can perform the following steps to complete a manual live mount restore (without theddbmoim command) by using a BoostFS mount.

1. Mount the Data Domain storage unit by using a BoostFS mount.



2. Fast copy the snapshot backups to copy the correct datafiles. For example:

[oracle@blrv027a080 datafile.OIM_INCR_MERGE08122019103055]$ ssh [email protected] filesys fastcopy source /data/col1/oim/navneet/3249522768/full/datafile.OIM_INCR_MERGE08122019103055 destination /data/col1/oim/navneet/3249522768/full/TESTData Domain OSPassword:Fastcopy status: fastcopy /data/col1/oim/navneet/3249522768/full/datafile.OIM_INCR_MERGE08122019103055 to /data/col1/oim/navneet/3249522768/full/TEST: copied 16 files, 1 directory in 0.01 seconds

[oracle@blrv027a080 datafile.OIM_INCR_MERGE08122019103055]$ ls -l /oimmount/navneet/3249522768/full/TESTtotal 275060-rw-r-----. 1 100 ftp 18464768 Aug 12 02:34 CONTROL_FILE.ctl-rw-r-----. 1 100 ftp 513810432 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSAUX_FNO-12_jdu90ur2_20190812-rw-r-----. 1 100 ftp 1174413312 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSAUX_FNO-3_j9u90uqr_20190812-rw-r-----. 1 100 ftp 513810432 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSAUX_FNO-7_jbu90uqr_20190812-rw-r-----. 1 100 ftp 513810432 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSAUX_FNO-9_jcu90uqr_20190812-rw-r-----. 1 100 ftp 262152192 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSTEM_FNO-11_jgu90ur5_20190812-rw-r-----. 1 100 ftp 849354752 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSTEM_FNO-1_jau90uqr_20190812-rw-r-----. 1 100 ftp 262152192 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSTEM_FNO-5_jeu90ur2_20190812-rw-r-----. 1 100 ftp 262152192 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-SYSTEM_FNO-8_jfu90ur2_20190812-rw-r-----. 1 100 ftp 10493952 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-TEMP01_FNO-14_jiu90ur5_20190812-rw-r-----. 1 100 ftp 110108672 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-UNDOTBS1_FNO-4_jhu90ur5_20190812-rw-r-----. 1 100 ftp 5251072 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-USERS_FNO-10_jku90ur6_20190812-rw-r-----. 1 100 ftp 5251072 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-USERS_FNO-13_jlu90ur6_20190812-rw-r-----. 1 100 ftp 5251072 Aug 12 02:34 data_D-NEWDB_I-3249522768_TS-USERS_FNO-6_jju90ur5_20190812-rw-r-----. 1 100 ftp 98304 Aug 12 02:34 SP_FILE.spfile-rw-r--r--. 1 100 ftp 151 Aug 12 02:35 tags.json

3. Create the init<SID>.ora file. For example, the file contains the following lines. For a PDBdatabase, add the line *.enable_pluggable_database=TRUE:

cat /tmp/TEST/initTEST.ora## Init.ora file with minimum parameters to start up TEST#*.db_block_size=8192*.db_domain=''*.db_name='TEST'*.control_files='/tmp/TEST/TEST_control01.ctl'*.audit_file_dest='/tmp/TEST/'*.audit_trail='db'*.db_create_file_dest='/tmp/TEST/'*.db_recovery_file_dest='/tmp/TEST/'*.diagnostic_dest='/tmp/TEST/'*.db_recovery_file_dest_size=8589934592*._allow_resetlogs_corruption=TRUE*._allow_error_simulation=TRUE*.enable_pluggable_database=TRUE



*.remote_login_passwordfile='EXCLUSIVE'*.compatible='12.1.0.2.0'

Note: Change the value 12.1.0.2.0 as required in the last line of the init<SID>.oraparameter file. The version must be compatible with the snapshot Data Domain backupimage copies.

4. Set the SID to the new database, for example, TEST:

oracle@blrv027a080 ~]$ ORACLE_SID=TEST sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Sun Jan 20 20:34:53 2019 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to an idle instance.

5. Start and mount the database, and create the control file. For example, the control filecontains the following lines:

SQL> startup nomount pfile=/tmp/TEST/initTEST.oraORACLE instance started.

cat /tmp/TEST/controlfile.ctlCREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS NOARCHIVELOGMAXLOGFILES 16MAXLOGMEMBERS 3MAXDATAFILES 512MAXINSTANCES 8MAXLOGHISTORY 292LOGFILEGROUP 1 '/tmp/TEST/TEST_redo01.log' SIZE 5M BLOCKSIZE 512 reuse,GROUP 2 '/tmp/TEST/TEST_redo02.log' SIZE 5M BLOCKSIZE 512 reuse,GROUP 3 '/tmp/TEST/TEST_redo03.log' SIZE 5M BLOCKSIZE 512 reuseDATAFILE'/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-DUMMY1_FNO-18_c1ubcbiu_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-DUMMY_FNO-17_c0ubcbis_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-10_bmubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-14_bnubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-3_bkubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-6_boubcbi9_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-13_brubcbij_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-1_blubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-5_bsubcbij_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-9_bqubcbia_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-11_buubcbir_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-15_bvubcbir_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-4_bpubcbia_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-8_btubcbin_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-USERS_FNO-12_c3ubcbiv_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-



ORCL_I-1538675391_TS-USERS_FNO-16_c4ubcbiv_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-USERS_FNO-7_c2ubcbiv_20190910';

6. When the control file is created, open the database with resetlogs:

alter database open resetlogs

7. Verify the tables.

For example, two databases are running with the TEST instance live mounted on /oimmount(Data Domain). The copy of the database is at the second backup. The TEST_TABLE is intactand can be exported and imported back to the BOOST databases. On completion, the TESTOracle instance is shut down and the snapshot is removed.

8. Export TEST_TABLE from the TEST database, import to the BOOST database, and clean up.For example:

[oracle@blrv027a080 ~]$ ORACLE_SID=TEST exp file=test.dmp tables=test_table rows=yORACLE_SID=BOOST imp file=test.dmp full=y

Performing a manual live mount restore by using an NFS mount

You can perform the following steps to complete a manual live mount restore (without theddbmoim command) by using an NFS mount.

1. Create the NFS share for the Data Domain storage unit.






l /home/oracle/boostfs is the mount path on which the storage unit needs to be mounted.



3. Mount the mount path directory by using the mount system call. For example:

mount /home/oracle/boostfs

4. To complete the live mount restore on the local host, perform the following steps:

a. Create a temporary snapshot restore directory in Data Domain, and fast copy the snapshotdatafiles from the datafile directory to the snapshot restore directory. For example:

ssh [email protected] filesys fastcopy source /data/col1/harboostfs/rmanagent/1538675391/full/datafile.INCR_MERGE09102019004954 destination /data/col1/harboostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE



b. Export the temporary ORACLE_SID to the temporary database name. For example:

export ORACLE_SID=TEST

c. Create a directory in /tmp with the exported database name, and create theinit<SID>.ora parameter file. For example, the file contains the following lines. For aPDB database, add the line *.enable_pluggable_database=TRUE:

cat /tmp/TEST/initTEST.ora## Init.ora file with minimum parameters to start up TEST#*.db_block_size=8192*.db_domain=''*.db_name='TEST'*.control_files='/tmp/TEST/TEST_control01.ctl'*.audit_file_dest='/tmp/TEST/'*.audit_trail='db'*.db_create_file_dest='/tmp/TEST/'*.db_recovery_file_dest='/tmp/TEST/'*.diagnostic_dest='/tmp/TEST/'*.db_recovery_file_dest_size=8589934592*._allow_resetlogs_corruption=TRUE*._allow_error_simulation=TRUE*.enable_pluggable_database=TRUE*.remote_login_passwordfile='EXCLUSIVE'*.compatible='12.1.0.2.0'

Note: Change the value 12.1.0.2.0 as required in the last line of the init<SID>.oraparameter file. The version must be compatible with the snapshot Data Domain backupimage copies.

d. Create a control file with the datafiles of the snapshot restore directory. For example, thecontrol file contains the following lines:

cat /tmp/TEST/controlfile.ctlCREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS NOARCHIVELOGMAXLOGFILES 16MAXLOGMEMBERS 3MAXDATAFILES 512MAXINSTANCES 8MAXLOGHISTORY 292LOGFILEGROUP 1 '/tmp/TEST/TEST_redo01.log' SIZE 5M BLOCKSIZE 512 reuse,GROUP 2 '/tmp/TEST/TEST_redo02.log' SIZE 5M BLOCKSIZE 512 reuse,GROUP 3 '/tmp/TEST/TEST_redo03.log' SIZE 5M BLOCKSIZE 512 reuseDATAFILE'/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-DUMMY1_FNO-18_c1ubcbiu_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-DUMMY_FNO-17_c0ubcbis_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-10_bmubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-14_bnubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-3_bkubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSAUX_FNO-6_boubcbi9_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-



ORCL_I-1538675391_TS-SYSTEM_FNO-13_brubcbij_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-1_blubcbhe_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-5_bsubcbij_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-SYSTEM_FNO-9_bqubcbia_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-11_buubcbir_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-15_bvubcbir_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-4_bpubcbia_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-UNDOTBS1_FNO-8_btubcbin_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-USERS_FNO-12_c3ubcbiv_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-USERS_FNO-16_c4ubcbiv_20190910','/home/oracle/boostfs/rmanagent/1538675391/full/SNAPSHOT-RESTORE/data_D-ORCL_I-1538675391_TS-USERS_FNO-7_c2ubcbiv_20190910';

e. Log in to the sqlplus, and start the database with the created init<SID>.ora file inthe nomount state. For example:

startup nomount pfile=/tmp/TEST/initTEST.ora

f. Run the control file script from sqlplus. For example:

@/tmp/TEST/controlfile.ctl

g. When the control file is created, open the database with resetlogs:

alter database open resetlogs

h. When the database is open, export the particular table from the temporary createddatabase and then import to the original database. For example:

l Export command: ORACLE_SID=TEST exp file=test.dmp tables= test_tablerows=y

l Import command: ORACLE_SID=BOOST imp file=test.dmp full=y

Performing the restore operations to a proxy hostYou can perform a restore operation to a proxy host through either an automated method thatuses the ddbmoim command or a manual method that uses a series of manual steps (without theddbmoim command). Oracle RMAN agent 19.3 introduced the automated method with theddbmoim command. The automated method can use either a BoostFS mount or an NFS mount.

The following topics describe all the supported methods of proxy host restores.

Note:For a proxy host restore, ensure that the database version, Oracle username, group ID, anduser ID are the same on both the production host and proxy host.

A proxy host restore with the ddbmoim command applies only to the same-named database. Amanual proxy host restore operation, as introduced with Oracle RMAN agent 19.2, applies toeither the same-named database or a different-named database.

When you perform a proxy host restore with ASM enabled source database backups, therestored database is converted to a stand-alone database that is created using a pfile of thedatabase instance.



If you need to perform backups of a proxy host restored database using the Oracle IncrementalMerge solution, then create an spfile from the pfile and restart the database using the spfile.

Performing an automated proxy host restore by using a BoostFS mount

You can perform the following steps for an automated proxy host restore that uses the ddbmoimcommand with a BoostFS mount.

1. Specify the required parameter settings for the automated proxy host restore through eitherof the following methods:


or



For example, the configuration file includes the following parameter settings for the automatedproxy host restore, where orcl is the Oracle SID of the database. The NFS_MOUNT setting ofFALSE specifies a BoostFS mount:

[SID_orcl]BACKUP_HOST = 10.31.140.154DELETE_ARCHIVELOG = TRUEDELETE_ARCHIVELOG_NUM_DAYS = 1MOUNT_PATH = /oraclemountSTORAGE_UNIT = oimOIM_TAG = TEST_2OPERATION = proxy-restoreORACLE_HOME = /u01/app/oracle/product/19.0.0/dbhome_1# PARALLELISM =# RETENTION =# RMAN_CATALOG_SERVICE =# RMAN_CATALOG_USER =# SCRIPT_PATH =# SYSBACKUP =# TNS_ADMIN =NFS_MOUNT = FALSEBACKUP_PATH = /oim/orcl_streams/1269163748/full/datafile.stream11122019151615TEMP_DATABASE_PATH = /home/oracle/test1ORACLE_BASE_PATH = /u01/app/oracle# TEMP_SNAPSHOT_PATH =# FORCE_LIVEMOUNT_CLEANUP =# ORACLE_VERSION_11G =

2. To perform the automated proxy host restore, run the ddbmoim command with theappropriate command options. For example:


Performing Oracle Incremental Merge operation.Starting BoostFS mount operation.Running the mount command. Mountpath: /oraclemountBoostFS mount operation completed successfully.Creating a temp livemount directory '/oim/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019192907' of backup directory '/oim/orcl_streams/1269163748/full/datafile.stream11122019151615'.Building the livemount repository in temp path completed successfully.Live mount restore directory creation completed successfullyStarting PFile restore from SPFile '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019192907/SP_FILE.spfile'.PFile restored successfully to '/home/oracle/test1/orcl/initorcl.ora'.



Starting control file restore /oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019192907/CONTROL_FILE.ctl.Control file '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019192907/CONTROL_FILE.ctl' restored successfully.Database 'orcl' Mounted successfully.Starting database 'orcl' open operationDatabase 'orcl' opened successfully.Proxy Restore of database 'orcl' done successfully.Starting the BoostFS unmount operation.BoostFS unmount operation completed successfully.Oracle Incremental Merge operation completed successfully.

Performing an automated proxy host restore by using an NFS mount

You can perform the following steps for an automated proxy host restore that uses the ddbmoimcommand with an NFS mount.

1. Specify the required parameter settings for the automated proxy host restore through eitherof the following methods:


or



For example, the configuration file includes the following parameter settings for the automatedproxy host restore, where orcl is the Oracle SID of the database. The NFS_MOUNT setting ofTRUE specifies an NSF mount:

[SID_orcl]BACKUP_HOST = 10.31.140.154DELETE_ARCHIVELOG = TRUEDELETE_ARCHIVELOG_NUM_DAYS = 1MOUNT_PATH = /oraclemountSTORAGE_UNIT = oimOIM_TAG = TEST_2OPERATION = proxy-restoreORACLE_HOME = /u01/app/oracle/product/19.0.0/dbhome_1# PARALLELISM =# RETENTION =# RMAN_CATALOG_SERVICE =# RMAN_CATALOG_USER =# SCRIPT_PATH =# SYSBACKUP =# TNS_ADMIN =NFS_MOUNT = TRUEBACKUP_PATH = /oim/orcl_streams/1269163748/full/datafile.stream11122019151615TEMP_DATABASE_PATH = /home/oracle/test1ORACLE_BASE_PATH = /u01/app/oracle# TEMP_SNAPSHOT_PATH =# FORCE_LIVEMOUNT_CLEANUP =# ORACLE_VERSION_11G =

2. Create an NFS share for the Data Domain storage unit.








l /home/oracle/boostfs is the mount path on which the storage unit must be mounted.



4. To perform the automated proxy host restore, run the ddbmoim command with theappropriate command options. For example:


Performing Oracle Incremental Merge operation.NFS mount of backup device is in progressNFS mount of backup device is completeCreating a temp livemount directory '/oim/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019200006' of backup directory '/oim/orcl_streams/1269163748/full/datafile.stream11112019171120'.Building the livemount repository in temp path completed successfully.Live mount restore directory creation completed successfullyStarting PFile restore from SPFile '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019200006/SP_FILE.spfile'.PFile restored successfully to '/home/oracle/test1/orcl/initorcl.ora'.Starting control file restore /oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019200006/CONTROL_FILE.ctl.Control file '/oraclemount/orcl_streams/1269163748/restore/orcl_streams_orcl_11142019200006/CONTROL_FILE.ctl' restored successfully.Database 'orcl' Mounted successfully.Starting database 'orcl' open operationDatabase 'orcl' opened successfully.Proxy Restore of database 'orcl' done successfully.NFS unmount of backup device is in progressNFS unmount of backup device is completeOracle Incremental Merge operation completed successfully.

Performing a manual proxy host restore

To perform a database restore to a proxy host by using the manual method, you must make localcopies from the specified snapshot Data Domain image copies and then restore the database tothe given point.

The following example shows the series of commands to run in RMAN for a manual restoreoperation to a proxy host.

1. Specify the production host database ID:

set dbid 1538675391;

2. Start the database:

startup force nomount;

3. Restore the spfile to the proxy host directory $ORACLE_HOME/dbs from the snapshot DataDomain image spfile:

restore spfile to "/home/oracle/app/oracle18/product/18.0.0/dbhome_1/dbs/spfileorcl.ora" from "/home/oracle/boostfs/rmanagent/1538675391/full/datafile.INCR_MERGE09112019043255/SP_FILE.spfile";



4. Create the pfile in the proxy host directory $ORACLE_HOME/dbs from the created spfile ofthe proxy host:

create pfile='/home/oracle/app/oracle18/product/18.0.0/dbhome_1/dbs/initorcl.ora' from spfile='/home/oracle/app/oracle18/product/18.0.0/dbhome_1/dbs/spfileorcl.ora';

5. Restore the control file from the snapshot Data Domain image control file copy to the defaultdirectory $ORACLE_HOME/dbs:

restore controlfile from "/home/oracle/boostfs/rmanagent/1538675391/full/datafile.INCR_MERGE09112019043255/CONTROL_FILE.ctl";create spfile from memory;shutdown abort;startup nomount;alter system set db_name='orcl' scope=spfile;

6. Run the following command for a PDB database:

alter system set "enable_pluggable_database"= TRUE SCOPE = SPFILE;

7. Shut down and restart the database:

shutdown abort;startup nomount;alter database mount;

8. Restore the database:

Note:When the production host datafile path does not exist on the proxy host, provide the newdatabase path with the set newname command and datafile format. During the databaserestore, the local copies are created from the snapshot Data Domain image copies.

When you run the set newname command, you must also run the switch datafileall command to switch all the datafiles to the new database format that is provided bythe set newname command.

run {set newname for database to '/home/oracle/app/oracle18/oradata/ORCL/%N_%f.dbf';restore database;switch datafile all;}

9. Run the database recovery preview and record the fuzziness SCN number:

recover database preview;

10. Run the database recovery and specify the recorded fuzziness SCN number, xxxxx:

recover database until scn xxxxx;

11. When the production host redo log path does not exist on the proxy host, rename the redo logfiles to the new database path on the proxy host:

select member from v$logfile;alter database rename file '/u01/app/oracle/oradata/ORCL/redo01.log' to '/home/oracle/app/



oracle18/oradata/ORCL/redo01.log';alter database rename file '/u01/app/oracle/oradata/ORCL/redo02.log' to '/home/oracle/app/oracle18/oradata/ORCL/redo02.log';alter database rename file '/u01/app/oracle/oradata/ORCL/redo03.log' to '/home/oracle/app/oracle18/oradata/ORCL/redo03.log';alter database open resetlogs;

Configuring the use of Data Domain Cloud Tier for datamovement to the cloud

You can configure the Oracle RMAN agent to use the Data Domain Cloud Tier for the movement ofbackup data to the cloud and the subsequent recall of the backup data from the cloud.

Data Domain (DD) Cloud Tier is a native feature of DD OS 6.0 and later for data movement fromthe active tier to low-cost, high-capacity object storage in the public, private, or hybrid cloud forlong-term retention. The Oracle RMAN agent 4.0 introduced support of the DD Cloud Tier formovement of DD Boost backup data to the cloud, which frees up space on the Data Domainsystem (active tier).

NOTICEIf the Oracle RMAN agent is integrated with PowerProtect, the following self-servicereplication and cloud tiering operations are disabled:

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

l Automatic recall of the backup data during restore, when the backup file is in the cloudtier. The PowerProtect administrator must explicitly recall the backup copy before it canbe restored by the DBA.

The PowerProtect Administration and User Guide provides more details about these limitations.

You must set up a DD Cloud Tier policy, also known as a data movement policy, for each MTree orstorage unit that the Oracle RMAN agent uses for data movement to the cloud.

After you have set up the data movement policies, you can configure and perform the followingoperations:

l Movement of backup data from the Data Domain system to the cloud.

l Recall of backup data from the cloud to the Data Domain system.

The following topics describe how to set up the required DD Cloud Tier policies to enable the datamovement to the cloud and how to perform the data recall from the cloud.

Setting up the data movement to the cloudThe Oracle RMAN agent moves the backup data from the active tier to the cloud according to theDD Cloud Tier policy. To enable the data movement to the cloud, you must set up the requiredpolicy for each MTree or storage unit.

About this task

DD Cloud Tier provides two types of data movement policy, the application-based policy and theage-based policy. The Oracle RMAN agent supports only the age-based policy. A file is movedfrom the active tier to the cloud tier based on the date that it was last modified. For data integrity,the entire file is moved at this time. The aged-based policy can specify the file age threshold, theage range for the files to be moved, and the destination. For example, files older than 1 month andyounger than 3 months can be moved to the cloud.

Set the age-based data movement policy on a per-MTree basis on the Data Domain system byusing the Data Domain Data Management console, as described in the Data Domain Operating



System Administration Guide. For example, the following procedure adds a data movement policy toan MTree.

Note: Data movement can be initiated manually or automatically by using the policy schedule.Once the policy is set up, the backup files on the Data Domain system are automatically movedto the cloud according to the schedule, and no manual intervention is required. You can alsoinitiate the data movement manually from the Data Domain Data Management console.

Procedure

1. Select Data Management > MTree.

2. In the top panel, select the MTree to which you want to add a data movement policy.

3. Click the Summary tab.

4. Under Data Movement Policy, click Add.

The Add Data Movement Policy dialog box appears:

5. For File Age in Days, set the file age threshold (Older than) and optionally the age range(Younger than).

Note: The minimum number of days for Older than is 14. Files moved to the cloud tiercannot be accessed directly and must be recalled to the active tier before you canaccess them. Select the age threshold value as appropriate to minimize or avoid theneed to access a file that is moved to the cloud tier.

6. For Destination, specify the destination cloud unit.

7. Click Add.

Performing the data recall from the cloudAfter the backup data has been moved to the cloud through the DD Cloud Tier policies, the datacan be recalled from the cloud automatically or manually. By default, the Oracle RMAN agentautomatically recalls data from the cloud to the Data Domain system as required to complete arestore operation. You can also recall the backup files manually, prior to a restore operation.

During a restore operation, if a backup file is requested and not in the active tier, the Oracle RMANagent automatically recalls the file from the cloud. The Oracle RMAN agent waits for the file tobecome available before continuing the restore. The time taken by the recall process depends onthe file size and the speed of the network between the cloud and the Data Domain system.

As an alternative, to avoid waiting a long time for the recall of files during a restore, you can recallfiles manually prior to a restore by running the following RMAN command:

RESTORE ... PREVIEW RECALL

This command produces the following results:



1. RMAN generates a list of the files that are required for the restore.

2. RMAN sends the list of files to the Oracle RMAN agent.

3. The Oracle RMAN agent recalls all the backup pieces from the list that are in the cloud tier.

If a file from the list is already in the active tier, the Oracle RMAN agent performs no actionrelated to the file.

RMAN crosscheck and deletion of backup data in the cloudAn RMAN crosscheck or deletion operates on a backup piece file that is created by the OracleRMAN agent, whether the file exists on the Data Domain system (active tier) or in the cloud tier.

The RMAN crosscheck command checks whether a backup piece file exists on the backupmedia and updates the file information accordingly in the RMAN catalog. For a backup piece filecreated by the Oracle RMAN agent, the crosscheck command reports the file as AVAILABLEwhen the file exists on the Data Domain system or in the cloud. The crosscheck command doesnot recall a file that exists in the cloud; the file remains in the cloud after the crosscheckoperation.

An RMAN deletion removes a backup piece file, regardless of the file location. The RMAN deletionremoves the file, whether it exists on the Data Domain system or in the cloud. If the backup piecefile exists in the cloud, it is removed from the cloud and can no longer be recalled from the cloud.

Usage limits on Data Domain resourcesThe Data Domain administrator can use the Data Domain OS commands or the Data DomainAdministration GUI to set limits on capacity or streams usage:

l Capacity refers to the amount of hard drive capacity that the Oracle RMAN agent uses on theData Domain host.

Note: Capacity limits are based on the used logical space. Logical space depends on howmuch data is written to a storage unit before deduplication. Logical capacity is the size ofthe uncompressed data. For example, when a 1 GB file is written twice to the same storageunit that was initially empty, then the storage unit has a logical size of 2 GB but a physicalsize of 1 GB.

l Streams refers to the number of DD Boost streams that the Oracle RMAN agent uses to readdata from a storage unit or write data to a storage unit on the Data Domain host.

The Data Domain OS supports soft limits and hard limits on capacity or streams usage:

l When a soft limit is exceeded, the Data Domain host generates an alert, and if a tenant-unitnotification list is configured, sends an email to the addresses on the list. An application cancontinue to use more of the limited resource after a soft limit is exceeded.

l When a hard limit is exceeded, an application cannot use any more of the limited resource.

The Data Domain documentation provides details on the Data Domain versions that support thesoft and hard limits for capacity or streams.

The Data Domain administrator can create a separate storage unit for each Oracle RMAN agenthost or for a set of hosts that will be limited.

For example, to limit the storage unit capacity used by each Oracle RMAN agent host, where thereare 10 Oracle RMAN agent hosts, the Data Domain administrator must create at least 10 storageunits. If the Data Domain administrator creates fewer storage units, you must group the OracleRMAN agent hosts and assign each group of hosts to a storage unit. In this case, you cannot limitthe amount of storage that will be consumed by each host. One of the Oracle RMAN agent hosts



could consume 100% of a storage unit resource. The resources are consumed on a first come, firstserved basis.

Oracle RMAN agent operations with Data Domain usage limits on capacityAt the start of a backup, the Oracle RMAN agent cannot determine how much capacity will berequired for the backup. The Oracle RMAN agent always tries to perform a requested backupwhen the destination device has any available space or storage capacity.

A capacity limit can be set on a storage unit. When the capacity soft limit is exceeded during abackup, alerts appear in the Current Alerts pane in the Data Domain Administration GUI.

If the storage unit is part of a tenant-unit with a notification list, the Data Domain host sends anemail to the addresses on the list. The Data Domain administrator and the Oracle RMAN agent usershould be included in the list.

The backup or restore operation continues without any adverse impact when the capacity softlimit is exceeded. The Oracle RMAN agent does not generate any warning or error message in itslog file or operational output.

When the capacity hard limit of a storage unit is exceeded during a backup, the Oracle RMANagent terminates the backup and generates a message to inform the user about the lack of spaceon the storage unit.

Oracle RMAN agent operations with Data Domain usage limits on streamsWhen the stream soft limit is exceeded during a backup and the storage unit is part of a tenant-unit with a notification list, the Data Domain host sends an email to the addresses on the list. TheData Domain administrator and the Oracle RMAN agent user should be included in the list.

Alerts appear in the Current Alerts pane in the Data Domain Administration GUI when the softlimit is exceeded, whether or not the storage unit is part of a tenant-unit.

The backup or restore operation continues without any adverse impact when the stream soft limitis exceeded. The Oracle RMAN agent does not generate any warning or error message in its logfile or operational output.

When the stream hard limit is exceeded during an operation, the Oracle RMAN agent terminatesthe operation with a message to inform the user that a higher streams limit is required. Themethod for displaying and logging messages is Oracle-specific.

Configuring usage limits on Data Domain resourcesYou must complete the required procedures on the Data Domain host to configure the capacity orstreams usage limits for the Oracle RMAN agent. The following topics provide the configurationdetails. Additional following topics provide guidelines and best practices related to the capacity orstreams usage limits on Oracle systems.

Configuring usage quota on Data Domain capacityTo configure a capacity usage quota for the Oracle RMAN agent, the Data Domain administratormust set the hard capacity limit for the storage unit that the Oracle RMAN agent uses forbackups.

Procedure

1. Determine which Oracle RMAN agent hosts will use the storage unit.

2. Determine how much capacity to allow for the storage unit.

3. Create the storage unit, and then set the capacity quota in the GUI or the CLI command.The Data Domain documentation provides more details.



4. Provide the Oracle RMAN agent users with the DD hostname, storage unit name, username,and password of the storage unit to be used for backups.

The Data Domain administrator can also set the soft capacity quota for the storage unit,which triggers alerts and notifications but does not limit the capacity usage.

The Data Domain administrator can use the Data Domain OS commands or the Data DomainAdministration GUI to add or modify the capacity quota of storage units. The Data Domaindocumentation provides more details.

NOTICE Use caution when decreasing a capacity quota. When a storage unit is almostfull and the capacity quota is decreased, the next backup might fail. Notify the OracleRMAN agent users when a capacity quota is decreased so that the users can evaluatethe potential impact on backups.

Configuring usage limits on Data Domain streamsA storage unit can have soft and hard limits for streams. Soft limits can be set both individually forread, write, and replication streams, and collectively for the total number of all types of streams. Ahard limit can be set only for the total number of all types of streams.

About this task

To configure a streams usage limit for a storage unit, the Data Domain administrator must set thehard limit for the storage unit that the Oracle RMAN agent uses for backups.

Procedure

1. Determine which Oracle RMAN agent hosts will use the storage unit.

2. Determine how many backup and restore streams to allow for the storage unit.

3. Create the storage unit. You can set the streams limit as part of the ddboost storage-unit create command or (after the storage unit is created) with the ddbooststorage-unit modify command. The Data Domain documentation provides moredetails.

Note: A streams limit cannot be set in the Data Domain Administration GUI.

4. Provide the Oracle RMAN agent users with the DD hostname, storage unit name, username,and password of the storage unit to be used for backups.

The Data Domain administrator can also set soft limits for the storage unit, which triggeralerts and notifications but do not limit the number of streams used.

The Data Domain administrator can use the ddboost storage-unit modify commandto modify the streams limits of storage units. The Data Domain documentation providesmore details.

NOTICE Use caution when setting a streams hard limit. Setting the streams limit to alow value can impact the backup and restore performance. Decreasing a streams limitcan cause a restore to fail. Notify the Oracle RMAN agent users when a streams limit isdecreased so that the users can evaluate the potential impact on backups.

Estimating the Data Domain resource usage on Oracle systemsThe following topics provide additional guidelines and best practices related to the Data Domainresource usage for Oracle systems.



Capacity usage on Oracle systemsIf the storage capacity of the Data Domain system is exceeded, the backup operation fails. TheOracle RMAN agent generates the following type of error message in the operational log:

SBT-10156 2017-04-24 12:12:18 PM sbtwrite2: ddp_write returned error 5194. Unable to write to a file due to reaching the hard quota limit.

Streams usage on Oracle systems

Note: The streams usage varies, depending on the number and type of parallel operations thatare performed at a given time. This topic provides typical numbers for the streams usage of asingle operation. To determine more exact numbers, you must monitor the number of streamsthat the storage units use over a period of time.

The number of streams that RMAN typically uses for backups, restores, and maintenanceoperations (such as crosscheck) corresponds to the number of used channels plus 1.

If the Data Domain system runs out of streams during a backup, the RMAN channel fails with thefollowing type of error message in the operational log:

SBT-10156 2017-04-24 12:12:18 PM sbtwrite2: ddp_write returned error 5519. Unable to write to a file because the streams limit was exceeded.

The backup continues and succeeds because RMAN reassigns the backup job to other channels:

RMAN-03009: failure of backup command on CH5 channel at 04/24/2017 16:38:20 ORA-19502: write error on file "CER4_1sr1pqjo_1_1", block number 33 (block size=8192)ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: Error received from media manager layer, error text: asdf_output_section1() failed xdr=0x0xb8183f8: bp=0x0xc19c538: send_len=262144: type=12800: fhand=0x0xc17e688: wrapper=0x(nil): directp=0x0x7f268ad9e000 (1:4:22)channel CH5 disabled, job failed on it will be run on another channel

If the Data Domain system runs out of streams during a restore, the RMAN channel fails with thefollowing type of error message in the operational log:

SBT-10156 2017-04-24 12:12:18 PM sbtread2: ddp_read returned error 5519. Unable to read from a file because the streams limit was exceeded.



CHAPTER 5

Data Domain System Administration

Note: This chapter applies only to stand-alone deployments on Data Domain systems. Forinformation about PowerProtect Data Manager and PowerProtect X400 deployments, refer tothe PowerProtect Data Manager and PowerProtect X400 documentation.


l Restricting DD Boost access to specific database servers................................................... 138l File replication version compatibility.................................................................................... 138l Modifying an interface group............................................................................................... 139


Restricting DD Boost access to specific database serversBy default, when the DD Boost service is enabled on a Data Domain system, the service isaccessible to all database servers. However, you can use the ddboost access command tooverride this default, and restrict access to a limited set of database servers.

The following example commands remove the default access permission for all servers and thenadd new access permissions for two specific database servers, databaseserver1.datadomain.comand databaseserver2.datadomain.com:

ddboost disableddboost access del clients *ddboost access add clients databaseserver1.datadomain.com databaseserver2.datadomain.comddboost enable

These commands establish a set of access controls that enables DD Boost access only to the twospecified database servers, databaseserver1.datadomain.com anddatabaseserver2.datadomain.com.

If no specific access controls are established, running the ddboost enable command configuresthe default access control, which allows all the hosts to access the DD Boost service. However, ifthere are any access control entries already established, running the ddboost enable commanddoes not modify the access control list, thus enabling the access controls that are alreadyestablished.

Note:

l Ensure that no backup jobs are running to the Data Domain system when you change theaccess control. Run the ddboost disable command to prevent operations while accessis changed. Disabling DD Boost disables data access to all the database servers.

l Specify only a fully qualified domain name, IP address, or resolvable DNS name for theclient when you modify the client access control list.

l If the username is changed or deleted, the change in access rights does not affect anycurrent operations. For example, deleting the current clients from the DD Boost access listby running the ddboost access del clients command does not stop a file backupthat is already in progress. All operations in progress will continue. The change in accessrights does not cause existing operations to fail.

l Run the ddboost enable command to re-enable DD Boost and enable RMAN operationsafter changing the access, which are now subject to the changed access rights.

l When access control is changed on a Data Domain system for a connected RMANapplication, RMAN is still able to perform according to the access rights established at thefirst connection. The first connection is when the first RMAN command was invoked byusing the Oracle RMAN agent. The next time RMAN is stopped and restarted, the newaccess rights are used.

File replication version compatibilityThe Data Domain policy of upgrade compatibility for file replication is as follows:



l All the maintenance and patch versions within a family are backward compatible. A family isidentified by the first two digits of the release number, such as 5.1. For example, 5.1.0.0,5.1.0.2, 5.1.1.0, and 5.1.2.0 are backward compatible.

l File replication is backward compatible across two consecutive release families, such as 5.1 and5.2.

l File replication over WAN should use the Data Domain ddboost file-replication optionto adjust for low bandwidth and long latency.

Modifying an interface groupAbout this task

After the interface group is set up, you can add or delete interfaces from the group. The followingexample shows how to remove an interface from the configured interface group on the DataDomain system.

Procedure

1. Ensure that no jobs are active from RMAN to the Data Domain system on the interface thatyou wish to remove from the group. You can do this from the Data Domain system bychecking the status of existing connections in the interface group, by running the followingcommand:

# ddboost show connections

2. Remove the interface from the group on Data Domain system:

# ddboost ifgroup del default 192.168.1.3

After this, the interface 192.168.1.3 is released from the group and is no longer used by theDD Boost storage server for any jobs from the database servers.

Note: Removing the interface registered with RMAN makes the Data Domain systeminaccessible to the database servers. The configuration of the ifgroup on the DataDomain system is not deleted.

To make any changes to any interface that is added to the interface group on the DataDomain system at the network layer, remove the interface from the group and add it back.

If you make changes by running the net command to modify the interfaces, such asenabling an interface that is configured for ifgroup, then run the ddboost showconnections command to update the load balancing view. This updating enables theifgroup to use the interface. show connections on page 157 provides more information.

Removing the advanced load balancing and link failover configurationAbout this task

The following example shows how to remove a configured interface group on the Data Domainsystem.



Procedure

1. Ensure that no jobs are active from RMAN to the Data Domain system. You can do this fromthe Data Domain system by checking the status of existing connections in the interfacegroup, by running the following command:

# ddboost show connections

show connections on page 157 provides information about sample output.

2. Ensure that there are no pending jobs from any of the connected database servers to thissystem.

3. Disable the feature on the Data Domain system:

# ddboost ifgroup disable default

4. Reset the interface group:

# ddboost ifgroup default reset

Results

All the interfaces are released from the group.



CHAPTER 6

Troubleshooting


l Troubleshooting overview.................................................................................................... 142l Investigating problems......................................................................................................... 142l Oracle limitations................................................................................................................. 142l Reporting problems..............................................................................................................142l Data Domain system settings for file replication.................................................................. 143l Lockbox troubleshooting information................................................................................... 143l Failure to load the media management library...................................................................... 144


Troubleshooting overviewThis chapter provides basic troubleshooting tips that can enable you to resolve issues with theproduct. For issues that cannot be resolved, contact the contracted support providers.

For more information, see the Data Domain Knowledge Base, which is available at https://support.emc.com.

Investigating problemsNote: This topic applies only to Data Domain systems, not PowerProtect Data Manager orPowerProtect X400 systems.

When you investigate a problem, be aware that the DD Boost software has components on both aData Domain system and an RMAN system. The two environments must be compatible. Thefollowing troubleshooting considerations apply to both systems:

l Supported configurations

Ensure that you have a supported configuration as specified in the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection. A supported configuration canbecome unsupported if any component changes.

l Authorization failures

If you encounter authorization failures, ensure that all the systems have correct accesscredentials for the other systems.

Oracle limitationsMany RMAN functions require specific editions of Oracle. For example, using COPIES 2 orparallelism requires the Enterprise Edition. For a complete list, refer to the Oracle documentationat http://oracle.su/docs/11g/license.112/e10594/editions.htm.com.

RMAN has numerous restrictions and limitations on how backups can be performed and what canbe backed up. The Oracle RMAN agent can only do backup and restore operations that RMANsupports. For example, control file autobackups are never multiplexed. This means that if COPIES2 is used to create a replica of a backup, the control files do not get replicated to the second(destination) Data Domain system. Using the INCLUDE CURRENT CONTROLFILE option in thebackup statement is one possible solution; this includes a copy of the current control file in abackup piece.

Reporting problemsWhen reporting a problem to Technical Support, always include the following information:

l The sbtio.log file, which is critical for analysis.

l Output of the RMAN command show all.

l All the RMAN commands that you used.

If possible, delete the sbtio.log file, re-create the problem in as few steps as possible, thencapture the sbtio.log file to send with your problem report. Set the TRACE level to 5 with theCONFIGURE CHANNEL command when you try to re-create the problem.

RMAN determines where the sbtio.log file is located. The sbtio.log file is usually located inthe directory defined by the user_dump_dest initialization variable or in the $ORACLE_HOME/

Troubleshooting






http://oracle.su/docs/11g/license.112/e10594/editions.htm.com

rdbms/log directory. If all else fails, go to the $ORACLE_HOME directory and run a findcommand to locate the file.

Data Domain system settings for file replicationNote: This topic applies only to Data Domain systems, not PowerProtect Data Manager orPowerProtect X400 systems.

For all DD OS versions, the replication throttle command controls replication. Setting thethrottle too low can lead to file replication problems. The Data Domain Operating SystemAdministration Guide provides information about using the replication throttle command todisplay or control the throttle settings.

Lockbox troubleshooting informationNote: This topic does not apply to PowerProtect Data Manager or PowerProtect X400deployments.

The ddboost.config file is the lockbox file for Oracle RMAN agent. The file contains the savedusername/password pairs for the Data Domain systems that you use. If you connect to systemddr-system as user ddr-user with password user-password, there is a corresponding entry in thefile. The entry specifies that connections to ddr-system are made by using username ddr-user withpassword user-password. The lockbox file is encrypted and maintained with the RSA lockboxlibraries, which are installed as part of the Oracle RMAN agent, and hence some of the errorstrings returned in sbtio.log refer to lockbox.

If you change the hostname of the Data Domain system without changing the hostname in all thescripts and so on, then attempts to connect to ddr-system fail because there is no host with thespecified hostname. If you use the new hostname in all scripts, you can add a new username-password entry for that hostname to the ddboost.config file. Registering each Data Domainsystem on page 62 provides instructions.

The ddboost.config file is located in the $RMAN_AGENT_HOME/config directory (Linux orUNIX) or in the %RMAN_AGENT_HOME%\config directory (Windows).

You cannot reference a lockbox except from the database server where the lockbox was created,unless at the time you created the lockbox, you set it up to be accessible from multiple servers. Registering a Data Domain system for shared lockbox access on page 67 provides moreinformation.

If you uninstall the boost library, check to see that the old ddboost.config files are deleted.There are four files:

l ddboost.configl ddboost.config.bakl ddboost.config.FCDl ddboost.config.bak.FCDDeleting the ddboost.config files never causes a problem because the entries will be re-created on demand if you re-run the RMAN commands that register the Data Domain systems.

Troubleshooting


Starting with Oracle RMAN agent 4.6, if you want to use an existing lockbox in a non-defaultdirectory, you must properly upgrade the lockbox. Otherwise, any subsequent backup, restore, orquery operations fail with one of the following types of error messages:

SBT-5047 08/18/17 09:32:40 error 7501: dd_rman_get_user_info: Unable to open config file '/home/oracle/opt/dpsapps/rmanagent/config/ddboost.config'. Error: The Lockbox is corrupt and failed to load.

SBT-5047 08/18/17 09:32:40 error 7501: dd_rman_get_user_info: Unable to open config file '/u01/app/oracle/product/10.2.0/db_1/config/ddboost.config'. Error: Lockbox tampering was detected, so it cannot be read.

To use an existing lockbox in a non-default directory, ensure that you perform one of the followingupgrade procedures:

l Run the following ddutil -U command to upgrade the lockbox and then copy the existinglockbox files to the default directory, $RMAN_AGENT_HOME/config or %RMAN_AGENT_HOME%\config. The command must include the complete pathname of the non-default directory.For example:

ddutil -U -a LOCKBOX_IMPORT=TRUE -a LOCKBOX_PATH=<non-default_lockbox_directory_pathname>cp <non-default_lockbox_directory_pathname>/ddboost.config* $RMAN_AGENT_HOME/config

l Copy the existing lockbox files from the non-default directory to the default directory,$RMAN_AGENT_HOME/config or %RMAN_AGENT_HOME%\config, and then run the followingddutil -U command to upgrade the lockbox:


Failure to load the media management libraryAbout this task

After installation and configuration of the Oracle RMAN agent is completed, attempts to use theOracle RMAN agent sometimes result in RMAN failures with the RMAN error message Failedto load Media Management Library as shown in the following RMAN error report:

RMAN-00571: =====================================RMAN-00569: ===ERROR MESSAGE STACK FOLLOWS======RMAN-00571: =============================================================================== RMAN-03009: failure of allocate command on dd0 channel at 01/07/2013 13:40:36 ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-27211: Failed to load Media Management Library

This error usually occurs in an AIX or Linux environment. The error message indicates that RMANis unable to locate one of the required libraries, either libddobk.so or libDDBoost.so oranother library that is used by these libraries.

The ddutil program can also fail due to an inability to load the required dependent libraries. If thisoccurs, ensure that the ddutil program is running from the installation directory of the OracleRMAN agent. Alternatively, set the RMAN_AGENT_HOME environment variable to enable thedependent libraries to be found.

If you encounter the preceding RMAN error message in the environment, you can use the followingsteps to help find the source of the problem and correct it.

Troubleshooting


Procedure

1. Check that the libddobk.so library pathname was specified correctly in the RMANconfiguration command.

Configuring the software on Linux and UNIX systems on page 57 or Configuring thesoftware on Windows systems on page 62 provides more information. If the pathname is notcorrect, the libddobk.so library cannot be found. Check that libddobk.so exists in thespecified directory and that the directory and library file have appropriate access for theuser.

2. Check that the home directory of the Oracle RMAN agent was specified correctly in theRMAN configuration command.

Configuring the software on Linux and UNIX systems on page 57 or Configuring thesoftware on Windows systems on page 62 provides more information. If the directory is notcorrect, the libDDBoost.so library cannot be found. Check that the lib subdirectoryexists in the home directory of the Oracle RMAN agent, the libDDboost.so library existsin this directory, and the directory and library file have appropriate access for the user.

3. Run the ldd command on the libddobk.so library to ensure that the libraries that it usescan be found, as shown in the following example:

Troubleshooting


Troubleshooting


CHAPTER 7

Using DD Boost Commands

Note: This chapter applies only to Data Domain systems, not PowerProtect X400 systems. Forinformation about the commands and configuration on PowerProtect X400 integrated storage,refer to the PowerProtect X400 documentation.


l DD Boost command summary.............................................................................................. 148l The ddboost command options............................................................................................ 148


DD Boost command summaryThe topics in this chapter describe how to use the ddboost command with the following options.

Table 12 Summary of DD Boost commands

access Manage the DD Boost access for clients. access on page148

clients Enable the encrypted backups and restores over the LAN, and specifythe encryption strength.

clients on page149

destroy Delete all the storage units and their contents from the Data Domainsystem.

destroy on page149

disable Disable DD Boost. disable on page149

enable Enable DD Boost. enable on page150

fc Add or modify the DD Boost over Fibre Channel devices. fc on page 150

file-replication Set, reset, or display the status of the low-bandwidth optimization orencryption option for file replication. Show or reset statistics, history,and performance.

file-replication onpage 150

ifgroup For advanced load balancing and link failover, manage the interfacegroup (IP addresses) on a Data Domain private network that processesthe data transfer.

ifgroup on page154

option Set, reset, or display the status of the distributed segment processingfeature.

option on page156

reset Delete the DD Boost user, and reset the statistics. Clear all the jobconnection counters shown in the output of the ddboost showconnections command in the event that the network connection is

lost.

reset on page 157

set user-name Set the DD Boost username when DD Boost is enabled. set user-name onpage 157

show Display the DD Boost connections, DD Boost histogram, or statistics. show on page 157

status Show whether DD Boost is enabled or disabled. status on page159

storage-unit Create and delete a storage unit, or list the storage units and files in astorage unit.

storage-unit onpage 159

The ddboost command optionsThe following topics provide details about the purpose of each ddboost command option.

accessUse this command option to manage the DD Boost access for clients.



ddboost access add clients

ddboost access add clients client-list

Use this command to add clients to the DD Boost access list.

ddboost access delete clients

ddboost access del clients client-list

Use this command to delete clients from the DD Boost access list.

ddboost access reset

ddboost access reset

Use this command to reset the DD Boost client access list to the factory default.

ddboost access show

ddboost access show

Use this command to display the DD Boost client access list.

clients

ddboost clients add <client-list> [encryption-strength {medium | high}]

Administrators use this command to enable encrypted backup and restore over LAN, and specifythe encryption strength on a specified client or group of clients.

destroy

ddboost destroy

Administrators use this command to delete all the storage units and their contents from the DataDomain system. The command permanently removes all the data (files) contained in the storageunits.

You must also manually remove (expire) the corresponding catalog entries.

disable

ddboost disable

Administrators use this command to disable DD Boost for the Data Domain system.



enable

ddboost enable

Administrators use this command to enable DD Boost for the Data Domain system.

Whenever the user, user ID (UID), or group ID (GID) changes, the Data Domain system updates allthe files and storage units the next time that the ddboost enable command is issued.

fcThe Data Domain Operating System Command Reference Guide provides a full list of ddboost fccommands.

fc group add

ddboost fc group add groupname initiator "initiator_names"

Administrators use this command to grant access to these DD Boost over Fibre Channel devicesthrough an initiator, by adding the initiator to a ddboost-type scsitarget access group.

fc group modify

ddboost fc group modify groupname device-set count count

Administrators use this command to control the number of DD Boost over Fibre Channel devicesadvertised to the initiator by configuring the device-set of the scsitarget access group. Themaximum number of supported DD Boost over Fibre Channel devices per Data Domain system is64.

file-replication

file-replication option reset

ddboost file-replication option reset {low-bw-optim | encryption}

Administrators use this command to reset the low-bandwidth optimization or encryption to itsdefault value, which is disabled.

file-replication option set

ddboost file-replication option set encryption {enabled | disabled}ddboost file-replication option set low-bw-optim {enabled | disabled}

This command must be run on both Data Domain systems, the source system and the destinationtarget system. Only an administrator can specify these options.

Encryption must be enabled on both the source and destination systems.

Low-bandwidth optimization, which is disabled by default, is designed for use on networks withless than 6 Mbps aggregate bandwidth. Do not use this option if the maximum file system writeperformance is required.



After you enable low-bandwidth optimization on both systems, both systems must undergo a fullcleaning cycle to prepare the existing data. Run the following command on the source anddestination systems:

filesys clean start

The amount of time used by the cleaning cycle depends on the amount of data currently on theData Domain system.

file-replication option show

ddboost file-replication option show [low-bw-optim | encryption]

Use this command to show whether low-bandwidth optimization and/or encryption is enabled ordisabled for file replication.

file-replication reset stats

ddboost file-replication reset stats

Administrators use this command to reset the file-replication statistics when DD Boost is enabled.

file-replication show active

ddboost file-replication show active

Use this command to display the status of a DD Boost file-replication transfer to a Data Domainsystem. Prior to DD OS 5.1, this command only showed the status of DD Boost file-replicationtransfers outbound from a Data Domain system. With DD OS 5.1, this command also shows thestatus of DD Boost file-replication transfers inbound to a Data Domain system.

The low-bandwidth optimization status output indicates either that it is enabled and running, orthat it is enabled but there is a configuration mismatch.

file-replication show detailed-file-history

ddboost file-replication show detailed-file-history [duration duration{day | hr}]

Use this command to display the file-replication history over time. The output is organized by file;it is not cumulative data. You must specify a duration.

The data for each file name is organized by date, time, and direction (outbound or inbound). Valuesare given in KB for pre-compressed, post-filtered, post-low-bw-option, post-compressed, andnetwork data. The last value is an error code; 0 indicates that no error occurred. The followingexample provides a description of each column:

l Date: 2010/06/16

l Time: 07:48:22

l Direction: Outbound

l File name: /data/col1/x-ddp1/PEOST_00000001:0000000000:BEOST:4:0::l Pre-compressed: 3,765,837

l Post-filtered: 30,802



l Post-low-bw-optim: 30,802

l Post-compressed: 17,423

l Network: 65,550

l Error code: 0

file-replication show detailed-history

ddboost file-replication show detailed-history [duration duration{day | hr}] [interval interval{hr}]

Use this command to display the file-replication history over time. A cumulative history isdisplayed, as opposed to a view by file name. You must specify a duration.

Data is organized by date, time, and direction (outbound or inbound). Cumulative values are givenin KB for pre-compressed, post-filtered, post-low-bw-option, post-compressed, and network data.The last value is an error code; 0 indicates no error occurred.

file-replication show file-history

ddboost file-replication show file-history [duration duration{day | hr}]

Use this command to display the data transfer history for inbound and outbound traffic on each filein Data Domain system’s backup directory for a given duration at a specified interval. Thefollowing example shows the inbound and outbound traffic by date and time:

l Amount of pre-compressed data in KB

l Amount of post-compressed data in KB

l Network transfer data in KB

l Low-bandwidth optimization factor

l Number of errors

Table 13 Inbound and outbound file transfer

Date Time Direction Filename Pre-Comp(KB)

Post-Comp(KB)

Network(KB)

Low-bw-optim

Errors

2009/08/31 15:13:09 Inbound /backup/source.tar

47,738 26,634 27,527 1.32 0

2009/08/31 15:13:09 Outbound /backup/destin.tar

14,327 8,638 9,034 1.21 0

file-replication show history

ddboost file-replication show history [duration duration{day | hr}] [interval interval{hr}]

Use this command to display the data transfer history between the source and destination (target)Data Domain systems. The following information is shown for inbound and outbound traffic for agiven duration at a specified interval:



l Amount of pre-compressed data in KB

l Amount of post-compressed data in KB

l Network transfer data in KB

l Low-bandwidth optimization factor

l Number of errors

Table 14 Inbound and outbound data transfer

Date Time Direction Pre-Comp(KB)

Post-Comp(KB)

Network(KB)

Low-bw-optim

Errors

2010/08/31 11:14 Inbound 47,738 26,634 27,527 1.32 0

2010/08/31 11:14:09 Outbound 14,327 8,638 9,034 1.21 0

file-replication show performance

ddboost file-replication show performance [interval sec] [count count]

Use this command to display in real time, for a given duration at a specified interval, the amount ofpre-compressed outbound and inbound data versus the actual network throughput, or post-compressed data.

04/30 11:14:16 Outbound Inbound Pre-comp Network Pre-comp Network (KB/s) (KB/s) (KB/s) (KB/s) --------- --------- --------- --------- 0 0 1644 325 0 0 2901 470 0 0 2430 458 0 0 14390 300 0 0 0 70 0 0 2308 446 0 0 2814 552 0 0 3010 529

file-replication show stats

ddboost file-replication show stats

Use this command to monitor outbound and inbound traffic on a Data Domain system duringreplication. The compression ratio increases when low-bandwidth optimization is enabled.

Direction: OutboundNetwork bytes sent: 88,383,976Pre-compressed bytes sent: 436,874,240Bytes after filtering: 153,080,417Bytes after low-bw-optim: 145,547,868Bytes after local compression: 83,628,271Compression ratio: 4.9

Direction: InboundNetwork bytes received: 88,383,976Pre-compressed bytes received: 436,874,240Bytes after filtering: 153,080,417Bytes after low-bw-optim: 145,547,868



Bytes after local compression: 83,628,271Compression ratio: 4.9

ifgroupThe ifgroup option specifies an interface group.

ifgroup add interface

ddboost ifgroup add interface group-name {interface ipaddr | client host}

Use this command to add an interface, client, or both to the group-name or default group. Prior toadding an interface, you must create the group-name unless the group name is the default group.

Note: The group-name “default” is created during an upgrade of a fresh install and is alwaysused if group-name is not specified.

Additionally, the IP address must be configured on the Data Domain system and its interface mustbe enabled. You can add public or private IP addresses for data transfer connections. After addingan IP address as an interface, you must enable advanced load balancing and link failover.

The Data Domain Operating System Administration Guide provides more information about interfacegroups.

ifgroup create group-name

ddboost ifgroup create group-name

Use this command to create a group with the name group-name for the interface. You can use thecommand option on a single node and on a master node in a Global Deduplication Array (GDA).

The group-name can contain the characters ^, [0-9, a-z, A-Z],* $, underscore(_), and hyphen (-).Hostnames and fully qualified hostnames can be used. You can specify wildcard hostnames, asindicated by an asterisk (*). Reserved group names that cannot be used are: default, all, none.

ifgroup del interface

ddboost ifgroup del group-name {interface ipaddr | client host}

Use this command to remove an interface, client, or both from the group-name or default group.Deleting the last IP address interface disables the ifgroup. If this is the case, you have the optionof terminating this command option.

ifgroup destroy group-name

ddboost ifgroup destroy group-name

Use this command to destroy the group name. Only empty groups can be destroyed. Interfaces orclients cannot be destroyed, but can be removed sequentially or by using the command optionddboost ifgroup reset group-name.

Note: The group-name default cannot be destroyed.



ifgroup disable group-name

ddboost ifgroup disable group-name

Use this command to disable a specific group by entering the group-name. If group-name is notspecified, the command applies to the default group.

ifgroup enable group-name

ddboost ifgroup enable group-name

Use this command to enable the group specified by group-name. If group-name is not specified,the command enables the default group.

ddboost ifgroup rename

ddboost ifgroup rename source-group-name destination-group-name

Use this command to rename the ifgroup source-group-name to destination-group-name. Thiscommand option does not require disabling of the group.

ifgroup reset group-name

ddboost ifgroup reset group-name

Use this command to reset the group specified by group-name. If group-name is not specified, thecommand disables the default group.

ifgroup show config

ddboost ifgroup show config {interfaces | clients | groups | all} group-name

Use this command to display the selected configuration options. If no selection is made, all theinformation about the specified group-name is displayed.

If group-name is not specified, all the information about the default group is displayed. Specify theall option to view the configuration options of all the groups. All users can specify this commandoption.

ifgroup status group-name

ddboost ifgroup status group-name

Use this command to display the status of link aggregation, as enabled or disabled. The status isdisplayed for all the groups unless group-name is specified. All users can specify this commandoption.



option

option reset distributed-segment processing

ddboost option reset distributed-segment processing

Administrators use this command to reset the distributed segment processing to the defaultoption, which is enabled.

option set distributed-segment processing

ddboost option set distributed-segment-processing {enabled | disabled}

Administrators use this command to enable or disable the distributed segment processing featureon the DD OS. By default, it is enabled for DD OS 5.1. If this feature presents any problem for adatabase server, use this command to disable the feature on the Data Domain system.

Distributed segment processing is supported only if the feature is enabled on the Data Domainsystem.

Note:

l Distributed segment processing is enabled by default in DD OS 5.1.

l If a system is upgraded from DD OS 4.9 to DD OS 5.0 and the boost option was disabledbefore the upgrade, then the distributed-segment-processing option is disabledafter the upgrade.

option show distributed-segment processing

ddboost option show distributed-segment-processing

Use this command to show whether the distributed segment processing option is enabled ordisabled.

option reset virtual-synthetics

ddboost option reset virtual-synthetics

Use this command to reset the virtual synthetics to the default option, which is disabled. Virtualsynthetics is supported on single-node configurations and DD Extended Retention systems only.

option set virtual-synthetics {enabled | disabled}

ddboost option set virtual-synthetics {enabled | disabled}

Use this command to enable or disable the virtual synthetics feature on the DD OS. Virtualsynthetics is supported on single-node configurations and DD Extended Retention systems only.

option show virtual-synthetics

ddboost option show [virtual-synthetics]



Use this command to display the status of the virtual synthetics, as enabled or disabled. All userscan run this command.

reset

reset stats

ddboost reset stats

Administrators use this command for either of the following purposes:

l To reset all the statistics when DD Boost is enabled.

l As a network recovery procedure to clear job connections after the network connection hasbeen lost.

reset user-name

ddboost reset user-name username

Use this command to delete and reset the DD Boost username.

Note: This command is deprecated. It is recommended that you use the ddboost userunassign command instead.

set user-name

ddboost set user-name user-name

Use this command to set the DD Boost username when DD Boost is enabled.

show

show connections

ddboost show connections

Use this command to display the following information:

l Number of active clients, and for each active client:

n Client’s name.

n Whether or not the client is idle (yes/no).

n Number of installed CPUs.

n Amount of memory in MiB.

n Version number of Installed Oracle RMAN agent.

n Name and version of the operating system.

n Oracle version number.

n RMAN version number.

l Number of connections that a system uses for DD Boost, and whether these connections arespread across interfaces by using advanced load balancing and link failover. The followingsample shows the output for client connections.



l Number of connections used for a given group, even when the interface has been removedfrom the ifgroup.

l Overview of interfaces available for DD Boost.

show histogram

ddboost show histogram

Use this command to display a DD Boost histogram for the Data Domain system.

Table 15 Output definitions for DD Boost histogram

OPER Name of the operation request sent from a DD Boost client to theData Domain system.

mean Mathematical mean time for completion of the operations, inmilliseconds (ms).

std-dev Standard deviation for the time to complete operations, derivedfrom the mean time, in ms.

<1ms Number of operations that took less than 1 ms.

<5ms Number of operations that took between 1 ms and 5 ms.



<1s Number of operations that took between 100 ms and 1 second.

<10s Number of operations that took between 1 second and 10 seconds.

>10s Number of operations that took more than 10 seconds.

total Total time taken for a single operation, in ms.

max Maximum time taken for a single operation, in ms.

min Minimum time taken for a single operation, in ms.

show stats

ddboost show stats [interval seconds] [count count]

Use this command to display the output of the previous show stats command, the number ofbytes written to and read from files contained in storage units, and the number of files created anddeleted from storage units. The number of errors encountered for each operation is also displayed.Optionally, you can display the statistics for a specific number of seconds. The count displays thenumber of lines equal to the count value.

If distributed segment processing is enabled, the number of bytes transferred through distributedsegment processing and the amount of compression achieved is displayed.

show user-name

ddboost show user-name



Use this command to display the default DD Boost user if one is configured, or otherwise displaythat there is no default user.

Note: This command is deprecated. It is recommended that you use the ddboost usershow command instead.

status

ddboost status

Use this command to determine whether DD Boost is enabled or disabled.

storage-unit

storage-unit create

ddboost storage-unit create storage_unit_name [quota-soft-limit n {MiB|GiB|TiB|PiB}] [quota-hard-limit n {MiB|GiB|TiB|PiB}]

Use this command to create a storage unit and set limits. The mtree command description in theData Domain Operating System Command Reference Guide provides details on quota limits. If thequota feature is not enabled, the quota is created but a message appears stating that the feature isdisabled and limits are not enforced, as shown in Example 2. The quota command description inthe Data Domain Operating System Command Reference Guide provides details.

Quotas can cause OpenStorage backup applications to report non-intuitive sizes and capacities.The Knowledge Base article 85210, available on the Support portal, provides details.

Example 1

ddboost storage-unit create SU_1 quota-soft-limit 793 GiB quota-hard-limit 1078 GiB

Created storage-unit SU_1 quota-soft-limit: 793 GiB, quota-hard-limit: 1078 GiB

Example 2

ddboost storage-unit create SU_2 quota-soft-limit 1586 GiB

** Quota is disabled. Quota limits are not enforced. Created storage-unit SU_2 quota-soft-limit: 1586 GiB, quota-hard-limit: N/A

storage-unit delete

ddboost storage-unit delete storage-unit-name

Administrators use this command to delete a specified storage unit and all of its contents. Youmust also manually remove (expire) the corresponding catalog entries.



storage-unit show

ddboost storage-unit show [compression] [storage-unit-name]

Use this command to display the names of all the storage units or, optionally, the names of all thefiles in a specified storage unit.

To display the compression for all the storage units (the original byte size, global compression, andlocal compression for all storage units), use the compression option.

Note: To interrupt the output of this command, press Ctrl+C.



APPENDIX A

Installation and Configuration Checklist

This appendix contains the following topics:

l Configure the Data Domain system......................................................................................162l Download and install the Oracle RMAN agent...................................................................... 162l Configure RMAN for the environment................................................................................. 162l Test the installation by using sbttest (optional) .................................................................. 163l Backup examples................................................................................................................. 163


Configure the Data Domain systemAbout this task

Configuring the Data Domain System for Stand-alone Oracle RMAN Agent Deployments on page33 provides details about the following steps.

Procedure

1. Add the DD Boost license.

2. Establish the server name, username, and password for the Data Domain system.

Note: The server name, username, and password must exactly match what is used in thesend command of Step 2 in Configure RMAN for the environment on page 162.

3. Enable DD Boost.

4. Create a logical storage unit, as described in Creating storage units on page 36.

5. Enable the distributed segment processing.

6. Check the connectivity. (Can I ping the DDR server name from the backup server?) Ensurethat the firewall is not blocking ports.

Download and install the Oracle RMAN agentAbout this task

Configuring the Oracle RMAN Agent for Stand-alone Deployment on page 49 provides detailsabout the following steps.

Procedure

1. Download the Oracle RMAN agent software.

2. Complete the software installation and setup procedures.

Configure RMAN for the environmentAbout this task

Configuring the Oracle RMAN Agent for Stand-alone Deployment on page 49 provides detailsabout the following steps.

Procedure

1. Run the command CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE'.

Configuring the software on Linux and UNIX systems on page 57 or Configuring thesoftware on Windows systems on page 62 provide more information. Ensure that the PARMSoption is set correctly.

2. Run the command ALLOCATE CHANNEL.

Registering each Data Domain system on page 62 provides more information. Set thelibrary, and run the send command to set the server name, username, and password. Theserver name, username, and password must match exactly what is used in step 2 in Configure the Data Domain system on page 162.



3. Run the command CONFIGURE DEFAULT DEVICE TYPE 'SBT_TAPE'.

Registering each Data Domain system on page 62 provides more information.

Test the installation by using sbttest (optional)Oracle provides the sbttest command as a diagnostic tool. Before you run sbttest with theOracle RMAN agent, set the following system environment variables by using the same values asrequired for the PARMS option in step 1 of Configure RMAN for the environment on page 162:

l ORACLE_HOMEl RMAN_AGENT_HOMEl BACKUP_HOSTl STORAGE_UNITLinux example

export ORACLE_HOME=/oracle_homeexport BACKUP_HOST=MyDDRexport STORAGE_UNIT=MyStorageUnitNamesbttest MyFileName -trace MyTraceFileName -libname <ddboost_directory>/lib/libddobk.so

Backup examples

RMAN> backup copies 2 database format '%u_%p', '<destination_system>/%u_%p' filesperset=1;

RMAN> backup database format '%u_%p';



APPENDIX B

Performing a Backup with Oracle EnterpriseManager


l Example screens.................................................................................................................. 166


Example screensFigure 9 Login window

Figure 10 Database instance page

Figure 11 Processing page

Performing a Backup with Oracle Enterprise Manager


Figure 12 Schedule Customized Backup: Options page

Figure 13 Schedule Customized Backup: Schedule page

Figure 14 Schedule Customized Backup: Review page



Figure 15 Execution page



APPENDIX C

Installing and Configuring the Oracle RMANAgent


l Installation and configuration examples................................................................................170


Installation and configuration examplesExtraction of Oracle RMAN agent software package

The following command and output provide an example of the software extraction for the OracleRMAN agent on Linux. You must run the tar -xvf <file_name> command to extract the OracleRMAN agent files from the tar file.

tar -vxf ddrman193_linux_x86_64.tar ././readme.txt./license.txt./libddobk.so./ddutil./install.sh./uninstall.sh./libLockbox.so./libEnshroud-OpenSSL.so./libDDBoost.so./rman_agent.cfg./ddbmcon./ddbmoim./libddboravalidate.so./libssl.so.1.0.0./libcrypto.so.1.0.0./libddvdisk.so./adm-agent-19.1.0.rpm

Oracle RMAN agent installation

The following command and output provide an example of the Oracle RMAN agent installation, inwhich the install.sh script guides the user through the process. The directoryRMAN_AGENT_HOME:/home/oracle1/rman_agent_home has been selected. The OracleRMAN agent is being installed for the first time on the system, which has no previous installationsof pre-19.3 Oracle RMAN agent software.

./install.sh Do you want to install under the default installation directory /home/oracle/opt/dpsapps/rmanagent? (y or n)yThe lib directory /home/oracle/opt/dpsapps/rmanagent/lib is created.The config directory /home/oracle/opt/dpsapps/rmanagent/config 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 breadcrumbs directory /home/oracle/opt/dpsapps/rmanagent/breadcrumbs is created.Installing the Oracle RMAN agent.Copying the lockbox libraries to /home/oracle/opt/dpsapps/rmanagent/lib/.Copying libddobk.so to /home/oracle/opt/dpsapps/rmanagent/lib/.Copying libDDBoost.so to /home/oracle/opt/dpsapps/rmanagent/lib/.Copying ddutil to /home/oracle/opt/dpsapps/rmanagent/bin/.Copying the dependency libraries to /home/oracle/opt/dpsapps/rmanagent/lib/.Copying the configuration file to /home/oracle/opt/dpsapps/rmanagent/config/.Copying the ddbmcon program to /home/oracle/opt/dpsapps/rmanagent/bin/.Creating the lockbox.Successfully installed the Oracle RMAN agent.Environment variable ORACLE_HOME is not defined.Installation is completed.

Installing and Configuring the Oracle RMAN Agent


Oracle RMAN agent installed files

The following command and output provide an example of the Oracle RMAN agent files that wereinstalled:

l The shared library libddobk.so and its dependent libraries were installed under the$RMAN_AGENT_HOME/lib directory.

l The ddutil binary was installed under the $RMAN_AGENT_HOME/bin directory.l The config directory was created for the lockbox.

Note: Currently, there is no lockbox because this is a new installation.

l The logs directory was created for the ddutil program logs.

/opt/dpsapps/rmanagent> ls -alR.:total 28drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 3 oracle oradba 4096 2018-02-01 12:00 ..drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 bindrwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 breadcrumbsdrwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 configdrwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 libdrwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 logs

./bin:total 23836drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 ..-rwxr-xr-x 1 oracle oradba 22697509 2018-02-01 12:00 ddbmcon-rwxr-xr-x 1 oracle oradba 1666061 2018-02-01 12:00 ddutil

./breadcrumbs:total 8drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 ..

./config:total 20drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 ..-rw-rw-r-- 1 oracle oradba 3334 2018-02-01 12:00 ddboost.config-rw-rw-r-- 1 oracle oradba 4 2018-02-01 12:00 ddboost.config.FCD-r-xr-xr-x 1 oracle oradba 1947 2018-02-01 12:00 rman_agent.cfg

./lib:total 27500drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 ..-rwxr-xr-x 1 oracle oradba 2998084 2018-02-01 12:00 libcrypto.so.1.0.0-rwxr-xr-x 1 oracle oradba 3520368 2018-02-01 12:00 libDDBoost.so-rwxr-xr-x 1 oracle oradba 6713824 2018-02-01 12:00 libddboravalidate.so-rwxr-xr-x 1 oracle oradba 1690051 2018-02-01 12:00 libddobk.so-rwxr-xr-x 1 oracle oradba 9965056 2018-02-01 12:00 libddvdisk.so-rwxr-xr-x 1 oracle oradba 2498081 2018-02-01 12:00 libEnshroud-OpenSSL.so-rwxr-xr-x 1 oracle oradba 206659 2018-02-01 12:00 libLockbox.so-rwxr-xr-x 1 oracle oradba 495171 2018-02-01 12:00 libssl.so.1.0.0

./logs:total 8drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 ..

Registration of the Data Domain user

The following commands and output provide an example registration of a Data Domain user withthe Data Domain server. This example shows the registration of the Data Domain user q_ost with



password 4U2build to enable access to the storage unit rman_oracle on the Data Domain servertest-data-domain.emc.com. The registration is required for each separate storage unit that isused with the same Oracle host and Data Domain system.

RMAN> connect target *2> 3> RUN {4> ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS5> 'BLKSIZE=1048576,6> SBT_LIBRARY=/home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so,7> ENV=(BACKUP_HOST=test-data-domain.emc.com,8> RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent/)';9> send 'set username qa_ost password 4U2build servername test-data-domain.emc.com storageunit rman_oracle';10> RELEASE CHANNEL CH1;11> }12> 13> 14> connected to target database: orcl (DBID=1040017416)

using target database control file instead of recovery catalogallocated channel: CH1channel CH1: SID=25 device type=SBT_TAPEchannel CH1: Data Domain Boost API

sent command to channel: CH1

released channel: CH1

Recovery Manager complete.

Oracle RMAN agent lockbox files

The following command and output provide an example of the lockbox files that were created afterthe registration.

~/opt/dpsapps/rmanagent/config> ls -altotal 20drwxrwxrwx 2 oracle oradba 4096 2018-02-01 12:00 .drwxr-xr-x 7 oracle oradba 4096 2018-02-01 12:00 ..-rw-rw-r-- 1 oracle oradba 3334 2018-02-01 12:00 ddboost.config-rw-rw-r-- 1 oracle oradba 4 2018-02-01 12:00 ddboost.config.FCD-r-xr-xr-x 1 oracle oradba 1947 2018-02-01 12:00 rman_agent.cfg

Oracle RMAN agent channel configuration and backup

The following commands and output provide an example of the channel configuration that isrequired to run backups and a subsequent backup operation.

Recovery Manager: Release 11.2.0.1.0 - Production on Thu Feb 1 13:03:53 2018

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

RMAN> connect target *2> connect catalog *3> 4> RUN {5> ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE' TRACE 5 PARMS6> 'BLKSIZE=1048576, SBT_LIBRARY=/home/oracle/opt/dpsapps/rmanagent/lib/libddobk.so, ENV=(STORAGE_UNIT=rman_agent, BACKUP_HOST=test-data-domain.emc.com, RMAN_AGENT_HOME=/home/oracle/opt/dpsapps/rmanagent/)';7> BACKUP FORMAT './rman/%U_%p_%t' DATABASE;



8> RELEASE CHANNEL CH1;9> }10> connected to target database: orcl (DBID=1040017416)

connected to recovery catalog database

allocated channel: CH1channel CH1: SID=58 device type=SBT_TAPEchannel CH1: Data Domain Boost API

Starting backup at 01-FEB-18channel CH1: starting full datafile backup setchannel CH1: specifying datafile(s) in backup setinput datafile file number=00001 name=/mnt/oracle/orcl/system_1/system.data1input datafile file number=00006 name=/mnt/oracle/orcl/system_1/system.data2input datafile file number=00002 name=/mnt/oracle/orcl/system_1/sysaux.dbfinput datafile file number=00003 name=/mnt/oracle/orcl/undo_1/undo.data1input datafile file number=00005 name=/mnt/oracle/orcl/system_1/cattbs.dbfinput datafile file number=00004 name=/mnt/oracle/orcl/orcl/orcl.data1channel CH1: starting piece 1 at 01-FEB-18channel CH1: finished piece 1 at 01-FEB-18piece handle=./rman/lgsq4uhs_1_1_1_966949436 tag=TAG20180201T130356 comment=API Version 2.0,MMS Version 19.3.0.0channel CH1: backup set complete, elapsed time: 00:00:03Finished backup at 01-FEB-18

Starting Control File Autobackup at 01-FEB-18piece handle=c-1040017416-20180201-07 comment=API Version 2.0,MMS Version 19.3.0.0Finished Control File Autobackup at 01-FEB-18

released channel: CH1

Recovery Manager complete.



Dell EMC PowerProtect Oracle RMAN Agent 19.3 ... · Dell EMC PowerProtect Oracle RMAN Agent Version...

Documents

Transcript of Dell EMC PowerProtect Oracle RMAN Agent 19.3 ... · Dell EMC PowerProtect Oracle RMAN Agent Version...