7 projects tagged "replication"
SymmetricDS is Web-enabled, database independent, data synchronization/replication software. It uses Web and database technologies to replicate tables between relational databases in near real time. The software was designed to scale for a large number of databases, work across low-bandwidth connections, and withstand periods of network outage. It includes support for Oracle, MySQL, PostgreSQL, H2, HSQLDB, Derby, MS SQL Server, Firebird, IBM DB2, Informix, Interbase, and Greenplum databases.
Mammoth PostgreSQL Replicator uses a transaction log and async replication model that nearly eliminates extra load on your master server regardless of the number of slaves you have in production. It supports advanced features such as large object, role, and ACL (grant/revoke) replication. It also supports promotion and failover.
MySQL Split Read/Write for Drupal is a patch for Drupal versions 5 and 6 that allows a Drupal-based Web site to access a multi-server MySQL setup with master/slave replication. This allows Drupal to send all MySQL select (read) queries to the slave nodes, while allowing insert, update, and select (write and read) queries to be pointed at the master node. The code modification allows for an increased 30% improvement under query-based transactions on this platform environment.
SymmetricDS Pro is software for data replication, change data capture, and data transformation in a heterogeneous enterprise environment. Performance and scalability allow it to replicate thousands of databases asynchronously in near real time. With flexible configuration and powerful scripting and programming interfaces, it can be extended to meet a range of requirements. Based on the popular open source version of SymmetricDS, the Pro edition enhances the experience with a click-through installer, Web management console, and production support.
zrep provides an easy-to-use program to manage zfs filesystem replication and failover. No configuration files are required. The program is developed under Solaris, but may work with any up to date zfs implementation. The executable is a single script. Initialization does a full data copy, but subsequent syncs are incrementals. It uses internal locking to make sure there is no danger of overlap if you just shove it in cron to run every minute. Design target is more "near-time replication", since the sync can be run every minute or more. However, it could conceivably be used for "backup" purposes as well.