HP StoreServ Application Suite for Oracle Media manual Periodic Database Synchronization

Recovery Manager for Oracle User’s Guide

4If 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 primary 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.

5Click 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.

6Click OK.

7.6.13Removing a Cloned Database

When a cloned database is no longer needed, it can be removed with the following procedure:

1Select a virtual copy with a status of Database.

2Right-click on the selected virtual copy and click Remove database.

3Click Yes.

4Click OK.

7.7Periodic 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 primary 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.

7.10

Periodic Database Synchronization