HP 3PAR Application Software Suite for Oracle User Manual

Page 49

Advertising
background image

6.

Click Finish.

If Recovery Manager for Oracle successfully connects to the database, it retrieves the database
tablespaces, datafiles, the archive log destination, and the virtual volumes where the database
resides.

After verification is completed, Recovery Manager for Oracle creates a virtual copy repository
on the backup server (/etc/3par/solutions/<db_server>.ora.<oracle_sid>)
and two configuration files are generated along with one subdirectory for database files
mapping information.

/etc/3par/solutions/<db_server>.ora.<oracle_sid>/config

/etc/3par/solutions/<db_server>.ora.<oracle_sid>/config_exp.sh

/etc/3par/solutions/<db_server>.ora.<oracle_sid>/gui

Creating a Recovery Manager for Oracle Configuration File for Remote Copy
Configuration

Before creating the configuration files for Recovery Manager for Oracle to use, you must do the
following:

Set up physical links between the local and remote HP 3PAR storage systems. Refer to the HP
3PAR Remote Copy Software User’s Guide
for instructions on setting up links.

Set up Remote Copy targets for the local and remote HP 3PAR storage systems.

Create one or two Remote Copy groups, assign all virtual volumes used by datafiles and
archive log destinations to one group if only one group is created, or two separate groups if
two groups are created.

CAUTION:

Symantec Volume Manager VxVM: If Symantec Volume Manager VxVM is being

used when assigning 3PAR virtual volumes to Remote Copy groups, all volumes in the same
VxVM disk group should be assigned to a Remote Copy group, whether they are actually
being used by the Oracle database or not. Otherwise, you might not be able to import and
mount file systems on the remote backup server. Therefore, it is strongly suggested that Symantec
VxVM disk groups only contain files used by one Oracle database.

HP LVM Volume Manager: If you are using HP LVM Volume Manager, you must admit all HP
3PAR virtual volumes that are used by the LVM volume groups to the corresponding Remote
Copy volume group, whether the volumes are actually being used by the Oracle database or
not. If you do not do so, you might not be able to import and mount file systems on the remote
backup system.

Start Remote Copy and verify its setup and ensure that the Remote Copy groups are in started
status and all virtual volumes are synced before using Recovery Manager for Oracle.

Creating a Recovery Manager for Oracle Configuration File Using the Command Line Interface

To create the Recovery Manager for Oracle configuration files:
1.

From the backup server, issue /opt/3PAR/RMOra/bin/rmora_config.

2.

When prompted, press ENTER.

3.

When prompted, answer the following questions:

ORACLE_SID of the database instance [h=help,q=quit]?

Enter ORACLE_SID of the database instance that you want to configure. If the database is an
RAC database, enter ORACLE_SID of any RAC instance.

Host name of the database server [h=help,q=quit]?

Enter the host name of the corresponding database server where the specified database
instance is running.

Recovery Manager for Oracle Configuration Files

49

Advertising