Backup Exec Agent Utility Help

Local instance name

Displays the name of the Oracle instance. If you edit an instance, you cannot change the instance name.

For Oracle RAC nodes, enter the fully qualified domain name of each physical node.

The fully qualified domain name of the node appears in the list of servers on the Backup and Restore tab.

The name is in the format RAC-<dbname>-<dbid>, where dbname is the database name, and dbid is the database ID.

User name

Displays the user name for the Oracle instance.

If the credentials for the Oracle instance change, you must enter a user with SYSDBA rights to the Oracle instance.

For Oracle RAC nodes, enter the same set of credentials for all of the nodes.

For an Oracle 12c and later supported database, you must enter a user name that has SYSBACKUP privileges.

Password

Displays the password for the Oracle instance user name.

Confirm password

Displays the password again to confirm it.

Oracle Home User will be granted the permissions to the Backup Exec Logs and Data folders

From Oracle 12c and later supported versions, the Oracle database supports the use of Oracle Home User. This user is a non-admin user; therefore, this user needs access rights to the Backup Exec Logs and Data folders.

Auxiliary instance path for PDB restores

For a point-in-time recovery of a pluggable database (PDB), RMAN first restores the PDB files from the appropriate backup. For the recovery of the PDB, RMAN needs a copy of the undo tablespace of the root container as it was in the specified point in time. To accomplish this recovery task, RMAN creates a temporary auxiliary database that consists of the root container's undo, system, and sysaux tablespaces.

If the database that you want to restore uses a Fast Recovery Area, RMAN creates the auxiliary database files in this area in the <FRA>/<SID>/datafile directory. However, if this area does not have enough space, RMAN displays the following error:

ORA-19809: limit exceeded for recovery files

If the database that you want to restore does not use a Fast Recovery Area, RMAN creates the auxiliary database data files in the location you specify in the Auxiliary instance path for PDB restores field.

The Agent Utility for Windows verifies the auxiliary path you specified. If this path is not available (non-existent), the utility creates an auxiliary path. If you do not specify this path, RMAN assumes that the Fast Recovery Area is configured and has sufficient space.

Agent Utility cannot validate a path specified on the ASM disk and accepts the path as specified. Therefore, you must ensure that the path you entered is correct and accessible.

Use recovery catalog

Indicates that you plan to use the Oracle recovery catalog.

The Oracle Agent supports the use of the RMAN recovery catalog to manage the backup, restore, and recovery of Oracle databases. If you choose not to use a recovery catalog, RMAN uses the source database control file as the sole repository of metadata.

The target for RMAN connection is either a target database (control file) or a recovery catalog. In Oracle 12c and later supported versions, RMAN connects to the container database if recovery catalog is not configured.

TNS name

Displays the Oracle Net Service name.

User name

Displays the user name for the Oracle recovery catalog.

Password

Displays the password for the Oracle recovery catalog.

Confirm password

Displays the password for the recovery catalog again to confirm it.

Backup Exec server name or IP address

Displays the name or IP address of the Backup Exec server where you want to send the DBA-initiated backup jobs.

You must use the same form of name resolution for all operations.

Job template name

Displays the name of the Backup Exec job template that you want the DBA-initiated job to use for backup and restore operations. You create the job template on the DBA-initiated Job Settings dialog box on the Backup Exec server. If you do not specify a job template, the default job template is used.