3.4. Replicating Data Out of an Existing Cluster
If you have an existing cluster and you want to replicate the data out to a
separate standalone server using Tungsten Replicator then you can create a
cluster alias, and use a master/slave topology to replicate from the
cluster. This allows for THL events from the cluster to be applied to a
separate server for the purposes of backup or separate analysis.
The deployment works by creating an alias into the Continuent Tungsten cluster,
and then uses this as the source information for configuring a separate
service from the alias into the standalone replicator.
Figure 3.4. Topologies: Master/Slave with Replicator
In order to configure this, there are three steps:
Setup a new server to hold the Tungsten Replicator service
Configure an alias to the existing Continuent Tungsten service
Configure a replicator that points to the alias acting as a slave
There are also the following requirements:
The host on which you want to replicate to must have Tungsten Replicator
2.1.2 or later
Hosts on both the replicator and cluster must be able to communicate
with each other.
Replicator must be able to connect as the
tungsten user to the databases
within the cluster
The tpm command to create the service on the replicator
is as follows:
On your staging server, download the release package.
Unpack the release package:
Change to the unpackaged directory:
Execute the tpm command to configure the
./tools/tpm configure defaults \
The description of each of the options is shown below; click the icon to
hide this detail:
Click the icon to show a detailed description of each argument.
Configures default options that will be configured for all future
The installation directory of the Tungsten service. This is where
the service will be installed on each server in your dataservice.
The profile script used when your shell starts. Using this line
modifies your profile script to add a path to the Tungsten tools so
that managing Continuent Tungsten™ are easier to use.
The operating system user name that you have created for the
The user name that will be used to apply replication changes to the
database on slaves.
The password that will be used to apply replication changes to the
database on slaves.
Set the port number to use when connecting to the MySQL server.
Tells tpm to startup the service, and report the
current configuration and status.
Now the defaults are configure, first we configure a cluster alias that
points to the masters and slaves within the current Continuent Tungsten
service that you are replicating from:
./tools/tpm configure beta \
This creates a configuration that specifies that the topology should be
a cluster alias, and that the cluster configuration of the cluster from
which you are replicating, the master is
hostA and the slave is
Now, the service that will replicate from the cluster alias into the
hostC can be created:
./tools/tpm configure gamma \
This creates the configuration that will replicate into the database on
the Tungsten Replicator. In this example:
If the installation process fails, check the output of the
for more information about the root cause.
Once the configuration has been completed, you can perform the
installation to set up the services using this configuration:
The replicator should be installed and ready to use.