User's Manual

2.17
Recovery Manager and Third-Party Backup Tools
Recovery Manager for Oracle User’s Guide
The following restrictions apply when backing up a database using the Recovery Manager
database backup utility.
■ For NBU (user-managed) backup:
◆ The NBU client must be installed on the backup host, as well as on the primary host.
◆ At least one NBU policy of standard type must be created and configured for database
backup. Optionally, a separate NBU policy of standard type can be created and
configured for archive log destination backup.
■ For Oracle RMAN backup:
◆ If RMAN sbt_tape backup is chosen, the NBU for Oracle client must be installed on the
backup host, as well as on the primary host.
◆ If RMAN sbt_tape backup is chosen, at least one NBU policy of the Oracle type must be
created and configured for database backup. Optionally, a separate NBU policy of the
Oracle type can be created and configured for archive log backup. See section 4.8
Setting Up NetBackup Policies for Oracle RMAN Backup on page 4.22 for details.
◆ An RMAN Recovery Catalog database must be created and configured prior to using the
backup utility.
There are two ways to perform backups:
■ Immediate backup - a backup that is initiated by Recovery Manager through the database
backup utility.
■ Automatic backup - a backup that is initiated by NBU from the NBU master server.
2.10.1.1 Immediate Backup
During an immediate backup, Recovery Manager performs the following:
■ Creates an online, offline, datafile, or archonly virtual copy for the database or archive log
destination.
■ Mounts the virtual copy on the backup host.
For NBU (user-managed) backup, Recovery Manager:
■ Generates an include list file that contains a list of datafiles and/or archive log destination
on the mounted virtual copy and stores it in the
/usr/openv/netbackup/
include_list.<policy_name>
file on the NBU client (the backup host).