My Oracle Support Banner

Master Note For Oracle Recovery Manager (RMAN) (Doc ID 1116484.1)

Last updated on JUNE 04, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Details

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support Notes with respect to Oracle Recovery Manager (RMAN).

In case you may want or need more about your current topic - please also access the Backup & Recover Community of Customers and Oracle Specialists directly via:
https://community.oracle.com/community/support/oracle_database/database_backup_and_recovery


This Master Note is subdivided into categories to allow for easy access and reference to notes that are applicable to your area of interest, within RMAN.This includes the following categories:



Actions

Introduction

Recovery Manager is Oracle’s utility to manage the backup, and more importantly the recovery, of the database. It eliminates operational complexity while providing superior performance and availability of the database. Recovery Manager debuted with Oracle8 to provide DBAs an integrated backup and recovery solution.

Recovery Manager determines the most efficient method of executing the requested backup, restore, or recovery operation and then executes these operations in concert with the Oracle database server. Recovery Manager and the server automatically identify modifications to the structure of the database and dynamically adjust the required operation to adapt to the changes.

This note applies to the following versions of these products:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.x
Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.x
Oracle Server - Enterprise Edition - Version: 11.2.0.1 to 11.2.0.x
Oracle Server - Enterprise Edition - Version: 12.1.0.1 to 12.2.0.x

Getting started with RMAN

The articles in this section give you a overview of the oracle utility RMAN,the new features of RMAN in Oracle 11 release 1,2,12.1,12.2 and FAQ on RMAN.

<Note.360416.1>  Getting Started with Recovery Manager (RMAN)
<Note.469777.1>  RMAN - Frequently Asked Question (FAQ)
<Note 809867.1>  RMAN 11gR1: New Features
<Note 1115423.1> RMAN Enhancements In Oracle 11g.
<Note 1534487.1> RMAN Enhancements in Oracle 12c
<Note 1521005.1> RMAN Pluggable Database Backup and Recovery in a Multitenant Environment
<Note 1521075.1> RMAN Pluggable Database Point in Time Recovery

 

 Rman compatibility

<Note.73431.1> RMAN Compatibility Matrix

 

Flash Recovery Area

The flash recovery area is an Oracle-managed directory, file system, or Automatic Storage Management disk group that provides a centralized disk location for backup and recovery files. All the files you need to completely recover a database from a media failure are part of the Flash Recovery Area. Oracle creates archived logs and flashback logs in the flash recovery area. RMAN can store its backup sets and image copies in the flash recovery area, and it uses it when restoring files during media recovery. The flash recovery area also acts as a disk cache for tape.

The articles mentioned in the following section help you in understanding the concepts and working of flash recovery area, RMAN integration with the flash recovery area,troubleshooting flash recovery area issues. 

<Note.305648.1> What is a Flash Recovery Area and how to configure it?
<Note.305796.1> RMAN and Flash Recovery Area
<Note.833663.1> Flash Recovery Area - FAQ
<Note.560133.1> Benefits Of Using Flash Recovery Area
<Note.315098.1> How is the space pressure managed in the Flash Recovery Area - An Example.
<Note.305812.1> Flash Recovery area - Space management Warning & Alerts
<Note.829755.1> Space issue in Flash Recovery Area(FRA)
<Note.305810.1> Configuring file creation in Flash recovery area and order of Precedence
<Note.305651.1> How to change Flash Recovery Area to a new location?
<Document 2308215.1> 12.2 Perform Flashback at PDB Level
<Document 1521524.1> RMAN RECOVER TABLE Feature New to Oracle Database 12c

 

Configuring the Environment for RMAN Backups

To simplify ongoing use of RMAN, you can set a number of persistent configuration settings for each target database. These settings control many aspects of RMAN behavior. For example, you can configure the backup retention policy, default destinations for backups, default backup device type, and so on. You can use the SHOW and CONFIGURE commands to view and change RMAN configurations.

The articles mentioned in the following section help you in configuring the rman persistent configurations,understanding their behavior and troubleshooting them.

<Note.462978.1> Rman backup retention policy
<Note.463875.1> Frequently asked questions on Rman backup retention policy
<Note.351455.1> Oracle Suggested Strategy & Backup Retention

 

Recovery Catalog for Rman backups.

A recovery catalog is a set of tables and views that Recovery Manager (RMAN) uses to store metadata (information about a database structure, archived redo logs, backup sets, and data file copies) about a target database (database that RMAN backups or restores). RMAN uses this metadata to conduct its backup, recovery, and maintenance operations. Recovery catalog is optional, i.e., if a recovery catalog is not created, RMAN uses the target database’s control file to store the metadata about the target database. Although RMAN can conduct all major backup and recovery operations by using the control file, some RMAN commands work only if a recovery catalog exists.

The articles in the following section describe the configuration, management of recovery catalog and some of the known issues related to recovery catalog.

<Note.452529.1> Recovery catalog for RMAN backup
<Note.467969.1> How To Configure RMAN Recovery Catalog Using Enterprise Manager DB Console.
<Note 2039848.1> Known Issues with RMAN Oracle12c Catalog

 

Backing up Database files using RMAN and Maintaining the backup records.

The articles and links in the following section describe the different methods to perform backups and useful rman backup methods.

Oracle Database Backup and Recovery Advanced User's Guide

<NOTE:388422.1>  Top 10 Backup and Recovery best practices
<Note 262853.1>  10G RMAN Fast Incremental Backups
<Note.745798.1>  Merged Incremental Backup Strategies
<Note.735953.1>  How To Configure RMAN Backups To Tape via Oracle Enterprise Manager 
<Note.550082.1>  How To Catalog Tape Backup Pieces
<Note.137181.1>  RMAN Backup Shell Script Example

 

Restore and recovery techniques/scenarios using RMAN.

The articles in this section provide various restore and recovery techniques and scenarios what can be achieved using rman.

<Note.144911.1>  RMAN:  Block-Level Media Recovery - Concept & Example
<NOTE:388422.1>  Top 10 Backup and Recovery best practices
<Note.94114.1>   Backup and Recovery Scenarios
<Note.372996.1>  Using RMAN to Restore and Recover a Database When the Repository and Spfile/Init.ora Files Are Also Lost
<Note.223543.1>  How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMAN
<Note.403883.1>  How To Restore Controlfile From A Backupset Without A Catalog Or Autobackup
<Note.580414.1>  RMAN - How to restore the controlfile using RMAN
<Note.419137.1>  How To Restore Rman Backups On A Different Node When The Directory Structures Are Different
<Note.415579.1>  HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node
<Note.472536.1>  10g RMAN Benefits of Simplified Recovery Through Resetlogs.
<Note.358171.1>  Oracle10g RMAN will not restore in parallel from tape
<Document 2300465.1> 12.2 NEW FEATURE : -RECOVER DATABASE UNTIL AVAILABLE REDO

 

Tablespace point in time recovery

Recovery Manager (RMAN) Automatic TSPITR enables quick recovery of one or more tablespaces in a database to an earlier time without affecting the rest of the tablespaces and objects in the database.Here are a few articles which explain the steps involved in performing a TSPITR:

<Note 335851.1> Automatic TSPITR in 10G RMAN -A walk Through
<Note 1531202.1> RMAN TSPITR Tips and Tricks
<Note 304305.1> Limitations of RMAN TSPITR

 

Rman Transportable tablespaces and database.

Rman can be used to create transportable tablespace sets and can be used to convert the datafiles for cross platform transportable tablespace and database. Here are a few articles which provide all the required information to understand the procedures:

<Note.371556.1> How move tablespaces across platforms using Transportable Tablespaces with RMAN
<Note.455593.1> Creating a transportable tablespace set from RMAN backupsets
<Note.831223.1> Using Rman Incremental backups To Update Transportable Tablespaces.
<Note.1401921.1> Cross-Platform Database Migration (across same endian) using RMAN Transportable Database
<Note.733205.1> Migration of Oracle Database Instances Across OS Platforms
<Note 1389592.1> 11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
<Note 2005729.1> 12C - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
<Document 2307383.1> 12.2 RMAN Cross Platform Tablespace Transport Over Network
<Document 2307358.1> 12.2 RMAN Cross Platform Transport Of TDE-encrypted tablespace


Rman Duplicate Database

Database duplication is the use of the DUPLICATE command to copy all or a subset of the data in a source database. The duplicate database (the copied database) functions entirely independently from the source database (the database being copied).In articles in this section help you in understanding the duplicate procedures and various techniques available for the rman duplicate operation.

<Note.228257.1>  RMAN 'Duplicate Database' Feature in Oracle9i / 10G and 11G
<Note.452868.1>  RMAN 'Duplicate Database' Feature in 11G
<Note.388431.1>  Creating a Duplicate Database on a New Host.
<Note.382669.1>  Duplicate database from non ASM to ASM (vise versa) to a different host
<Note.388424.1>  How To Create A Production (Full or Partial) Duplicate On The Same Host
<Note.293717.1>  How to duplicate a database to previous incarnation
<Note.1910175.1> RMAN DUPLICATE / RESTORE including Standby in ASM with OMF / non-OMF / Mixed Name for Datafile / Online Log / Controlfile
<Note.1913937.1> RMAN Duplicate Database From RAC ASM To RAC ASM
<Note.840647.1>  Article on How to do Rman Duplicate on ASM/RAC/OMF/Single Instance
<Note.360962.1>  Manual Completion of a Failed RMAN Duplicate
<Note.369644.1>  Answers To FAQ For Restoring Or Duplicating Between Different Versions And Platforms
<Note.1079563.1> RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support
<Note 1375864.1> Perform Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups
<Document 2022820.1> Upgrade to 12c(12.1 /12.2) through RMAN Duplicate using BACKUP LOCATION with NOOPEN clause

 

Rman Performance.

<Note.360443.1>  RMAN Backup Performance
<Note 740911.1>  RMAN Restore Performance
<Note 247611.1>  Known RMAN Performance Problems
<Note 579158.1>  Advise On How To Improve Rman Performance
<Note 463227.1>  Oracle10g RMAN Recovery Catalog Known Performance Issues
<Note 1487262.1> Script to monitor RMAN Backup and Restore Operations

 

RMAN and Media managers

Oracle designed an architecture that allows RMAN to manage the process of database backup and recovery, yet integrate with industry-leading tape storage management subsystems. The interface between Rman and media management vendor products is keyed on an Oracle design specification. This specification allows Oracle RMAN to use third party media management software to back-up to and restore from tape.

Many organizations rely on Oracle to provide solutions for very large or highly distributed mission critical systems. In addition to needing databases capable of handling large amounts of data and complex queries, these organizations also need robust backup and recovery technology. Recovery of data quickly and reliably is paramount should some aspect of the system fail. To address these needs, Oracle has created the Backup Solutions Program (BSP), a cooperative program designed to facilitate tighter integration between Oracle's backup products and those of third-party media management vendors. Together, Oracle and media management vendors provide robust easy-to-use database backup and recovery solutions to customers with high-end requirements.

The link to access the information regarding backup solutions program is:

http://www.oracle.com/technetwork/database/features/availability/bsp-088814.html


"Under the BSP, vendors are committed to integrating Recovery Manager (RMAN) with their media management software packages and provide first line technical support for the integrated backup and recovery solutions for Oracle RDBMS."

So any issues related to the media manager functionality or configuration has to be addressed only by the vendors and not by Oracle.

Below are a few articles which help you in understanding the most common issues with rman backups to tape, environment variable used for backups to tape and procedure to check if the media manager installation has been done properly.

<Note.942418.1>  How To Verify A Media Manager Layer Installation?
<Note 227517.1>  Main Index of Common Causes for ORA-19511
<NOTE.312737.1>  RMAN and Specific Media Managers Environment Variables.

 

Rman and Dataguard

Data Guard and RMAN were both designed with the Oracle database architecture in mind. Together, they offer the most reliable and tightly integrated solution to achieve superior levels of Oracle database availability supporting your mission critical applications. Data Guard and RMAN are both fully supported features of the Oracle Database Enterprise Edition (RMAN is also provided with Oracle Database Standard Edition).Here are a few articles that help you in effectively using rman with dataguard and some of the known rman issues with dataguard.

<Note.848716.1> Using RMAN Effectively In A Dataguard Environment
<Note.357759.1> Known RMAN - Dataguard Problems
<Note 836986.1> Steps to perform for Rolling forward a standby database using RMAN Incremental Backup.

 

Rman and Rac

<Note 243760.1> RMAN: RAC Backup and Recovery using RMAN
<Note.415579.1> HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node
<Note.1913937.1> RMAN Duplicate Database From RAC ASM To RAC ASM
<Note.840647.1> Article on How to do Rman Duplicate on ASM/RAC/OMF/Single Instance

 

Rman and Corruption

Rman is a very effective utility in identifying the database block corruption. Here are are a few article which provides the information about using rman to detect and fix corruption.

<Note 836658.1> Identify the corruption extension using RMAN/DBV/ANALYZE etc
<Note.561010.1> Which Blocks Will RMAN Check For Corruption Or Include In A Backupset?
<Note 428570.1> Best Practices for Avoiding and Detecting Corruption
<Note.472231.1> How to identify all the Corrupted Objects in the Database reported by RMAN
<Note 471716.1> 11g New Feature V$Database_block_corruption Enhancements and Rman Validate Command

 

Related Master Notes

<Note 1199803.1> Master Note For Oracle Backup And Recovery
<Note 1096952.1> Master Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle Grid Infrastructure
<Note 1088018.1> Master Note for Oracle Database Corruption
<Note 1101938.1> Master Note for Data Guard

 

Using My Oracle Support Effectively

<Note 747242.5> My Oracle Support Configuration Management FAQ


<Note 166650.1> Working Effectively With Global Customer Support
<Note 199389.1> How To Request Management Attention to a Service Request (SR) with Oracle Support Services

 

Generic Links

<Note 854428.1>  Patch Set Updates for Oracle Products
<Note 1061295.1> Patch Set Updates - One-off Patch Conflict Resolution
<Note 756671.1>  Oracle Recommended Patches -- Oracle Database
<Note 268895.1>  Oracle Database Patchset Information, Versions 10.2.0 to 12.1.0
<Note 161549.1> Oracle Database Server and Networking Patches for Microsoft Platforms
<Note 161818.1> Oracle Database (RDBMS) Releases Support Status Summary

 

Community Discussion

You can directly participate in the Discussion about this article below. The Frame is the interactive live Discussion - not a Screenshot ;-)

Contacts

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Details
Actions
 Introduction
 Getting started with RMAN
 Backing up Database files using RMAN and Maintaining the backup records.
 Restore and recovery techniques/scenarios using RMAN.
 Tablespace point in time recovery
 Rman Transportable tablespaces and database.
 Rman Performance.
 RMAN and Media managers
 Rman and Dataguard
 Rman and Rac
 Rman and Corruption
 Related Master Notes
 Using My Oracle Support Effectively
 Generic Links
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.