Session id: 40179

Oracle Database 10g Data

Warehouse Backup & Recovery:
Automatic, Simple, And Reliable
George Lumpkin
Director Product Management
Oracle Corporation
Tammy Bednar
Sr. Product Manager
Oracle Corporation

Agenda
y Data warehouse characteristics
y Oracle Backup & Recovery review
y Understand your backup and recovery
requirements
y DW Recovery Methodology

Best Practice#1 Archivelog Mode

Best Practice#2 Use RMAN
Best Practice#3 Read-Only Tablespaces
Best Practice#4 Nologging Operations
Best Practice#5 Exclude Tablespace

You can back up your data

warehouse in exactly the same
way as you back up your OLTP
database.
But

But
y Your OLTP system is 50GB and your data warehouse
is 5TB. Do you have the budget to buy 100X more
backup hardware to support your data warehouse?
y Your OLTP system must be recoverable in 30
minutes. Does your data warehouse require the same
recovery time?
y Your OLTP system contains new customer orders, so
it can never lose any transactions. Does you data
warehouse require zero data loss?
The best practices for DW backup/recovery should leverage
the unique characteristics of your data warehouse

Data Warehouse
Characteristics
y Large amounts of data

Production systems up to 10s of terabytes

y Lower availability requirements than OLTP

Often hours or days, not minutes

y Data enters data warehouse via controlled processes

(ETL)

Data feeds can be re-run if necessary

y Significant portions of data warehouse may be static

Older data generally does not change

Agenda
y Data warehouse characteristics
y Oracle Backup & Recovery review
y Understand your backup and recovery
requirements
y DW Recovery Methodology

Best Practice#1 Archivelog Mode

Best Practice#2 Use RMAN
Best Practice#3 Read-Only Tablespaces
Best Practice#4 Nologging Operations
Best Practice#5 Exclude Tablespace

Oracle Backup & Recovery

What should you backup?
y Oracle Database Architecture

Datafiles
Archive logs
Control file
Configuration Files

9
9

Backup and Recovery Methods

and Tools
y Recovery Manager

Oracles tightly integrated utility for creating, managing,

restoring and recovering databases

y Oracle Enterprise Manager

GUI interface to Recovery Manager

y Oracle Data Pump (export/import)

Logical database backups

y User Managed

Database is backed up and restored

manually using OS commands

Recovery Manager:
Oracles Backup & Recovery Utility
y Over 25 Man Years of Engineering
Technology provides:
Recovery
Manager
Enterprise Manager
& 3rd Party Tools

Media Management Layer

Network

Intimate knowledge of database file

formats and recovery procedures
Manages and automates the backup,
restore, and recovery process
Creates and maintains backup
policies
Catalogs all backup and recovery
activities
Operates on-line and in parallel for
fast processing
Corrupt block detection during
backup and restore and the ability to
validate backups
Integrated with Enterprise Manager
& 3rd Party Tools

Backup Management
y List RMAN backups

View files included

in a backup set

y Perform maintenance

Remove obsolete
backups
with a single click

Other Oracle10g B&R

Enhancements
y Compression of archive logs and backups
y Restore tolerates missing or corrupt backup

Automatically fails over to previous backup

y Automated recovery through a previous point in time

recovery

y
y
y
y

Recovery through resetlogs

Fully automated tablespace point-in-time recovery

Automatic channel failover on backup or restore
Tablespace Rename
Drop Database

Oracle Database 10g

Data Pump
y What is it?

High speed, parallel, bulk data and metadata movement of

Oracle database contents
Replacement for original Export and Import
New server-side infrastructure for utilities
Public documented package interfaces

y What can you use it for?

Data/Metadata movement between databases

y Test

Development

Production

Changing HW/OS platforms, version releases, character

sets
Data archiving
Logical backup of full or partial database

Agenda
y Data warehouse characteristics
y Oracle Backup & Recovery review
y Understand your backup and recovery
requirements
y DW Recovery Methodology

Best Practice#1 Archivelog Mode

Best Practice#2 Use RMAN
Best Practice#3 Read-Only Tablespaces
Best Practice#4 Nologging Operations
Best Practice#5 Exclude Tablespace

What is your Recovery Time

Objective?
y Analyze and identify the cost associated with
unavailable data
y Design recovery requirements around data
criticality and logical relationships
y Build and integrate the backup and recovery
plan
y Manage and evolve your processes as your
data, IT infrastructure, and business change

What is your Recovery Point

Objective?
RPO

RTO1

RTO2

Backups are
run at scheduled
interval.

Critical data
Is available &
Database is open.

Remainder of
Data is re-inserted.

No
backup
of data

Restore
Backup

Data is re-inserted
via ETL

Time
mm Hours
mm Hours
0
Automated recovery Manual recovery procedures
Normal procedures
Normal procedures procedures
-nn Hours

How do you backup all of that

data?
y Backing up to Tape

The time to backup to tape is a function of your

hardware

# of tape devices + tape library = time to backup

y Divide and Conquer

Breakup the database backup over the course of

several days
RMAN provides automatic windowing capability

Agenda
y Data warehouse characteristics
y Oracle Backup & Recovery review
y Understand your backup and recovery
requirements
y DW Recovery Methodology

Best Practice#1 Archivelog Mode

Best Practice#2 Use RMAN
Best Practice#3 Read-Only Tablespaces
Best Practice#4 Nologging Operations
Best Practice#5 Exclude Tablespace

DW Recovery Methodology
Best Practice#1 Archivelog Mode
y Archivelog Mode

Recover more completely from media failure

Create backups while the database is open and
available
Provides more recovery options

y No Archivelog Mode

Backup only when the database is closed

Restore data as of the last good backup

y Keep more archive logs on disk using archive

log compression

DW Recovery Methodology
Best Practice#2 Use RMAN
1. Extensive Reporting
2. Easily integrates with Media Managers
3. Incremental Backups
4. Block Media Recovery (BMR)
5. Downtime Free Backups
6. Archive log validation and management
7. Backup and Restore Validation
8. Corrupt Block Detection
9. Backup and Restore Optimization
10. Trouble Free Backup and Recovery

DW Recovery Methodology
Best Practice#3 Read-Only Tablespaces
y Leverage partitioning and read-only tablespaces to
minimize the amount of data to be backed-up

Jan

Read-only tablespaces only need to backed-up once

Older data can often be converted to read-only
Feb

Read-only Tablespace

Mar

Apr

May

Read-write
Read-only Tablespace
Tablespace

Jun

Jul

Read-write Tablespace

y Caveat: This strategy improves backup times, but

not recovery times

DW Recovery Methodology
Best Practice#4 Nologging Operations
y Most data warehouses use NOLOGGING
operation to accelerate bulk-data processing
y B+R considerations for NOLOGGING:

Do not backup a tablespace while nologging

operations are running on that tablespace
y Schedule backups to run after nologging operations

Devise a strategy for recovering data loaded using

nologging operations

DW Recovery Methodology
Best Practice#4 Nologging Operations
y

Strategy #1: Recover nologging operations via ETL

1.
2.

3.

Pros

Take a weekly backup of the data warehouse

Every night, store/backup a copy of the raw data files
which are loaded into the data warehouse
To recover, restore the backup of the data warehouse,
then re-run the nightly ETL processes to roll the data
warehouse forward
Minimal resources required to support backup scenario

Cons

Manual process of storing and replaying ETL

DW Recovery Methodology
Best Practice#4 Nologging Operations
y

Strategy #2: Recover nologging operations via

Incremental Backups
1.
2.
3.

Pros

Take a weekly backup of the data warehouse

Every night, do an incremental backup of all modified
tablespaces after all nologging operations are completed
To recover, restore the backup of the data warehouse,
then apply the nightly incremental backups to roll the data
warehouse forward
Can be completely managed via RMAN
Simple and complete backup of new data

Cons

Backup required nightly following the ETL window

DW Recovery Methodology
Best Practice#5 Exclude Tablespace
y Not every tablespaces in a data warehouse needs to
be backed-up

Oracle Temporary Tablespaces

y By default, RMAN does not back these up
User Scratch Tablespaces
y Tablespaces used by users to store incremental results
and other temporary data sets

y Not every tablespace needs to be backed-up as

frequently

Some data may be less critical than other data

y Weekly backups instead of nightly backups

Summary
y Data warehouse characteristics
y Oracle Backup & Recovery review
y Understand your backup and recovery
requirements
y DW Recovery Methodology

Best Practice#1 Archivelog Mode

Best Practice#2 Use RMAN
Best Practice#3 Read-Only Tablespaces
Best Practice#4 Nologging Operations
Best Practice#5 Exclude Tablespace

Next Steps for High Availability

High Availability Sessions from Oracle
Tuesday in Moscone Room 304

Wednesday in Moscone Room 304

11:00 AM

8:30 AM

How Oracle Database 10g

Revolutionizes Availability and
Enables the Grid

Oracle Database 10g - RMAN and ATA

Storage in Action
11:00 AM

3:30 PM

Oracle Recovery Manager (RMAN)

10g: Reloaded

Oracle Data Guard: Maximum Data

Protection at Minimum Cost
1:00 PM

5:00 PM

Proven Techniques for Maximizing

Availability

Oracle Database 10g Time

Navigation: Human-Error Correction
4:30 PM

Data Guard SQL Apply: Back to the

Future

For More Info On Oracle HA Go To http://otn.oracle.com/deploy/availability/

Next Steps for High Availability

High Availability Sessions from Oracle
Thursday

Database HA Demos All Four Days

In The Oracle Demo Campground

8:30 AM in Moscone Room 304

Oracle Database 10g Data

Warehouse Backup and Recovery:
Automatic, Simple, Reliable
8:30 AM in Moscone Room 104

Building RAC Clusters over

InfiniBand

Real Application Clusters

Data Guard
Database Backup & Recovery
Flashback Recovery
LogMiner, Online Redefinition, and
Cross Platform Transportable
Tablespaces

For More Info On Oracle HA Go To http://otn.oracle.com/deploy/availability/

Next Steps for DW / BI

Data Warehousing DB Sessions
Monday

Tuesday

11:00 AM
#40153, Room 304

8:30 AM
#40125, Room 130

Oracle Warehouse Builder:

New Oracle Database 10g Release

Oracle Database 10g:

A Spatial VLDB Case Study

3:30 PM
#40176, Room 303

3:30 PM
#40177, Room 303

Security and the Data Warehouse

Building a Terabyte Data Warehouse,

Using Linux and RAC

4:00 PM
#40166, Room 130

5:00 PM
#40043, Room 104

Oracle Database 10g

SQL Model Clause

Data Pump in Oracle Database 10g:

Foundation for Ultrahigh-Speed Data
Movement

For More Info On Oracle BI/DW Go To http://otn.oracle.com/products/bi/db/dbbi.html

Next Steps for DW / BI

Data Warehousing DB Sessions
Thursday
8:30 AM
#40179, Room 304

Oracle Database 10g Data

Warehouse Backup and Recovery

Business Intelligence and Data

Warehousing Demos All Four Days
In The Oracle Demo Campground
Oracle Database 10g
Oracle OLAP

11:00 AM
#36782, Room 304

Experiences with Real-Time Data

Warehousing using Oracle 10g
1:00PM
#40150, Room 102

Oracle Data Mining

Oracle Warehouse Builder
Oracle Application Server 10g

Turbocharge your Database, Using

the Oracle Database 10g
SQLAccess Advisor

For More Info On Oracle BI/DW Go To http://otn.oracle.com/products/bi/db/dbbi.html