You are on page 1of 40

5

Using RMAN to Create Backups

Copyright © 2007, Oracle. All rights reserved.


Objectives

After completing this lesson, you should be able to:


• Create image file backups
• Create a whole database backup
• Create a full database backup
• Enable fast incremental backup
• Create duplex backup sets
• Back up a backup set
• Create an archival backup for long-term retention
• Create a multisection backup
• Create a compressed backup
• Create an encrypted backup
• Report on and maintain backups

5-2 Copyright © 2007, Oracle. All rights reserved.


Creating Backup Sets

RMAN> BACKUP AS BACKUPSET


2> FORMAT '/BACKUP/df_%d_%s_%p.bus'
3> TABLESPACE hr_data;

Datafile Datafile
1 1

Datafile Datafile
2 2

Datafile Datafile
3 3
Tablespace Backup
HR_DATA set

5-3 Copyright © 2007, Oracle. All rights reserved.


Creating Image Copies

RMAN> BACKUP AS COPY DATAFILE '/ORADATA/users_01_db01.dbf';


RMAN> BACKUP AS COPY ARCHIVELOG LIKE '/arch%';

Copy of data file 3


Data file 3 Data file 3

Copy of archived log


Archived Archived
log file log file

5-4 Copyright © 2007, Oracle. All rights reserved.


Creating Image Copies
Full Notes Page

5-5 Copyright © 2007, Oracle. All rights reserved.


Creating a Whole Database Backup

RMAN> BACKUP DATABASE


PLUS ARCHIVELOG;

Control
Archived log Data file file SPFILE
file copies copies

5-6 Copyright © 2007, Oracle. All rights reserved.


Creating a Whole Database Backup
Full Notes Page

5-7 Copyright © 2007, Oracle. All rights reserved.


Saving Backup Space with
Unused Block Compression
The following blocks may be
skipped during certain types of
backup operations:
• Unallocated blocks: These are
above the data file’s high-water Unused
mark (HWM).
• Unused blocks: These are Allocated
blocks that have been allocated HWM
but no longer belong to a
Unallocated
segment.

Data file

5-8 Copyright © 2007, Oracle. All rights reserved.


RMAN Backup Types

• A full backup contains all used data Full, or "level 0


file blocks. incremental backup"

• A level 0 incremental backup is


equivalent to a full backup that has
been marked as level 0.
• A cumulative level 1 Cumulative
incremental backup
incremental backup contains
only blocks modified since the
last level 0 incremental
backup.
Differential
• A differential level 1 incremental backup
incremental backup contains
only blocks modified since the
last incremental backup.

5-9 Copyright © 2007, Oracle. All rights reserved.


RMAN Backup Types
Full Notes Page

5 - 10 Copyright © 2007, Oracle. All rights reserved.


Fast Incremental Backup

Implemented by block change tracking, which:


• Maintains a record of what blocks have changed since the
last backup
• Writes this record to a file, as redo is generated
• Is automatically accessed when a backup is done, making
the backup run faster

List of changed
1011001010110 Change
blocks
CTWR 0001110100101 tracking
Redo 1010101110011 file
generation
SGA Redo log

5 - 11 Copyright © 2007, Oracle. All rights reserved.


Enabling Fast Incremental Backup

ALTER DATABASE
{ENABLE|DISABLE} BLOCK CHANGE TRACKING
[USING FILE '...']

5 - 12 Copyright © 2007, Oracle. All rights reserved.


Monitoring Block Change Tracking

SQL> SELECT filename, status, bytes


2 FROM v$block_change_tracking;
SQL> SELECT file#, avg(datafile_blocks),
2 avg(blocks_read),
3 avg(blocks_read/datafile_blocks)
4 * 100 AS PCT_READ_FOR_BACKUP,
5 avg(blocks)
5 FROM v$backup_datafile
6 WHERE used_change_tracking = 'YES'
7 AND incremental_level > 0
8 GROUP BY file#;

5 - 13 Copyright © 2007, Oracle. All rights reserved.


Creating Duplexed Backup Sets

To create a duplexed backup set, use:


• CONFIGURE ... BACKUP COPIES
• BACKUP...COPIES

Data file Data file


1 1 Data file
1
Data file
Data file 2 Data file
2 2
Data file
Data file 3 Data file
3 3
Backup set
Tablespace Backup set
copy 1
HR_DATA copy 2

5 - 14 Copyright © 2007, Oracle. All rights reserved.


Creating Duplexed Backup Sets Using
CONFIGURE BACKUP COPIES

Two copies of the


backup are made to
two different tapes.

RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES


2> FOR DEVICE TYPE sbt TO 2;
RMAN> CONFIGURE DATAFILE BACKUP COPIES
2> FOR DEVICE TYPE sbt TO 2;
RMAN> BACKUP DATABASE PLUS ARCHIVELOG;
RMAN> BACKUP DEVICE TYPE DISK AS COPY DATABASE;

Not affected by the


COPIES configuration
setting. Only one
copy is made on disk.

5 - 15 Copyright © 2007, Oracle. All rights reserved.


Creating Duplexed Backup Sets Using
BACKUP COPIES

RMAN> BACKUP AS BACKUPSET DEVICE TYPE sbt


2> COPIES 2
3> INCREMENTAL LEVEL 0
4> DATABASE;

5 - 16 Copyright © 2007, Oracle. All rights reserved.


Creating Backups of Backup Sets

RMAN> BACKUP DEVICE TYPE DISK AS BACKUPSET


2> DATABASE PLUS ARCHIVELOG;
RMAN> BACKUP DEVICE TYPE sbt BACKUPSET ALL;

Datafile Datafile
1 1
Datafile
Datafile 2
2 Datafile
3
Datafile
3 Archived
redo logs
Archived
redo logs
Backup sets

5 - 17 Copyright © 2007, Oracle. All rights reserved.


Backing Up Read-Only Tablespaces

Considerations for backing up read-only tablespaces:


• Backup optimization causes RMAN to back up read-only
tablespaces only when there does not exist a backup that
satisfies the retention policy.
• If you change the tablespace to read/write, back it up
immediately.
• You can use the SKIP READONLY option of the RMAN
BACKUP command to skip read-only tablespaces or data
files.

5 - 18 Copyright © 2007, Oracle. All rights reserved.


Archival Backups: Concepts

Archival backup
Log 250 Log 900

Backup A Backup B Backup S

Now

End of Q1 Recovery window of 7 days

Log nnn and Backup Not needed for retention policy

Backup Needed for retention policy

5 - 19 Copyright © 2007, Oracle. All rights reserved.


Archival Backups: Concepts
Full Notes Page

5 - 20 Copyright © 2007, Oracle. All rights reserved.


Creating Archival Backups with EM

5 - 21 Copyright © 2007, Oracle. All rights reserved.


Creating Archival Backups with RMAN

When the database is in the OPEN state, specifying the KEEP


clause causes both data file and archive log backup sets to be
included.
KEEP {FOREVER | UNTIL TIME [=] ' date_string '}
[RESTORE POINT rsname]

5 - 22 Copyright © 2007, Oracle. All rights reserved.


Managing Archival Database Backups

1 Archiving a database backup:


RMAN> CONNECT TARGET /
RMAN> CONNECT CATALOG rman/rman@catdb
RMAN> CHANGE BACKUP TAG 'consistent_db_bkup'
2> KEEP FOREVER;

2 Changing the status of a database copy:

RMAN> CHANGE COPY OF DATABASE CONTROLFILE NOKEEP;

5 - 23 Copyright © 2007, Oracle. All rights reserved.


Multisection Backups: Overview

Channel 1
Section 1

Channel 2
Section 2

Channel 3
Section 3

Channel 4
Section 4

Channel 5
Section 5

Channel 6
Section 6
One large data file

5 - 24 Copyright © 2007, Oracle. All rights reserved.


Creating RMAN Multisection Backups

BACKUP <options> SECTION SIZE <integer> [M | K | G]

VALIDATE DATAFILE <options> SECTION SIZE <integer> [M | K | G]

Example:

RMAN> BACKUP DATAFILE 5 SECTION SIZE = 25M TAG 'section25mb';


backing up blocks 1 through 3200
piece handle=/u01/.../o1_mf_nnndf_SECTION25MB_382dryt4_.bkp
tag=SECTION25MB comment=NONE
...
backing up blocks 9601 through 12800
piece handle=/u01/.../o1_mf_nnndf_SECTION25MB_382dsto8_.bkp
tag=SECTION25MB comment=NONE

5 - 25 Copyright © 2007, Oracle. All rights reserved.


Compressing Backups

RMAN can perform binary compression on any backup


generated.
• It can be performed in addition to unused block
compression.
• By default, RMAN uses the ZLIB compression algorithm.
• BZIP2 is an alternative algorithm, and generally differs from
ZLIB in the following respects:
– It has a better compression ratio.
– It is slower.
• No extra steps are required by the DBA to restore a
compressed backup.

5 - 26 Copyright © 2007, Oracle. All rights reserved.


Encrypting Backups

Password: **********

5 - 27 Copyright © 2007, Oracle. All rights reserved.


Encrypting Backups

Password: **********

5 - 28 Copyright © 2007, Oracle. All rights reserved.


Backing Up Recovery Files

• Back up only the files in the Flash Recovery Area:


RMAN> BACKUP RECOVERY AREA

• Back up all recovery files:


RMAN> BACKUP RECOVERY FILES

Flash Recovery Area

5 - 29 Copyright © 2007, Oracle. All rights reserved.


Using a Media Manager

Server
Recovery session
Manager (channel)

Media
Management
Library
Oracle Secure Or
Backup with
built-in MML Media
management
server software

5 - 30 Copyright © 2007, Oracle. All rights reserved.


Using a Media Manager
Full Notes Page

5 - 31 Copyright © 2007, Oracle. All rights reserved.


Performing Proxy Copies

Server
Recovery session
Manager (channel)

Media
Management
Library

Media
management
server software

Storage Area Network (SAN)

5 - 32 Copyright © 2007, Oracle. All rights reserved.


Creating an Oracle-Suggested Backup

5 - 33 Copyright © 2007, Oracle. All rights reserved.


Managing Backups: Reporting

Use the following RMAN commands to obtain information about


your backups:
• LIST: Displays information about backup sets, proxy copies,
and image copies recorded in the repository
• REPORT: Produces a detailed analysis of the repository
• REPORT NEED BACKUP: Lists all data files that require a
backup
• REPORT OBSOLETE: Identifies files that are no longer
needed to satisfy backup retention policies

5 - 34 Copyright © 2007, Oracle. All rights reserved.


Managing Backups: Reporting
Full Notes Page

5 - 35 Copyright © 2007, Oracle. All rights reserved.


Managing Backups: Dynamic Performance Views

Query the following dynamic performance views in the target


database to obtain information about your backups:
• V$BACKUP_SET: Backup sets created
• V$BACKUP_PIECE: Backup pieces that exist
• V$DATAFILE_COPY: Copies of data files on disk
• V$BACKUP_FILES: Information about all files created when
creating backups

5 - 36 Copyright © 2007, Oracle. All rights reserved.


Using Enterprise Manager to View
Backup Reports

5 - 37 Copyright © 2007, Oracle. All rights reserved.


Managing Backups: Cross-Checking and Deleting

Use the following RMAN commands to manage your backups:


• CROSSCHECK: Verifies the status of backups and copies
recorded in the RMAN repository against media such as disk
or tape
• DELETE EXPIRED: Removes only files whose status in the
repository is EXPIRED
• DELETE OBSOLETE: Deletes backups that are no longer
needed

5 - 38 Copyright © 2007, Oracle. All rights reserved.


Summary

In this lesson, you should have learned how to:


• Create image file backups
• Create a whole database backup
• Create a full database backup
• Enable fast incremental backup
• Create duplex backup sets
• Back up a backup set
• Create an archival backup for long-term retention
• Create a multisection backup
• Create a compressed backup
• Create an encrypted backup
• Report on and maintain backups

5 - 39 Copyright © 2007, Oracle. All rights reserved.


Practice 5 Overview:
Creating Backups
This practice covers the following topics:
• Taking an archival backup
• Enabling block change tracking
• Recovering from a damaged block
• Reporting on existing backups
• Backing up the control file
• Creating an encrypted backup
• Creating a compressed backup
• Using the Media Management Library to take backups

5 - 40 Copyright © 2007, Oracle. All rights reserved.

You might also like