Oracle® Database Recovery Manager Reference 10g Release 1 (10.1) Part Number B10770-02 |
|
|
View PDF |
configure::=
backupConf::=
Text description of backupConf
cfauConf::=
deviceConf::=
Text description of deviceConf
To configure persistent settings affecting RMAN backup, restore, duplication, and maintenance jobs. These configurations are in effect for any RMAN session until the configuration is cleared or changed.
Use CONFIGURE
to set the following:
DISK
or sbt
) for RMAN jobsON
or OFF
ON
or OFF
RMAN uses default settings for CONFIGURE
options. You can return to the default value for any CONFIGURE
command by running the same command with the CLEAR
option.
See Also:
Oracle Database Backup and Recovery Basics to learn how to configure the RMAN environment |
CONFIGURE
cannot be used within a RUN block.ALLOCATE CHANNEL
override any configured automatic channels.BACKUP
command.CONFIGURE
CHANNEL
command, then RMAN uses the same numbers in the system-generated channel names.CONNECT
or PARMS
options to create backups or copies, then you must either use the same configured channels or manually allocate channels with the same options to restore or crosscheck these backups.SYSTEM
tablespace from whole database backups.REDUNDANCY
and RECOVERY
WINDOW
options are mutually exclusive. Only one type of retention policy can be in effect at any time.CONFIGURE
...
CLEAR
. For example, you can run CONFIGURE
CHANNEL
DEVICE
TYPE
sbt
CLEAR
but not CONFIGURE
CHANNEL
DEVICE
TYPE
sbt
MAXPIECESIZE
5M
CLEAR
.CONFIGURE
CHANNEL
. In other words, you cannot issue a command such as CONFIGURE
CHANNEL
2
DEVICE
TYPE
DISK
, but you can issue a command such as CONFIGURE
CHANNEL
2
DEVICE
TYPE
DISK
MAXPIECESIZE
2500K
.CONFIGURE
CONTROLFILE
AUTOBACKUP
FORMAT
format string must include the %F substitution variable. It cannot contain any other substitution variable.Syntax Element | Description |
---|---|
|
Governs archived redo log deletion policy for the flash recovery area. Possible settings are:
|
|
Configures the auxiliary filename for the specified target datafile to If you are performing TSPITR or running the For example, use this command during TSPITR if the datafiles are on raw disk and you need to restore auxiliary datafiles to raw disk for performance reasons. Typically, you set the When renaming files with the See Also: Oracle Database Backup and Recovery Advanced User's Guide to learn how to perform RMAN TSPITR, and Oracle Database Backup and Recovery Advanced User's Guide to learn how to duplicate a database with RMAN |
Configures default backup options such as duplexing, optimization, excluding tablespaces, backup set sizes, and retention policies. |
|
Configures control file autobackup settings |
|
Configures default backup settings for devices, such as the default backup device, channel configurations for devices, default backup types for each device, and parallelism. |
|
|
Configures the snapshot control file filename to The default value for the snapshot control file name is platform-specific and dependent on the Oracle home. For example, the default on some UNIX system is See Also: Oracle Database Backup and Recovery Advanced User's Guide for more information about snapshot control files |
Syntax Element | Description |
---|---|
|
Specifies the number of copies of each backup set for Note: Control file autobackups on disk are a special case and are never duplexed. RMAN always writes one and only copy. Note: RMAN raises an error if you try to duplex backups to the flash recovery area. You cannot duplex backups to the flash recovery area. |
|
Toggles backup optimization Optimization does not back up a file to a device type if the identical file is already backed up on the device type. For two files to be identical, their content must be exactly the same. You can override backup optimization by using the RMAN does not signal an error if optimization causes all files to be skipped during a backup. Note that Backup optimization is enabled when all of the following conditions are met:
The retention policy has an effect on which files backup optimization skips. See Also: Oracle Database Backup and Recovery Advanced User's Guide for a description of how RMAN determines that it can skip the backup of a file |
|
Excludes the specified tablespace from You can still back up the configured tablespace by explicitly specifying it in a |
|
Specifies the maximum size of each backup set created on a channel. By default Note: This option is ignored by |
|
Specifies a persistent, ongoing policy for datafile and control file backups and copies that RMAN marks as obsolete, that is, not needed and eligible for deletion. As time passes, RMAN marks backups and copies as obsolete according to the criteria you specify in the retention policy. RMAN does not automatically delete any backups or copies: manually run the For backups, the basic unit of the retention policy is a backup set (not a backup piece) or image copy. For example, |
Resets the retention policy to its default ( |
|
Specifies a time window in which RMAN should be able to recover the database. The window stretches from the current time ( |
|
Specifies that RMAN should retain |
|
Disables the retention policy feature. RMAN does not consider any backups or copies as obsolete. |
Syntax Element | Description |
---|---|
|
Controls the control file autobackup feature. By default, this feature is not enabled. |
Returns the feature to its default setting of |
|
|
Configures the default filename format for the control file autobackup on the specified device type. If a flash recovery area is enabled, then RMAN creates the disk autobackup in the flash recovery area. Otherwise, RMAN creates it in an operating system specific location ( By default, the initial format is
Specify The formatSpec can specify an Automatic Storage Management disk group. The following example configures a channel for an ASM disk group: CONFIGURE CONTROLFILE AUTOBACKUP FOR DEVICE TYPE DISK TO '+dgroup1'; See Also: "formatSpec", for the semantics of the |
Disables the autobackup feature. ( |
|
If
The first channel allocated during the backup or copy job creates the autobackup and places it into its own backup set; for post-structural autobackups, the default disk channel makes the backup. RMAN writes the control file and the server parameter file to the same backup piece. After the control file autobackup completes, the database writes a message containing the complete path of the backup piece and the device type to the alert log. The default location for the autobackup on disk is the flash recovery area (if configured) or a platform-specific location (if not configured). RMAN automatically backs up the current control file using the default format of |
Syntax Element | Description |
---|---|
|
Specifies the standard or If you configure a generic channel (that is, if you do not specify a channel number), then RMAN uses the generic settings for every parallelized channel except any channel number that you have explicitly configured. A generic channel setting specifies options for all channels not configured explicitly. For generic channels of a specified device type, a new command erases previous settings for this device type. Assume that you run these commands: CONFIGURE CHANNEL DEVICE TYPE sbt MAXPIECESIZE 1G; CONFIGURE CHANNEL DEVICE TYPE sbt FORMAT 'bkup_%U'; The second command erases the If See Also: Oracle Database Backup and Recovery Advanced User's Guide to learn how configure automatic channels specified by channel number |
Specifies control options for the allocated channel. Note that the CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '+dgroup1'; See Also: "allocOperandList" |
|
Clears the specified channel. For example, |
|
|
Specifies the default device type for automatic channels. By default, By default, the The |
|
Specifies the device type (disk or sbt) to which to apply the settings specified in this |
Resets backup type and parallelism settings for this device to their defaults.. |
|
Configures the default backup type for disk or tape backups to either For sbt devices the The default for If the backup type is set to The default location for disk backups is the flash recovery area, if one is configured; otherwise, backups are stored in a platform-specific location (for Unix and Windows, this is |
|
Configures the device types that are eligible for use in jobs that use automatic channels and sets the degree of channel parallelism ( The By default, To change the parallelism for a device type to CONFIGURE DEVICE TYPE sbt PARALLELISM 3; CONFIGURE DEVICE TYPE sbt PARALLELISM 2; Note: If you configure |
This example configures RMAN so that the BACKUP
command does not back up files to a device type if the identical file has already been backed up to the device type:
CONFIGURE BACKUP OPTIMIZATION ON;
This example configures a retention policy with a recovery window of 2 weeks, and then resets the retention policy to its default value of REDUNDANCY
=
1
:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS; CONFIGURE RETENTION POLICY CLEAR;
This example configures generic DISK
and sbt
channels, sets the default device type to sbt
, and sets PARALLELISM
to 3
:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/?/%U'; CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'ENV=(NSR_SERVER=bksrv1)'; CONFIGURE DEFAULT DEVICE TYPE TO sbt; CONFIGURE DEVICE TYPE sbt PARALLELISM 3;
This example configures the default device type to sbt
, backs up the archived logs on the default sbt
channel, and then backs up the database to disk on the default disk channel:
CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'ENV=(NSR_SERVER=bksrv1)'; CONFIGURE DEFAULT DEVICE TYPE TO sbt; BACKUP ARCHIVELOG ALL; BACKUP DEVICE TYPE DISK DATABASE;
This example configures automatic disk channels across three file systems:
CONFIGURE DEVICE TYPE DISK PARALLELISM 3; CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/disk1/backup/%U'; CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/disk2/backup/%U'; CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT '/disk3/backup/%U'; BACKUP DEVICE TYPE DISK DATABASE PLUS ARCHIVELOG;
This example allocates automatic sbt
channels for two nodes of an Oracle Real Application Clusters database:
CONFIGURE DEVICE TYPE sbt PARALLELISM 2; CONFIGURE DEFAULT DEVICE TYPE TO sbt; CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT 'SYS/change_on_install@node1' PARMS 'ENV=(NSR_SERVER=bkserv1)'; CONFIGURE CHANNEL 2 DEVICE TYPE sbt CONNECT 'SYS/change_on_install@node2' PARMS ENV=(NSR_SERVER=bkserv2)';
This example clears manually numbered DISK
channels 2
and 3
and the generic sbt
channel:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR; CONFIGURE CHANNEL 3 DEVICE TYPE DISK CLEAR; CONFIGURE CHANNEL DEVICE TYPE sbt CLEAR;
This example sets DISK
parallelism to 2
, then changes it to 3
, then returns it to the default parallelism of 1
:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2; CONFIGURE DEVICE TYPE DISK PARALLELISM 3; CONFIGURE DEVICE TYPE DISK CLEAR;
This example configures duplexing to 3
for DISK
backups of datafiles and control files (control file autobackups on disk are a special case and are never duplexed) and then runs a database backup, specifying three different file systems for the copies:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 3; BACKUP DEVICE TYPE DISK DATABASE FORMAT '/disk1/backup/%U', '/disk2/backup/%U', '/disk3/backup/%U';
This example configures a new location for the snapshot control file and then resynchronizes the recovery catalog.
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '?/oradata/snap.cf';
This example excludes the example
tablespace from whole database backups, then returns the tablespace to its default value of "not excluded":
CONFIGURE EXCLUDE FOR TABLESPACE example; CONFIGURE EXCLUDE CLEAR;
This example duplicates a database to a remote host with a different directory structure, by using CONFIGURE
AUXNAME
to specify new filenames for the datafiles:
# set auxiliary names for the datafiles CONFIGURE AUXNAME FOR DATAFILE 1 TO '/oracle/auxfiles/aux_1.f'; CONFIGURE AUXNAME FOR DATAFILE 2 TO '/oracle/auxfiles/aux_2.f'; CONFIGURE AUXNAME FOR DATAFILE 3 TO '/oracle/auxfiles/aux_3.f'; CONFIGURE AUXNAME FOR DATAFILE 4 TO '/oracle/auxfiles/aux_4.f'; RUN { ALLOCATE AUXILIARY CHANNEL dupdb1 TYPE DISK; DUPLICATE TARGET DATABASE TO dupdb LOGFILE GROUP 1 ('?/dbs/dupdb_log_1_1.f', '?/dbs/dupdb_log_1_2.f') SIZE 200K, GROUP 2 ('?/dbs/dupdb_log_2_1.f', '?/dbs/dupdb_log_2_2.f') SIZE 200K REUSE; } # Un-specify the auxiliary names for the datafiles so that they are not overwritten # by mistake: CONFIGURE AUXNAME FOR DATAFILE 1 CLEAR; CONFIGURE AUXNAME FOR DATAFILE 2 CLEAR; CONFIGURE AUXNAME FOR DATAFILE 3 CLEAR; CONFIGURE AUXNAME FOR DATAFILE 4 CLEAR;
This example turns on the autobackup feature, then changes the default format for the DISK
and sbt
devices, then clears the autobackup setting:
CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '?/oradata/%F'; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE sbt TO 'cf_auto_%F'; CONFIGURE CONTROLFILE AUTOBACKUP CLEAR; # returns to default setting of OFF