Downloaded 215 times
![15
starting with version 0.149
Single-tier System Replication and DEV / QAS
( A → [B] + DEV )
Pacemaker
System Replication
node 1 node 2
SAP HANA
PR1
primary
SAP HANA
DEV / PR1 secondary
System
PR1
vIP
System
PR1
System
DEV
Cost optimized
Operating non-prod systems on Secondary
Resources freed (no data pre-load) to be offered to one or more non-prod installations
During take-over the non-prod operation has to be ended
Take-over performance similar to cold start-up
Needs another disk stack for non-prod usage load](https://image.slidesharecdn.com/1suse-150521072835-lva1-app6892/75/SAP-HANA-System-Replication-simplified-15-2048.jpg)
Uploaded byDirk Oppenkowski
SAP HANA System Replication simplified
This document discusses SAP HANA system replication which can be automated using the SUSE High Availability Solution. It provides an overview of SAP HANA scenarios for high availability and disaster recovery. It also summarizes the steps to install and configure SAP HANA system replication using the SUSE clustering and automation tools. New use cases that will be supported in upcoming versions are also presented such as single-tier replication with additional non-production systems and multi-tier cascading replication configurations.
More Related Content
Similar to SAP HANA System Replication simplified
SAP HANA System Replication simplified
- 1. SAP HANA Systemreplication Simplified PeterSchinagl peters@suse.com Senior Technical Architect SUSE SAP Global Alliance
- 2. 2 Simplify Linux forSAP SUSE Linux Enterprise Server for SAP Applications Page Cache Management Antivirus ClamAV Extended Service Pack Support 18 Month Grace Period Faster Installation SAP Installation Wizard High Availability SAP HANA & SAP NetWeaver Reliable, Scalable, and Secure Operating System SUSE Linux Enterprise Server SAP specific update channel 24x7 Priority Support for SAP 24x7 Priority Support for SAP
- 3. Automate SAP HANASystem Replication
- 4. 4 SAP HANA Scenarios Source:SAP HANA in Data Centers HWSAP Business Continuity HA per Datacenter Disaster recovery between Datacenter SAP HANA Host Auto Failover (scale out with standby) SAP HANA System Replication SAP HANA System Replication SAP HANA Storage Replication SAP HW SAP
- 5. 5 Automate SAP HANA SystemReplication Service Level Agreement SAP HANA System Replication SUSE High Availability Solution
- 6. 6 SAP HANA SystemReplication Powered by SUSE High Availability Solution resource failover node 1 node 2 HANA Database HANA memory-preloadmemory-preload System Replication HANA PR1 primary HANA PR1 secondary Performance optimized Secondary system completely used for the preparation of a possible take-over Resources used for data pre-load on Secondary Take-overs and Performance Ramp shortened maximally N M A B N M A B A B
- 7. 7 From Concept toImplementation SUSE High Availability Solution for SAP HANA SAP HANA Primary SAP HANA Secondary vIP SAPHana Master/Slave Resource Master Slave SAPHanaTopology Clone Resource Clone Clone suse01 suse02 Cluster Communication Fencing
- 8. 8 Four Steps toInstall and Configure Install SAP HANA Configure SAP HANA System Replication Install and initialize SUSE Cluster Configure SR Automation using HAWK wizard
- 9. 9 Allowed Scenarios (initialversion) Two-node clusters Scale-up (single-box to single-box) HANA system replication Only Single-tier System Replication ( A → B ) no multi-tier no other SAP HANA system (like DEV, TST, QAS) on the replicating node that needs to be stopped during takeover Both physical and “virtual” SAP host names
- 10. 10 Requirements Both SAP HANAinstances have the same SAP Identifier (SID) and Instance Number Both cluster nodes in-time sync (ntp) Both nodes are in the same network segment (layer2) Technical users and host names resolved locally Distance / Latencies
- 11. 11 SAPHanaSR HAWK Wizard Technicalpreview included in the shipping.
- 12.
- 13. 13 What is theDelivery? SUSE Linux Enterprise Server for SAP Applications The package SAPHanaSR the two resource agents SAPHanaTopology SAPHana HAWK setup Wizard (as technical preview) The package SAPHanaSR-doc the important SetupGuide
- 14.
- 15. 15 starting with version0.149 Single-tier System Replication and DEV / QAS ( A → [B] + DEV ) Pacemaker System Replication node 1 node 2 SAP HANA PR1 primary SAP HANA DEV / PR1 secondary System PR1 vIP System PR1 System DEV Cost optimized Operating non-prod systems on Secondary Resources freed (no data pre-load) to be offered to one or more non-prod installations During take-over the non-prod operation has to be ended Take-over performance similar to cold start-up Needs another disk stack for non-prod usage load
- 16. Requirements Needs to beimplemented as a project, because this is not a simple pre-build solution. HW Partner needed because of different HANA systems (disks and general sizing) Fencing is HW specific Cluster-rules needs to be adopted to the customer specific implementation
- 17. 17 starting with version0.149 Multi Tier System Replication – Cascading Systems Datacenter Datacenter asyncronsyncron Production Local standby with data preload Remote standby system with or without preload (mixed usage with non-prod.) Available since SAP HANA SPS7 (Three cascading systems)
- 18. Requirements Needs to beimplemented as a project, because this is not a simple pre-build solution. Side C is not in the cluster, therefore the administrator need to do many tasks manually after an switchover.
- 19. 19 starting with version0.149 Multi-tier System Replication (cascading systems) Chain Topology ( A → B → C ) asyncsync Cluster PP S A B C Default Setup - ChainChain
- 20. 20 starting with version0.149 Multi-tier System Replication (cascading systems) Chain Topology ( A → B → C ) asyncsync Cluster PP S A B C Default Setup - ChainChain Cluster async PP A B C only async now
- 21. 21 starting with version0.149 Multi-tier System Replication (cascading systems) Chain Topology ( A → B → C ) asyncsync Cluster PPS A B C asyncsync Cluster PP S A B C Default Setup - ChainChain Cluster async PP A B C only async now
- 22. 22 starting with version0.149 Multi-tier System Replication (cascading systems) Chain Topology ( A → B → C ) asyncsync Cluster PPS A B C asyncsync Cluster PP S A B C Default Setup - ChainChain Cluster async PP A B C only async now Not allowed from SAPNot allowed from SAP This would be a starstar
- 23. 23 async Cluster PP A B C Onlyasync starting with version 0.149 Multi-tier System Replication Chain Topology ( A → B → C )
- 24. 24 async Cluster PP A B C ADMIN: BreakReplication complete async Cluster PP A B C Only async starting with version 0.149 Multi-tier System Replication Chain Topology ( A → B → C )
- 25. 25 async sync PPS A B C Againa chain async Cluster PP A B C ADMIN: Break Replication complete async Cluster PP A B C Only async starting with version 0.149 Multi-tier System Replication Chain Topology ( A → B → C ) ADMIN: Create new SystemReplication
- 26. 26 Our Community Developed jointlyin the SAP Linux Lab in Walldorf Integration of the solution in partner products Upstream open-source project Scoping, discussing and implementing Scale-Out You are invited to join our community :-) Visit our booth or contact us via sapalliance@suse.com or saphana@suse.com
- 27. 27 SUSE SAPHanaSR in3 Facts Reduces complexity - provides a wizard for easy configuration with just SID, instance number and IP address - automates the sr-takeover and IP failover ("bind") Reduces risk - includes always a consistent picture of the SAP HANA topology - provides a choice for automatic registrations and site takeover preference Increases reliability - provides short takeover times in special for table preload scenarios - includes the monitoring of the system replication status to increase data consistency
- 28.
- 29. Thank you. 29 Visit usonline to learn more about the SUSE and SAP partnership at http://www.suse.com/sap http://www.suse.com/products/sles-for-sap
- 30. Corporate Headquarters Maxfeldstrasse 5 90409Nuremberg Germany +49 911 740 53 0 (Worldwide) www.suse.com Join us on: www.opensuse.org 30
- 31. Unpublished Work ofSUSE LLC. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE LLC. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.
Editor's Notes
- #5 As more and more HANA systems are productive today, business continuity become a higher priority. There are two scenarios which play a role here SAP = SAP provides a solution HW = Hardware Vendor provides a solution / or is needed for the solution
- #6 It is all about the service level agreements of such systems. . The good thin is that SAP has some build in mechanisms with HANA, as well we within SLES4SAP . These two product features from SAP and SUSE will help you to achive your SLA's . Let's have a more detailed look...
- #7 SR is ONE possibility for increasing the availability of a HANA system. . The Benefits are: - HW independent - short failover time possible due to “memory-preload” option - Distance depend on network - No shared disks for data needed . The Drawbacks are: - manual switch, not automated - cmdline for more complex tasks - needs additional solution to take care of client connection . HINT: because it is a two node cluster * STONITH is mandatory!!!!!! * SBD as shared drive(s) for fencing or IPMI / ILO
- #8 We use our SLE HAE which is included in SLES4SAP . We take care of - Clients ( and the network ) - automatic switch - fencing + web based gui and setup wizard . Pacemaker is a cluster resource manager. Corosync (and Heartbeat) is the message layer . Resource Types Groups – syntactic shortcut Clone – active on multiple hosts MultiState – Multiple Modes = Master/Slave . STONITH is an acronym for “Shoot-The-Other-Node-In-The-Head” and it protects your data from being corrupted by rogue nodes or concurrent access.
- #14 The two packages are delivered as maintenance update for SLES4SAP 11 SP3 . They are out since 01 Juli 2014 . So every customer get it for free . We have restrictions which are documentet in the “SetupGuide” . At the moment (Nov.2014) we support ONLY the two node scenario – NOTHING ELSE!
- #16 Single-tier System Replication and DEV / TST ( A → [B] + DEV ) - Cluster configuration already available - Partner Tests expected in Q4/2014 * additional disk needed for QAS data * QA1 will be shutdown, if takeover needed * normal SAPDatabase or SAPInstance * Tests still to be done for support statement *Take over takes quite long, because data need to be loaded into memory
- #18 Single-tier System Replication and DEV / TST ( A → [B] + DEV ) - Cluster configuration already available - Partner Tests expected in Q4/2014 * additional disk needed for QAS data * QA1 will be shutdown, if takeover needed * normal SAPDatabase or SAPInstance * Tests still to be done for support statement *Take over takes quite long, because data need to be loaded into memory
- #20 Multi-tier System Replication – Chain Topology ( A → B → C ) - Currently under testing - Partner Tests expected in Q4/2014
- #21 Multi-tier System Replication – Chain Topology ( A → B → C ) - Currently under testing - Partner Tests expected in Q4/2014
- #22 Multi-tier System Replication – Chain Topology ( A → B → C ) - Currently under testing - Partner Tests expected in Q4/2014
- #23 Multi-tier System Replication – Chain Topology ( A → B → C ) - Currently under testing - Partner Tests expected in Q4/2014