A whole
database backup is a copy of all data files and the control file. You can
optionally include the server parameter file (SPFILE) and archived redo log
files. Using Recovery Manager (RMAN) to make an image copy of all the database
files simply requires mounting or opening the database, starting RMAN, and
entering the BACKUP command. Optionally, you can supply the DELETE INPUT option
when backing up archivelog files. That causes RMAN to remove the archivelog
files after backing them up. This is useful especially if you are not using a
Flash Recovery Area, which would perform space management for you, deleting
files when space pressure grows.
RMAN> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT;
You must
have issued the following CONFIGURE commands to make the backup:
•
CONFIGURE
DEFAULT DEVICE TYPE TO disk;
•
CONFIGURE
DEVICE TYPE DISK BACKUP TYPE TO COPY;
•
CONFIGURE
CONTROLFILE AUTOBACKUP ON;
You can
also create a backup (either a backup set or image copies) of previous image
copies of all data files and control files in the database by using the
following command:
RMAN> BACKUP COPY OF
DATABASE;
By default,
RMAN executes each BACKUP command serially. However, you can parallelize the
copy operation by:
•
Using
the CONFIGURE DEVICE TYPE DISK PARALLELISM n command, where n is the desired
degree of parallelism
•
Allocating
multiple channels
•
Specifying
one BACKUP AS COPY command and listing multiple files
