Tungsten Replicator 2.2.0
Implements open source database-neutral master/slave replication
· Availability - Failing over to a slave database if your master database dies
· Performance Scaling - Spreading reads across many copies of data
· Cross-Site Clustering - Maintaining active database replicas across WANs
· Change Data Capture - Extracting changes to load data warehouses or update other systems
· Zero Downtime Upgrade - Performing upgrades on a slave server which then becomes the master
The Tungsten Replicator architecture is flexible and designed to support addition of new databases easily. It includes pluggable extractor and applier modules to help transfer data from master to slave.
The Replicator is designed to include a number of specialized features designed to improve its usefulness for particular problems like availability.
· Replicated changes have transaction IDs and are stored in a transaction history log that is identical for each server. This feature allows masters and slaves to exchange roles easily.
· Smooth procedures for planned and unplanned failover.
· Built-in consistency check tables and events allow users to check consistency between tables without stopping replication or applications.
· Support for statement as well as row replication.
· Hooks to allow data transformations when replicating between different database types.
Tungsten Replicator is not a toy. Tungsten Replicator is designed to allow commercial construction of robust database clusters. You are welcome to use Tungsten Replicator for any purpose for which it seems suitable.
In a hurry? Add it to your Download Basket!
What's New in This Release:
- Tungsten Replicator 2.2.0 is a bugfix and feature release that contains a number of key improvements to the installation and management of the replicator:
- tpm is now the default installation and deployment tool; use of tungsten-installer, configure, configure-service, and update are deprecated.
- tpm incorporates support for both INI file and staging directory deployments. See Section 4.4.4, “tpm INI File Configuration”.
- Deployments are possible using standard Linux RPM and PKG deployments. See Section 2.2.2, “Using the RPM and DEB package files”.