DOCSLIB.ORG

Oracle Database Service HA with Data Guard

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Oracle Database Service HA with Data Guard Oracle Database Service High Availability with Data Guard? Robert Bialek Senior Principal Consultant @RobertPBialek doag2017 Who Am I Senior Principal Consultant and Trainer at Trivadis GmbH in Munich. – Master of Science in Computer Engineering. – At Trivadis since 2004. – Trivadis Partner since 2012. Focus: – Data and Service High Availability, Disaster Recovery. – Architecture Design, Optimization, Automation. – New Technologies (Trivadis Technology Center). – Open Source. – Technical Project Leadership. – Trainer: O-GRINF, O-RAC, O-DG. 2 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Our company. Trivadis is a market leader in IT consulting, system integration, solution engineering and the provision of IT services focusing on and technologies in Switzerland, Germany, Austria and Denmark. We offer our services in the following strategic business fields: O P E R A T I O N Trivadis Services takes over the interacting operation of your IT systems. 3 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? With over 600 specialists and IT experts in your region. COPENHAGEN 14 Trivadis branches and more than 600 employees. HAMBURG 200 Service Level Agreements. Over 4,000 training participants. Research and development budget: DÜSSELDORF CHF 5.0 million. FRANKFURT Financially self-supporting and sustainably profitable. STUTTGART Experience from more than 1,900 FREIBURG VIENNA MUNICH projects per year at over 800 BRUGG customers. BASEL ZURICH BERN GENEVA LAUSANNE 4 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Technology on its own won't help you. You need to know how to use it properly. 5 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Database Service High Availability – Goal Increase database service uptime, by: – eliminating any single point of failure to avoid unplanned outages. – minimizing the effect of an unplanned outage on the end user (automatic failover). – reducing downtimes during planned outages. Consider the whole SW/HW stack. Find the best cost/risk ratio. Effort Downtime Costs Database Application Complexity Storage Clients Server(s) Server(s) Best cost/risk ratio Availability 6 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Database Service High Availability – Options HA Cluster – primarily used option for service high availability: – Real Application Clusters. SPOF – RAC One Node. – Cold Failover Cluster. HA Data Replication – used mostly for data, rather than service high availability: – Data Guard (Fast-Start Failover/Global Data Services). – GoldenGate (Global Data Services). – Other replication technologies. HA 7 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Agenda 1. Introduction 2. Configuration 3. Special Cases 4. Conclusions 8 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Introduction 9 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Database Service HA with Data Guard? – Introduction Data Guard Yes, it can also be used for service high availability: – Planned downtimes – manual switchover. – Unplanned downtimes – fast-start failover or manual failover. Primary Standby FSFO Configuration Why might we consider Data Guard for service high availability: – Less complex than a cluster installation. – Infrastructure requirements not that high (even local storage is sufficient). – Not subject to additional license fees (EE license assumed). – Additionally, many other advantages: data high availability, snapshot standby, potentially rolling upgrade capability, ... But, with some restrictions we need to consider... 10 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Database Service HA with Data Guard? – Big Picture Backup Observers (optional, 12.2) Database Clients Master Observer Required Ping Ping Ping Primary RW Service Transparency required (failover/ switchover) ... Primary Target Candidate Target Failover Standbys Failover Standby (optional, 12.2) 11 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Database Service HA with Data Guard? – Monitoring Observer Failover condition detected Reconnect interval expired Logoff Timeout ObserverReconnect DGMGRL – Threads property set and reached Connect Failover re-tries W000 B001 P001 S001 SLEEP SLEEP ~ 3sec. Connect ~ 3sec. Enter PING State PING PING PRIMARY TARGET STANDBY 12 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Configuration 13 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Data Guard Protection Modes with FSFO – Prerequisites FSFO: Guaranted zero data FSFO: Data loss possible. FSFO: Guaranted zero data loss. loss. MaxAvailability (10.2+) MaxPerformance (11.1+) MaxProtection (12.2) ▪ LogXptMode=SYNC or ▪ LogXptMode=ASYNC ▪ LogXptMode=SYNC FASTSYNC (12.1+) ▪ FastStartFailoverTarget(*) ▪ FastStartFailoverTarget(*) ▪ FastStartFailoverTarget(*) ▪ FastStartFailoverLagLimit ▪ Flashback Database ▪ Flashback Database ▪ Flashback Database ▪ Recommended: at least 2 STDBY DBs (protection Mostly used mode downgrade!) protection mode All Protection Modes DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverThreshold = <xy>; DGMGRL> ENABLE FAST_START FAILOVER; Value in seconds 14 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Observer Fast-Start Failover – Observer (1) Ping Monitoring component, initiates a failover procedure. In 12.2, up to 3 observers (in background) can be started: W000 B001 P001 S001 – One master and up to two backup (standby) observers. PRIMARY TARGET DGMGRL> START OBSERVER OBS1.TRIVADIS.COM IN BACKGROUND Failover Standby FILE IS '$ADMIN_SID/fsfo_$ORACLE_SID.dat' LOGFILE IS '$ADMIN_SID/fsfo_$ORACLE_SID.log' CONNECT IDENTIFIER IS <Alias1>.TRIVADIS.COM; Oracle wallet required In older releases: – Only one running observer (HA needs to be adressed). nohup dgmgrl -logfile $ADMIN_SID/fsfo_$ORACLE_SID.log <<EOD & CONNECT $CONNECT_DATA START OBSERVER FILE='$ADMIN_SID/fsfo_$ORACLE_SID.dat'; EOD 15 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Observer Fast-Start Failover – Observer (2) Ping Fast start-failover is initiated by the master observer to the target standby database, if one of the following W000 B001 conditions is detected: P001 S001 – observer and the target standby database cannot reach PRIMARY TARGET the primary database (default: ObserverOverride=‘FALSE‘). Failover Standby – user-configurable condition is met. – DBMS_DG.INITIATE_FS_FAILOVER function has been executed. Additonally, other pre-condidtions enforced by a protection mode need to be fulfilled: – MaxProtection/MaxAvailability: target failover standby is in SYNC. – MaxPerformance: FastStartFailoverLagLimit not reached for the target failover standby. 16 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Data Guard: Role-Based Services For a Data Guard system, we need a role-based service, Database Clients that is running only if database has a specific role: – Read-write service on a primary database. – Optionally, a service on standby databases for reporting. ? – Optionally, a service on snapshot standby databases. To accomplish this task: Service Service – Use Oracle Grid Infrastructure role-based services. R/W R/O [SNAP] – Create your own AFTER STARTUP ON DATABASE trigger. 17 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Data Guard: Example Role-Based Services Example role-based services with Grid Infrastructure. srvctl add service -db DB_SITE1 –service SRV_RW.trivadis.com -role PRIMARY srvctl add service -db DB_SITE1 –service SRV_RO.trivadis.com -role PHYSICAL_STANDBY srvctl add service -db DB_SITE1 -service SRV_SP.trivadis.com -role SNAPSHOT_STANDBY Services are started only if database and service role match. SvcAgent::start 680 query_db_role SvcAgent::start 710 not starting service srv_rw Role mismatch - Service role:PRIMARY, current DB role:PHYSICAL_STANDBY Depending on used client HA features (TAF, FAN/FCF, AC) additional service properties need to be specified. 18 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? Client-Side Configuration – Main Problems To Address CASE 1 CASE 2 New network session (connect) Already established network session Database Clients Database Clients 2 Connect attempts 4 Client failover 1 Connected 5 Client failover 3 Re-connect attempts 3 Wait for Problem Problem connect timeout 4 Wait for Problem re-connect timeout Problem 1 IP not reachable (server/network/… issue) 2 IP not reachable (server/network/… issue) 19 23.11.2017 Trivadis DOAG17: Oracle Database Service High Availability with Data Guard? New Oracle Net Session – Connect Timeout (1) 1 sqlnet.ora parameters (OCI, ODP.net) – Applies to each IP that a host name resolves to! – All Oracle client versions supported. LSNR LSNR TCP.CONNECT_TIMEOUT=3 #default 60 sec. 2 Oracle Net SQLNET.OUTBOUND_CONNECT_TIMEOUT=5 #no default Three-way handshake 3 For clients >=11.2: OLTP.trivadis.com = (DESCRIPTION = (FAILOVER=ON) (LOAD_BALANCE=OFF) Introduced in 12.1.0.2 (CONNECT_TIMEOUT=5)(RETRY_COUNT=3)(RETRY_DELAY=1)(TRANSPORT_CONNECT_TIMEOUT=3) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP )(HOST = italy )(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP
Load more

Recommended publications
  • 8. IBM Z and Hybrid Cloud
    The Centers for Medicare and Medicaid Services The role of the IBM Z® in Hybrid Cloud Architecture Paul Giangarra – IBM Distinguished Engineer December 2020 © IBM Corporation 2020 The Centers for Medicare and Medicaid Services The Role of IBM Z in Hybrid Cloud Architecture White Paper, December 2020 1. Foreword ............................................................................................................................................... 3 2. Executive Summary .............................................................................................................................. 4 3. Introduction ........................................................................................................................................... 7 4. IBM Z and NIST’s Five Essential Elements of Cloud Computing ..................................................... 10 5. IBM Z as a Cloud Computing Platform: Core Elements .................................................................... 12 5.1. The IBM Z for Cloud starts with Hardware .............................................................................. 13 5.2. Cross IBM Z Foundation Enables Enterprise Cloud Computing .............................................. 14 5.3. Capacity Provisioning and Capacity on Demand for Usage Metering and Chargeback (Infrastructure-as-a-Service) ................................................................................................................... 17 5.4. Multi-Tenancy and Security (Infrastructure-as-a-Service) .......................................................
    [Show full text]
  • Ipswitch Failover V9.5 Administrator's Guide
    Administrator's Guide For Ipswitch Failover v9.5 Copyright ©1991-2016 Ipswitch, Inc. All rights reserved. This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the express prior written consent of Ipswitch, Inc. The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Ipswitch, Inc. While every effort has been made to assure the accuracy of the information contained herein, Ipswitch, Inc. assumes no responsibility for errors or omissions. Ipswitch, Inc., also assumes no liability for damages resulting from the use of the information contained in this document. WS_FTP, the WS_FTP logos, Ipswitch, and the Ipswitch logo, MOVEit and the MOVEit logo, MessageWay and the MessageWay logo are trademarks of Ipswitch, Inc. Other products and their brands or company names, are or may be trademarks or registered trademarks, and are the property of their respective companies. Contents Preface: About This Book.........................................................................vii Part I: Getting Started..................................................................................9 Chapter 1: Ipswitch Failover Concepts.................................................................................11
    [Show full text]
  • Setup for Failover Clustering and Microsoft Cluster Service
    Setup for Failover Clustering and Microsoft Cluster Service Update 1 VMware vSphere 6.5 VMware ESXi 6.5 vCenter Server 6.5 Setup for Failover Clustering and Microsoft Cluster Service You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation, submit your feedback to [email protected] VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com © Copyright 2006-2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents About Setup for Failover Clustering and Microsoft Cluster Service 5 1 Getting Started with MSCS 6 Clustering Configuration Overview 6 Clustering MSCS Virtual Machines on a Single Host 7 Clustering Virtual Machines Across Physical Hosts 7 Clustering Physical Machines with Virtual Machines 9 Hardware and Software Requirements for Clustering 10 Supported Shared Storage Configurations 10 PSP_RR Support for MSCS 11 iSCSI Support for MSCS 11 FCoE Support for MSCS 12 vMotion support for MSCS 12 vSphere MSCS Setup Limitations 13 MSCS and Booting from a SAN 14 Set up CCR and DAG Groups 14 Setting up AlwaysOn Availability Groups with SQL Server 2012 15 2 Cluster Virtual Machines on One Physical Host 16 Create the First Node for Clusters on One Physical Host 16 Create Additional Nodes for Clusters on One Physical Host 17 Add Hard Disks to the First Node for Clusters on One Physical Host 18 Add Hard Disks to Additional Nodes for Clusters on One Physical Host 19 3 Cluster Virtual Machines Across
    [Show full text]
  • A High Availability Clusters Model Combined with Load Balancing and Shared Storage Technologies for Web Servers
    International Journal of Grid Distribution Computing Vol.8, No.1 (2015), pp.109-120 http://dx.doi.org/10.14257/ijgdc.2015.8.1.11 A High Availability Clusters Model Combined with Load Balancing and Shared Storage Technologies for Web Servers A. B. M. Moniruzzaman, Md. Waliullah, Md. Sadekur Rahman Departement of Computer Science and Engineering, Daffodil International University [email protected], [email protected], [email protected] Abstract This paper designs and implements a high availability clusters and incorporated with load balance infrastructure of web servers. The paper described system can provide full facilities to the website hosting provider and large business organizations. This system can provide continuous service though any system components fail uncertainly with the help of Linux Virtual Server (LVS) load-balancing cluster technology and combined with virtualization as well as shared storage technology to achieve the three-tier architecture of Web server clusters. This technology not only improves availability, but also affects the security and performance of the application services being requested. Benefits of the system include node failover overcome; network failover overcome; storage limitation overcome and load distribution. Keywords: Linux Virtual Server (LVS), load-balancing, high availability clusters, Web server clusters, failover 1. Introduction This is a system which can provide full facilities to the website hosting provider and large business organizations High Availability Cluster with Load Balancing” is such a system, which can provide continuous service though any system components fail uncertainly. Without clustering, a server running a particular application as when that particular server crashes, the application will be unavailable until the crashed server is fixed.
    [Show full text]
  • Introduction to the New Mainframe: Networking
    Front cover Introduction to the New Mainframe: Networking Concepts of mainframe-based data communications Methods for implementing TCP/IP and SNA on z/OS Basic skills in network operations, security, and problem determination Christopher Hastings Matt Nuttall Micky Reichenberg ibm.com/redbooks International Technical Support Organization Introduction to the New Mainframe: Networking August 2006 SG24-6772-00 Note: Before using this information and the product it supports, read the information in “Notices” on page 329. First Edition (August 2006) This edition applies to Version 1, Release 7, Modification 0 of z/OS (5694-A01). © Copyright International Business Machines Corporation 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. iii iv Introduction to the New Mainframe: Networking Contents Preface . xiii How this text is organized . xiv How each chapter is organized . xv The team that wrote this redbook. xvi Comments welcome. xvii Part 1. Introduction to networking on the mainframe . 1 Chapter 1. Mainframes and networks . 3 1.1 Mainframes, networks, and you . 4 1.2 Networks and online systems . 5 1.3 Why are networks important? . 7 1.4 Examples of mainframe-based networks . 7 1.4.1 ATM cash withdrawal . 8 1.4.2 Credit purchase at a retail store . 9 1.4.3 Technology choices abound in network technology . 9 1.5 Who supports the network?. 10 1.6 What are the basic elements of a network? . 11 1.7 Overview of mainframe network capabilities . 12 1.7.1 z/OS Communications Server.
    [Show full text]
  • High Availability Overview
    IBM i Version 7.2 Availability High availability overview IBM IBM i Version 7.2 Availability High availability overview IBM Note Before using this information and the product it supports, read the information in “Notices” on page 37. This edition applies to IBM i 7.2 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright IBM Corporation 2002, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents High availability overview ....... 1 | Logical replication .......... 20 | What's new for IBM i 7.2 .......... 1 | Switched disk ........... 21 PDF file for High availability overview ..... 2 | Switched logical unit ......... 21 Benefits of high availability ......... 3 | Geographic mirroring ......... 22 Planned outages ............ 3 | Metro Mirror ............ 24 Unplanned outages ........... 4 | Global Mirror............ 24 Disaster recovery ............ 4 | DS8000 Full System HyperSwap ..... 25 Backup window reduction ......... 5 | DS8000 HyperSwap with independent Load balancing ............ 6 | auxiliary storage pools (IASPs) ...... 26 High availability criteria .......... 7 | Use Case scenario's ......... 26 Budget ............... 7 | FlashCopy ............. 31 Uptime requirements .......... 7 | HA Technologies combined ........ 32 Outage coverage ............ 8 | High availability management ....... 32 Recovery time objective (RTO) ....... 9 | IBM PowerHA SystemMirror for i interfaces 32 Recovery point objective (RPO) ....... 9 | PowerHA graphical interface ..... 33 Resilience requirements .........
    [Show full text]
  • Failover and Load Sharing in SIP Telephony
    Failover and Load Sharing in SIP Telephony Kundan Singh and Henning Schulzrinne Department of Computer Science, Columbia University kns10,hgs @cs.columbia.edu f g Abstract We apply some of the existing web server redundancy techniques for high service availability and scalability to the relatively new IP telephony context. The paper compares various failover and load sharing methods for registration and call routing servers based on the Session Initiation Protocol (SIP). In particular, we consider the SIP server failover techniques based on the clients, DNS (Domain Name Service), database replication and IP address takeover, and the load sharing techniques using DNS, SIP identifiers, network address translators and servers with same IP addresses. Additionally, we present an overview of the failover mechanism we implemented in our test-bed using our SIP proxy and registration server and the open source MySQL database. Keywords: Availability; scalability; failover; load sharing; SIP Contents 1 Introduction 2 2 Related Work 3 3 High Availability: Failover 4 3.1Client-basedfailover......................................... 4 3.2DNS-basedfailover.......................................... 4 3.3 Failover based on database replication . 5 3.4FailoverusingIPaddresstakeover................................. 5 3.5 Reliable server pooling . 6 4 Scalability: Load sharing 8 4.1DNS-basedloadsharing....................................... 8 4.2Identifier-basedloadsharing..................................... 9 4.3Networkaddresstranslation..................................... 9 4.4ServerswiththesameIPaddress.................................. 9 5 Implementation 11 6 Conclusions and Future Work 13 7 Acknowledgment 14 A Two-way replication in MySQL 15 1 1 Introduction The Session Initiation Protocol (SIP) [1] is a distributed signaling protocol for IP telephony. The SIP- based telephony services have been proposed as an alternative to the classical PSTN (public switched tele- phone network) and offers a number of advantages over the PSTN [2].
    [Show full text]
  • Administrator Guide Vmware Vcenter Server Heartbeat V6.4 Update 1
    Administrator Guide VMware vCenter Server Heartbeat 6.4 Update 1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-000728-00 Administrator Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] Copyright © 2009-2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 7 Getting Started 1 Introduction 11 vCenter Server Heartbeat Concepts 11 Architecture Overview 11 vCenter Server Heartbeat Protection Levels 12 vCenter Server Heartbeat Communications 15 vCenter Server Heartbeat Switchover and Failover Processes 16 2 Configuring vCenter Server Heartbeat 19 Server Configuration Wizard 19 Configuring the Machine 20 Configuring the Channel 20 Configuring Public IP Addressing
    [Show full text]
  • Getting Started with IBM Z Resiliency
    Front cover Getting Started with IBM Z Resiliency Bill White Marc Coq Pabitra Mukhopadhyay Carlos Alberto Pistillo David Raften Mai Zeng Redbooks IBM Redbooks Getting Started with IBM Z Resiliency March 2020 SG24-8446-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (March 2020) © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . .x Comments welcome. .x Stay connected to IBM Redbooks . xi Chapter 1. Resiliency is key to the survival of a digital business . 1 1.1 What’s the cost of downtime . 2 1.1.1 Fixed costs . 2 1.1.2 Lost revenue . 3 1.1.3 Intangible costs . 3 1.1.4 Balancing IT risk and costs of mitigation. 4 1.2 Measuring availability . 4 1.2.1 Availability objectives . 5 1.2.2 Recovery objectives: RPO and RTO. 6 1.2.3 Aspects of availability . 7 1.3 A path to higher availability . 9 1.3.1 Model 1: Starting with a resilient and reliable base. 10 1.3.2 Model 2: Reducing the duration of outages with failover capability . 11 1.3.3 Model 3: Reducing the impact of outages with a fault tolerant architecture and GDPS. 12 1.3.4 Model 4: Adding GDPS Continuous Availability for maximal resilience . 13 Chapter 2.
    [Show full text]
  • PDF File for High Availability Overview
    IBM i Version 7 Release 3 Availability High availability overview IBM IBM i Version 7 Release 3 Availability High availability overview IBM Note Before using this information and the product it supports, read the information in “Notices” on page 33. This edition applies to IBM i 7.3 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright IBM Corporation 2002, 2015. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents High availability overview ....... 1 | IBM PowerHA SystemMirror for i overview ... 16 | What's new for IBM i 7.3 .......... 1 | Comparison of PowerHA data resiliency PDF file for High availability overview ..... 2 | technologies ............. 17 Benefits of high availability ......... 2 | Switched logical unit ......... 17 Planned outages ............ 2 | Geographic mirroring ......... 18 Unplanned outages ........... 3 | Metro Mirror ............ 20 Disaster recovery ............ 4 | Global Mirror............ 21 Backup window reduction ......... 4 | DS8000 Full System HyperSwap ..... 21 Load balancing ............ 6 | DS8000 HyperSwap with independent High availability criteria .......... 6 | auxiliary storage pools (IASPs) ...... 22 Budget ............... 6 | Use Case scenario's ......... 23 Uptime requirements .......... 7 | FlashCopy ............. 27 Outage coverage ............ 7 | HA Technologies combined ........ 28 Recovery time objective (RTO) ....... 8 | High availability management ....... 28 Recovery point objective (RPO) ....... 8 | IBM PowerHA SystemMirror for i interfaces 28 Resilience requirements .........
    [Show full text]
  • Large-Scale Commercial Computing
    Front cover Introduction to the New Mainframe: Introduction to the New Mainframe: Large-Scale Learn why mainframes process much of the world’s commercial workload Find out why mainframes are so reliable Understand mainframe popularity Mike Ebbers Frank Byrne Pilar Gonzalez Adrados Rodney Martin Jon Veilleux ibm.com/redbooks International Technical Support Organization Introduction to the New Mainframe: Large-Scale Commercial Computing December 2006 SG24-7175-00 Note: Before using this information and the product it supports, read the information in “Notices” on page 237. First Edition (December 2006) © Copyright International Business Machines Corporation 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Preface . ix How this text is organized . x How each chapter is organized. x About the authors . x Acknowledgements . .xi Reviewers . xi Chapter 1. The new mainframe . 1 1.1 What is a mainframe? . 2 1.2 An evolving architecture . 3 1.3 Mainframes in our midst . 4 1.4 Who uses mainframe computers?. 5 1.5 Factors contributing to mainframe use . 6 1.5.1 Capacity . 7 1.5.2 Scalability . 7 1.5.3 Integrity and security . 8 1.5.4 Availability . 8 1.5.5 Access to large amounts of data. 9 1.5.6 Systems management . 10 1.5.7 Autonomic capabilities . 10 1.6 Typical mainframe workloads . 10 1.6.1 Batch processing. 11 1.6.2 Online transaction processing. 14 1.7 Summary . 17 1.8 Questions for review . 18 1.9 Topics for further discussion .
    [Show full text]
  • High Availability Concepts for Video Surveillance
    High Availability Concepts for Video Surveillance www.intransa.com / Intransa, the VideoAppliance™ Company 1 Table of Contents Introduction ................................................................................................................. 3 Defining High Availability ............................................................................................. 4 The Cost of Downtime .................................................................................................. 5 Reducing the Probability of Downtime ......................................................................... 6 Achieving High Availability ........................................................................................... 7 Technology .........................................................................................................................7 People .............................................................................................................................. 10 Process ............................................................................................................................. 10 High Availability Concepts for Video Surveillance Systems ......................................... 11 Write Failover (recording) ................................................................................................. 11 Read Protection (playback) ............................................................................................... 11 Summary...................................................................................................................
    [Show full text]