Ingres Replicator is a database connectivity system that manages replication. It provides transparent replication of data across databases on local or remote sites.

You can replicate between different databases on the same machine or on different machines on the other side of the world, as long as they are in a distributed network. So instead of having all your users throughout the world access the same database in one location, you can have a replicated database in every region.

Data from a transaction are not available for replication until the transaction has committed locally.

Ingres Replicator works behind the scenes to replicate data asynchronously by transaction. Designed as a layer that sits between the database and an application, Ingres Replicator is transparent to users.

Ingres Replicator queues each replicated transaction and uses two-phase commit to move the transaction from the Ingres Replicator queues to the target database. In the event of a source, target, or network failure, data integrity is enforced through this two-phase commit protocol by ensuring that either the whole transaction is replicated, or none of it is.

If the replication fails during two-phase commit, it remains in the queue and is tried again. Therefore, if one replicated database goes down, all the transactions that must be replicated to it remain queued and are sent again in the correct order as soon as it becomes available. For more information, see How Two-phase Commit Works.

Ingres Replicator also allows you to monitor your replicated transactions and run reports on your replication system.