# RMAN Example: Performing Oracle Full Backups

Backups for any instance start with a full backup. The full backup is the baseline for other backups. For example, a full backup must be performed before an archive log backup can be initiated.

Perform a full backup of an online or offline database. If the database is in NOARCHIVELOG mode, perform an offline backup.

Best Practice: Use separate scripts for data and logs because only one data type can be passed through the argument file. This system uses the data type to mark the archive files created by the backups as DATA or LOG in the CommServe database. If you have scripts containing both data and logs, the archive files are marked as either DATA or LOG, depending on the data type that is defined in the argument file. The drive reservation retry mechanism works more efficiently when you use separate RMAN scripts for data and log backups.

An RMAN full database backup includes all data blocks in the specified file and can also include the control file.

If you do not use the incremental option, the backup is treated as an Oracle full backup and is not used in incremental strategies. If you specify the incremental level=0 command, the backup is used as the base for the incremental level backups.

## Procedure

On the RMAN command line, run the following sample script, substituting any required or optional parameters. For information on required and optional parameters, see Oracle Agentless SBT Parameters for RMAN Jobs.

    RMAN>configure controlfile autobackup on;
    run
    {
    allocate channel ch1 type sbt
    PARMS="SBT_LIBRARY=$[Oracle plugin location]/libcvobk_thinlibrary.so";
    allocate channel ch2 type sbt
    PARMS="SBT_LIBRARY=$[Oracle plugin location]/libcvobk_thinlibrary.so";
    send "--cv-host $[Backup host hostname] --cv-clientname $[Pseudo client name]";
    backup incremental level = 0 format='%d_%u' database plus archivelog delete input;
    }

×

Loading...