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

The following configuration requirements must be met:
•
The HP 3PAR StoreServ Storage system must be running HP 3PAR OS 2.3.1 or higher.
•
The backup server must belong to a domain set, which contains all database servers’ virtual
domains to be managed by the backup server.
•
The HP 3PAR OS user used by Recovery Manager for Oracle to access the HP 3PAR StoreServ
Storage system from the backup server must belong to the virtual domains of all the database
servers.
Recovery Manager for Oracle and Host Sets
Database servers (nodes) within the same Real Application Cluster (RAC) can be grouped into a
set, which can then be managed as a single object. If the backup server also belongs to a host
set, Recovery Manager for Oracle continues to export/deport database Virtual Copies to the
backup server, rather than the host set that contains the backup server.
Recovery Manager for Oracle and Virtual Volume Sets
Database virtual volumes can be grouped into a set on the database server, which can be managed
as a single object. Recovery Manager for Oracle works with the volume sets, but from the backup
server, it does not make use of them as database virtual volumes must still be discovered in order
to ensure all database volumes are included in the volume set.
Recovery Manager for Oracle with Remote Copy
Recovery Manager for Oracle integrates with HP 3PAR Remote Copy Software to copy database
virtual volumes from one HP 3PAR StoreServ Storage system (local/primary) to another
(remote/secondary). Once copied, database Virtual Copies (application consistent snapshots) are
created on the remote/secondary storage system. The Virtual Copies can be used for disaster
recovery or other off-host processing purposes. Recovery Manager for Oracle supports synchronous
and asynchronous periodic mode Remote Copy, as well as Synchronous Long Distance Remote
Copy. See the HP 3PAR Remote Copy Software User's Guide for additional information.
Recovery Manager for Oracle and Peer Motion
You do not need to uninstall and then reinstall Recovery Manager for Oracle when you migrate
data with HP 3PAR Peer Motion.
Preparing Recovery Manager for Oracle for Peer Motion Data Migration
1. Before you use Peer Motion to migrate data, remove all existing Recovery Manager for Oracle
Virtual Copies in the following order:
a.
Remove all clone databases; to do so, use the GUI or the rmora_removedb command.
b. Unmount all currently mounted Virtual Copies; to do so, use the GUI or the rmora_umount
command.
c. Remove all existing Virtual Copies; to do so, use the GUI or the rmora_remove command.
2. Start the data migration. While Peer Motion is migrating data, do not use Recovery Manager
for Oracle.
3. Finish host configuration for the new HP 3PAR StoreServ Storage system.
4. Remove the old system from the storage system setup.
5. After Peer Motion migration is complete, reconfigure SSH to allow the database and backup
servers to access the new HP 3PAR StoreServ Storage system.
6. Modify the Recovery Manager for Oracle configuration file to reflect the new HP 3PAR StoreServ
Storage system; to do so, use the GUI or rmora_config command.
7. Begin Recovery Manager for Oracle operations.
22 Overview of Recovery Manager Operations