OFFLOAD
The OFFLOAD section of the profile configuration
contains information that is related to IBM® Storage Protect
backups from a snapshot.
File names that are specified in the offload section typically point to files that are on a backup server. The offload section is optional for Oracle. The parameters do not depend on the storage device.
- BACKUP_METHOD
- This parameter is preset during the configuration, and is set to ORACLE.
- Default
- Oracle.
- Advanced mode only
- Yes.
OFFLOAD Oracle parameters
- OVERWRITE_DATABASE_PARAMETER_FILE
- This parameter specifies whether the database configuration file on the backup server is
overwritten with the file from the production server. The database configuration file on the backup
server is used to mount the database so that it can be offloaded to IBM Storage Protect. Specify one of the following values:
- YES
- Automatically copies the database configuration file to the backup system with the version that is defined on the production system.
- NO
- Do not copy the production system database configuration file to the backup system.
If the production database is configured to use a text-based Oracle parameter file (PFILE), this setting requires that the default database configuration file <$ORACLE_HOME>/dbs/init<$ORACLE_SID>.ora is available and valid on the backup system. If the name of the database configuration file on the production database is not the default file name, <$ORACLE_HOME>/dbs/init<$ORACLE_SID>.ora, use the TARGET_DATABASE_PARAMETER_FILE parameter, in the ORACLE section, to specify the correct name of the configuration file. If the production database is configured to use a binary Oracle SPFILE, this setting requires that the database configuration file <Oracle_instance_owner_$HOME_directory>/acs/tempfiles/init<$ORACLE_SID>.ora_fromSPfile is available and valid on the backup system. If you need a modified version of the SPFILE from the production system, set OVERWRITE_DATABASE_PARAMETER_FILE YES to create this file automatically with a first backup and offload, then switch OVERWRITE_DATABASE_PARAMETER_FILE NO and modify this file for subsequent backups and offloads.
- Default
- YES
- Advanced mode only
- Yes.
- DATABASE_BACKUP_INCREMENTAL_LEVEL
- This parameter specifies the level of backup. Any numerical value can be entered. The following
conditions apply:
- To complete a full backup, use option 0. A full backup must be completed before an incremental backup can be run.
- To complete an incremental backup, enter a numerical value greater than 0. Incremental backups are progressive. For example, a level 0 backup must complete before a level 1 backup can start. A level 1 backup must be complete before a level 2 backup can occur.
- Default
- 0
- Advanced mode only
- No.
- ASM_INSTANCE_USER
- This parameter is used for the backup server. If this parameter is not specified for the
OFFLOADsection, the value of this parameter, as specified in theORACLEsection, is used for the backup server.- user name
- Specify the user name of the ASM instance owner. Use this parameter when the target database and the ASM instance are running under different user IDs. The ASM instance has one of the following permissions: sysdba, sysasm, or sysadm.
- AUTO
- When this parameter is set to AUTO, the database user who is running the process is used.
- Default
- There is no default value.
- Advanced mode only
- Yes.
- ASM_INSTANCE_ID
- This parameter specifies the SID of the ASM instance. This parameter is used for the backup
server. If this parameter is not specified for the
OFFLOADsection, the value of this parameter, as specified in theORACLEsection, is used for the backup server.You can have a SID for the ASM instance other than +ASM. In this scenario, this profile parameter specifies the ASM instance SID.
- Default
- 0
- Advanced mode only
- Yes.
- ASM_ROLE
- Specify the role that is used when you are connecting to the ASM instance. When you use Oracle
11g, specify the sysasm role.
- Default
- 0
- Advanced mode only
- Yes.