Centralized management

Manage data replication across servers from one centralized location

Abstract

The FairCom Replication Manager is distributed in a .zip or .tar package — for example, FairCom DB.<platform>.ReplicationManager.<build>.

The Replication Manager runs on a central server or cluster that is independent of the servers it manages.

The Replication Manager contains:

Embedded FairCom Database that maintains data specific for managing replication.
Embedded App Server that delivers a browser-based application for managing replication.
JSON RPC API over HTTP that any application can use to automate replication.
C++ API that any application can use to automate replication.

You can modify ctsrvr.cfg in the <faircom>/config folder to change the server name and ports:

Note

Replication Manager web ports are defined in <faircom>/config/chttpd.json.

SERVER_NAME default MEMPHIS which converted to TCP/IP port 5532
SQL_PORT default TCP/IP port 7000

Each FairCom DB server has a UUID that is used when registering with the Replication Manager.

The UUID takes precedence over the server name, host, local path, and any other server identification.
If a registering server's UUID matches an existing server's UUID in the Replication Manager, the Replication Manager assumes they are the same server. The existing server information is updated with the registering server's information.
All FairCom DB servers connecting to a Replication Manager server must have a unique UUID. See Multiple server instances, for more information on server UUIDs.

Register a FairCom server with Replication Manager

Each FairCom server participating in a replication environment registers with Replication Manager. These are configured in a local <faircom>/config/ctagent.json configuration file.

{
	"use_replication _agent_manager": true,
	"log_file": "agentLog.txt",
	"memphis_server_name": "MEMPHIS",
	"memphis_sql_port": 7000,
	"memphis_host": "l0.1.1.101",
	"memphis_database": "MEMPHIS",
	"ctree_check_mask": "*.dat;*.idx;*.fdd;*.fsd",
	"inactive_timeout": 600,
	"accept_conn": true
        "dbengine_ip_address": <IP address>
        "dbengine_behind_nat": false
}

Property	Description	Default	Values
dbengine_behind_nat	Supports multiple machines using virtual IP under the same real IP address.	false	true false
dbengine_ip_address	Define which IP address Replication Manager should use when connecting to the current dbengine.		IP address

Property

Description

Default

Values

dbengine_behind_nat

Supports multiple machines using virtual IP under the same real IP address.

false

true

false

dbengine_ip_address

Define which IP address Replication Manager should use when connecting to the current dbengine.

IP address

dbengine_behind_nat

If true, duplicate IP addresses will be allowed and all registered servers are assumed to have a valid unique hostname.

Once registered, FairCom servers can be managed by the Replication Manager.

Replication Manager adds and stores metadata in its local database for each managed server. It also stores all replication publications and subscriptions that it manages to make it easy to manage replication for hundreds of FairCom servers across multiple environments.

dbengine_ip_address

When the FairCom database engine starts, it registers itself in the Replication Manager and tries to identify which machine it is running on by retrieving the local hostname from the OS and all the IP addresses for the local network adapters.

Depending on the network topology, there are cases where the Replication Manager and the other database engines need to use some specific IP address for connecting to the machine where the database engine is running. This specific IP address should be configured in this property. If it is not set, the Replication Manager and the other database engines will try to connect using the list of IP addresses automatically registered.