Backing Up Oracle - Computing at Cornell

The following is an explanation of various statements in our coding example:
set maxcorrupt for datafile 1 to 0 causes Oracle to abort the backup
process if RMAN detects corrupt blocks in the SYSTEM tablespace.
In our database, we used AUTOEXTEND=ON for all datafiles. Datafile 1 is
always used for the SYSTEM tablespace.
backup full causes a whole database backup.
filesperset 3 forces RMAN to include maximal 3 files in a backup set.
A possible restore from a single datafile will be processed faster.
format ‘%d%t%s%p’ creates a TSM low level name including database
name/timestamp/backup set number/backup piece number
tag ‘paris offline 20010316.1111’ is a user defined symbolic name which
is assigned to backup sets. It makes it easier to address these backups in
RMAN restore or change commands.
alter database open finally makes the database accessible to users.
6.4.2 Archived redo log backup
The next examples show how to back up archived redo logs.
In both examples, the current log is archived before the backup archivelog is
started.
The first example uses only one log archive destination as input for the RMAN
backup and two different channels to speed up the process.
With the filesperset 20 RMAN creates up to 20 backup pieces in one backup
set.
The delete input option tells RMAN to deletes the archive logs on disk after a
successful backup:
Chapter 6. Oracle backup considerations on UNIX 83