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

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.
For an RAC database, archive log destinations of all RAC instances must be on shared storage
(same cluster file systems or same ASM disk groups).
The Database Restoration Utility
The database restoration utility of HP 3PAR Recovery Manager Software for Oracle restores
databases, tablespaces, datafiles, or archive logs from a backup image of a Virtual Copy. The
Virtual Copy must have been previously backed up using the rmora_backup command. The
Virtual Copy must have a backup status of Y in order to be restored. The backup status of a Virtual
Copy can be retrieved using the Recovery Manager display utility (see
“The Virtual Copy Display
Utility” (page 12) ).
For an NetBackup (user-managed) restoration, the database restoration utility can be used to restore
a backup image of a Virtual Copy to the backup server, and it can also be used to restore to an
alternate server on an alternate mount point. For an Oracle RMAN restoration, the backup image
is always restored to the database server.
The following restrictions apply when restoring from a backup image of a Virtual Copy:
•
When restoring the database control file (using the -c option) using Oracle RMAN, the
database must be in STARTED mode (startup nomount). In addition, restoring the database
control file along with the individual datafile or tablespace is not supported as it is not possible
to perform media recovery.
•
When restoring a database, the database must be in CLOSED or MOUNTED mode for NBU
restore or Oracle RMAN restore, respectively. For an RAC database, all RAC instances must
be in CLOSED or MOUNTED mode.
•
When restoring individual tablespaces or datafiles, the database can be OPEN, but the
corresponding tablespaces must be offline.
•
If the database is an ASM managed database, all ASM disk groups must be mounted prior
to running the restore utility.
•
For an NBU (user-managed) restoration, the
/usr/openv/netbackup/db/altnames/<database_hostname|virtual
_hostname> file must be created on the NBU master server prior to running the restore utility,
where <database_hostname|virtual_hostname> is the host name of the database
server.
Depending on the type (online, offline, datafile, or archive log) of backup image of the Virtual
Copy, corresponding database files are restored appropriately.
20 Overview of Recovery Manager Operations