Restarting a running replicator temporarily stops and restarts replication. When using Multi-Site/Active-Active, restarting the additional replicator will stop replication between sites.
These instructions assume you have installed the additional replicator
with the executable-prefix=mm option.
If not, you should go to
/opt/replicator/tungsten/tungsten-replicator/bin
and run the replicator and trepctl commands directly.
Before stopping a replicator it is good practice to take it offline cleanly first. Doing so will ensure a clean stop of any replication in flight and ensure replication positions are correctly recorded.
If Parallel Apply is in use, this is essential, see Section 4.1.4, “Parallel Replication and Offline Operation” for more information
The Tungsten Replicator services that connect clusters in a Multi-Site/Active-Active topology are not managed by the individual cluster services, and therefore the cluster will not automatically restart the cross-site replicator services.
To shutdown a running Tungsten Replicator you must switch off the replicator:
shell>mm_trepctl -all-services offlineshell>mm_replicator stopStopping Tungsten Replicator Service... Stopped Tungsten Replicator Service.
To start the Tungsten Replicator service if it is not already running:
shell> mm_replicator start
Starting Tungsten Replicator Service...To restart the Tungsten Replicator service if it is running:
shell>mm_trepctl -all-services offlineshell>mm_replicator restartStopping Tungsten Replicator Service... Stopped Tungsten Replicator Service. Starting Tungsten Replicator Service...
To start the Tungsten Replicator service if it is not already running, but ensure replication is offline:
shell> mm_replicator start offline
Starting Tungsten Replicator Service...