With the introduction of IBM® DB2® Analytics Accelerator, IBM enhanced DB2 for z/OS® capabilities to efficiently process long-running, analytical queries. Consequentially, the need arose to integrate the accelerator into existing High Availability (HA) architectures and Disaster Recovery (DR) processes. This paper focuses on different integration aspects of the IBM DB2 Analytics Accelerator into existing HA and DR environments and shares best practices to provide wanted Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO).
HA systems are usually a requirement in business critical environments and can be implemented by redundant, independent components. A failure of one of these components is detected automatically and their tasks are taken over by another component. Depending on business requirements, a system can be implemented in a way that users do not notice outages (continuous availability), or in a major disaster, users notice an outage and systems resume services after a defined period, potentially with loss of data from previous work.
System z® was strong for decades regarding HA and DR. By design, storage and operating systems are implemented in a way to support enhanced availability requirements. Parallel Sysplex® and Globally Dispersed Parallel Sysplex (GDPS®) offer a unique architecture to support various degrees of automated failover and availability concepts.
This IBM Redpaper® publication shows how IBM DB2 Analytics Accelerator can easily complement existing System z topologies for HA and DR.
Table of contents