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 faster processed.
format ‘%d%t%s%p’ creates a TSM low level name including database
name/timestamp/backup set number/backup piece number.
tag ‘beach offline Monday Full’ 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.
10.3.2 Archived redo log backup
This example shows how to back up the archived redo logs. Before you back
up the archived redo logs, Oracle recommends that you archive the current
online redo log file by using the alter system archive current log command.
C:\oracle\admin\scripts>rman target internal/manager@beach rcvcat rman/rman@ri
cmdfile=backup_archlog_beach log=backup_archlog_beach.log
The next example shows how to back up archived redo logs from one
archivelog destination.
sql 'alter system archive log current' ;
run {
allocate channel t1 type 'sbt_tape' parms
'ENV=(DSMO_AVG_SIZE=1)';
allocate channel t2 type 'sbt_tape' parms
'ENV=(DSMO_AVG_SIZE=1)';
backup
filesperset 20
format '%d/LOGS/%t/%s/%p'
archivelog all
delete input ;
release channel t1 ;
release channel t2 ;
}
Chapter 10. Oracle backup considerations on Windows 2000 165