> CommCell Console > Backup and Restore Agents > Databases > Oracle > Oracle Backup Administrator Guide > Replication of Oracle Databases

Performing an Oracle Replication Operation

You can perform a replication operation to a non-standby database.

replication uses the default subclient for the database that you want to replicate, so the default subclient content must contain the entire database, the log files and the control file.

The replication feature performs the following procedures:

  • Initiates the replication automatically after a backup is completed on the source database.

  • Minimizes the impact on production systems CPU and I/O by using the backup data for replications. This method avoids the need to read the source database again for replication.

  • Copies the backup data to remote disaster recovery (DR) sites with deduplication to minimize the wide area network (WAN) traffic. replication then runs at the DR site.

  • Initiates replication after the auxiliary copy completes, when you use a copy precedence for replication.

After you configure replication, the Commvault software runs a full backup, or uses the most recent backup to automatically copy the data from the source database to the destination so that the databases are synchronized.

You can schedule archive log backups, or create an automatic log schedule (see Creating an Automatic Schedule for Database Log Backups). The software uses the log backups to keep the destination database in sync with the source database.

If no new backups have been run since the last replication, then the scheduled replication does not run.

Best Practice: Have both the source and destination databases in ARCHIVELOG mode.

Before You Begin

  1. Install the Oracle Agent on the Windows or the UNIX destination database host. For more information, see Getting Started for Oracle.

  2. Add an Oracle instance on the destination client.

  3. Set up an Oracle instance for the replication destination database. For more information, see Setting Up an Oracle Instance for replication.

  4. Verify that the default subclient content contains the entire database, the log files and the control file.

  5. If you plan to use a storage policy copy, or secondary media, make sure that the copy precedence exists for both the data and log files, and that there is a scheduled auxiliary copy job.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle.

  2. Right-click the instance, point to All Tasks, Live Sync and then Configuration.

    The Oracle Live Sync Options dialog box appears.

  3. On the General tab, select the replication options:

    1. From the Destination Client list, select the client where the software replicates the data.

    2. From the Destination Instance list, select the instance where the software replicates the data.

      Note

      The software only displays the Oracle instances that support replication. For example, the software does not list +ASM instances.

    3. In the Baseline for Sync area, select the backup to use:

      • To use the latest full backup, select Use most recent full backup.

      • To run a new backup for the replication operation, select Run a new full backup.

    4. In the Number of Streams box, type the number of streams that the software will use for the replication.

  4. Optional: Restore from a storage policy copy, or secondary media.

    Note

    When you specify a copy precedence, the software only replicates changes when the source database backup is available on the secondary media or the secondary copy. The backup is available on the media after the auxiliary job completes, so that is when the software attempts the replication.

    1. Click Advanced.

      The Oracle Live Sync Advanced Options dialog box appears.

    2. On the Copy Precedence tab, select the following options:

      1. Select the Restore from copy precedence check box.

      2. In the Copy Precedence box, select the number of the backup copy.

    3. Click OK.

  5. If the destination database directory structure is different from the source, set the redirect path:

    1. Click Advanced.

      The Oracle Live Sync Advanced Options dialog box appears.

    2. On the Redirect tab, choose one of the following options:

      • To redirect all of the displayed tablespaces, select the Redirect All Table Spaces/Database To check box and then type the full path in the box.

      • To redirect a set of tablespaces, select the Redirect check box and the choose one of the following options.

      • To select individual tablespaces, click the New Path column associated with the tablespace, and then in the New Path box, type the path.

      • To redirect multiple tablespaces, click Find & Replace, and then enter the new path in the New Path box.

    3. To set the path on the destination client where the software creates the redo logs, on the Redirect tab, in the Redirect Online Redo logs box, type the path.

      Set this value when the destination client does not have the same file path as the source client.

    4. Click OK.

  6. Click OK.

Results

After the job completes, the software opens the replication destination database in read-only mode.

If you want to perform a backup operation on the replication destination database after the replication operation completes, open the database in read-write mode. Oracle does not allow a control file backup when the database is in read-only mode, so make sure to open the database in read-write mode so that you can have a successful backup.

The first replication job is marked as Completed with Errors (CWE).

For replication jobs, the Job Controller tab shows Replication as the Operation Type.

The software creates a new schedule every time you replicate to a new destination. For example, if you restore to client1 and then client2, the software creates a schedule for each client.

What to Do Next

Perform these tasks when any of the following conditions are met:

  • The source database is recovered and opened with the reset logs option.

  • The source and destination need a complete resync.

  • The destination database is opened in read write mode and has the reset logs option.

  • The destination database is recovered and opened with the reset logs option.

  • Delete the replication schedule (the schedule type is Restore).

    For information on how to view and delete schedules, see the following procedures:

Perform the replication procedure to recreate the schedule.

×

Loading...