About script-based Oracle policies
NetBackup users or automatic schedules can start database backups by specifying a shell script in the file list of the Oracle policy. The shell script specifies the backup commands that RMAN performs on the client.
Note:
All scripts must be stored and run locally. One recommendation is that scripts should not be world-writable. Scripts are not allowed to be run from network or remote locations. Any script that is created and saved in the NetBackup db_ext (UNIX) or dbext (Windows) location needs to be protected during a NetBackup uninstall.
For more information about registering authorized locations and scripts, review the following article:
Registering authorized locations used by a NetBackup database script-based policy
On UNIX, NetBackup for Oracle includes a library of functions that enable RMAN to use NetBackup. You can link to this library.
On Windows, NetBackup for Oracle includes a library of functions that enable RMAN to use NetBackup. This library is in c:\Windows\system32.
When you use the RMAN backup command, each resulting backup set contains at least one backup piece (data file, data file copy, control file, or archive log) from the target database. You must give each backup piece a unique name using the format operand. Several substitution variables are available to aid in generating unique names. You can specify the format operand in the backup command. NetBackup considers the backup piece name as the file being backed up, so this name must be unique in the catalog.
For a backup, the following items apply:
The rman command starts the requested operation on the databases.
When the process requires media to store backup data, RMAN starts a user-directed backup by issuing a backup request.
The NetBackup media server connects to NetBackup for Oracle on the client. NetBackup for Oracle on the client sends the database data to the NetBackup media server which saves the data to secondary storage. A restore works in essentially the same manner except that RMAN issues a restore request. This request causes NetBackup to retrieve the data from secondary storage and send it to NetBackup for Oracle on the client.
RMAN supports parallel operations, so a single rman command can start more than one backup, or restore on the NetBackup system.
The status for an RMAN operation is stored in the RMAN catalog or in the database control file. This same status appears in the output of the RMAN command that is used to run the backup or restore. This status is the only status that a database administrator must check to verify that a backup or restore has been successful.
NetBackup also logs status, but only for its own part of the operation. The database administrator cannot use the NetBackup status to determine whether rman was successful. Errors can occur in rman that do not affect NetBackup and are not recorded in its logs.