Creates a backup of all data files in the database. If generating a backup set, then RMAN can include only data files and control files: it cannot include archived redo log files.
If the backupSpec includes data file 1, and if CONFIGURECONTROLFILE AUTOBACKUP is OFF, then RMAN automatically includes the control file in the backup. If the instance is started with a server parameter file, then RMAN also includes this parameter file in the backup.
If the backupSpec includes data file 1, and if CONFIGURECONTROLFILE AUTOBACKUP is ON, then RMAN does notautomatically include the control file in the output. Instead, RMAN generates a separate control file autobackup piece. If the instance is started with a server parameter file, then RMAN includes this parameter file in the autobackup piece.
Full database backups should usually be either image copies or compressed backup sets. Image copies are more flexible than backup sets for some purposes (such as use in an incrementally updated backups strategy), and compressed backup sets make more efficient use of storage space, if the CPU overhead involved in creating them is tolerable.
Note: To force RMAN to include the current control file in the backup when CONTROLFILE AUTOBACKUP is ON, specify the INCLUDE CURRENT CONTROLFILE clause.
See Also: The TABLESPACE description to learn about backup behavior when the database includes bigfile tablespaces
PLUS ARCHIVELOG
Includes archived redo log files in the backup (see Example 2-15). Causes RMAN to perform the following steps:
Run an ALTER SYSTEM ARCHIVE LOG CURRENT statement.
Run the BACKUP ARCHIVELOG ALL command. If backup optimization is enabled, then RMAN only backs up logs that have not yet been backed up.
Back up the files specified in the BACKUP command.
Run an ALTER SYSTEM ARCHIVE LOG CURRENT statement.
Back up any remaining archived redo log files. If backup optimization is not enabled, then RMAN backs up the logs generated in step 1 plus all the logs generated during the backup.
You cannot specify PLUS ARCHIVELOG on the BACKUP ARCHIVELOG command or BACKUP AS COPY INCREMENTALcommand (or BACKUP INCREMENTAL command when the default backup type is COPY). You cannot specify PLUS ARCHIVELOG when also specifying INCREMENTAL FROM SCN.
Unless the online redo log is archived after the backup, DUPLICATE is not possible with this backup.
DELETE [ALL] INPUT
Deletes the input files after successfully backing them up.
Specify this option only when backing up archived redo log files, data file copies (COPY OF or DATAFILECOPY), or backup sets. The BACKUP ARCHIVELOG command only backs up one copy of each distinct log sequence number, so if the DELETE INPUT option is used without the ALL keyword, RMAN only deletes the copy of the file that it backs up.
Specifying the DELETE INPUT option is equivalent to issuing the DELETE command for the input files. When backing up archived redo log files, RMAN uses the configured settings to determine whether an archived redo log can be deleted (CONFIGUREARCHIVELOG DELETION POLICY TO BACKED UP).
The ALL option applies only to archived redo log files. If you run DELETE ALL INPUT, then the command deletes all copies of corresponding archived redo log files or data file copies that match the selection criteria in theBACKUP command (as shown in Example 2-19). For example, if you specify the SEQUENCEn clause, then RMAN deletes all archived redo log files with same sequence number n.
Note: The database retains archived redo log files in the fast recovery area as long as possible and deletes them automatically when disk space is required. You can use the BACKUP DELETE INPUT, DELETEARCHIVELOG, andDELETE OBSOLETE commands to delete log files manually from inside or outside the recovery area. You do not need to specify BACKUP DELETE INPUT when backing up the recovery area because the database automatically deletes log files based on the archived redo log deletion policy and other fast recovery area rules.
Example 2-19 Backing Up and Deleting Archived Redo Log Files
This example assumes that you have two archiving destinations set: /disk2/PROD/archivelog/ and /disk1/arch/. The command backs up one archived redo log for each unique sequence number. For example, if archived redo log 1000 is in both directories, then RMAN only backs up one copy this log. The DELETE INPUTclause with the ALL keyword specifies that RMAN should delete all archived redo log files from both archiving directories after the backup.
扫一扫
3463
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
