Getting Started with Tungsten MI for Tungsten Replicator
The process to launch TMI will depend upon the cloud environment you are launching into.
Follow the guides below appropriate to the Cloud provider you are using.
- "Launching from the Amazon (AWS) Marketplace"
- "Launching from the Google (GCP) Marketplace"
- Microsoft Azure (Coming Soon)
| Name | Description | AWS | GCP |
|---|---|---|---|
| Tungsten Replicator for MySQL Extraction | Required for all use-cases. Can be configured to extract from a remote MySQL Instance, a local MySQL Instance (must be manually configured first), Amazon Aurora, Google MySQL or Azure Cloud SQL. All flavours and versions of MySQL supported up to and including MySQL 8.4. | Y | Y |
| Tungsten Replicator for MySQL Appliers | Can be configured to apply to a remote MySQL Instance, a local MySQL Instance (must be manually configured first), Amazon Aurora, Google MySQL or Azure Cloud SQL. All flavours and versions of MySQL supported up to and including MySQL 8.4. | Y | Y |
| Tungsten Replicator for PostgreSQL Appliers | Can be configured to apply to a remote PostgreSQL Instance, or a local Instance (must be manually configured first). | Y | Y |
| Tungsten Replicator for Oracle Appliers | Can be configured to apply to a remote Oracle Instance, or a local Instance (must be manually configured first). | Y | Y |
| Tungsten Replicator for Kafka Appliers | Can be configured to apply to a remote Kafka Instance, or a local Instance (must be manually configured first). Currently requires zookeeper. | Y | Y |
| Tungsten Replicator for MongoDB | Can be configured to apply to a remote MongoDB Instance, a local Instance (must be manually configured first), or MongoDB Atlas. | Y | Y |
| Tungsten Replicator for Hadoop Appliers | Can be configured to apply to a remote Hadoop cluster. | Y | Y |
| Tungsten Replicator for Vertica Appliers | Can be configured to apply to a remote Vertica cluster. | Y | Y |
| Tungsten Replicator for Redshift Appliers | Can be configured to apply to Amazon Redshift. Requires S3 access and only available as an AWS AMI. | Y | N |
| Tungsten Replicator for S3 Appliers | Coming Soon... | N | N |
Launching from the Amazon (AWS) Marketplace
You can launch your instances in Amazon AWS by launching the instances via the Marketplace console.
First you will need to subscribe through the Amazon Marketplace by clicking here, or by simply searching for "Continuent" in the AWS Catalog.
You can choose an annual subscription or an hourly based usage subscription. The Amazon Marketplace will provide all the information required to allow you to subscribe accordingly.
Once subscribed you can then start to configure your instance. When choosing the instance size there are a number of factors to take into account
- Images do not deploy with a database installed, in most cases a t3.medium will be sufficient, however should you choose to install a database locally, then you should increase the instance size to suit the needs of the database you are configuring.
- How much data are you replicating? Each instance launches with a 40Gb partition. Tungsten Replicator will store THL logs on this partition. A THL log is similar to a MySQL binary log and contains all the transactions and data we are replicating. These files are kept by default for 7 days. If you are replicating significant amounts of data you may need to increase this volume and/or consider reducing the THL retention which can be done during the instance configuration.
Quantity of instances and their Location
- As mentioned earlier, you will need at least one "Tungsten Replicator for MySQL Extraction". Ideally this should reside in the same region and zone as the source database that you are extracting from.
- You will need at least one "Tungsten Replicator for xxxx Appliers" where xxxx relates to the target type. Ideally this should reside in the same region and zone as the target database.
- The source and target replicator instances do not have to reside in the same region, and can replicate globally. They can even be used to replicate into and out of AWS between on premise instances and other cloud providers.
- For more details and to understand the different topologies, see "deployment-mysql-extractor" and "deployment-appliers". Whilst the launch wizard on the launched VM will assist you to pre-configure a single extractor or applier service, users with advanced understanding of Tungsten Replicator can manually configure for more advanced topologies such as Fan-In and Fan-Out.
By default, the instances only launch with the default SSH security group. Based on your business rules, you will need to configure the appropriate security group to allow communication between all nodes within the topology, and to allow your hosts to communicate with the source and target database instances.
A full breakdown of the network requirements can be found here: "Networking Requirements"
After launching your instances, you can now proceed to configure them, see "Configuring Instances through the Launch Wizard" for instructions.
Launching from the Google (GCP) Marketplace
You can launch your instances in GCP via the Marketplace. Simply search for "Continuent" to view all the listings available.
Once subscribed you can then start to configure your instance. When choosing the instance size there are a number of factors to take into account.
- Images do not deploy with a database installed, in most cases a t3.medium will be sufficient, however should you choose to install a database locally, then you should increase the instance size to suit the needs of the database you are configuring.
- How much data are you replicating? Each instance launches with a 40Gb partition. Tungsten Replicator will store THL logs on this partition. A THL log is similar to a MySQL binary log and contains all the transactions and data we are replicating. These files are kept by default for 7 days. If you are replicating significant amounts of data you may need to increase this volume and/or consider reducing the THL retention which can be done during the instance configuration.
Quantity of instances and their Location
- As mentioned earlier, you will need at least one "Tungsten Replicator for MySQL Extraction". Ideally this should reside in the same region and zone as the source database that you are extracting from.
- You will need at least one "Tungsten Replicator for xxxx Appliers" where xxxx relates to the target type. Ideally this should reside in the same region and zone as the target database.
- The source and target replicator instances do not have to reside in the same region, and can replicate globally. They can even be used to replicate into and out of GCP between on premise instances and other cloud providers.
- For more details and to understand the different topologies, see "Deploying MySQL Extractors" and "Deploying Appliers".
Whilst the launch wizard on the launched VM will assist you to pre-configure a single extractor or applier service, users with advanced understanding of Tungsten Replicator can manually configure for more advanced topologies such as Fan-In and Fan-Out.
Based on your business rules, you will need to configure the appropriate network rules to allow you to access the host via your chosen terminal application, additionally you will need to allow communication between all nodes within the deployment, and to allow your instances to communicate with the source and target database instances.
A full breakdown of the network requirements can be found here: "Networking Requirements"
After launching your instances, you can now proceed to configure them, see "Configuring Instances through the Launch Wizard" for instructions.