The only book on high availability for DB2, straight from IBM, this single source covers all aspects of database availability including configuration and tuning information, and teaches database administrators how to set up their DB2 system to meet availability and cost requirement needs.

As organizations strive to do more with less, IBM® DB2® for Linux, UNIX, and Windows provides various built-in high availability features. DB2 further provides high availability solutions by using enterprise system resources with broad support for clustering software, such as IBM PowerHA® SystemMirror®, IBM Tivoli® System Automation for Multiplatforms (Tivoli SA MP), and Microsoft Windows Cluster Server. This IBM Redbooks® publication describes the DB2 high availability functions and features, focusing on High Availability Disaster Recovery (HADR) in the OLTP environment. The book provides a detailed description of HADR, including setup, configuration, administration, monitoring, and preferred practices. This book explains how to configure Cluster software PowerHA, Tivoli SA MP, and MSCS with DB2 and show how to use these products to automate HADR takeover. DB2 also provides unprecedented enterprise-class disaster recovery capability. This book covers single system view backup, backup and restore with snapshot backup, and the db2recovery command, in detail. This book is intended for database administrators and information management professionals who want to design, implement, and support a highly available DB2 system.

The Temenos T24 core banking application is a critical application for the banks that use it and has a primary focus on providing an appropriate level of high availability and disaster recovery. The level of availability is determined largely by the configuration of the infrastructure that supports T24. This infrastructure is built on hardware, middleware, and networking, in addition to the operational procedures and practices that are used to operate T24. Many options are available for meeting a client's high availability and disaster recovery requirements. The solution chosen by a Temenos T24 user depends on many factors. These factors include a user's detailed availability and recovery requirements; their existing datacenter standards, practices, and processes; and the available network infrastructure. Therefore, the optimum solution must be determined on a case-by-case basis for each deployment. This IBM® RedpaperTM publication serves as a guide to help IT architects and other technical staff who are designing, configuring, and building the infrastructure to support Temenos T24. It shows how IBM software can deliver high availability and disaster recovery for Temenos T24 to meet a client's requirements. This software might run on IBM AIX®, IBM WebSphere® Application Server, WebSphere MQ Server, and IBM DB2®. These IBM software components are typically used for a Temenos T24 deployment on an IBM middleware stack to ensure a highly available infrastructure for T24.

IBM® Db2® Analytics Accelerator is a workload optimized appliance add-on to IBM DB2® for IBM z/OS® that enables the integration of analytic insights into operational processes to drive business critical analytics and exceptional business value. Together, the Db2 Analytics Accelerator and DB2 for z/OS form an integrated hybrid environment that can run transaction processing, complex analytical, and reporting workloads concurrently and efficiently. With IBM DB2 Analytics Accelerator for z/OS V7, the following flexible deployment options are introduced: Accelerator on IBM Integrated Analytics System (IIAS): Deployment on pre-configured hardware and software Accelerator on IBM Z®: Deployment within an IBM Secure Service Container LPAR For using the accelerator for business-critical environments, the need arose to integrate the accelerator into High Availability (HA) architectures and Disaster Recovery (DR) processes. This IBM RedpaperTM publication focuses on different integration aspects of both deployment options of the IBM Db2 Analytics Accelerator into HA and DR environments. It also shares best practices to provide wanted Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO). HA systems often are 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. IBM 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. IBM Parallel Sysplex® and IBM Globally Dispersed Parallel Sysplex (IBM 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 V7 can easily integrate into or complement existing IBM Z topologies for HA and DR. If you are using IBM Db2 Analytics Accelerator V5.1 or lower, see IBM Db2 Analytics Accelerator: High Availability and Disaster Recovery, REDP-5104.

This IBM Redbooks publication addresses the challenges posed by monitoring high availability, scalability, and performance in an SAP sysplex data sharing environment. It introduces the motivations for utilizing a design based on DB2 data sharing. It includes the principal SAP-DB2 data sharing architecture options and trade-offs used in the industry today and issues that play a role in both high availability and scalability, such as failover design, database connectivity design, workload splitting and load balancing, MCOD, and coupling facility design. The book discusses single point of failure, important failover scenarios and outage avoidance, automation of high availability constructs, and backup and recovery considerations in data sharing environments. Performance issues are detailed in the order you would approach them at planning and implementation time. First, it discusses tuning the sysplex, which is the base for a well-performing DB2 data sharing system, then tuning the DB2 data sharing system, which is the base for a well-performing SAP system, and finally, tuning the SAP system. The book focuses on initial planning for performance and monitoring it afterward, and explains the key points to look for to health-check your system and maintain high performance.

This IBM Redbooks publication describes and demonstrates common, prescriptive scenarios for setting up disaster recovery for common workloads using IBM WebSphere Application Server, IBM DB2, and WebSphere MQ between two IBM PureApplication System racks using the features in PureApplication System V2. The intended audience for this book is pattern developers and operations team members who are setting up production systems using software patterns from IBM that must be highly available or able to recover from a disaster (defined as the complete loss of a data center).