Final v21

1
Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Backup and Recovery of

Oracle Exadata
Best Practices & Experiences
Andrew Babb, Consulting Member of Technical Staff
Donna Cooksey, Principal Product Manager
Levi Norman, Product Marketing Director
Exadata - One Machine | Many Workloads

DATA WAREHOUSING
OLTP
MIXED WORKLOADS
DATABASE CONSOLIDATION
DATABASE CLOUD
A Complete, Integrated, Optimized Platform

100% Supported by Oracle
Scale-Out Database Servers
High Volume 2 or 8 socket servers
Oracle Database 11g, RAC, ASM, EM12c
Compatible with all 11g databases, apps, tools
Scale-Out Intelligent Storage Servers
High Volume 2-socket storage servers
Exadata Storage Server Software
InfiniBand Network
Unified internal connectivity ( 40 Gb/sec )
Oracle Exadata Innovation

Storage Server Software
10X
Up to
50X
Hybrid Columnar Compression
Smart Flash
Cache
Smart Scan Queries
Standardized and Simple to Deploy

Delivered Ready-to-Run
Oracle Exadata Database Machines Are The Same
Thoroughly Tested & Highly Supportable
Identical Configuration Used by Oracle Engineering
Run Existing OLTP and DW Applications

30 Years of Oracle DB Capabilities
No Exadata Certification Required
Leverage Oracle Ecosystem

Skills, Knowledge Base, People, & Partners
1000s of Deployments at Leading Companies

50% Data Warehouses, 50% OLTP / Mixed Workloads
Petabyte Warehouses
E-business Suite, PeopleSoft,
Siebel, JDE, SAP
Regulatory Reporting
Online Financial Trading

E-Commerce Sites
Consolidation of 100s of
Databases
The Data Protection Dilemma
Weekly Full +
Daily Incremental
To Tape
Agenda
Overview of Oracle Data Protection Technologies

Architecting an Exadata Backup and Recovery Solution
Database Consolidation and Data Protection
Recovery is King
Oracle Data Protection Strategies

Backup & Recovery
Physical Data Protection
Recovery Manager (RMAN)
Oracle Secure Backup (OSB)
Logical Data Protection - Flashback Technologies

Recovery Analysis - Data Recovery Advisor
Disaster Recovery
Physical Data Protection - Data Guard
10
Recovery Time Objective (RTO)

Days/Hours
Hours/Minutes
Minimizes time for problem identification & recovery
planning

Minutes/Seconds
What are Your Recovery Requirements?

Begin by Asking Questions
How quickly do you need to recover?
Recovery Point Objective (RPO)

How much data, if any, can be lost?
Backup Retention Policy

What are the onsite, offsite and long-term retention objectives?
What is the acceptable performance

Do you need to minimize the impact of the backup?
11
Exadata Backup & Recovery Rates

Exadata
Storage
ZFS
Storage
Appliance
StorageTek
Tape
Library
Database
Backup
20 TB/hr
- 25 TB/hr
27 TB/hr
13 TB/hr
9 TB/hr
Database
Restore
20 TB/hr
- 25 TB/hr
27 TB/hr
8 TB/hr
8 TB/hr
12
Storage
Expansion
Rack
The fine print
These are the fastest rates performed during quiet periods
Rates achieved using Exadata Database Machine X2-2/X2-8 Full Rack and Exadata Storage Expansion Rack
ZFS Storage Appliance using IPMP Active/Active Interface
Tape backup rate limited by number of tape drives. Rate achieved using Oracle Secure backup 10.4.0.2 using RDMA transport and
Direct I/O.
Exadata Backup Targets

Considerations - Performance and Cost Trade-offs
Highest Performance
20 25 TB / hour
All Exadata smart

features
ZFS
Storage
Appliance
(ZFS/SA)
Exadata
Storage
Expansion
Rack
Exadata
Storage
High Performance and Added Flexibility
27 TB / hour
Fastest Backup and Restore
ILM Historical Archive
Second DATA2 Disk Group
13 TB / hour
Backups of database &
non-database files
Snapshots
Clones
Cost Varies with hardware configuration

Note*: Backup Rate limited by number of tape drives 8 x T10000C Drives
13
StorageTek
Tape
Library
9 TB hour*
Backup of database and
non-database files
Offsite Backups
Vaulting
RMAN Backup Stategy Overview

Full Backups
Incremental Backups
-Online or offline backups

-Faster restore
-Higher overheads on the servers
-Reduces backup window

-Reduced overhead on the servers
-Ideal with low-medium change rate e.g. < 20%
-Enable BLOCK CHANGE TRACKING for fast incremental backups
-Database must be in archived log mode
Image Copy or Backup Set
Incrementally Updated Backups
Full / Incremental Backup Strategy
Image copy:
Must be on Disk
Same size as database less temp files
Backup set:
Disk or tape
Smaller than an image copy
Can be compressed
Disk only
Recovery window: typically 1 7 days
Incremental forever strategy after initial
copy
Disk or tape
Typically - weekly fulls and daily
incrementals
Retention:
On-disk: days to weeks
Tape: weeks to years
Can be compressed
14
Fast Recovery Area (FRA)

Database Manages the Disk Space
Unified storage location for all recovery files
15
Resides on Exadata Storage in an Exadata environment

Contains archived logs and flashback logs
May contain control files, online redo log files and backups
Minimize the number of initialization parameters to set when you

create a database
Oracle-Integrated Backup to Disk and/or Tape

Multi-media Strategy: Disk-to-Disk-to-Tape (D2D2T)
Fast Recovery Area
D2D2T
Exadata
BACKUP RECOVERY AREA;
Backup to Tape
BACKUP BACKUPSET;
RMAN Disk Backup

ZFS Storage
Appliance
(ZFSSA)
16
StorageTek
Tape Library
In D2D2T environments, the database server(s) are involved in both disk

and tape backup
Overhead on Exadata nodes is minimal typically < 1 CPU core
RMAN can restore seamlessly from disk or tape!
How Many RMAN Channels?
Determine optimal number of RMAN channels

No more than 2 RMAN channels per node (Exadata X3-2)
No more than 8 RMAN channels per node (Exadata X3-8)
Spread RMAN channels across database nodes
One RMAN channel per tape drive
Monitor memory and I/O usage during backups
17
Minimizing Impact of the Backup

Why?
No impact on production workload
SLAs must be maintained
How?
Reduce the degree of parallelism
Utilize DBRM & IORM
18
Diagnosing Performance Bottlenecks

Using RMAN BACKUP VALIDATE
Likely bottleneck is:
Read phase if BACKUP VALIDATE Time ~= Actual Backup Time
Copy or write phases if BACKUP VALIDATE Time < Actual Backup Time
Phase
Tuning Ideas
Read
Investigate slow performing files - find files high (LONG_WAITS/IO_COUNT)ratio
Copy
Decrease level of RMAN backup compression or use tape drive compression

Use AES192 compression algorithm or hardware encryption
Write*
Tune RMAN output buffer size by adjusting the BLKSIZE*

If backing up to SBT, review media manager settings
Note*: With Oracle Database 11g Release 2 and ASM, all buffers are automatically sized for optimal performance
19
High Performance or High Capacity Drives

Maximizing Fastest Drives for DATA Disk Groups
Exadata Rack - high performance (HP) Drives for DATA and RECO
Fast Recovery Area resides in the RECO disk group
At a minimum it is 20% of the available space
Contains archived redo logs and flashback log files
Exadata Expansion Rack high performance (HP) Drives

Expand the DATA and RECO disk groups for application data
Exadata Expansion Rack - high capacity (HC) Drives for BKUP

Holds database backups for the fastest possible database restoration
Holds ILM data for long term retention
20
Processing Offloaded From Database Nodes

Incremental Backup Scans Occur on Exadata Storage Cells
Block Change Tracking (BCT) enables fast incremental backups
RMAN tracks 32k data file sections which include a changed block(s)
During an incremental backup, RMAN scans these 32k file sections to
determine which block(s) have changed

Only these changed blocks are included in the incremental backup
Scan of blocks occurs

on the database server
Scan of blocks is
offloaded to the
Exadata Storage Cells
Database Server
Exadata
Note: Incremental backup without Block Change Tracking (BCT) enabled
all database blocks are scanned to determine what has changed
21
Architecting an Exadata
Backup and Recovery
Solution
22
Assign Databases to Tier(s) of Storage

Based on Recovery Requirements and Available Resources
Fast Recovery Area
Tier 1
Flashback logs
Exadata Storage
Incrementally Updated Backups
Tier 2
Active / Data Guard
Exadata Expansion Rack
All databases:
Control file backups
Databases in archived log mode:

Online redo and archived logs
Tier 3
Optional:
Offload backups
from production to
standby
ZFS
Storage
Appliance
RMAN Disk Backup
ZFS Storage Appliance
Tier 4
Tape
Tier 5
Tape
Full / Incremental
Weekly full only
Exadata
Expansion
Rack
23
D2D2T as required
StorageTek
Tape Library
Offsite
Location
Safaricom
Tier 3 and Tier 4 Backup Example ZFSSA, OSB & StorageTek
24
Exadata Disk-to-Disk-to-Tape (D2D2T) Strategy

RMAN Backup From ZFSSA to Tape via OSB
OSB
Administrative
Server
RMAN Backup
to tape via OSB
OSB Media
Server(s)
StorageTek
Tape Library
RMAN Backup
to disk
Oracle Exadata
Database Machine
25
ZFS Storage
Appliance (ZFSSA)
InfiniBand QDR Network
Fibre Channel
Considerations and Trade-offs
26
Strategy
Advantage
Disadvantage
RMAN backup compression
Reduces space consumption 4 levels:

BASIC included in Enterprise Edition
LOW, MEDIUM, HIGH available with Oracle
Advanced Compression Option (ACO)
Incurs CPU overhead on database server

Typically 1 CPU core per channel
RMAN backup encryption
Secures backup prior to files leaving the database
Incurs CPU overhead on database server
Incremental backup strategy
Reduces backup window with fast incrementals
Dependency on full backup for restoration
Full backup strategy
Improves recovery time (potentially)
More overhead on the servers
Integrated D2D2T
Seamless restore from disk or tape
Database server involved in both disk and

tape backup operation
Backup of Compressed Data

Effects on Sizing and Processes
Compressed data remains compressed in the backup
This data will not benefit from further compression during the
backup (e.g. RMAN backup or tape drive compression)

Deduplication software cannot deduplicate compressed data
HCC Data
OLTP Compressed Tables
SecureFiles
Compressed/Deduplicated
RMAN backup compression is effective on non-compressed database files

Avoid using RMAN backup compression on HCC tablespaces by separating the
backups as shown below:

Restore is no different than if the backups had not been separated
CONFIGURE EXCLUDE FOR TABLESPACE historical_data;

CONFIGURE COMPRESSION ALGORITHM 'low;
BACKUP TABLESPACE historical_data;
BACKUP AS COMPRESSED BACKUPSET database;
27
RMAN Catalog
Highly Recommended
RMAN catalog advantages:
Stores backup metadata for longer periods of time
Centralizes management and storage of multiple databases
Enables use of the KEEP FOREVER clause
No licensing fee for an RMAN catalog database

Common strategy is to co-locate the RMAN, OSB and EM catalogs on
the same server
28
Protecting Exadata Operating System Files
On the Exadata Storage Cells, the internal USB stick provides the
backup
On the Exadata database nodes, backup the operating
system(OS) files in the same manner as with any other database
server
Please refer to the documentation for more information:
http://wd0338.oracle.com/archive/cd_ns/E13877_01/doc/doc.112/e13874/maintenance.htm#CHD
IDGAI
29
Complete Backup and Recovery

Who Better to Backup Oracle Than Oracle?
Storage Expansion Rack
Fastest Backup and Restore
ILM Historical Archive
Second DATA2 Disk Group
Ethernet
InfiniBand
Network
10GigE or
InfiniBand
Network
10GigE or
InfiniBand
Network
30
Oracle Secure Backup

Admin Server

Media Servers
Fiber Channel
SAN
SL3000 tape library

Offsite Backups
Vaulting
ZFS Storage Appliance
Backups of database & non-database files
Snapshots
Clones
Database Consolidation
and Data Protection
31
Data Protection Best Practices

In Consolidated Environments
Schedule
Accordingly
Create Plan
- Group applications with
similar RTO / RPO
- Stagger backups
Do the Math
- Identify I/O constraints
32
Create a Plan
Group Databases by RTO / RPO
RTO < 5 minutes, RPO = Near-zero data loss
Incrementally Updated Backup Strategy 2 day recovery on disk
Fast recovery area on Exadata or Exadata Expansion Rack
Backup to tape from the standby 7 year retention period
Backups encrypted on tape via tape drive encryption
Active Data Guard
Remote
Standby
FRA
RTO < 6 hours, RPO < 1 hour

Full / Incremental backup 1 week retention on disk
Disk backup to ZFS Storage Appliance
Fast recovery area on Exadata
RMAN backup compression or ZFS compression
RTO > 6 hours, RPO < 1 day

Backup directly to tape 3 month
retention period
Remember Archived Log sweep
Exadata
Expansion Rack
33
Tape
Backup
ZFS
Storage
Appliance
RMAN Disk Backup
Offsite
Location
Note: Solutions may vary based on database size (e.g. 100 TB data warehouse)
StorageTek Tape Library
Fast Recovery Area (FRA)

Sizing Depend on What Is Kept in It
Recovery Files
Comments
Control file and archived

log backups
Estimate total size of all archived logs generated between successive

backups on the busiest days x 2 (in case of unexpected redo spikes)
Flashback logs
(Redo rate x Flashback retention target time) x 2
Image copy backup
Size of database minus temporary files
Backup set backups (full)
# of full backups x estimated size
Incremental backups
# of incremental backups x estimated size

Note: Fast Recovery Area is not required for backups
Further details:
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1019211
34
Utilize a Single FRA Location

Backup to Exadata Storage
Set each DB FRA location to
<consolidated RECO disk group name>

Simplify backup storage management
Ensure that consolidated RECO disk group
>= Sum {FRA size for each DB}
RECO
DB 1
DB1
DB2
DB 2
FRA
Set each databases FRA size according to individual space
requirements
Each database has a separate subdirectory within the FRA for all its files
Upon first file creation within the FRA, an <DB_NAME> subdirectory is created
automatically
35
Garmin: OLTP Consolidation

Exadata V2
DB Consolidation
Exadata V2
Standby/Dev/Test
StorageTek
SL8500
Data Guard
High-Capacity
Exadata Storage Servers
5 Production
databases
Data
archive
Database failover
Offload backups
Dev/test databases
RMAN backup
to tape
Oracle Exadata helped us meet our challenges by enabling us to consolidate to a single footprint.
- Ed Link, Vice-President IT, Garmin
36
Sizing - Full / Incremental Backup Strategy

Retention Requires Recovery Window + One
Recovery Window (Cycle)
(Point-in-Time-Recovery)
Full / Incremental Backups Required
Archived Logs Required
1 Week (7 days)
2 weeks worth (2 fulls, 12 incrementals)
14 days
2 Weeks (14 days)
3 weeks worth (3 fulls, 18 incrementals)
21 days
And So On
Day:
Day:
37
Full
Inc.
Inc.
Inc.
Inc.
Inc.
Inc.
Full
Inc.
Inc.
Inc.
Inc.
Inc.
Inc.
10
11
12
13
14
Full/incrementals must
be treated as a group
Monsanto Company
COMPANY OVERVIEW
Industry: Bio-Technology/Agriculture
Employees: ~22,000
Revenue: US$11.8 billion in FY 2011
Monsanto is a leading global provider of agricultural products that improve farm
productivity and food quality. The company is committed to producing more,
conserving more and Improving lives.
Double yields in our core crops by 2030

Use one-third fewer resources per unit of output
Improves lives of farmers all over the world
CHALLENGES / OPPORTUNITY
Putting better seeds into the hands of farmers faster will help them feed a growing world
population. To produce these new products, we leverage innovative technologies such as
biotechnology and molecular breeding, both information-intensive activities that require fast
turnaround times and massive computing power. Harvest data collected from the fields must
be processed quickly so scientists can make advancement decisions about potential products.
Researchers analyze huge volumes of data to determine which potential products have the
right combination of traits for combating insects, controlling weeds, and increasing yield, while
ensuring, quality, flavor, and nutrition of the resulting harvest.
CUSTOMER PERSPECTIVE
We plan the harvest season for two or three times the load on our
information systems. The Oracle Exadata systems contain Oracle
hardware, Oracle software, and Oracle database technology, all integrated
into a cohesive system. Working with a single vendor has made it a lot
easier to resolve issues. Theres no question about responsibility or
ownership if something goes wrong.
We were no longer comfortable with our ability to recover the entire
database within a days time. Now, with the Sun ZFS Storage Appliance, if
we have any type of data corruption issue, we can resolve it very quickly.
ZFS provides a more accessible, faster solution
SOLUTIONS
Oracle Exadata Database Machine
Oracle Real Application Clusters
Sun ZFS Storage Appliance
Oracle Active Data Guard
Oracle WebLogic Server
Oracle Service Bus
Oracle Coherence
Oracle Managed Services
Website: http://www.monsanto.com/
Monsanto Exadata Architecture
Monsanto Exadata Transformation

Targeted Goals
Platform
Consolidation
High Availability /
Zero Outage
Improved data backup

and recovery
Exadata Differentiator
Migrated over 80 business critical applications
to Exadata Platform
Consolidation of 21 databases into single RAC
and storage platform
Maintain 4 Production like environments with
equal data size and similar outage, backup
and recovery process
Efficient use of Maximum Availability
Architecture
Proactive Monitoring and Reporting
Proactive patching
Onsite Exadata support staff
Predictive hardware failure and issues
resolution
RMAN compression algorithm changes and

implementation of BUR best practices
Optimized use of ZFS storage
Enabled multi-level compression options
based on application data.
Improved disk refresh process through
continuous process improvements
Realized Benefits
Reduced Support and Maintenance cost related
to managing multiple platforms and Databases
Implementation of standard support process
across all environments
100% availability during Harvest season

99.95% availability during Non Harvest season
Reduced planned and unplanned outages by
effectively using Standby
Zero impact to customer during component failure
Capacity management of disk backup for larger

databases.
Over 40% improvements in tape backup performance
Improved ZFS disk refresh process (RTO of 8 hrs)
Reduced ZFS disk backup time from 11 to 4 hrs
Sizing Backup Server(s)

Administrative
Server
Media servers - workload is focused on data

movement, not processing power
Assume about 2GB/s throughput via IB (TCP/IP)
per media server
Media Server(s)
Administrative / Master Server requires enough

disk space for catalog growth
What if multiple databases are consolidated on Exadata?

Bandwidth, throughput and capacity remain the same whether one or more
databases No effect on media server sizing
For more information on sizing an Exadata tape backup environment, refer to:
http://www.oracle.com/technetwork/database/focus-areas/availability/maa-exadata-backup-methodology-495297.pdf
41
Schedule Accordingly
Based on Available Hardware Throughput and Requirements
One 80 TB database
Database grows to 120 TB
Backup takes 15 hours
Backup takes 10 hours
Backup
Throughput =
8 TB / hour
Two databases:
Stagger backups to run

sequentially
80 TB = 10 hours then
40 TB = 5 hours
Total backup time = 15 hours
Run backups concurrently
Backups complete in 15
hours although unpredictable
as to when each completes
1 = 80 TB and 2 = 40 TB
Backup
Throughput = 8
TB / hour
Two databases:
1 = 80 TB and 2 = 40 TB
Backup window = 5 hours
42
Purchase additional hardware

increasing total backup
throughput to 24 TB / hour
Tape environment - assign

tape drives to each database
(Assume 8 drives at 1TB/h
each): 5 to DB 1 would
complete in 16 hrs and 3
drives to DB 2 would
complete in 13.3 hours
Recovery is King
43
You May Be Out of School

BUT You Are Not Done with Tests!
Some highly recommended tests:

Parachute packed properly before jumping out of a plane?
Brakes working before driving on the autobahn?
Batteries in your smoke detector still good?
Regular Data Recovery Tests --Just as Important!

44
Recovery Plan and Scheduled Recovery Testing

Job Security 101.
1.
Documented recovery plan for database and object level

recovery - (must be written, doesnt count if its just in your head)
2.
Best practice:
Schedule monthly full recovery tests

Next best thing to best practice:
Object level recovery & block corruption monthly
Full database recovery semi-annually
Refresh test environments using RMAN
RESTORE VALIDATE quarterly
3.
4.
45
Thinking out-of-the-box: Next, next best thing to best practice:
RESTORE VALIDATE quarterly
Object level recovery & block corruption monthly
Full database recovery annually
Think documented in that your CIO

or the DBA who joined last week
could follow!
Yes true recovery testing involves
some hardware and storage capacity
---- Is your data worth it?
Come on Ya, must do something!

---- If not, dont call me on the
weekend at 2am .
Restore / Recovery Tests

Using RMAN RESTORE VALIDATE
RMAN RESTORE VALIDATE:
Tests whether RMAN can restore a specific file or set of files from a
backup:
RESTORE DATABASE VALIDATE;
RESTORE ARCHIVELOG ALL VALIDATE;
This takes about as long and uses as much overhead as a traditional
restore operation less time writing to disk

To reduce impact, reduce the number of RMAN channels
46
Summary/Key Takeaways
Exadata Backup and Recovery
RMAN backup / recovery on Exadata is the same as other
platforms just faster!

Oracle data protection technologies meet diverse RTO /
RPO and budget requirements
Database consolidation and data protection is ideally
suited to the Exadata platform
Who Better to Backup Oracle Than Oracle?

47
Additional Resources
Oracle Exadata Database Machine
http://www.oracle.com/exadata
OTN HA Portal
http://www.oracle.com/goto/availability
Maximum Availability Architecture (MAA)
http://www.oracle.com/goto/maa
MAA Blogs
http://blogs.oracle.com/maa
Exadata on OTN
http://www.oracle.com/technetwork/database/exadata/index.html
Oracle HA Customer Success Stories on OTN
http://www.oracle.com/technetwork/database/features/ha-casestudies-098033.html
48
49
50

Final v21

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final v21

Uploaded by

Copyright:

Available Formats

1

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Backup and Recovery of

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Exadata - One Machine | Many Workloads

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

A Complete, Integrated, Optimized Platform

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Oracle Exadata Innovation

Hybrid Columnar Compression

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Smart Scan Queries

Standardized and Simple to Deploy

Run Existing OLTP and DW Applications

Leverage Oracle Ecosystem

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

1000s of Deployments at Leading Companies

Online Financial Trading

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

The Data Protection Dilemma

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Overview of Oracle Data Protection Technologies

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Oracle Data Protection Strategies

Logical Data Protection - Flashback Technologies

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Recovery Time Objective (RTO)

Recovery Time Objective (RTO)

What are Your Recovery Requirements?

Recovery Point Objective (RPO)

Backup Retention Policy

What is the acceptable performance

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Exadata Backup & Recovery Rates

The fine print

These are the fastest rates performed during quiet periods

ZFS Storage Appliance using IPMP Active/Active Interface

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Exadata Backup Targets

All Exadata smart

High Performance and Added Flexibility

Cost Varies with hardware configuration

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

RMAN Backup Stategy Overview

-Online or offline backups

-Reduces backup window

Image Copy or Backup Set

Incrementally Updated Backups

Full / Incremental Backup Strategy

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Fast Recovery Area (FRA)

Unified storage location for all recovery files

Resides on Exadata Storage in an Exadata environment

Minimize the number of initialization parameters to set when you

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

Oracle-Integrated Backup to Disk and/or Tape

Fast Recovery Area

BACKUP RECOVERY AREA;

RMAN Disk Backup

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

In D2D2T environments, the database server(s) are involved in both disk

How Many RMAN Channels?

Determine optimal number of RMAN channels