BACKUP EXAMPLES

by Jeff Hunter, Sr. Database Administrator

Contents
1. RMAN Default Configuration Parameters
2. Offline Backup - (using configured defaults)
3. Offline Backup - (without using configured defaults)
4. Backup Archive Logs (All)
5. Online Backup - (using configured defaults)
6. Keeping Backups
7. Incremental Backups
8. Mirroring Backups
9. Copying Disk Backup to Tape
10. Backup Failures

RMAN Default Configuration Parameters

Several of the examples in this article will make use of
RMAN default configuration parameters. Starting with
Oracle9i, many of the RMAN parameters can be
configured with default settings. Here is a listing of those
parameters that I have set for all of the examples in this
article:
This example assumes that the target database is already
configured with automatic channels. The following will
perform an offline backup. Notice that you you can use
RMAN to shutdown and startup the database (which is
required for performing an offline backup):
% ORACLE_SID=TARGDB; export TARGDB

% rman target backup_admin/backup_admin nocatalog

Recovery Manager: Release 9.2.0.5.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: TARGDB (DBID=2528050866)

using target database controlfile instead of recovery catalog

RMAN> show all;

RMAN configuration parameters are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE
DISK TO '/orabackup/rman/TARGDB/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; #
default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
# default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT
'/orabackup/rman/TARGDB/backup_db_%d_S_%s_P_%p_T_%t'
MAXPIECESIZE 1024 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO
'/u01/app/oracle/product/9.2.0/dbs/snapcf_TARGDB.f'; # default

Offline Backup - (using configured defaults)

This example assumes that the target database is already
configured with automatic channels. The following will
perform an offline backup. Notice that you you can use
RMAN to shutdown and startup the database (which is
required for performing an offline backup):
% rman target backup_admin/backup_admin

RMAN> shutdown immediate

RMAN> startup mount
RMAN> backup database;
RMAN> alter database open;

Offline Backup - (without using configured defaults)

This example assumes that the target database is not
configured with and will not be using any configured
defaults (i.e. automatic channels). The following will
perform an offline backup. Notice that you you can use
RMAN to shutdown and startup the database (which is
required for performing an offline backup):
% rman target backup_admin/backup_admin nocatalog

RMAN> shutdown
RMAN> startup mount
RMAN> run {
2> allocate channel c1 device type disk format
'/orabackup/rman/TARGDB/backup_db_%d_S_%s_P_%p_T_%t';
3> allocate channel c2 device type disk format
'/orabackup/rman/TARGDB/backup_db_%d_S_%s_P_%p_T_%t';
4> setlimit channel c1 maxpiecesize 25m;
5> set maxcorrupt for datafile 1 to 0;
6> backup full
7> skip inaccessible
8> tag rman_backup_hot_full
9> filesperset 4
10> (database include current controlfile);
11> # backup current controlfile;
12> }

allocated channel: c1
channel c1: sid=13 devtype=DISK

allocated channel: c2
channel c2: sid=14 devtype=DISK
executing command: SET MAX CORRUPT

Starting backup at 22-DEC-04

channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00011
name=/u06/app/oradata/TARGDB/perfstat01.dbf
input datafile fno=00007
name=/u06/app/oradata/TARGDB/example01.dbf
input datafile fno=00004
name=/u06/app/oradata/TARGDB/drsys01.dbf
input datafile fno=00006 name=/u06/app/oradata/TARGDB/xdb01.dbf
channel c1: starting piece 1 at 22-DEC-04
channel c2: starting full datafile backupset
channel c2: specifying datafile(s) in backupset
input datafile fno=00002
name=/u06/app/oradata/TARGDB/undotbs01.dbf
input datafile fno=00003
name=/u06/app/oradata/TARGDB/cwmlite01.dbf
input datafile fno=00005 name=/u06/app/oradata/TARGDB/odm01.dbf
input datafile fno=00008 name=/u06/app/oradata/TARGDB/indx01.dbf
channel c2: starting piece 1 at 22-DEC-04
channel c1: finished piece 1 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_18_P_1_T_
545604600 comment=NONE
channel c1: starting piece 2 at 22-DEC-04
channel c1: finished piece 2 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_18_P_2_T_
545604600 comment=NONE
channel c1: starting piece 3 at 22-DEC-04
channel c1: finished piece 3 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_18_P_3_T_
545604600 comment=NONE
channel c1: starting piece 4 at 22-DEC-04
channel c1: finished piece 4 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_18_P_4_T_
545604600 comment=NONE
channel c1: starting piece 5 at 22-DEC-04
channel c1: finished piece 5 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_18_P_5_T_
545604600 comment=NONE
channel c1: starting piece 6 at 22-DEC-04
channel c2: finished piece 1 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_19_P_1_T_
545604600 comment=NONE
channel c2: backup set complete, elapsed time: 00:02:11
channel c2: starting full datafile backupset
channel c2: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00001
name=/u06/app/oradata/TARGDB/system01.dbf
input datafile fno=00009
name=/u06/app/oradata/TARGDB/tools01.dbf
input datafile fno=00010
name=/u06/app/oradata/TARGDB/users01.dbf
channel c2: starting piece 1 at 22-DEC-04
channel c1: finished piece 6 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_18_P_6_T_
545604600 comment=NONE
channel c1: backup set complete, elapsed time: 00:02:14
channel c2: finished piece 1 at 22-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_20_P_1_T_
545604731 comment=NONE
channel c2: backup set complete, elapsed time: 00:01:58
Finished backup at 22-DEC-04

Starting Control File and SPFILE Autobackup at 22-DEC-04

piece handle=/orabackup/rman/TARGDB/c-2528050866-20041222-04
comment=NONE
Finished Control File and SPFILE Autobackup at 22-DEC-04
released channel: c2
released channel: c1

RMAN> exit;

% ls -l /orabackup/rman/TARGDB/*
-rw-r----- 1 oracle dba 26214400 Dec 22 20:50
backup_db_TARGDB_S_18_P_1_T_545604600
-rw-r----- 1 oracle dba 26214400 Dec 22 20:50
backup_db_TARGDB_S_18_P_2_T_545604600
-rw-r----- 1 oracle dba 26214400 Dec 22 20:51
backup_db_TARGDB_S_18_P_3_T_545604600
-rw-r----- 1 oracle dba 26214400 Dec 22 20:51
backup_db_TARGDB_S_18_P_4_T_545604600
-rw-r----- 1 oracle dba 26214400 Dec 22 20:51
backup_db_TARGDB_S_18_P_5_T_545604600
-rw-r----- 1 oracle dba 19333120 Dec 22 20:52
backup_db_TARGDB_S_18_P_6_T_545604600
-rw-r----- 1 oracle dba 343392256 Dec 22 20:52
backup_db_TARGDB_S_19_P_1_T_545604600
-rw-r----- 1 oracle dba 331636736 Dec 22 20:54
backup_db_TARGDB_S_20_P_1_T_545604731
-rw-r----- 1 oracle dba 7946240 Dec 22 20:54 c-2528050866-
20041222-04

Observations
 Notice first, that like all offline backups, we need
to first shutdown and startup (mount) the
database. This can all be done within the RMAN
session.
 Next, we have a run block, which will contain
one or more statements contained within the
braces and all will execute as one block. Oracle
will not run any of the commands within the
braces of the run block until all statements have
been entered. The run block is completed with
the closing brace, at which time Oracle will be
compiled and executed.
 Then we see the allocate channel statements. In
this example, we have two channels allocated.
Each time a you create a channel, Oracle will
create one or more backup sets for that one
channel. In most cases, each channel will create
one backup set - but it is possible to have a
channel create more than one backup set. In
 this example, I will show that my configuration
will be the exception to the rule and it will
create multiple backup sets for one channel.
You show also notice that with each channel, I
can define the format it will use for each backup
piece.
 Now that I created two channels, RMAN will
automatically try to parallelize the backup
stream amoung those channels.
 When using multiple channels, you can
configure and control the maximum piece size,
read rate, rate, and maximum open files for
each backup piece by using the channel name
you assigned to it. In my example, I have two
defined channels - c1 and c2.
o I put no limits on the second channel c2.

o You will notice that I did define limits on the

first channel c1. In this example, I am asking

RMAN to limit each backup piece to 25MB.
This can be seen with the listing that I do
after the backup has completed. Notice that
each backup piece in backup set 18 is a
maximum of 25MB in size. When writting to
the backup piece, once it hit 25MB, RMAN
will start another backup piece. In the
 listing you can see that all together, that
channel c1 created 6 backup pieces.
 Notice that with the backup command, I am
including many options and that it spans several
lines. One of the key options I would like to
point out is filesperset 4. This is the exception to
the rule "one channel will create one backup
set" that I talked about earlier. With the
filesperset option, I am telling RMAN that I only
want a maximum of 4 Oracle datafiles to be
backed in each backup set. Looking at the listing
I performed (and the output of the RMAN run),
you will see that RMAN created two backup sets
for channel c2 to store a total of 7 Oracle
datafiles:
o Backup Set 19

 /u06/app/oradata/TARGDB/undotbs01.dbf
 /u06/app/oradata/TARGDB/cwmlite01.dbf
 /u06/app/oradata/TARGDB/odm01.dbf
 /u06/app/oradata/TARGDB/indx01.dbf
o Backup Set 20
 /u06/app/oradata/TARGDB/system01.dbf
 /u06/app/oradata/TARGDB/tools01.dbf
 /u06/app/oradata/TARGDB/users01.dbf

Also note that the filesperset 4 option I provided in

the backup command applies to all channels in
 the backup. As a note, notice that channel c1
creates one backup set with 4 Oracle datafiles.
o Backup Set 18
 /u06/app/oradata/TARGDB/perfstat01.dbf
 /u06/app/oradata/TARGDB/example01.dbf
 /u06/app/oradata/TARGDB/drsys01.dbf
 /u06/app/oradata/TARGDB/xdb01.dbf

Backup Archive Logs (All)

In the following example, I provide an RMAN command
to backup all archive logs and to delete the archive redo
log files from their archive destination (on disk) when the
backup it complete.
% rman target backup_admin/backup_admin nocatalog

RMAN> backup archivelog all delete input;

Starting backup at 23-DEC-04

current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=15 recid=5 stamp=545694669
channel ORA_DISK_1: starting piece 1 at 23-DEC-04
channel ORA_DISK_1: finished piece 1 at 23-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_34_P_1_T_
545694669 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archive log(s)
archive log
filename=/u06/app/oradata/TARGDB/archive/arch_t1_s15.dbf recid=5
stamp=545694669
Finished backup at 23-DEC-04

Starting Control File and SPFILE Autobackup at 23-DEC-04

piece handle=/orabackup/rman/TARGDB/c-2528050866-20041223-04
comment=NONE
Finished Control File and SPFILE Autobackup at 23-DEC-04

Observations
 The above command created a backup set
containing all archived redo logs. I marked
several of the lines in the output in blue that are
important in observing the actions performed
by RMAN.
 First, notice that RMAN performed a log as one
of it first actions. The output above shows that
this action was performed by the line reading
"current log archived".
 Now let's look at the backup set that RMAN
created -
(backup_db_TARGDB_S_34_P_1_T_545694669). It only
contains one archived redo log - the archived
 redo log that RMAN switched. In this example
there were no archived redo logs in the
destination directory. The only archived redo log
was the one that was created when RMAN
performed a log switch.
 Finally, notice that this backup performed a
backup of the current control file (and SPFILE)
even though I didn't ask for it. RMAN created
the control file (and SPFILE) backup set because
I had set the default configuration parameter
"CONTROLFILE AUTOBACKUP" to ON. If I had set this
configuration parameter to OFF, then RMAN
would not have created the control file (and
SPFILE) backup set.

Online Backup - (using configured defaults)

This example performs an online (hot) backup of the
Oracle database using RMAN. Before performing an
online backup, the Oracle database must be in archive log
mode. You can use the command "archive log list" to confirm
that the database is in archive log mode:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u06/app/oradata/TARGDB/archive
Oldest online log sequence 16
Next log sequence to archive 17
Current log sequence 17
Oracle9i introduced the ability to perform an RMAN
backup of the database along with all archived redo logs
in one command. The details of what will happen from
the command below have been already talked about.
The only thing in this example is that all of the
commands are put into one line.
% rman target backup_admin/backup_admin nocatalog

RMAN> backup database plus archivelog delete input;

Starting backup at 23-DEC-04

current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=17 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=16 recid=6 stamp=545696327
channel ORA_DISK_1: starting piece 1 at 23-DEC-04
channel ORA_DISK_1: finished piece 1 at 23-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_38_P_1_T_
545696328 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archive log(s)
archive log
filename=/u06/app/oradata/TARGDB/archive/arch_t1_s16.dbf recid=6
stamp=545696327
Finished backup at 23-DEC-04

Starting backup at 23-DEC-04

using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001
name=/u06/app/oradata/TARGDB/system01.dbf
input datafile fno=00002
name=/u06/app/oradata/TARGDB/undotbs01.dbf
input datafile fno=00011
name=/u06/app/oradata/TARGDB/perfstat01.dbf
input datafile fno=00007
name=/u06/app/oradata/TARGDB/example01.dbf
input datafile fno=00003
name=/u06/app/oradata/TARGDB/cwmlite01.dbf
input datafile fno=00004
name=/u06/app/oradata/TARGDB/drsys01.dbf
input datafile fno=00005 name=/u06/app/oradata/TARGDB/odm01.dbf
input datafile fno=00006 name=/u06/app/oradata/TARGDB/xdb01.dbf
input datafile fno=00008 name=/u06/app/oradata/TARGDB/indx01.dbf
input datafile fno=00009
name=/u06/app/oradata/TARGDB/tools01.dbf
input datafile fno=00010
name=/u06/app/oradata/TARGDB/users01.dbf
channel ORA_DISK_1: starting piece 1 at 23-DEC-04
channel ORA_DISK_1: finished piece 1 at 23-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_39_P_1_T_
545696330 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:04:15
Finished backup at 23-DEC-04

Starting backup at 23-DEC-04

current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=17 recid=7 stamp=545696585
channel ORA_DISK_1: starting piece 1 at 23-DEC-04
channel ORA_DISK_1: finished piece 1 at 23-DEC-04
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_40_P_1_T_
545696585 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archive log(s)
archive log
filename=/u06/app/oradata/TARGDB/archive/arch_t1_s17.dbf recid=7
stamp=545696585
Finished backup at 23-DEC-04

Starting Control File and SPFILE Autobackup at 23-DEC-04

piece handle=/orabackup/rman/TARGDB/c-2528050866-20041223-06
comment=NONE
Finished Control File and SPFILE Autobackup at 23-DEC-04

Observations
 The key thing to mention here is that we needed
to drop the keyword "all" that appeared after
the "archivelog" token used in the example of
backing up archived redo logs.
 Like in our previous example, notice that RMAN
performs a log switch since we included the "...
plus archivelog" clause.
 After performing the log switch, RMAN first
creates a backup set of any archived redo logs
(including the on that was just created from the
log switch). This is backup set
"backup_db_TARGDB_S_38_P_1_T_545696328" in the
example above.
 After created the backup set for all archived
redo logs, RMAN then creates a backup set for
the actual backup of all Oracle database files. In
the example above, this is done in backup set
"backup_db_TARGDB_S_39_P_1_T_545696330".
 During the backup of the Oracle database files,
changes were being made to the data contained
in those files. This information is being made to
the online redo logs during that time. It is for
this reason that RMAN performs another log
switch and creates an archived redo log backup
set. This is backup set
"backup_db_TARGDB_S_40_P_1_T_545696585" in this
example.
 Finally, just like in our last example, since the
RMAN configuration parameter "CONTROLFILE
 AUTOBACKUP" was set to ON, RMAN creates a
backup set for the control file (and SPFILE).

Keeping Backups
You can mark backups that can override the default
retention policy.
The KEEP FOREVER option requires the use of a true
recovery catalog:
RMAN> backup tablespace users keep forever consistent;
RMAN> backup database keep until time '01-MAR-2005' logs;

Starting backup at 04-JAN-05

using channel ORA_DISK_1
backup will be obsolete on date 01-MAR-05
archived logs required to recover from this backup will expire when this
backup expires
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001
name=/u06/app/oradata/TARGDB/system01.dbf
input datafile fno=00002
name=/u06/app/oradata/TARGDB/undotbs01.dbf
input datafile fno=00011
name=/u06/app/oradata/TARGDB/perfstat01.dbf
input datafile fno=00007
name=/u06/app/oradata/TARGDB/example01.dbf
input datafile fno=00010
name=/u06/app/oradata/TARGDB/users01.dbf
input datafile fno=00003
name=/u06/app/oradata/TARGDB/cwmlite01.dbf
input datafile fno=00004
name=/u06/app/oradata/TARGDB/drsys01.dbf
input datafile fno=00005 name=/u06/app/oradata/TARGDB/odm01.dbf
input datafile fno=00006 name=/u06/app/oradata/TARGDB/xdb01.dbf
input datafile fno=00008 name=/u06/app/oradata/TARGDB/indx01.dbf
input datafile fno=00009
name=/u06/app/oradata/TARGDB/tools01.dbf
channel ORA_DISK_1: starting piece 1 at 04-JAN-05
channel ORA_DISK_1: finished piece 1 at 04-JAN-05
piece
handle=/orabackup/rman/TARGDB/backup_db_TARGDB_S_126_P_1_T
_546727961 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:04:25
Finished backup at 04-JAN-05

Starting Control File and SPFILE Autobackup at 04-JAN-05

piece handle=/orabackup/rman/TARGDB/c-2528050866-20050104-04
comment=NONE
Finished Control File and SPFILE Autobackup at 04-JAN-05

Incremental Backups
This example performs an incremental (online) backup of
the Oracle database using RMAN.
In this example, it is assumed that you want to take one
full database backup once a week, and one incremental
database backup every day. The backup cycle starts on
Friday. A full backup is taken on Friday, and an
incremental backup is then taken every day.
Also in this example, it is assumed that I will be using
RMAN default configurations. One of the parameters I
set is "CONFIGURE RETENTION POLICY TO REDUNDANCY 3". The
retention policy of REDUNDANCY 3 applies only to full
(not incremental) backups, so the combination of that
policy and this backup schedule ensures that you can
restore to any incremental backup time for the last 3
weeks.
run {
# -----------------------------------------------------------
# The following RMAN commands are run each Friday to start
# the backup cycle.
# The steps are:
# - Backup database with incremental level 0.
# - Backup (and then delete) all archivelog files.
# -----------------------------------------------------------
backup
incremental level 0
filesperset 4
(database);
 backup
archivelog all
delete input;
}
Now, let's look at what happens on those other days. The
following commands can be run from Saturday through
Thursday to take cumulative incremental backups. Notice
that LEVEL 1 is specified with the BACKUP command.
Also notice that the options LEVEL 1 CUMULATIVE indicate
that only the blocks that have changed since the last
level 0 backup will be backed up. If the CUMULATIVE option
was not specified, then only the blocks that have
changed since the last LEVEL 1 backup will be backed up.
The advantage of a cumulative backup is that only one
incremental backup ever needs to be applied during
recovery.
run {
backup
incremental level 1 cumulative
filesperset 4
(database);
}

Mirroring Backups
It is possible to multiplex up to 4 copies per set at
runtime:
run {
set backup copies 2;
backup full
format
'/orabackup1/rman/TARGDB/backup_db_%d_S_%s_P_%p_T_%t'
,
'/orabackup2/rman/TARGDB/backup_db_%d_S_%s_P_%p_T_%t'
(database);
}

Copying Disk Backup to Tape

It is possible to copy a disk backupset to tape. (Backing
up a backup)
backup device sbt backup set all;

You can also copy a disk backup to tape then remove files
to create room for the next disk backup:
backup device sbt backup set created before 'SYSDATE - 1' delete
input;
Backup Failures
If the above backup fails for any reaon, you can use the
NOT BACKED UP SINCE option on the BACKUP command (9i
restartable backup feature) to continue from the point of
failure. The small value of FILESPERSET is good for
restartable backups. However you should note that
smaller FILESPERSET produces more backup sets.
run {
# -----------------------------------------------------------
# To re-start from the point of failure, run following
# commands.
# -----------------------------------------------------------
backup
incremental level 0
filesperset 4
not backed up since time 'sysdate-1'
(database);
}