Skip to content

What is Offline Replicator?#

Offline Replicator#

Background#

In the above diagram, some XLogs of SYSTEM A may not be sent to the remote server (SYSTEM B) when the SYSTEM A has a failure. In this case, the system has to fail over to SYSTEM B, but SYSTEM B needs those unsent XLogs to start the service, otherwise, data in between those systems will be inconsistent. This can be achieved if SYSTEM B is able to access the log files of SYSTEM A and apply them locally.

How to use Offline Replicator?#

Follow the steps below if you need to use Offline Replicator feature.

Replication Steps Table (Markdown Version)

steps Description
1 Mount a volume with the access enabled for SYSTEM-B
2 Create Offline Replicator on SYSTEM-B

iSQL> CREATE REPLICATION rep1 OPTIONS OFFLINE '/data1/logfiles' WITH '192.168.1.13', 30300 FROM SYS.table TO SYS.table;
3 Execute SQL to start offline replication

iSQL> ALTER REPLICATION rep1 START WITH OFFLINE;

Status of Offline Replicator becomes "stop" once it completes its work.
You can start the fail over procedure after checking this status.

To learn more, refer to this manual