If the initialization parameter DB_BLOCK_CHECKSUM=TRUE, and if MAXCORRUPT and NOCHECKSUM are not set, then specifying CHECK LOGICAL detects all types of corruption that are possible to detect. Some SBT2.0 vendors may support longer filenames. Causes the database to issue an error message when it cannot proxy copy rather than creating conventional backup sets. With the COMPRESSED option, binary compression is used. Note: This option cannot be used with BACKUP AS COPY and results in an error message. A datafile is only considered inaccessible if it cannot be read. Note: This option cannot be used with BACKUP AS COPY and results in an error message. FORMAT setting, that setting is used to generate output file names, If a flash recovery area is configured, the backups are placed in the flash recovery area. RMAN also skips other datafile blocks that do not currently contain data, if all of the following conditions apply: The COMPATIBLE initialization parameter is set to 10.2, There are currently no guaranteed restore points defined for the database, The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup. You cannot make a backup (either normal or incremental) in NOARCHIVELOG mode when the database is open or is closed after an instance failure or SHUTDOWN ABORT. RMAN can back up tablespaces with different block sizes, but puts each differently sized datafile into its own backup set. Some offline datafiles can still be read because they still exist on disk. Assume that this backup set has primary key 1234. The command backs up all datafiles to tape, as well as the current control file, the server parameter file, and archived logs: Scripting Incremental Backups: ExampleThis example shows a series of scripts that you can run to make regular incremental backups of the database: Performing a Cumulative Incremental Backup: ExampleThis example backs up all blocks changed in the database since the most recent level 0 backup: Backing Up Tablespaces and Datafiles to Disk as Backup Sets: ExampleThis command uses two backupSpec clauses to back up tablespaces and datafiles and lets RMAN perform automatic parallelization of the backup: Backing Up Tablespaces and Datafiles to Disk as Image Copies: ExampleThis command uses two backupSpec clauses to back up tablespaces and datafiles and lets RMAN perform automatic parallelization of the backup: Backing Up Datafile Copies: ExampleThis example finds three datafile copies with the tag LATESTCOPY, copies them to directory /copies and names the new copies by means of subsitution variables: Backing Up Archived Logs and Deleting the Input: ExampleThis example assumes that you have two archive destinations set: /arch1 and /arch2. When you specify MAsXSETSIZE, RMAN attempts to limit the size in bytes of the backup sets according to the MAXSETSIZE parameter. If the backup command is part of a RUN block, subsequent commands in the RUN block do not execute. RMAN can apply a binary compression algorithm as it writes data to backup sets. Note: It is not necessary for the image copies that you are backing up to have been created by a single BACKUP command. Note: If the flash recovery area is not enabled but has been enabled in the past, then files that were created in the previous flash recovery area location are backed up. Full database backups should usually be either image copies or compressed backupsets. LIKE 'pattern' specifies a filename pattern. The ALL option applies only to archived logs. Therefore, use uncompressed backup sets and turn on the compression provided by the media management vendor when backing up to locally attached tape devices. Backs up only those files (of the files specified on the command) that RMAN has never backed up. The tag is not case sensitive. Image copy files can only exist on disk. If you specify the tag at: The command level, then all backup sets created by the command have the tag. This behavior is similar to RMAN's behavior when backing up archived logs that exist in multiple archiving destinations. Vendors supporting SBT 1.1 must support filenames up to 14 characters. If you specify FOR STANDBY, then RMAN creates a backup of the control file usable for creation of a standby database. By using the BACKUP INCREMENTAL FOR RECOVER OF COPY WITH TAG syntax you can create level 1 incremental backups suitable for rolling forward a level 0 incremetal image copy backup of your database. Note: You cannot assign a tag to a backup of the current control file. Backing Up Datafiles, Tolerating Corrupt Blocks: ExampleThis example backs up datafile 3 and specifies that no more than two blocks with corruption should be tolerated: Making an Image Copy of a Database Copy: ExampleThis example makes an image copy of the database copy with tag TEST to the default destination, gives the output copy the tag DUPTEST, and performs logical checking: Creating a Long-Term Database Backup: ExampleThis example creates a consistent backup of the database and server parameter file that is exempt from the retention policy. Note: This option does not apply with AS COPY and results in an error message. A BACKUP command is decomposed into multiple independent backup steps by RMAN. Causes RMAN to ignore backup optimization. You cannot use the DELETE INPUT option when backing up objects other than datafile copies, archived redo logs, or backup sets. To back up a database, tablespace, datafile (current or copy), control file (current or copy), SPFILE, archived log, or backup set. Copyright1996, 2005,Oracle. You cannot back up locally-managed temporary tablespaces (although you can back up dictionary-managed tablespaces). All changed blocks captured in the incremental backup are updated at the standby, bringing it up to date with the original. Specifies a maximum time for a backup command to run. Backup sets containing archived logs are encrypted if any of the following are true: SET ENCRYPTION ON is in effect at the time that the archive log backup is being created. If the instance is started with a server parameter file, then RMAN also includes this parameter file in the backup. Incremental backups copy only those blocks that have changed since a previous backup. 'filename' specifies an image copy by filename, ALL specifies that all datafile image copies should be backed up. If no automatic channel is configured for the specified device type, then you must manually allocate a channel for each execution of the BACKUP command. You can use the following parameters: Prevents the inclusion of identical datafile copies in a backup operation. Thus, to limit a backup set to 3 MB, specify MAXSETSIZE = 3M. ), Unused Block Compression Of Datafile Backups to Backup Sets, When backing up datafiles into backup sets, RMAN does not back up the contents of data blocks that have never been allocated. (In previous releases, this behavior was referred to as NULL compression.). Note: Duplexing cannot be used when creating files in the flash recovery area. However, RMAN permits a single FORMAT string to exist in multiple backupSpec clauses. Each backupSpec clause generates one or more backup sets (AS BACKUPSET) or image copies (AS COPY). If you do not specify TAG, then RMAN backs up the most recent datafile copy for each datafile in the tablespace. You must use a current control file when using the BACKUP command. For example, if you run BACKUP AS BACKUPSET COPIES 1 DATABASE TAG TUE_PM, then only one copy of the backup set exists and each piece in the backup set has tag TUE_PM. Note: The output of this command can be image copies or backup sets. Note that if backup optimization is enabled, then RMAN only backs up logs that have not yet been backed up. Backs up the specified files by means of the proxy copy functionality, which gives the media management software control over the data transfer between storage devices and the datafiles on disk. RMAN compares the DISKRATIO value to the actual number of devices involved in the backup and uses the lowest value. Otherwise a platform-specific default FORMAT (which includes a %U for generating a unique filename) is used. The media managernot RMANdecides how and when to move data. Specify size in bytes (default), kilobytes (K), megabytes (M), or gigabytes (G). For AS BACKUPSET, the backupSpec clause generates multiple backup sets if the number of datafiles specified in or implied by its list of objects exceeds the default limit of 4 datafiles or 16 archived logs in each backup set. Note: You can also specify this parameter in the backupSpec clause. If you make a level 1 incremental backup, then RMAN backs up all blocks changed since the pre-RESETLOGS level 0 backup. If you do, and some data blocks in the files being backed up are modified before being read by the backup session, then the backup is not usable after being restored because it requires recovery. Specifies the filenames of one or more datafile image copies. The default number of files in each backup set is 4 for datafiles and 16 for archived logs. Dual-mode encryption, where backups can be created using either as with transparent encryption or password-based encryption, and where decryption can be performed based upon either the Oracle Encryption Wallet, or a password the DBA supplies at decryption time. For, Identifies the backup being created as an incremental backup to be used in rolling forward an image copy. When the AS BACKUPSET option is used, RMAN generates one or more backup sets, which are RMAN-specific logical structures. Creates an incremental backup of all specified datafiles which includes all datafile blocks changed at SCNs greater than or equal to the specified SCN. If you have multiple channels allocated, and one channel fails or encounters a problem during a backup step, then RMAN attempts to complete the work on another channel. If you specify DEVICE TYPE DISK, then RMAN will back up to random access disks. Consult your media management documentation to see whether the. If no manual channel is allocated, then RMAN uses the default channels (as set using the CONFIGURE command). Useful in strategies other than the incrementally updated backups strategy, which uses the, Lets you specify that this incremental should contain all changes since the SCN of a specified datafile copy (level 0 incremental backup) of your database. If a backup command does not complete in the specified duration, the backup being taken stops. RMAN does not support incremental backups of control files, archived redo logs, or backup sets. The command instructs RMAN to keep the backup for the next year, but not to keep the archived logs necessary to recover it: Exempting Copies from the Retention Policy: ExampleThe following example copies the control file and two datafiles and exempts them from the retention policy forever. For example, if you duplexed a backup to 4 locations, then RMAN deletes all 4 backup sets. You must back up files onto valid media. Use this command periodically to check for physical and logical errors in database files. For details on block change tracking, including how to enable and disable it, see Oracle Database Backup and Recovery Basics. If multiple backup sets are created by one BACKUP AS BACKUPSET command, then each backup piece is assigned the same default tag. Note:Backup Unused Space Compression, described in "Unused Block Compression Of Datafile Backups to Backup Sets", causes some datafile blocks to be skipped during full backups of datafiles as backup sets. For example, ASM does not support the use of the - character in the filenames it uses interally, so a tag including a - (for example, weekly-incremental) is not a legal tag name if you are storing backups in ASM disk groups. If you wish to prevent the use of block checksums in your backup, use the NOCHECKSUM option. However, when you use RMAN to create image copies, they are recorded in the RMAN repository, and are more easily available for use in restore and recovery operations. The percent sign (%) as a wildcard meaning 0 o r more characters; an underscore (_) is a wildcard meaning 1 character. RMAN backs up all datafiles that are currently part of the tablespaces. If AS BACKUPSET is set, then this feature is only useful if RMAN generates multiple backup sets during the backup. "CONFIGURE" describes the complete set of circumstances in which autobackups occur. If you rename a tablespace (for example, from users to customers), then RMAN detects that the tablespace has changed its name and updates the recovery catalog on the next resynchronization. The target database must be mounted or open when using the RMAN BACKUP command. With MINIMIZE LOAD the backup will take the full specified duration. When you run BACKUP with the PROXY option, RMAN performs these steps: Searches for a channel of the specified device type that is proxy-capable. The checksum is verified when restoring from the backup and written to the datafile when restored. The maximum length of a backup piece filename is platform-specific. When using encrypted backups, datafiles from tablespaces with different encryption settings are never written into the same backup set. If you specify neither parameter, then DISKRATIO defaults to 4. RMAN comes with a DISK channel preconfigured but no preconfigured channels for sbt devices. Specifies a range of archived redo logs to be backed up. Specify this option only when backing up archived logs, datafile copies (. LIKE 'pattern' specifies a filename pattern. Encryption is configured for backups of the whole database or at least one tablespace. Specify the tablespaces in the list by tablespace name (for example, users) or specify a particular copy by tag name (for example, 0403_CPY_OF_USERS). The database performs checks when attempting to create a level 1 incremental backup, to ensure that the incremental backup is usable by a subsequent RECOVER command. (Note that KEEP FOREVER requires a recovery catalog.). Note: Do not spread I/O over more than the minimum number of disks required to keep the tape streaming. The algorithms that control which backups RMAN selects for use in a restore and recovery do not select incremental backups created using FROM SCN. You cannot make an image copy of a backup set, although you can make an image copy of an image copy. The backup contains only the standby control file. Creates image copies (rather than backup sets). For SBT backups using a media manager, the length is also limited by the limit in the supported version of the media management API. The default size is in bytes, rounded down from kilobytes. The backup set is the smallest unit of a backup. The ALL option is redundant, that is, it does not add any functionality. Tags are not case sensitive. If the database being backed up is running at or near its maximum load, you may find the overhead from using AS COMPRESSED BACKUPSET unacceptable. When backing up datafiles into backup sets, RMAN only backs up blocks that are currently in use. Although the database depends on other types of files for operation, such as network configuration files, password files, and the contents of the Oracle home, these files cannot be backed up with RMAN. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up. The backup set includes the standby control file and the object backed up. Creates a snapshot of the current control file and places it into each backup set produced by this clause. The default location of the incremental is the dbs subdirectory under the Oracle home. Specifies the date after which RMAN should back up files that have no backups. Typically, a tag is a meaningful name such as MONDAY_EVENING_BACKUP or WEEKLY_FULL_BACKUP. If you specify INCREMENTAL, then in the backupSpec clause you must set one of the following parameters: DATAFILE, DATAFILECOPY, TABLESPACE, or DATABASE. With disk backups, you can use MINIMIZE TIME run the backup at maximum speed (default) , or MINIMIZE LOAD to slow the rate of backup to lessen the load on the system. In practice, most disk drives have physical block sizes of 512 bytes, so this limitation rarely affects backup. If RMAN locates a proxy-capable channel, it calls the media manager to check if it can proxy copy the files. If the, Limits the set of files to be backed up according to whether a specified number of backups are already present (and not obsolete), or whether the files have been backed up since a specified date. RMAN creates no output files. AS BACKUPSET is the only possibility when backing up to tape, and for creating level 1 incremental backups to any destination. You can only backup a database running in NOARCHIVELOG mode after a consistent shutdown. Instead, RMAN generates a separate control file autobackup piece. For an overview of the encrypted backups mechanism, a guide to its use and information on choosing among the different modes of encryption, see Oracle Database Backup and Recovery Advanced User's Guide. If you do not want RMAN to try a conventional copy when a proxy copy fails, use the ONLY option. You can also specify the tag at the backupSpec level. In other words, all files in the same backup set have the same completion time. If you run BACKUP AS COPY on a channel that has MAXSETSIZE set, then MAXSETSIZE is silently ignored. Recovery files are full and incremental backup sets, control file autobackups, archived logs, and datafile copies. If you specify DEVICE TYPE sbt, then you can back up to any media supported by the media manager. Specifies a variety of options and parameters that affect the, Specifies the type of backup being created, either backup sets or image copies. You can use, Specifies a maximum size for a backup set.RMAN limits all backup sets to this size. See, Specifies the media pool in which the backup should be stored. For example, if you specify the SEQUENCE n clause, then RMAN deletes all archive logs with same sequence number n, including duplicate archived logs (that is, logs with same log sequence number and thread). Specifies options related to the maximum time for a backup command to run. Flashback logs, the current control file, and online redo logs are, Backs up the server parameter file currently used by the database. An incremental backup at level 0 is identical in content to a full backup, but unlike a full backup the level 0 backup is considered a part of the incremental strategy. The RMAN CONFIGURE, SET and SHOW commands are used to manage the encryption settings for your database backups. The number of files to be backed up is divided by the number of channels. For example, assume that datafiles are distributed across 10 disks. Others have been deleted or moved and so cannot be read, making them inaccessible. See Also: "CONNECT" for information on the effect of recovery catalog compatibility on this command. For example, you back up the database, but the instance fails halfway through. See Also: "formatSpec" for legal substitution variables. The, Backs up only those archived logs that have not been backed up at least. Backs up any remaining archived redo logs. This option is a convenient way to back up new files after adding them to the database. When used with commands that create backupsets, specifies the maximum number of files to include in each backupset created. You cannot specify the number of backup pieces that should go in a backup set. If CONFIGURE CONTROLFILE AUTOBACKUP is set to ON, then RMAN automatically backs up the control file after BACKUP commands. The limit on the number of files in a backup set will apply even if the total size of the resulting backup set is less than MAXSETSIZEs. You cannot specify DEVICE TYPE DISK when running the BACKUP RECOVERY AREA command. A level 0 backup must exist as the base backup for an incremental strategy. If the disks supply data at 10 bytes/second, and if the tape drive requires 50 bytes/second to keep streaming, then set DISKRATIO = 5 to direct RMAN to include datafiles from at least 5 disks in each backup set. Note: You can duplex backups of backup sets by using BACKUP COPIES and SET BACKUP COPIES. Each backup set contains at least one backup piece, which is an RMAN-specific physical file containing the backed up data. You can also use the BACKUP command to generate a proxy copy, which is a backup to a third-party medium in which the entire data transfer is conducted by a media manager. RMAN offers three modes of encryption: Transparent encryption, in which RMAN can create and restore encrypted backups with no special DBA intervention, as long as the required Oracle key management infrastructure is available. Allows specifying a backup by tag. Backing Up a Database: ExampleThis example assumes that CONFIGURE CONTROLFILE AUTOBACKUP is OFF. The characters used in a tag must be limited to the characters that are legal in filenames on the target filesystem. The backupSpec level, then backup sets created as a result of different backup specifications can have different tags. Excludes datafiles or archived redo logs from the backup according to the criteria specified by the following keywords. The BACKUP command optimizes backups, that is, does not back up files that are identical to files that are already backed up, when the following conditions are met: The CONFIGURE BACKUP OPTIMIZATION ON command has been run. When DURATION is used with MINIMIZE TIME, the file most recently backed up is given the lowest priority to back up. Overrides any configured retention policy for this backup so that the backup is not considered obsolete. (The two types of compression should not be used together; see the discussion of BACKUP AS BACKUPSET below for details on choosing between using RMAN compression and the tape compression for backup sets. If the database is already maintaining block checksums, then this flag has no effect. For example, if DISKRATIO is 4 and the datafiles are located on three disks, then RMAN attempts to include datafiles from three disks in each backup set. Backups to tape can only be backup sets. When backing up to a locally attached tape device, compression provided by the media management vendor is usually preferable to the binary compression provided by BACKUP AS COMPRESSED BACKUPSET. This scheduling mechanism provides for the eventual complete backup of the database during successive backup windows, as different datafiles are backed up in round-robin fashion.

Otherwise, you increase restore time for a file without increasing performance. If the, Deletes the input files upon successful creation of the backup. You can create image copy backups of datafiles, datafile copies, and archived redo log files. In most other circumstances, compressing backupsets saves enough disk space to be worth the CPU overhead. To backup a backupset, use BACKUP BACKUPSET. Each independent step can be executed on any channel allocated for a specific device. You specify a channel of only one device type, that is, you do not mix channels that use different device types. The DISKRATIO parameter is easier for datafile backups when the datafiles are striped or reside on separate disk spindles and you either: Use a high-bandwidth tape drive that requires several datafiles to be multiplexed in order to keep the tape drive streaming. If the instance is started with a server parameter file, then RMAN includes this parameter file in the autobackup piece. RMAN searches for all available backup copies when the copy that it is trying to back up is corrupted or missing. Level 1 incremental backups capture changes since a previous backup. See Also: "archivelogRecordSpecifier" for syntax, and Oracle Database Backup and Recovery Advanced User's Guide explanations of backup failover for logs and automatic log switching. For example, MAXSETSIZE = 3000 is rounded down to 2 KB (2048 bytes). See the reference entries for those commands for more details. For example, if you configure disk and tape channels, then configure, Directs RMAN to populate each backup set with datafiles from at least integer disks. Runs an ALTER SYSTEM ARCHIVE LOG CURRENT statement. If RMAN finds logical corruption, then it logs the block in the, Copies the data blocks used since the most recent backup at level 0 or lower, where, Allocates automatic channels for the specified device type only. Note: If you run BACKUP ARCHIVELOG ALL, or if the specified log range includes logs from prior incarnations, then RMAN backs up logs from prior incarnations to ensure availability of all logs that may be required for recovery through an OPEN RESETLOGS. The percent sign (%) is a wildcard that means zero or more characters; an underscore (_) is a wildcard that means one character. The TABLESPACE keyword is merely a convenience; tablespace names are translated internally into a list of datafiles. Note: The MAXCORRUPT setting specifies the total number of physical and logical corruptions permitted on a file. You must use some non-RMAN backup solution for any files not in the preceding list. Note: 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. Creates backup sets (rather than image copies) on the specified device type. See. The date and time refer to when RMAN started the backup. Level 1 backups can be cumulative, in which case they capture changes since the last level 0 incremental backup, or differential, in which case they capture changes since the last level 0 or level 1 incremental backup. Creates a backup of all blocks of datafiles included in the backup. For example, a DISK device with a block size of 2K can only be used as a destination for backups of Oracle files with logical block sizes of 2K, 4K, 6K and so on.

An image copy is a byte-for-byte identical copy of the original file. Specifies the size of data, such as a file, in kilobytes (K), megabytes (M) or gigabytes (G). You cannot use the DEVICE TYPE option for a device other than DISK if you have not already run CONFIGURE DEVICE TYPE for this device. RMAN performs backup set failover when backing up backup sets. Tags must be 30 characters or less.

Backing Up Backup Sets to Tape: ExampleIn this example, the goal is to keep recent backup sets on disk and older backup sets on tape, and to avoid keeping copies of the same backup set on disk and tape simultaneously. If you specify FOR STANDBY, then RMAN generates a backup of the control file that is usable during creation of a standby database.