About Oracle databases

You can register your application database that you want to protect. You can select a server, RMC displays the list of databases configured for the server. From the list of databases, you can select a database.

The Oracle Databases screen displays the registered databases. You can use Actions option from this screen to Edit, Refresh, Unregister, Clone/Restore, Add Protection, and Protect Once.

About Oracle standby database

An Oracle standby database is a synchronized copy of the production database. You can use the snapshot of a standby database to promote standby database volumes. However, you cannot use the snapshot to promote primary database volumes (even though a backup of the snapshot can be used to restore the primary database). The Oracle standby databases are supported if:
  • The Oracle Database version is 11g or 12c.

  • The standby database is a physical database. Logical or snapshot standby databases are not supported.

  • The primary database (not standby) is registered with Oracle Recovery Catalog while using RMAN backup.

About Production database configuration

This section describes the storage configuration that the database must fulfill to take snapshots and perform backup operations. All the datafiles and archive logs must reside on the same HPE 3PAR StoreServ storage. However, the datafiles and archive logs cannot coexist on the same volumes. CONTROLFILE, SPFILE and redo logs cannot be present on datafile volumes or archive log volumes. The same condition is applicable for ASM diskgroups.


The Oracle parameter and control files are not compatible with the standby and primary databases. You cannot use these files to restore the primary database unless Oracle RMAN is used. The Oracle parameter and control files of the primary database must be backed up manually outside of RMC-O.