HP 3PAR Application Software Suite for Oracle - Manual (Page 19)

NOTE: The RMAN backup scripts (rmora_rman_dbbackup.sh and
rmora_rman_archbackup.sh) are generated at
/etc/3par/solutions/<db_server>.ora.<oracle_sid> during the creation of the
Recovery Manager Configuration file.
Automatic Backup
NOTE: NBU automatic backup can be used when Recovery Manager for Oracle is configured
to run as either root user or Oracle owner.
NOTE: If Recovery Manager for Oracle is configured to be run as an Oracle user and this is an
upgrade from previous Recovery Manager release, the rmora_config command must be run
again for each database that is configured for automatic backup.
During an automatic backup, NBU initiates a backup process on the NBU client (the backup server).
For an NBU (user-managed) backup:
•
The NBU client executes the bpstart_notify.<policy_name> script.
•
The bpstart_notify script creates a virtual copy of the database or archive log destination,
mounts it on the backup server, then generates the include list in the
/usr/openv/netbackup/include_list.<policy_name>
file, which contains a list of
files on the virtual copy for backup.
•
Once the backup process is completed, the NBU client executes the
bpend_notify.<policy_name>
script to perform virtual copy cleanup.
NOTE: The bpstart_notify and bpend_notify scripts are generated at
/usr/openv/netbackup/bin during the creation of the Recovery Manager Configuration file.
By default, the bpstart_notify script (for database backup policy) will perform an online
backup. If an offline or datafile backup is desired, edit this file to set the value of BACKUP_MODE
to 'offline' or 'datafile' respectively. In addition, the database must be manually shutdown for
offline backup.
For an Oracle RMAN backup:
•
The NBU client executes the backup script rmora_nbu_dbbackup.sh or
rmora_nbu_archbackup.sh
, which must be specified in the Backup Selection List of the
NBU policy.
•
The backup script creates a virtual copy of the database or archive log destination, mounts it
on the backup server, starts up a cloned database in MOUNTED mode, then calls the RMAN
backup scripts (rmora_rman_dbbackup.sh or rmora_rman_archbackup.sh) to backup
the cloned database.
NOTE: The backup scripts (rmora_nbu_dbbackup.sh and rmora_nbu_archbackup.sh)
and the RMAN backup scripts (rmora_rman_dbbackup.sh and
rmora_rman_archbackup.sh
) are generated at
/etc/3par/solutions/<db_server>.ora.<oracle_sid> during the creation of the
Recovery Manager Configuration file. By default, the rmora_nbu_dbbackup.sh script (for
database backup policy) will perform an online backup. If an offline or datafile backup is desired,
edit this file to set the value of BACKUP_MODE to 'offline' or 'datafile' respectively. In addition,
the database must be manually put in MOUNTED mode for offline backup.
NOTE: To perform automatic backup, SSH must have been configured for root user as Symantec
NetBackup always initiates a backup as root user.
If the virtual copy is to be backed up using Oracle RMAN, a Recovery Catalog must have been
created and configured prior to using the backup utility.
Recovery Manager for Oracle and Third-Party Backup Tools 19