The ca_backup command includes the following Oracle RMAN database options:
-use_rmancat
[-rman_catdbname <rman_catdbname>] [-rman_catuser <rman_catuser>] [-rman_catpassword <rman_catpassword>] -bkincremental [-rman_incrementallevel <bkincremental> [-cumulative] [-bkrecoveryarea] [-oracle_offline] [-oracle_purgelog] [-rman_numberofchannels <rman_numberofchannels>] [-rman_archlogsel al_all | al_pattern -rman_alpattern <rman_alpattern> | al_time [-rman_alfromtime <rman_alfromtime>] [rman_aluntiltime <rman_aluntiltime>] | al_scn [-rman_alfromscn <rman_alfromscn>] [-rman_aluntilscn <rman_aluntilscn>] | al_logseq [-rman_alfromlogseq <rman_alfromlogseq>] [rman_aluntillogseq <rman_aluntillogseq>] [-rman_althread <rm_althread>]] [-rman_bakpieceprefix <rman_bakpieceprefix>] [-rman_bakpiecesuffix <rman_bakpiecesuffix>] [-rman_bakpiecesize <rman_bakpiecesize>] [-rman_baksetsize <rman_baksetsize>] [-rman_blocksize <rman_blocksize>] [-rman_readrate <rman_readrate>] [-rman_maxopenfile <rman_maxopenfile>] [-rman_numcopies <rman_numcopies>] [-rman_numfilesperbakset <rman_numfilesperbakset>] [-rman_baktag <rman_baktag>] [-rman_script <rman_script>]
Note: The ca_backup database options are described in a separate topic titled "Database Options" and can be viewed from the actual CLI by entering the following command: ca_backup allusage.
Note: When using the Arcserve Backup CLI (command line interface) to back up or restore an Oracle object with a DBCS (double-byte character set) or a MBCS (multi-byte character set) in the name, you must ensure the Arcserve Backup server and the agent box have the same language setting.
Use a catalog (recommended). Indicates if an RMAN catalog is to be used for the operation or not. It is always recommended to use one because RMAN will use the database control file if no catalog is to be used. The loss of this control file will prevent RMAN from restoring the database.
Default: Checked
This switch is used to include the catalog database name when you attempt to run a Oracle RMAN ca_backup job with a Recovery Catalog Database.
Default: Empty
Name of the Oracle user who owns the RMAN catalog.
Password for the user that owns the RMAN catalog.
This is the alternative value of the Full Backup option. It tells RMAN to send only the blocks of data that have not been backed up since the last backup made, depending on the Incremental Level and Cumulative options described below. It is represented by a radio button in the Backup Manager and is not selected by default. Of course, Incremental Backup cannot be selected with Full Backup. It cannot be used if the Oracle object to be backed up is the control file or the archived logs.
Use this option to specify the level of incremental backup to be performed. RMAN will only back up the data blocks that have changed since the last incremental backup of the specified level or less. The valid values for this field vary between 0 and 4, for Oracle 8, 8i and 9i. With Oracle 10g, the levels are limited to 0 and 1 only. The user can enter data in this field only if the Incremental Backup option was selected.
Default: 0 (full backup)
This option indicates that RMAN will send data blocks that have been used since the last incremental backup made at level n-1 or lower. This is represented by a check box in the Backup Manager.
Default: Unchecked
This switch is used to include the Oracle Recovery Area in the list of objects to be backed up. Applies only to Oracle 10g or later.
Default: Unchecked
Oracle database backup specific. Back up the Oracle database in off-line mode (no tablespace backup).
Oracle database backup specific. Purge the log after it has been backed up.
Use this option to specify how many channels to be allocated by RMAN to perform the backup operation. RMAN will submit jobs in parallel, one for each channel.
Default: 1 channel
The “Archived Logs Selection” section of this panel allows the user to select which archived logs will be backed up, assuming that the “archived logs” object has been included in the Source panel of the Backup Manager GUI. The selection is represented by radio button options. All indicates that all archived logs will be backed up.
Default: All
String pattern used to select the archived logs based on their name.
Use this option to indicate that the archived logs to be backed up will be selected based on the time they were created. This field determines the lower time boundary for the archived logs selection. Only the archived logs created after this time will be backed up.
Use this option to indicate that the archived logs to be backed up will be selected based on the time they were created. This field determines the upper time boundary for the archived logs selection. Only the archived logs created before this time will be backed up.
Use this option to indicate that the range of the archived logs to be backed up is not determined by the time, rather by the SCN (System Change Number). This field indicates the lowest SCN boundary for the archived logs selection. It can be left empty, assuming that the Until SCN field is not.
Use this option to indicate that the range of the archived logs to be backed up is not determined by the time, rather by the SCN (System Change Number). This field is used to determine the upper SCN boundary to the archived logs selection. It is optional, as long as the user has entered a value for the From SCN field.
Use this option to specify that archived logs selection is to be based on the archived log sequence number. This field corresponds to the lowest log sequence number used to determine which archived logs will be backed up. This field can be left empty only if a value is provided for the Until Log Sequence option (-rman_aluntillogseq).
Use this option to indicate that the archived logs selection is to be based on the archived log sequence number. This field is used to enter the upper archived log sequence number boundary for the archived logs selection. Providing a value for this field is optional, as long as the user enters a value in the From Log Sequence field.
Use this option to specify the thread number used to identify the Oracle server that generated the archived logs. This parameter is only used with the Time Based, SCN Based or Log Sequence Based options described below. It will be ignored if the All or Pattern Based option is used.
Default: 1
Note: This value is only useful for OPS (Oracle Parallel Server, for Oracle 8 and 8i) or RAC (Real Application Clusters, for Oracle 9i and 10g), otherwise the thread number is always one.
Left part (or prefix) of the Backup Piece Format entry.
Right part (or suffix) of the Backup Piece Format entry.
Use this option to limit the size of a backup piece generated by RMAN. When this option is set, if the data blocks to be backed up do not fit into a single backup piece, then RMAN will generate as many backup pieces as required to contain all the data. By default, the field should be empty. This means that RMAN will typically put the data from one backup command (for one channel) into a single backup piece.
Default: Empty
Use this option to limit how much data should go into a backup set. This command determines the maximum size in KBytes that a backup set can have.
Default: Empty
Use this option to specify a value that determines the size of the data blocks that RMAN will send to the Oracle agent when performing a backup. This field should be left empty by default. If the user enters a value for it, then the same block size must also be entered by the user when he wants to restore from this backup. Otherwise, RMAN will produce an error message indicating that there is a mismatch between the backup block size and the restore one. In that case, the value used during the backup will be put in the error message. If no value is provided, then RMAN uses 64 KB for Oracle 8 or 8i and 256 KB for Oracle 9i.
This parameter does not exist anymore with Oracle 10g.
Default: Empty
This is a performance tuning option. You can use this option to slow down the rate at which RMAN reads data from the hard disk to avoid contention. By default, it is empty, however if you want to set this option, the value represents the maximum number of buffers per second that RMAN can use to read data from the disk. The size of a buffer corresponds to the value DB_BLOCKSIZE * DB_FILE_DIRECT_IO_COUNT which are parameters defined in the Oracle database configuration.
Default: Empty
Use this option to limit the total number of files that RMAN will open at the same time. This command lets you decrease the potential for a “too many open files” error. Leaving the field empty will make RMAN use the default value.
Default: 8 files (for Oracle 10g)
Default: 32 files (for Oracle 8, 8i and 9i)
Use this option to specify how many copies of the backup pieces will be generated by RMAN. The valid values for this parameter are 1 to 4.
Oracle 8.0 does not support this parameter.
Default: 1 copy
Use this option to limit the number of files (backup pieces) that RMAN should put per backup set. If not specified, then RMAN will use the lesser values of these two: 64 or the number of input files divided by the number of channels.
Default: Empty
Use this option to enter a backup identifier called a 'tag'. This tag can then be used to identify which version of the Oracle objects should be used by RMAN during a restore operation.
Use this option to enter the path of an RMAN script. Providing a value for this field will cause the Oracle agent to ignore all other options that might have been entered by the user in the GUI. The script will be passed as is to RMAN and the Oracle agent will perform the backup operation normally.
|
Copyright © 2016
|
|