Dell Avamar for Oracle 19.10 User Guide

PDF

Backup options

Backup plug-in options enable you to control backup functionality that is specific to the Avamar Plug-in for Oracle. You can specify plug-in options for on-demand and scheduled backups.

The following table lists options that are available for the Avamar Plug-in for Oracle when you perform an on-demand backup or when you configure dataset for scheduled backups.

Table 1. Backup plug-in optionsThe following table displays the backup plug-in options.
Option	Description
Oracle Instance Name	Leave this field blank. The Avamar Plug-in for Oracle determines the Oracle instance name when you browse and select a target to back up.
Username	Specifies the username that is used to authenticate the Oracle database. Username and password consist of a connection string to Oracle. The connection string must specify a user that has backup privileges for the database. If left blank, RMAN tries to log in with the same username and password that the Avamar client agent uses and attempts to assume SYSDBA (or SYSBACKUP) privileges. Typically, this field should contain the special account name (backup user). Creating the Oracle user account provides more information.
Password	Specifies the password for the username account.
Number of RMAN Channels	Specifies the number of channels to allocate during a backup or restore. The maximum number is 10. The default is 1. This option impacts the number of streams that Data Domain systems use. The formula that determines the number of streams is: NUMBER OF RMAN CHANNELS x NUMBER OF DATA DOMAIN STREAMS. NOTE:The number of Data Domain streams is set when you add a Data Domain system to the Avamar configuration. NOTE:Allocating multiple channels for backups and restores can improve performance. Performance improvements for backups and restores, however, depend on the Oracle server configuration. In some instances, allocating too many channels can lock out processes, which can result in a time-out error. This problem does not occur when using RMAN scripts.
Back up database	Backs up the Oracle database. You can use this option by itself or with the Backup archive logs option.
Back up archive logs	Backs up Oracle archive logs. You can use this option by itself or with the Back up database option. NOTE:The backup process does not use Incremental Backup options if you select only the Back up archive logs option.
Delete archive logs after backup	Automatically deletes Oracle archive logs after a successful database backup.
Media Management Library Bitwidth	Specifies Media Management Library (MML) bitwidth. Select an option: Automatic (default) 32-bit 64-bit If the application bitness and OS bitness are not the same, select the appropriate setting from the Media Management Library Bitwidth list. If the application bitness and OS bitness are the same, leave the Media Management Library Bitwidth set to Automatic. NOTE:The Media Management Library Bitwidth option is available for Linux and UNIX Oracle RMAN plug-ins. This option does not apply to Windows platforms.
Exit a multiple target backup when any one backup fails	Prevents a multiple target backup from continuing after one of the backups fails.
Enable debugging messages (advanced option)	Writes maximum information to log files. Use with caution.
NLS_DATE_FORMAT (advanced option)	Specifies a valid timestamp format for the target machine. For example: `mm`/`dd`/`yyyy`.
Enhanced Data Deduplication (advanced option)	Enables or disables data compression. During backups, enhanced data deduplication can reduce the amount of client data that is sent to the server, but might require additional client CPU resources. Select an option: To back up the data files without using compression, select Default. To use the global data compression setting that is already set on the server, select Default. This is the default setting. To use enhanced data deduplication for the backup, select Enabled.
Full backup	Backs up all data files. You can optionally choose to backup the archive logs during a Level 0 (incremental) backup or later. Full backups do not use the Block Change Tracking option. This option is the default.
Level 0 backup	Performs a level 0 backup. Level 0 backups back up all data files. You must perform a level 0 backup before you perform a level 1 backup.
Level 1 differential backup	Backs up all database blocks that have changed since the most recent level 1 or level 0 backup. You must perform a level 0 backup before you perform a level 1 backup. Selecting the Level 1 backup option before you create a level 0 backup results in a level 0 backup.
Level 1 cumulative backup	Backs up all database blocks that have changed since the most recent level 0 backup.
Use recovery catalog	Select this option to use the values in the Recovery Catalog Server Name, Recovery Catalog Username, and Recovery Catalog Password fields to form a recovery catalog server connection string for RMAN. Using a recovery catalog server enables you to use specialized features of RMAN. A thorough discussion of these features is beyond the scope of this guide. The Oracle documentation provides more information.
Recovery Catalog Server Name	Specifies the recovery catalog server name.
Recovery Catalog Username	Specifies the recovery catalog username.
Recovery Catalog Password	Specifies the recovery catalog password.
Run user-defined script at beginning of backup (advanced option)	Specifies the name of a script that runs at the beginning of the backup. The preprocessing script must be in the /avamar/etc/scripts directory on the client.
Exit backup if script fails (advanced option)	Stops processing the script when the script returns a non-zero status code.
Run user-defined script at end of backup (advanced option)	Specifies the name of a script that runs at the end the backup. The postprocessing script must be in the /avamar/etc/scripts directory on the client.
Exit process with script failure exitcode (advanced option)	Exits the script with an exitcode from the script rather than with the standard avoracle exitcode.
Filesperset	Specifies the number of files that RMAN can include in each backup set. The default is 1.
Store backup on Data Domain system	Backs up the data to the Data Domain system rather than to the Avamar server. Select the checkbox, and then choose a Data Domain system from the list.
Encryption method to Data Domain system	Specifies the encryption method for data transfer between the client and the Data Domain system during the backup.
Show Advanced Options	Displays advanced options.
SECTION SIZE	Directs the RMAN to create a backup set where each backup piece contains the blocks from one file section. A file section is a continuous range of blocks in a file. This type of backup is called a multisection backup. The section size RMAN parameter allows the backup of the large files to be parallelized across multiple RMAN channels. If you specify a section size that is larger than the size of the Oracle datafile, then the RMAN does not use multisection backups.
MAXOPENFILES	Defines the number of files that the RMAN can read and write simultaneously in each backup piece per channel.
MAXPIECESIZE	Defines the maximum size of a backup piece.
MAXSETSIZE	Defines the maximum size of a backup set.
FORMAT	Allows you to customize the backup file names. The default value for the format is %d_%U.
TAG	Attaches a tag as an identifier for every backup that it creates. This tag helps in identifying that the backup can be used with RMAN commands.
SKIP OFFLINE	Skips the offline datafiles. Some offline datafiles can still be read as they exist on the disk. The datafiles that have been deleted or moved cannot be read, making them inaccessible.
SKIP READONLY	Skips the datafiles that are in read-only tablespaces.
SKIP INACCESSIBLE	Skips the datafiles that RMAN cannot read.