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

synchronous, asynchronous periodic mode, and 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 need not 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 server 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.
Recovery Manager for Oracle and Fat-to-Thin and Thin-to-Fat
To improve the existing RMO setup environment, an unlimited bidirectional conversion of volumes
from Fat-to-Thin and Thin-to-Fat is featured with HP 3PAR Operating System Software. The user
may better balance between performance and spacial optimization.
Converting Virtual Volumes
CAUTION: Due to the limitations of HP 3PAR OS, RMO is unable to retain repository information
after online Fat-to-Thin or online Thin-to-Fat conversion process. As a result, all existing Virtual
Copies, including the mounted ones, must be unmounted and removed prior to performing any
online Fat-to-Thin or Thin-to-Fat conversion. Use either the GUI or CLI (rmora_remove) to remove
all Virtual Copies. Do not use the RMO creation process during conversion. Only use the RMO
creation process when the conversion process is complete. RMO can only detect conversion on
specified volume. For example, you can still create a Virtual Copy on a datafile while a conversion
is in progress on archive log volume.
To convert database Virtual Volumes:
1.
On HP 3PAR Backup system, use the Recovery Manager GUI or command line interface to
remove all Virtual Copies of the database before converting the volumes.
2. On HP 3PAR StoreServ Storage system, enter tunevv to convert the virtual volumes.
NOTE: For more details about using the tunevv command, see the HP 3PAR Operating
System Software User Guide.
3. On HP 3PAR StoreServ Storage system, enter showtask to monitor the Virtual Volume
conversion completion.
Recovery Manager for Oracle and Peer Motion 25