Skip to main content
Tungsten Replicator

Deploying an Extractor for Cloud Managed SQL

Replicating from Cloud managed databases, such as Amazon Aurora or Google SQL, operates by directly accessing the binary log provided by the service and enables you to replicate from the remote instance, or to a standard instance within your cloud provider environment, or even out to self-hosted instances. The complexity with Cloud Managed instance is that there is no access to the host that is running the instance, or the MySQL binary logs.

To use this service, two aspects of the Tungsten Replicator are required, direct mode and unprivileged user support. Direct mode reads the MySQL binary log over the network, rather than accessing the binlog on the filesystem. The unprivileged mode enables the user to access and update information within Aurora (for example) without requiring SUPER privileges, which are unavailable within a Cloud Managed instance. For more information, see "MySQL Unprivileged Users".

The deployment requires a host for the extractor installation, this can be an instance within your cloud environment, or it could be a remote host in your own environment.

This deployment follows a similar model to an Offboard Installation

Topologies: Cloud Extraction
Topologies: Cloud Extraction

Before starting the installation, the prerequisites must have been completed (see "Installation Prerequisites") on both the Host designated for the installation of the extractor, and within the source database instance.

  • Install the Tungsten Replicator RPM package, or download the compressed tarball and unpack it to a staging directory:

    shell> cd /opt/continuent/software
    shell> tar zxf tungsten-replicator-8.0.4-132.tar.gz

  • Change to the Tungsten Replicator staging directory:

    shell> cd tungsten-replicator-8.0.4-132

  • Configure the replicator for extraction (In this example, the service name is alpha)

    Example tungsten.ini
    [defaults]
    install-directory=/opt/continuent
    user=tungsten
    profile-script=~/.bash_profile
    mysql-allow-intensive-checks=true
    skip-validation-check=InstallerMasterSlaveCheck
    skip-validation-check=MySQLPermissionsCheck
    skip-validation-check=MySQLBinaryLogsEnabledCheck
    skip-validation-check=MySQLMyISAMCheck
    skip-validation-check=RowBasedBinaryLoggingCheck
    rest-api-admin-user=apiuser
    rest-api-admin-password=secret
    replicator-rest-api-address=0.0.0.0
    cloud-install=true

    [alpha]
    master=localhost
    members=localhost
    enable-heterogeneous-service=true
    privileged-master=false
    replication-host=rds.endpoint.url
    replication-port=3306
    replication-user=tungsten_alpha
    replication-password=secret
    datasource-mysql-conf=/dev/null
    svc-extractor-filters=dropcatalogdata
    property=replicator.service.comments=true
    Show argument definitions
    user=tungstenOS System User, for example tungsten. DO NOT use root.
    profile-script=~/.bash_profileAppend commands to include env.sh in this profile script.
    rest-api-admin-user=apiuserSpecify the initial Admin Username for API access.Available from v7.0.0
    rest-api-admin-password=secretSpecify the initial Admin User Password for API access. rest-api-admin-password alias only available from version 7.1.2 onwards.Available from v7.0.0
    replicator-rest-api-address=0.0.0.0Address for the API to bind too.Available from v7.0.0
    cloud-install=trueWhen set to true (false by default) tpm will skip checks for the endpoint hostname existing in the /etc/hosts file, allowing for much smoother installations against cloud based sources or targets such as Amazon Aurora and Google Cloud SQL.Available from v8.0.0

  • Once the prerequisites and configuring of the installation has been completed, the software can be installed:

    shell> ./tools/tpm install

In the above examples,

If the installation process fails, check the output of the /tmp/tungsten-configure.log file for more information about the root cause.

Once the installation has been completed, you can now proceed to configure the Applier service following the relevant step within "Deploying Appliers".

Following installation of the applier, the services can be started. For information on starting and stopping Tungsten Replicator see "Starting and Stopping Tungsten Components"; configuring init scripts to startup and shutdown when the system boots and shuts down, see "Configuring Startup on Boot".

Monitoring the extractor is the same as an extractor from MySQL, for information, see "Monitoring the MySQL Extractor".