On-demand replication v7

Suggest edits

After you create a primary definition node, its publication, and additional primary nodes, you have two choices for starting the replication process:

  • Perform replication immediately by performing an initial on-demand snapshot. After you perform the on-demand snapshot, you can perform synchronization replication.
  • Schedule replication to start later by creating a schedule. See Creating a schedule.

Perform snapshot replication

A snapshot replication occurs from the primary definition node to a selected primary node.

When you create a primary node for the first time, you can perform an initial snapshot (see Step 3 of Creating additional primary nodes). You can also perform snapshots to this primary node later.

  1. In the Replication Server cojsole, select the Publication node under the primary node for which you want to perform snapshot replication.

  2. Select the Snapshot icon.

  3. In the Snapshot dialog box, select Verbose Output if you want to display the output from the snapshot in the dialog box. Don't select this option in a network address translation (NAT) environment as a large amount of output from the snapshot can delay the response from the Snapshot dialog box.

  4. To start snapshot replication, select Snapshot. Snapshot Taken Successfully appears when the snapshot is complete.

  5. Select OK.

The status messages of each snapshot are saved in the Migration Toolkit log files named mtk.log[.n] in the following directories. ([.n] is an optional history file count if log file rotation is enabled.)

For Linux:

/var/log/edb/xdb/

For Windows:

POSTGRES_HOME\.enterprisedb\xdb\x.x

POSTGRES_HOME is the home directory of the Windows postgres account (enterprisedb account for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode). The specific location of POSTGRES_HOME depends on your version of Windows. The Replication Server version number is represented by x.x.

The publication is now replicated from the primary definition node to the selected primary node. A record of the snapshot is saved in the replication history. See Viewing replication history for more information.

Perform synchronization replication

Note

Be sure an initial snapshot replication was performed from the primary definition node to every other primary node in the multi-master replication system. If a newly added primary node didn't undergo an initial snapshot, any later synchronization replication might not apply the transactions to that primary node. You can take the initial snapshot when the primary node is first added (see Creating additional primary nodes) or by performing an on-demand snapshot (see Performing snapshot replication).

When you perform synchronization replication in a multi-master replication system, a series of synchronization operations occur between every primary node pair in the replication system.

For example, if a replication system consists of primary nodes A, B, and C, synchronization is applied to the following node pairs whenever synchronization replication is initiated:

  • Changes on node A are applied to node B.
  • Changes on node A are applied to node C.
  • Changes on node B are applied to node A.
  • Changes on node B are applied to node C.
  • Changes on node C are applied to node A.
  • Changes on node C are applied to node B.

Changes made on different nodes might result in conflicts. Conflict resolution discusses the types of conflicts that can occur and how to resolve them.

To start an on-demand synchronization replication:

  1. In the Replication Server console, select the Publication node under any primary node. Whatever primary node you choose, synchronization is applied to every primary node pair in the replication system.

  2. Select the Synchronize icon.

  3. In the Synchronize dialog box, to start synchronization replication, select Synchronize. When synchronization is complete, Publication Synchronized Successfully appears.

  4. Select OK.

You can now see the operations that were applied to the publication tables in the replication history. See Viewing replication history for more information.

You can see conflicting changes that occurred in the conflict history. See Viewing conflict history for more information.

← Prev

Control schema objects created in primary nodes

Next →

Conflict resolution