Skip to main content
Tungsten Replicator

Preparing for MySQL Replication

Configure the source and target hosts following the prerequisites outlined in "Installation Prerequisites" then follow the appropriate steps for the required extractor topology outlined in "Deploying MySQL Extractors".

  • MySQL Target

    Applies to:

    • Standalone (on-prem) hosted instances

    • Cloud hosted instances

    To prepare the target MySQL Database, ensure the user accounts are created as per the steps outlined in "MySQL Database Setup"

  • Cloud-Managed Target

    For Cloud-Managed based targets (For example Amazon Aurora), as we do not have access to the host, nor can we configure accounts with elevated privileges, follow the steps in "MySQL Unprivileged Users" to prepare the target for replication

The data replicated from MySQL can be any data, although there are some known limitations and assumptions made on the way the information is transferred.

  • Table format should be updated to UTF8 by updating the MySQL configuration (my.cnf):

    character-set-server=utf8
    collation-server=utf8_general_ci

  • To prevent timezone configuration storing zone adjusted values and exporting this information to the binary log, fix the timezone configuration to use UTC within the configuration file (my.cnf):

    default-time-zone='+00:00'

If your target is a Cloud-Managed Instance, that has not yet been created, follow the steps in the next section below.

If your target is a hosted MySQL environment, proceed to "Install MySQL Applier"

Prepare Cloud-Managed Instance​

  • Create the Instance

    If the instance does not already exist, create it via your cloud providers recommended steps, ensuring the configuration meets your needs. Take a note of the endpoint URL or Public-IP reported. This information will be required when configuring the replicator service.

    Also take a note of the user and password used for connecting to the instance.

  • Check your security group configuration.

    The host used as the Target for applying changes to the instance must have been added to the relevant security groups. Within the cloud console, configure the networking to allow hosts that are allowed to connect to the instance, and hence update information within the database. The configuration must include the IP address of the Applier replicator, whether that host is within the same cloud environment or external.

  • Change instance properties

    Depending on the configuration and data to be replicated, the parameters of the running instance may need to be modified. For example, the max_allowed_packet parameter may need to be increased.

    The process for changing parameters differs between cloud providers and therefore you should consult the documentation appropriate to your provider if you are unsure on how to change database properties