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

4 Using the Recovery Manager Command Line Interface
This chapter describes the Recovery Manager for Oracle command line utilities.
NOTE: The command line utilities are located in /opt/3PAR/RMOra/bin.
To view error messages, their explanations, and appropriate troubleshooting actions in a web
browser, select Help
→Event Messages from the menu bar. Alternatively, see
“Troubleshooting”
(page 140) .
Recovery Manager Commands
rmora_backup
SYNTAX
rmora_backup -s <oracle_sid> -p <db_server> [-t <timestamp>] [-o
full|incr|cinc] [-v]
or
rmora_backup -s <oracle_sid> -p <db_server> [-o
online|offline|datafile|archlog|archonly[,full|incr|cinc]] [-v]
DESCRIPTION
Recovery Manager for Oracle integrates HP 3PAR Virtual Copy Software feature with Symantec
NetBackup (NBU) and Oracle RMAN to perform snapshot off-host backup. Snapshot off-host
backup can dramatically reduce performance impact on the database server as well as minimize
database down time or the time database in backup mode during backup.
The first form of rmora_backup command initiates an immediate backup of an existing database
Virtual Copy. The Virtual Copy must have Available status (not mounted) in order to be backed
up. The rmora_backup command mounts (presents) the Virtual Copy to the backup server before
initiating an immediate backup (off-host).
The second form of rmora_backup command creates a new database Virtual Copy, mounts
(presents) it to the backup server before initiating an immediate backup (off-host). If the database
being snapshot is a physical standby database and Oracle release is not 11g, the Oracle parameter
file and control file of the production database must be backed up manually in addition to the
Virtual Copy. This is because the parameter file and control file are not compatible between the
standby and production database.
Recovery Manager for Oracle supports NBU (user-managed) backup and Oracle RMAN backup
methods, which can be specified during the Recovery Manager for Oracle configuration process.
If Oracle RMAN is used for backup, the primary (not standby) database must be registered with
the Oracle Recovery Catalog Database. For the Oracle RMAN backup method, you can select
the SBT_TAPE or DISK option to backup to tape or to a local disk on a backup server, respectively.
Starting with Oracle 11g, an RMAN backup image of a standby database to local disk cannot
be seen from the Recovery Catalog from the production database. Therefore, the backup image
cannot be restored to the production database using the rmora_restore command. Please see
the rmora_restore command man page on how to perform restore manually. Regardless of
backup method, Recovery Manager for Oracle supports full backup of an Oracle database or
archive log destination. However, incremental (differential or cumulative) backup of the whole
Oracle database is only available for Oracle RMAN backup method. Incremental (differential or
cumulative) backup of archive log destination is only available for NBU (User-managed) backup
method.
Backup is not supported on Remote Copy configuration.
54 Using the Recovery Manager Command Line Interface