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

7.10 Periodic Database Synchronization
Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide
4 If an ascii control file is chosen to clone the database (this is default option), provide one or
more mount points on the backup host for the control files and the redo log files (control
files and redo log files are multiplexed across the mount points).
Example: If you provide /clone_directory1 , /clone_directory2 , +CLONE_DATA
notice combined ASM diskgroup and file systems are allowed in this operation, make sure
adequate permissions are granted for the user executing the clone utility. If the binary
control file is chosen to clone the database, the clone operation will use exactly the same
structure as that in the database database. The virtual copy must be mounted at '/' before
the database creation operation starts in order to ensure the clone database has exactly the
same structure for all database files.
5 Click Finish.
After the cloned database operation has completed, the Virtual Volume column is
changed from Mounted to Database to indicate the cloned database is up and running.
6 Click OK.
7.6.13 Removing a Cloned Database
When a cloned database is no longer needed, it can be removed with the following procedure:
1 Select a virtual copy with a status of Database.
2 Right-click on the selected virtual copy and click Remove database.
3 Click Yes.
4 Click OK.
7.7 Periodic Database Synchronization
The periodic synchronization process is an asynchronous process. Synchronization takes
minutes to hours for the synchronized process to finish depending on data changes, network
speed, and load on the database host, backup host, primary/local and secondary/remote InServ
Storage Servers. When the synchronization completes, Recovery Manager creates a virtual copy
on the remote (secondary) InServ Storage Server, updates the navigation view, and sends
notification to the user.