Download Free Db2 10 For Linux On System Z Using Z Vm V62 Single System Image Clusters And Live Guest Relocation Book in PDF and EPUB Free Download. You can read online Db2 10 For Linux On System Z Using Z Vm V62 Single System Image Clusters And Live Guest Relocation and write the review.

IBM® z/VM® 6.2 introduced significant changes to z/VM with a multi-system clustering technology that allows up to four z/VM instances in a single system image (SSI) cluster. This technology is important because it offers you an attractive alternative to vertical growth by adding new z/VM systems. In the past, this capability required duplicate efforts to install, maintain, and manage each system. With SSI, these duplicate efforts are reduced or eliminated. Support for live guest relocation (LGR) allows you to move Linux virtual servers without disrupting your business or incurring loss of service, thus reducing planned outages. The z/VM systems are aware of each other and take advantage of their combined resources. LGR enables you to relocate guests from a system requiring maintenance to a system that will remain active during maintenance. A major advantage for DB2 v10 customers is that using z/VM 6.2 does not require any changes to existing DB2 structures. This remarkable benefit is due to the fact that DB2 v10 is installed as part of the LInux guest on z/VM and is fully integrated into LGR. This allows you to smoothly move DB2 v10 when you move Linux virtual servers, without interrupting either DB2 v10 or z/VM operations and services. This IBM Redbooks® publication will help you understand how DB2 10 on Linux for System z® behaves while running on a z/VM that is being relocated using z/VM's 6.2 Live Guest Relocation feature. In this book, we explore memory management, the DB2 Self-tuning memory manager feature, time synchronization, networking, and storage and performance considerations with regards to relocation. We also offer some best practices found during a live guest relocation for DB2 v10.
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.
This book was written by IBM® IT specialists who have experience implementing IBM Z® solutions, especially Linux on IBM LinuxONETM (LinuxONE) or IBM Z servers. Therefore, the content of this book follows the guidelines from Linux and IBM z/VM® regarding LinuxONE and IBM Z installations. The preferred practices described in this book are gathered from the experiences of those specialists in hundreds of projects at IBM and customer environments. This publication provides you with all of the information that you need to decide the best scaling architecture when implementing Linux on IBM Z or LinuxONE. This book has the following goals: To inform you about x86 sprawl problems To inform you that x86 Vertical Scale out architectures are problematic going forward To provide solutions to x86 server sprawl problems To inform you about the LinuxONE and IBM Z differentiation for each x86 server sprawl problem To provide virtulization and security options for LinuxOne and IBM Z The scaling up and scaling out architectures enable you to scale the capacity of an existing system to attend a sporadic application demand or an application workload. This gives you some freedom to operate in the environment. However, if this activity is performed without correct planning and the correct architecture choice, it leads to a server sprawl situation where your environment houses more servers than it should based on its current and predicted requirements. Although scaling out on x86 systems is a common form of scaling because of their popularity, the x86 systems were originally designed as cheap computers. Unfortunately, the scale out on x86 can easily become a problem in terms of total cost of ownership (TCO) when the environment starts to increase in terms of number of physical servers. The LinuxONE and IBM Z servers solve the sprawl problem caused by the scaling out of x86 servers, and are an excellent choice for cloud, mobile, big data, blockchain, analytics, and other workloads that require a robust and flexible environment. This publication describes the advantages and disadvantages of the scaling options. The audience of this publication consists of the following groups: Customers, IBM Business Partners, and IBM consultants planning and installing Linux on IBM Z, IBM Z family or x86 platform System administrators administering the Linux Systems If you are a customer considering LinuxONE and IBM Z family as a platform for your applications (analytics, blockchain, cloud, or other) or a pre-sales person, read those publications.
This IBM® Redbooks® publication shows the power of IBM System z® virtualization and flexibility in sharing resources in a flexible production environment. In this book, we outline the planning and setup of Linux on System z to move from a development or test environment into production. As an example, we use one logical partition (LPAR) with shared CPUs with memory for a production environment and another LPAR that shares some CPUs, but also has a dedicated one for production. Running in IBM z/VM® mode allows for virtualization of servers and based on z/VM shares, can prioritize and control their resources. The size of the LPAR or z/VM resources depends on the workload and the applications that run that workload. We examine a typical web server environment, Java applications, and describe it by using a database management system, such as IBM DB2®. Network decisions are examined with regards to VSWITCH, shared Open Systems Adapter (OSA), IBM HiperSocketsTM and the HiperPAV, or FCP/SCSI attachment used with a storage area network (SAN) Volume Controller along with performance and throughput expectations. The intended audience for this IBM Redbooks publication is IT architects who are responsible for planning production environments and IT specialists who are responsible for implementation of production environments.
This IBM® Redbooks® publication is Volume 3 of a series of three books called The Virtualization Cookbook for IBM z Systems. The other two volumes are called: The Virtualization Cookbook for IBM z Systems Volume 1: IBM z/VM 6.3, SG24-8147 The Virtualization Cookbook for IBM z Systems Volume 2: Red Hat Enterprise Linux 7.1 Servers, SG24-8303 It is suggested that you start with Volume 1 of this series, because IBM z/VM® is the base "layer" when installing Linux on IBM z SystemsTM. Volume 1 starts with an introduction, describes planning, and then describes z/VM installation into a two-node, single system image (SSI) cluster, configuration, hardening, automation, and servicing. It adopts a cookbook format that provides a concise, repeatable set of procedures for installing and configuring z/VM using the SSI clustering feature. Volumes 2 and 3 describe how to roll your own Linux virtual servers on z Systems hardware under z/VM. The cookbook format continues with installing and customizing Linux. Volume 3 focuses on SUSE Linux Enterprise Server 12. It describes how to install and configure SUSE Linux Enterprise Server 12 onto the Linux administration system, which does the cloning and other tasks. It also explains how to use AutoYaST2, which enables you to automatically install Linux using a configuration file, and explains how to create and use appliances and bootable images from configuration files. In addition, it provides information about common tasks and tools available to service SUSE Linux Enterprise Server.
Data is one the most critical and valuable assets of a business. Critical strategic decisions can be made more quickly and effectively when they are based on complete, accurate, and timely operational data. From this point of view, it is important to have an enterprise data management architecture that supports a flexible global view of the business. Many environments today are heterogeneous with a high quantity and diversity of data. In this IBM® Redbooks® publication, we help enterprise architects and IT managers with these environments make decisions for a centralized database or data warehouse. We recommend a centralized data management environment on Linux® on System z®. We include guidance for IBM z/VSETM and Linux specialists to reorganize existing IBM DB2® VSE data and build a database environment with continuous operation in Linux on System z. We begin this book by describing the possibilities and advantages of enterprise data management and different technical ways to realize it. Then we discuss planning, which is important for setting the foundation of the architecture that is implemented. We explain the hardware considerations for capacity and performance planning. For the z/VSE system and Linux on System z, we describe considerations for operation in a logical partition (LPAR) and in a virtualized environment with IBM z/VM®. In addition, we discuss the disk behavior for different workloads, storage dependencies, network connections, and DB2 database considerations. We also guide you in customizing the DB2 server for z/VSE, z/VM, and DB2 on Linux to allow existing z/VSE and z/VM applications to access the database on Linux on System z. We include the data migration, application considerations, dependencies, compatibility, monitoring, and tuning possibilities in such an environment.
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.
As business cycles speed up, many customers gain significant competitive advantage from quicker and more accurate business decision-making by using real data. For many customers, choosing the path to co-locate their transactional and analytical workloads on System z® better leverages their existing investment in hardware, software, and skills. We created a project to address a number of best practice questions on how to manage these newer, analytical type workloads, especially when co-located with traditional transactional workloads. The goal of this IBM® Redbooks® publication is to provide technical guidance and performance trade-offs associated with resource management and potentially DB2® data-sharing in a variety of mixed transactional / data warehouse System z topologies. The term co-location used here and in the rest of the book is specifically defined as the practice of housing both transactional (OLTP) and data warehouse (analytical) workloads within the same System z configuration. We also assumed that key portions of the transactional and data warehouse databases would reside on DB2 for z/OS®. The databases may or may not reside in a DB2 data-sharing environment; we discuss those pros and cons in this book. The intended audience includes DB2 data warehouse architects and practitioners who are facing choices in resource management and system topologies in the data warehouse arena. This specifically includes Business Intelligence (BI) administrators, DB2 database administrators (DBAs) and z/OS performance administrators / systems programmers. In addition, decision makers and architects can utilize this book to assist in making platform and database topology decisions. The book is divided into four parts. Part I, "Introducing the co-location project" covers the System z value proposition and why one should consider System z as the central platform for their data warehousing / business analytics needs. Some topics are risk avoidance via data consolidation, continuous availability, simplified disaster recovery, IBM Smart Analytics Optimizer, reduced network bandwidth requirements, and the unique virtualization and resource management capabilities of System z LPAR, z/VM® and WLM. Part I also provides some of the common System z co-location topologies along with an explanation of the general pros and cons of each. This would be useful input for an architect to understand where a customer is today and where they might consider moving to. Part II, "Project environment" covers the environment, products, workloads, workload drivers, and data models implemented for this study. The environment consisted of a logically partitioned z10TM 32way, running z/VM, Linux®, and z/OS operating system instances. On those instances we ran products such as z/OS DB2 V9, IBM Cognos® Business Intelligence Version 8.4 for Linux on System z, InfoSphereTM Warehouse for System z, InfoSphere Change Data Capture, z/OS WebSphere® V7, Tivoli® Omegamon for DB2 Performance expert. Utilizing these products we created transactional (OLTP), data warehouse query, and data warehouse refresh workloads. All the workloads were based on an existing web-based transactional Bookstore workload, that's currently utilized for internal testing within the System p® and z labs. While some IBM Cognos BI and ISWz product usage and experiences information is covered in this book, we do not go into the depth typically found in IBM Redbooks publications, since there's another book focused specifically on that
This IBM Redbooks publication discusses running Linux under z/VM on IBM System z9 and zSeries platforms. We describe enhancements available in z/VM Version 5.1. The intended audience for this book is IT administrators responsible for installing and configuring z/VM 5.1 systems running Linux guests. Using Fibre Channel Protocol (FCP), z/VM 5/1 can be installed on and operate from SCSI disks. Configured as emulated Fixed Block Architecture (FBA) disks, z/VM 5.1 can use FCP-attached disks for its system paging, spooling, directory, and minidisks. z/VM 5.1 adds new functions for Virtual Switches (VSWITCH). For increased network security, guests must have authorization before connecting to a VSWITCH. z/VM 5.1 introduces VSWITCH Layer 2 support. Operating at Layer 2, a VSWITCH delivers and receives network traffic in Ethernet frames. This provides the ability to handle non-IP protocols such as SNA, NetBIOS, and IPX. In addition, Layer 2 support reduces network latency and CPU overhead.