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

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 155) .
Recovery Manager Commands
rmora_backup
SYNTAX
rmora_backup -s <oracle_sid> -p <db_server> [-t <timestamp>]
[-o <backup_type>] [-v]
or
rmora_backup -s <oracle_sid> -p <db_server>
[-o online|offline|datafile|archlog,[<backup_type>]] [-v]
For Symantec NetBackup, Oracle RMAN or Oracle RMAN with Symantec NetBackup:
<backup_type> = {full | incr | cinc}
For Oracle RMAN with HP Data Protector:
<backup_type> = {full | incr1 | incr2 | incr3 | incr4}
DESCRIPTION
Recovery Manager for Oracle integrates HP 3PAR Virtual Copy Software feature with Symantec
NetBackup (NBU), HP Data Protector, 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 a client-side 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 client-side 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.
If the database is a physical standby database and Oracle release is earlier than 11g, the Oracle
initialization parameter file and control file of the production database must be backed up manually
in addition to the virtual copy. This is because the initialization parameter file and control file are
not compatible between the standby and production database.
Recovery Manager for Oracle supports Symantec NetBackup and Oracle RMAN backup methods.
The backup method can be specified during Recovery Manager configuration process. Symantec
NetBackup backup method can be used to perform backup of a database whose database files
are on file systems. Oracle RMAN backup method can be used to perform backup of a database
whose database files are either on file systems or ASM disk group. For Oracle RMAN backup
66 Using the Recovery Manager Command Line Interface