RMAN Performance Tuning Using Buffer Memory Parameters
(Doc ID 1072545.1)
Last updated on JANUARY 04, 2021
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2]
Enterprise Manager for Oracle Database - Version 188.8.131.52 to 184.108.40.206 [Release 11.1]
Oracle Database - Enterprise Edition - Version 10.2.0.5 to 220.127.116.11 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 16-Aug-2013***
The purpose of RMAN performance tuning is to identify the bottlenecks for a given backup or restore job and use RMAN commands, initialization parameters, or adjustments to physical media to improve overall performance.
As database sizes continue to grow unabated, with tens to hundreds of terabytes prevalent in customer's environments, server and storage systems have also dramatically increased in resource, network, and I/O capacity to support required database backup and restore windows. Against this backdrop, RMAN performance tuning becomes more important than ever.
This document details RMAN performance tuning guidelines as they relate to buffer memory usage during backup and restore operations. These guidelines are targeted to systems where the available I/O exceeds 100 MB/s, while memory, CPU, network consumption, and tape drive throughput do not constrain overall RMAN performance. This is especially true in very high performance configurations, e.g. Exadata. In these environments, the default RMAN buffer sizes are usually inadequate and should be increased.
It is assumed that the reader has a basic understanding of RMAN performance tuning concepts. See the Backup and Recovery User's Guide for an overview of RMAN tuning.
DBA with intermediate-advanced RMAN experience
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