HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

rmora_restore
SYNTAX
rmora_restore -s <oracle_sid> -p <db_server> [-t <timestamp>]
[-T <tablespaces>] [-D <dbf1,dbf2,...>] [-m <mountpoint>]
[-h <alt_server>] [-S <alt_sid>] [-H <alt_home>] [-c] [-v]
DESCRIPTION
Restores database files from a Virtual Copy backup image.
The rmora_restore command restores databases, tablespaces, data files, and/or archive logs
from a Virtual Copy backup image. The Virtual Copy must have been previously backed up using
the rmora_backup command. The Virtual Copy must have a status of Y in order to be restored.
The Virtual Copy’s backup status can be retrieved using the rmora_display command.
For NBU (User-managed) restore, the command can also be used to restore to an alternate server
on an alternate mount point. For Oracle RMAN restore, it is always restored to the database server.
If a Virtual Copy’s name is not specified, the rmora_restore command restores from the most
recent full back up.
If Symantec NetBackup is used and if a restore is performed to an alternate host, ensure that backup
images created from the backup server are available to the alternate host. For example, if the
system date on the alternate host is earlier than that from the Recovery Manager for Oracle backup
server, backup images may not be available to be restored to the alternate host.
Restore is not supported on Remote Copy configuration.
The following restrictions apply when restoring from a Virtual Copy’s backup image:
• When restoring the database control file (-c option), the current database instance must be
in STARTED mode (startup nomount). If the database is a Real Application Cluster (RAC)
database, all other RAC instances must be in CLOSED mode. Restoring the database control
file along with individual datafile or tablespace is not supported as it is not possible to perform
media recovery. If the original database is a physical standby database, the backup control
file generally cannot be used to restore to the primary (production) database since they are
not compatible unless Oracle 11g is in use and Oracle RMAN is used to restore.
• When restoring a database instance without restoring control file, the database instance must
be in MOUNTED mode. If the database is a Real Application Cluster (RAC) database, all
other RAC instances must be in CLOSED mode.
• When restoring individual tablespaces or datafiles, the database can be in OPEN or
MOUNTED mode. If the database is in OPEN mode, the corresponding tablespaces must be
offline.
• Restoring control files along with datafiles and/or tablespaces is not allowed.
• If the database is an ASM managed database, all ASM disk groups must be mounted prior
to running this command.
• For NBU (user-managed) restore, a file named
/usr/openv/netbackup/db/altnames/<alt_server> or
/usr/openv/netbackup/db/altnames/No.Restrictions must be created on the
NBU master server in order to perform restoration to a host (including the original database
server) that differs from the backup server. <alt_server> is the host name of the database
server to restore.
• If the backup tool was chosen to be RMAN backup to local disk, then the backup images must
be accessible to the restore host.
• Starting with Oracle 11g, a RMAN backup image of a standby database, which was backup
to local disk, cannot be restored using the rmora_restore command since the backup
92 Using the Recovery Manager Command Line Interface