RMAN can store the backup in one or more binary files called a backup set that contain data from one ore more data files, archive logs, control files or an SPFILE. This example shows a snapshot location that is determined by the default rule: This example shows a snapshot control file that has a nondefault filename: Use the CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'filename' command to change the name of the snapshot control file. See the post Setting up RMAN for backup and recovery using Database Control if you would prefer to perform these steps using the Database Control. On Solaris, for example, the default is: ?/dbs. I have gained wide knowledge on Oracle and Non-Oracle software stack running on-prem and on Cloud and have worked on several big projects for multi-national companies. In contrast, you must reissue the SET NEWNAME command every time you rename files. The exclusion condition applies to any datafiles that you add to this tablespace in the future. Configure specific channels by number when it is necessary to control the parameters set for each channel separately. If you set the PARALLELISM for a device, and then make the device default, then RMAN uses the generic configured channel settings for each parallelized channel. Login to the sqlprompt and login as sysdba user. CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT /rman/bkup_%U; In such a case, RMAN creates backup pieces and image copies in the flash recovery area, with names in Oracle Managed Files name format. Your page can go viral. ii)CONFIGURE BACKUP OPTIMIZATION OFF; # default. We have to meet below requirements for our database: Database to backup: BRIJ DATAFILE BACKUP COPIES The following examples show possible configurations: If you use the duplexing feature in conjunction with multiple FORMAT strings, then you can name each individual backup set copy. By default it is disbaled. This configuration is enough to get you started in exploring backup and recovery with RMAN. RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; REQUIRMENT 4 Control File is to be automatically backed up every time a back up is taken. Otherwise, it uses the generic configuration for channels for that device type, as specified by the CONFIGURE CHANNEL command without a channel number. You could copy and paste one of those lines in an RMAN prompt. CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default The difference is that after you set the AUXNAME the first time, you do not need to reset the filename when you issue another DUPLICATE command: the AUXNAME setting remains in effect until you issue CONFIGURE AUXNAME CLEAR.
CONFIGURE CONTROLFILE AUTOBACKUP ON; RMAN can create control file autobackups in the flash recovery area. RMAN> configure device type disk PARALLELISM 1 backup type to compressed backupset; Run Show All command again to check the changed RMAN configuration. Use the following steps to confirm that RMAN is able to load the media management library when allocating a channel for your media manager. CONFIGURE BACKUP OPTIMIZATION OFF; # default If you do not set any value for LOG_ARCHIVE_DEST, LOG_ARCHIVE_DEST_n, or DB_RECOVERY_FILE_DEST, then the redo logs are archived to a default location that is platform-specific. The output below is from the database configured in this document. The following procedure illustrates only one method. RMAN> configure controlfile autobackup format for device type disk to /backups/brij/controlfile_brij_%F; REQUIRMENT 6 backups should be made using backup sets. Now all RMAN backups will be made in the /backups/brij directory, even if youve configured a flash recovery area and there is plenty of free space in it. Each individual file in a back set is called a backup piece. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO /rman/controlfile/ctl_%F; xiii) CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default.
We can test this out with a simple backup. Then enter: Issue the SHOW DEVICE TYPE command to display the configured devices and their PARALLELISM and backup type settings. This CONFIGURE setting applies to any channel, whether manually allocated or configured, when the BACKUP command is used to create backup sets. new RMAN configuration parameters are successfully stored new RMAN configuration parameters are successfully stored. The assumption in all cases is that a flash recovery area has already been configured for your database. If you havent enabled a flashback area, RMAN will create the autobackups in an operating systemspecific location ($ORACLE_HOME/dbs on Unix), vi)CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default. After you have confirmed that the database server can load the media management library, test to make sure that RMAN can back up to the media manager. The value 1244946728 is the database ID, 20100601 is the date and 00 is the sequence number in hexadecimal. Only If you have enabled the Oracle Database 11g Release 2 Advanced Compression Option, you can set it to HIGH, MEDIUM & LOW. However, for production jobsinvolving sophisticated backup strategies, you need to customize RMANs configuration settings to fulfill all your requirement. CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default Whenever channel allocation fails, the database writes a trace file to the USER_DUMP_DEST directory. I am very new to RMAN and configured the RMAN backup against the guidelines posted with your thread. A media manager is not an Oracle product and must be obtained from a third-party vendor. The conflict is usually caused when two jobs are both backing up the control file, and the job that first starts backing up the control file waits for service from the media manager. This command allocates three channels for jobs on device type DISK : These commands back up to a media manager using two tape drives in parallel: Each configured sbt channel will back up roughly half the total data. Subsequent snapshot control files that RMAN creates use the specified filename. #######################################. { RMAN does not change the PARALLELISM setting for the device type because PARALLELISM is specified through a separate CONFIGURE command. CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default This deletion policy applies to all archiving destinations, including the flash recovery area. For example, assume that you run the following: In this case, RMAN clears the settings for CHANNEL 3, but leaves the settings for the generic DISK channel (the channel with no number manually assigned) intact. Configuring persistent channel settings greatly simplifies the use of RMAN. For an overview of configured channels and how they are used, refer to the section "Configuring Channels". Search for: Mertisos tips go viral, Your email address will not be published. With the Partitioning, Automatic Storage Management, OLAP, Data Mining Once you make it ON, RMAN will automatically back up your target database control file, as well as the current server parameter file, during any following events occurs: Successful completion of backup/copy command Oracle Database Backup and Recovery Reference for ALLOCATE CHANNEL syntax, Oracle Database Backup and Recovery Reference for channel control options. Backup optimization skips the backup of files in certain circumstances if the identical file or an identical version of the file has already been backed up. RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 2; REQUIRMENT 3 Use Disk for keeping the backup pieces CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters: The configured settings are stored in the RMAN repository.
There are other substitution variables that can be used in place or in conjunction with the %U see the documentation Oracle Database Backup and Recovery Reference for a complete list. This section describes the generic steps for configuring RMAN for use with a media manager. This error indicates that the media management software is not correctly configured. I enjoy working with leading-edge technology and have a passion for Cloud architecture, automation, database performance, and stability. After connecting to the target database and recovery catalog (if you use one), run the SHOW EXCLUDE command. It is sometimes required that the location and name of the snapshot control file be changed from its default. Save my name, email, and website in this browser for the next time I comment.
The log member filenames are automatically generated by the database. xi) CONFIGURE ENCRYPTION ALGORITHM AES128; # default. The CONFIGURE CHANNEL DEVICE TYPE CLEAR command erases the channel configuration for the specified device type. CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default To limit backup piece sizes, use the parameter MAXPIECESIZE, which you can set in the CONFIGURE CHANNEL and ALLOCATE CHANNEL commands. Some media managers have limits on the maximum size of files that they can back up or restore. CONFIGURE BACKUP OPTIMIZATION OFF; # default iii)CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default. 5. CONFIGURE MAXSETSIZE TO UNLIMITED; In the configuration enter all parameters that you tested in the section "Testing a Backup to the Media Manager". The default value is given in bytes and is rounded down to the lowest kilobyte value. For example, you can run: By default, backup optimization is configured to OFF. To take maximum advantage of the flash recovery area, it should be used to store and manage as many different types of file as possible: online redo logs, archived redo logs, control files and RMAN's own working files for backup and restore operations. CONFIGURE MAXSETSIZE TO UNLIMITED; # default This document will detail a quick set up of RMAN for disk based backups using Oracle Database 11gR2 base. If you are using a raw partition to store a 10GB datafile, and your operating system only supports 4GB files on the file system, you cannot take image copy backups of that file. Then, obtain and install the third-party media management module for integration with the database server. Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 64bit Production In general, you should only need to set the snapshot control file location when you are upgrading to the current release from a release earlier than 8.1.7. ARCHIVELOG BACKUP COPIES For example, to test whether your backup goes successfully to tape, you might run the following command: The specifics of your PARMS and FORMAT settings depend on the media management software that you are using. The PARALLELISM setting is not constrained by the number of specifically configured channels. By default, RMAN allocates a one DISK channel with default options, and uses it for backup commands. Also, if you use a media manger, you must configure any required options for it, such as PARMS, FORMAT, MAXPIECESIZE, and so forth. LOW: Least effect on backup throughput. For example, enter: Sample output for SHOW MAXSETSIZE follows: Run the CONFIGURE command to enable and disable backup optimization. To direct the restored archived redo logs to the flash recovery area, set one of the LOG_ARCHIVE_DEST_n parameters to 'LOCATION=USE_DB_RECOVERY_FILE_DEST", and make sure you are not using SET ARCHIVELOG DESTINATION to direct restored archived logs to some other destination. A hanging backup usually indicates that the media manager is waiting to mount a tape. Copyright (c) 1982, 2011, Oracle. 1. 4. 3. Copyright (c) 1982, 2011, Oracle and/or its affiliates. CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default After connecting to the target database and recovery catalog (if you use one), issue the SHOW MAXSETSIZE command. The CONFIGURE MAXSETSIZE command limits the size of backup sets created on a channel. connected to target database: PRODDB (DBID=588708646), starting full resync of recovery catalog EXIT; You should keep it ON and specially it is highly recommended to enable the control file autobackup feature ON if you arent using a recovery catalog. In order for RMAN to read or write data it must have a channel configured. RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON; REQUIRMENT 5 Control file backups are to be stored on disk in the /backups/brij directory. Assume that you want to back up to your media manager using two tape drives in parallel. CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default Contact your media management vendor for details. You can always override configured channels with ALLOCATE CHANNEL for a particular backup job surrounded by a RUN block. Before you can begin using RMAN with a media manager, you must install it and make sure that RMAN can communicate with it. When you are testing it on your personal system, you probably can get by with RMANs default configuration settings. Besides configuring a generic channel for a device, you can also configure one or more specific channels for each device type by manually assigning your own channel numbers to the channels. new RMAN configuration parameters:
It means that by default RMAN doesnt make multiple copies of a backup file. CONFIGURE MAXSETSIZE TO UNLIMITED; # default Note that if you have a flash recovery area configured, the default location for the snapshot control file is not the flash recovery area. CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE ENCRYPTION ALGORITHM AES128; # default CONFIGURE ENCRYPTION ALGORITHM AES128; # default To show the default device type and currently configured settings for disk and sbt devices: After connecting to the target database and recovery catalog (if you use one), run the SHOW DEVICE TYPE command. CONFIGURE ENCRYPTION ALGORITHM AES128; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default Assume that you issue the following commands at the RMAN prompt: The backup of the users tablespace uses the configured sbt channel and the configured default MAXSETSIZE setting of 7500K. Oracle Multitenant DB 4 : Parameters/SGA/PGA management in CDB-PDB, Oracle Multitenant DB 3 : Data Dictionary Architecture in CDB-PDB, Oracle Multitenant DB 2 : Benefits of the Multitenant Architecture, Physical and Logical Block Corruption in Oracle Database, RMAN: GRANTING RESTRICTED ACCESS USING VIRTUAL PRIVATE CATALOG, Configure Parallel Concurrent Processing (PCP) in EBS R12, RMAN: RECOVERY SCENARIOS RELATED TO DATABASE, RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process. You need initial traffic boost only. You can use SHOW BACKUP OPTIMIZATION to view the current settings of backup optimization as configured with the CONFIGURE BACKUP OPTIMIZATION command. If you do not provide a value for this parameter, RMAN looks in a platform-specific default location. The initialization parameters CONTROL_FILES, DB_CREATE_ONLINE_LOG_DEST_n, DB_RECOVERY_FILE_DEST, and DB_CREATE_FILE_DEST all interact to determine the location where the database control files are created. RMAN configuration parameters for database with db_unique_name PRODDB are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default, CONFIGURE BACKUP OPTIMIZATION OFF; # default, CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default, CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default, CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO %F; # default, CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default, CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default, CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default, CONFIGURE MAXSETSIZE TO UNLIMITED; # default, CONFIGURE ENCRYPTION FOR DATABASE OFF; # default, CONFIGURE ENCRYPTION ALGORITHM AES128; # default, CONFIGURE COMPRESSION ALGORITHM BASIC AS OF RELEASE DEFAULT OPTIMIZE FOR LOAD TRUE ; # default, CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default, CONFIGURE SNAPSHOT CONTROLFILE NAME TO /oracle/product/11.2.0.3/db_1/dbs/snapcf_proddb.f; # default, RMAN> configure backup optimization on; 1 AES128 AES 128-bit key YES See Chapter 8, "RMAN Tablespace Point-in-Time Recovery (TSPITR)" for more details on using CONFIGURE AUXNAME in connection with TSPITR, and Chapter 13, "Creating and Updating Duplicate Databases with RMAN" for more on using CONFIGURE AUXNAME in performing database duplication. On Windows the default library location is %ORACLE_HOME%\bin\orasbt.dll. To ensure that RMAN does not connect to a dispatcher when the target database is configured for a shared server, the net service name used by RMAN must include (SERVER=DEDICATED) in the CONNECT_DATA attribute of the connect string. new RMAN configuration parameters are successfully stored CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 2 G; If you do not specify the FORMAT parameter, then RMAN automatically generates a unique filename with the %U substitution variable. For example, enter: When performing tablespace point-in-time recovery (TSPITR) or duplicating a database using RMAN, you may want to set the names of datafiles in the auxiliary instance before startingthe actual TSPITR or database duplication. Issue the SHOW SNAPSHOT CONTROLFILE command to display the value set by CONFIGURE SNAPSHOT CONTROLFILE NAME. You may need to manage the naming of backup pieces to be written to the media manager, so that backup pieces have unique names. REQUIRMENT 8 Each backup set piece size should be 2GB or smaller, RMAN>CONFIGURE CHANNEL DEVICE TYPE disk MAXPIECESIZE 2G, REQUIRMENT 9 backups should be in compressed format in order to save storage space. Configuring parallelism for a device type specifies the number of server sessions to be used for I/O to that device type. Whatever archiving scheme you choose, it is always advisable to create multiple copies of archived logs. CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default If you want to use the flash recovery area, you cannot use the LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST initialization parameters. HIGH: Best suited for backups over slower networks where the limiting factor is network speed. For example, CONFIGURE DEVICE TYPE CLEAR does not clear CONFIGURE DEFAULT DEVICE TYPE. Privileges, Roles and Users in Oracle Enterprise Manager 11gR1 Grid Control, Data Guard Standby Archive Destination Full, Setting up RMAN for backup and recovery using Database Control, Oracle Database Backup and Recovery Reference. 8) Each backup set piece size should be 2GB or smaller, 9) Backups should be in compressed format in order to save storage space, The show all command displays both settings that you have configured and any default settings. You can configure different backup retention policies, for example, for different databases. Any structural changes (adding/dropping tablespace/datafiles etc) to the database that modify the contents of the control file. When discussing how long to keep a backup we are talking about a retention policy. CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default It is by no means intended to be an exhaustive introduction to RMAN nor should what is presented be used for production based backup configuration. BACKUP COPIES command to set the number of identical copies that RMAN makes of each of several types of backup. The backup of the tools tablespace uses the MAXSETSIZE setting of 5G used in the BACKUP command. You can override the configured MAXSETSIZE value by specifying a MAXSETSIZE option for an individual BACKUP command. BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default The control file is to be automatically backed up every time a back up is taken and when the structure of the database changes in manner that would require a new backup of the control file. By default the default device type is disk and RMAN is configured to write backup sets to disk. Use the CONFIGURE CHANNEL command to configure options for DISK and sbt channels. CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default document.getElementById( "ak_js_2" ).setAttribute( "value", ( new Date() ).getTime() ); 2022 ORACLE-SCN. Note that you can specify the FORMAT string on the BACKUP, CONFIGURE CHANNEL, and ALLOCATE CHANNEL commands. Specifying the snapshot controlfile format (File name and location): For example, you can enter one of the following commands: You can disable the exclusion feature for cwmlite and example as follows: RMAN includes these tablespaces in future whole database backups. CONFIGURE ENCRYPTION FOR DATABASE OFF; # default Disk device, disk is the default device type for all automatic channels. CONFIGURE SNAPSHOT CONTROLFILE NAME TO /u01/oracle/DB11G/product/11.2.0/dbhome_1/dbs/snapcf_brij.f; # default. #, ############################################################ If you configure settings for a specific channel using CONFIGURE CHANNEL with a channel number, RMAN uses those specified configured settings. SHOW EXCLUDE shows how you have used the CONFIGURE EXCLUDE command to exclude tablespaces from whole database backups. CONFIGURE CHANNEL takes the same options used to specify one-time options with ALLOCATE CHANNEL. This chapter describes how to perform setup and configuration tasks. Thankfully my work allows me time for researching new technologies (and to write about them). # 0-59 0-23 1-31 1-12 0-6 (0=Sunday) Using RMAN you can choose a recovery window (have a rolling window of days), or a set redundancy (rolling number of backups). The commands are: Do not specify a FORMAT option to the BACKUP command, and do not configure a FORMAT option for disk backups. To show the default device type for backups: After connecting to the target database and recovery catalog (if you use one), run the SHOW DEFAULT DEVICE TYPE command. full resync complete. RMAN> configure CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO /rman/controlfile/ctl_%F; RMAN> configure channel device type disk format /rman/bkup_%U; new RMAN configuration parameters: Ensure that the steps in, Create a new database in the current release. The backups should be made using backup sets and stored on disk. It means that by default RMAN wont skip the backing up of unchanged data blocks in the datafiles OR in other words, It will NOT allow Oracle to skip backups of files that already have identical backups on the device being backed up to. If DB_RECOVERY_FILE_DEST is specified (that is, if a flash recovery area is configured) and no LOG_ARCHIVE_DEST_n is specified, then LOG_ARCHIVE_DEST_10 is implicitly set to the flash recovery area. From the above output show all command we can clearly see that there was no changes reflected in the configuration. starting full resync of recovery catalog full resync complete, new RMAN configuration parameters: The CONFIGURE DEVICE TYPE CLEAR command removes the configuration for the specified device type and returns it to the default (PARALLELISM 1). Read the following sections in order when configuring the media manager: Prerequisites for Using a Media Manager with RMAN, Locating the Media Management Library: The SBT_LIBRARY Parameter, Testing Whether the Media Manager Library Is Integrated Correctly, Configuring SBT Channels for Use with a Media Manager. It is generally a third-party product which must be purchased separately. CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
and Real Application Testing options. These image copies are not created in an RMAN specific format. RMAN needs a snapshot control file only when resynchronizing with the recovery catalog or when making a backup of the current control file. By default, RMAN has preconfigured a disk channel so that you can back up to disk without doing any manual configuration. CONFIGURE CONTROLFILE AUTOBACKUP ON; For example we will copy the configure line for BACKUP OPTIMIZATION.
By default, RMAN uses the AES 128-bit key algorithm for encryption. Like the CONTROLFILE AUTOBACKUP FORMAT, the CHANNEL FORMAT has a substitution variable %U. RMAN configuration parameters for database with db_unique_name BRIJ are: After connecting to the target database and recovery catalog (if you use one), run the SHOW ARCHIVELOG BACKUP COPIES or SHOW DATAFILE BACKUP COPIES commands. Note that you cannot disable the default device type: it is always either DISK (default setting) or sbt. For example, you can exclude testing tablespaces cwmlite and example from whole database backups as follows: If you run the following command, then RMAN backs up all tablespaces in the database except cwmlite and example: You can still back up the configured tablespaces by explicitly specifying them in a BACKUP command or by specifying the NOEXCLUDE option on a BACKUP DATABASE command. The following shows sample output: Your operating system specific database documentation and the documentation supplied by your media vendor for instructions on how to achieve media manager integration on your platform, "After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario" for troubleshooting scenarios involving media manager problems.
If you set the maximum set size to 2049, then RMAN rounds down this value to 2 kilobytes (2048 bytes). CONFIGURE BACKUP OPTIMIZATION OFF; # default For example, assume that the default device type is configured to sbt, and you execute this command: In this case, RMAN uses only the disk channel that you manually allocated within the RUN block, overriding any defaults set by using CONFIGURE DEVICE TYPE, CONFIGURE DEFAULT DEVICE, or CONFIGURE CHANNEL settings. This module contains the media management library that the Oracle database loads and uses when accessing the media manager. CONFIGURE BACKUP OPTIMIZATION ON; In this case, you can run the following commands: You can configure persistent settings for your channels, such as channel parameters, parallelism, and the default device type for backups. CONFIGURE MAXSETSIZE TO UNLIMITED; # default Oracle Database Backup and Recovery Basics, "After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario", Oracle Database Backup and Recovery Reference, "Locating the Media Management Library: The SBT_LIBRARY Parameter", "Configuring RMAN to Make Backups to a Media Manager", "Configuring Channel Settings for a Device Type", "Determining Channel Parallelism to Match Hardware Devices", Oracle Database Backup and Recovery Reference', "Automatic Channel-Specific Configurations", "Configuring Specific Channels: Examples", "Backing Up Files Using Backup Optimization", Chapter 8, "RMAN Tablespace Point-in-Time Recovery (TSPITR)", Chapter 13, "Creating and Updating Duplicate Databases with RMAN", "Backup Fails Because of Control File Enqueue: Scenario", Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide, "Setting the Snapshot Control File Location". BACKUP COPIES, Configuring Tablespaces for Exclusion from Whole Database Backups, Setting the Snapshot Control File Location, Setting Up RMAN for Use with a Shared Server. } CONFIGURE COMPRESSION ALGORITHM BASIC AS OF RELEASE DEFAULT OPTIMIZE FOR LOAD TRUE ; # default Notify me of follow-up comments by email. "About RMAN Channels" to learn about configured and allocated channels, Oracle Database Backup and Recovery Reference for ALLOCATE syntax, Oracle Database Backup and Recovery Reference' for CONFIGURE syntax. By specifying the default, OPTIMIZE FOR LOAD TRUE, you ensure that RMAN optimizes CPU usage and avoids pre-compression block processing. 
By default the RMAN configuration is stored in the control file. Then, determine which PARMS settings are needed for the ALLOCATE CHANNEL or CONFIGURE CHANNEL commands as well as the recommended FORMAT string for the BACKUP command (if needed).