IBM InfoSphere Replication Server
Features and benefits
- IBM InfoSphere® Replication Server distributes, consolidates, and synchronizes data for high availability, high throughput, and business continuity solutions as well as data distribution and consolidation environments.
- One solution delivers two replication models, queue-based and SQL-based, providing asynchronous log-based replication that maximizes flexibility and function.
- Both models support partitioned database environments for DB2 on Linux, UNIX, and Windows, automatically merging the changes captured from the logs.
- Queue-based replication supports high volume, low latency data replication with managed conflict detection and resolution:
- IBM WebSphere MQ message queues provide a high performance, robust, and reliable data delivery mechanism.
- A sophisticated apply engine determines transaction dependencies and replays transactions on target systems, maximizing parallelism to minimize latency.
- Conflict detection and resolution features allow backup systems to also be used for productive work, maximizing resource utilization and enabling application workload distribution across multiple servers.
- Data filtering features ensure that only the data of interest is replicated.
- Transformation capabilities on the apply side expand the scope of the replication.
- DB2 for z/OS is supported as a source and a target through InfoSphere Replication Server for z/OS.
- SQL-based replication maximizes flexibility in managing schedules, transformation, and distribution topologies for populating warehouses or marts. It maintains data consistency between applications and efficiently manages distribution and consolidation scenarios among multiple locations:
- Data can be distributed from one database to many and consolidated from many databases to one.
- Horizontal and vertical data filtering features simplify the replication of only the data that is needed.
- Extensive transformations can be performed in-line with the data movement.
- Replication can be on a specific schedule, at designated intervals, continuous, or event-driven.
- Replication can be managed table-at-a-time, such as for warehouse loading during batch windows, or with transaction consistency for data that is never offline.
