Q Replication captures changes to source tables and converts committed transactional data to messages. The data is not staged in tables. As soon as the data is committed at the source and read by Q Replication, the data is sent to the target location through WebSphere MQ
- They replicate data from and to one or more DB2 for z/OS nodes within a site or across sites.
- They require a high throughput replication solution that keeps up with their source transactional and batch workloads.
- They rely on a resilient solution that includes recovery procedures in case of outages.
- They rely on conflict detection, resolution, and conflict avoidance strategies when conflicts are a possibility.
The Software you need for Q-replication are Websphere-MQ and Q replication server.
Software replication solution
They choose a software-replication solution because it provides the following features:
- Can guarantee shorter recovery times. When replicated sites are separated by very large distances, some hardware solutions cannot match the low latency requirement. This requirement comes as the solution is shifting focus from a failover solution to a near continuous availability solution.
- Replicates only the necessary subset of the data. This option delivers tight control over access to critical data as data is available only where it needs to be.
- Supports application-level granularity. Critical workloads have access to their data immediately (at a primary site) while non-critical workloads can be routed to a replicated site.
- Supports read/write access at all replicated sites (with tight control over update of the data.