Performing a DB2 Replication Operation

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

After you set up replication, the Commvault software performs a replication restore job that uses the most recent backup of the source database to automatically replicate the data from the most recent backup to the destination database so that the databases are synchronized. Also, the Commvault software automatically starts a replication restore job after any traditional backup or snapshot backup, which include the following:

  • Full

  • Incremental

  • Delta

  • Log file

  • Snapshot full

  • Application command line full

  • Application command line incremental

  • Application command line delta

  • Load copy incremental

Before You Begin

If you plan to use a storage policy copy, make sure that the copy precedence exists for both the data and log files, and that there is a scheduled auxiliary copy job. For more information about copy precedence, see Copy Precedence.

Procedure

  1. From the CommCell Browser, go to Client Computers > client > DB2 > DB2_instance.

  2. Right-click the backup set, and then go to All Tasks > Live Sync > Configuration.

    The DB2 Live Sync Options dialog box appears.

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

    1. From the Destination Client list, select the client that you want to use to replicate the data.

    2. From the Destination Instance list, select the instance that you want to use to replicate the data.

    3. In the Target Database Name text box, type the database name.

    4. In the Target Database Path field, browse to or type the database path.

  4. Optional: Restore from a storage policy copy (also called secondary media).

    Note

    When you specify a copy precedence, the software replicates changes only 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 DB2 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 you have an automatic database, specify the storage path, or if you have a non-automatic database, specify the redirect information.

  6. Database Type

    Procedure

    Automatic or mixed database

    Note

    DB2 storage paths are displayed only if there are GUI backup jobs that have run for this database. You won't see storage paths displayed for third-party command line backup jobs.

    To specify the storage path, on the Storage Paths tab:

    1. Select the Redirect storage groups check box.

      The DB2 storage groups appear.

    2. From the Storage group box, select the DB2 storage group to view the existing path on the source database.

    3. In the Path box, select the path on the DB2 storage device.

      • To change a path for this storage group, click it, then click Edit. Type the changes to the path.

      • To add a path for this storage group, click Add, and then type the path.

    Non-Automatic databases

    To redirect tablespaces, on the Redirect tab:

    1. Select the Redirect All Table Spaces/Database to check box.

    2. Enter or browse to the path to redirect the tablespaces and database.

  7. Click OK.

  8. Click OK.

Results

After the replication schedule is created, a replication restore job automatically starts. The replication operation creates a replication destination database in the Roll-forward Pending State.

For information about viewing schedules, see Viewing Job Schedules. For information about modifying or deleting schedules, see Scheduling - Advanced.

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

What to Do Next

If any of the following conditions occur, create a new replication schedule or run a cross-server restore:

  • The source database is restored for any reason.

  • The source database and the destination database need a complete resync.

  • Roll-forward on the destination replication database is complete or the database is damaged.

×

Loading...