Infosphere Data Replication For Db2 For Z Os And Websphere Message Queue For Z Os Performance Lessons
Download Infosphere Data Replication For Db2 For Z Os And Websphere Message Queue For Z Os Performance Lessons PDF/ePub or read online books in Mobi eBooks. Click Download or Read Online button to get Infosphere Data Replication For Db2 For Z Os And Websphere Message Queue For Z Os Performance Lessons book now. This website allows unlimited access to, at the time of writing, more than 1.5 million titles, including hundreds of thousands of titles in various foreign languages.
InfoSphere Data Replication for DB2 for z/OS and WebSphere Message Queue for z/OS: Performance Lessons
Understanding the impact of workload and database characteristics on the performance of both DB2®, MQ, and the replication process is useful for achieving optimal performance.Although existing applications cannot generally be modified, this knowledge is essential for properly tuning MQ and Q Replication and for developing best practices for future application development and database design. It also helps with estimating performance objectives that take these considerations into account. Performance metrics, such as rows per second, are useful but imperfect. How large is a row? It is intuitively, and correctly, obvious that replicating small DB2 rows, such as 100 bytes long, takes fewer resources and is more efficient than replicating DB2 rows that are tens of thousand bytes long. Larger rows create more work in each component of the replication process. The more bytes there are to read from the DB2 log, makes more bytes to transmit over the network and to update in DB2 at the target. Now, how complex is the table definition? Does DB2 have to maintain several unique indexes each time a row is changed in that table? The same argument applies to transaction size: committing each row change to DB2 as opposed to committing, say, every 500 rows also means more work in each component along the replication process. This RedpaperTM reports results and lessons learned from performance testing at the IBM® laboratories, and it provides configuration and tuning recommendations for DB2, Q Replication, and MQ. The application workload and database characteristics studied include transaction size, table schema complexity, and DB2 data type.
End-to-End High Availability Solution for System z from a Linux Perspective
As Linux on System z becomes more prevalent and mainstream in the industry, the need for it to deliver higher levels of availability is increasing. This IBM Redbooks publication starts with an explanation of high availability (HA) fundamentals such as HA concepts and terminology. It continues with a discussion of why a business needs to consider an HA solution and then explains how to determine your business single points of failure. We outline the components of a high availability solution and describe these components. Then we provide some architectural scenarios and demonstrate how to plan and decide an implementation of an end-to-end HA solution, from Linux on System z database scenarios to z/OS, and include storage, network, z/VM, Linux, and middleware. This implementation includes the IBM Tivoli System Automation for Multiplatforms (TSA MP), which monitors and automates applications distributed across Linux, AIX®, and z/OS® operating systems, as well as a GDPS based solution. It includes the planning for an end-to-end scenario, considering Linux on System z, z/VM, and z/OS operating environments, and the middleware used. The TSA MP implements HA for infrastructure, network, operating systems, and applications across multiple platforms and is compared to a Linux HA implementation based on open source Linux-HA, which is Linux only.
The Value of Active-Active Sites with Q Replication for IBM DB2 for z/OS An Innovative IBM Client's Experience
Any business interruption is a potential loss of revenue. Achieving business continuity involves a tradeoff between the cost of an outage or data loss with the investment required for achieving the recovery point objective (RPO) and recovery time objective (RTO). Continuous system availability requires scalability, as well as failover capability for maintenance, outages, and disasters. It also requires a shift from standby to active-active systems. Active-active sites are geographically distant transaction processing centers, each with the infrastructure to run business operations and with data synchronized by using database replication, such as the Q Replication technology that is part of IBM® InfoSphere® Data Replication software. This IBM Redbooks® publication describes preferred practices and introduces an architecture for continuous availability and disaster recovery that is used by a very large business institution that runs its core business on IBM DB2® for z/OS® databases. This paper explains the technologies and procedures that are required for the implementation of an active-active sites architecture. It also explains an innovative procedure for major IT upgrades that uses Q Replication for DB2 on z/OS, Multi-site Workload Lifeline, and Peer-to-Peer Remote Copy/Extended Distance (PPRC-XD). This paper is of value to decision makers, such as executive and IT architects, and to database administrators who are responsible for design and implementation of the solution.