SAP HANA Disaster Recovery With SUSE High Availability .

3y ago
3.46 MB
66 Pages
Last View : 23d ago
Last Download : 5m ago
Upload by : Tia Newell

SAP HANA Disaster Recoverywith SUSE High AvailabilityExtensionCleber Paiva de Souza / Gabriel Cavalcante{cleber,gabriel} Systems and Solutions

S-SYS and SUSE2 S-SYS officially born inJan/2014 SUSE partner sincebeginning Formed by professionalswith experience in SUSEproducts, Linux ingeneral, training andsoftware development Acting together withSUSE engineers in presales and project delivery

Fujitsu Brazil Case: Sap HANAAppliances3 Fujitsu offers PrimergyRX600 S6 andPRIMEQUEST machineswith SAP HANA. SAP HANA HA studies tookplace at Fujitsu PlatformSolution Center (PSC). Integration between S-SYSand Fujitsu teams. Knowledge transfer allowedFujitsu to delivery SAPHANA integrated withSUSE High Availability.

Fujitsu RX600 hardware specification4 Up to 4x Powerful Intel Xeon processors E7 family Expandable to 1 TB of DDR3RAM with mirroring support Robust I/O design and 10 PCIExpress slots 8x hard drive bays and supportup to 8 TB local storage Integrated Remote ManagementController (iRMC) providingadvanced management features 4U rack server form factor

Fujitsu Rx600 real hardware specification5 4 Intel Xeon E7 4870 2.4GHz. (10 cores * 2 threads * 4sockets 80 cores) 1 TB of RAM 2 x Fusion-IO PCI cards (1.2GB in RAID 1) 8 x 900 GB SAS 10000 RPMsin RAID5 6 x 10GE Network interfaces 6 x 1GE Network interfaces (4onboard and 2 PCI)

Fujitsu Primequest PRIMEQUEST Hardware SpecificationHighlights of the new generation 8-Socket Server with up to 4 independent HW partitions and flexible I/O based onlatest Intel Xeon E7-x800v3 Maximum performance by new Intel Haswell-EX processor generation with up to18 cores Increased memory capacity and performance by 192x DDR4 DIMM slots with1866Mhz System self repair with flexible-IO and reserved-SB functionality 12Gbps RAID controller with 1/2GB cacheProduct facts 6up to 8x Intel Xeon E7-x800v3 (Haswell-EX)Up to 12 TB RAM (using 192 x 64GB)Up to 24 x 2.5” HDD/SSD sUp to 16 PCIe slots internalAdditional 48 PCIe hot plug slots in 4 x ext. PCI BoxUp to 8 x 10GbE internal with 4 x IOUF All parts are redundant and/or hot swappable Enhanced ServerView management Improved Enterprise RAS feature set

HANA in SLES HAE ClusterHANA Single Box – System Replication / Scale-up7

Considerations8 We are Linux experts not SAP experts. SLES for SAP SLES 11 HA extension SAPsupport SAPHanaSR. All tests done on SLES for SAP 11 SP3. Two-node clusters only (Scale-up / single-boxreplication). AUTOMATED REGISTER “false” By default SAP HANA instances are not started duringboot. Cluster take care of services. Synchronous system replication. SAP HANA SPS 08 release 85.

Definitions9ParameterValueCluster node 1hana01Cluster node 2hana02SIDHDBInstance number00User rd1SYSTEMP@ssword1slehalocPassword1

Problem10 SAP HANA System Replication on SLES for SAPApplications from June/2014 did not provideconfigurations for IPMI as a STONITH resource. SAPHanaSR Hawk template does not provide IPMIconfiguration.


Procedures for setup121)Install SLES for SAP2)Configure network interfaces3)Configure NTP and timezone4)Setup disk layout5)Check hostnames and IP addresses6)Install SAP HANA database7)Setup HANA8)Configure SLES HA Extension9)Testing takeover10)Stress test

1) Install SLES for SAP

Install SLES for SAP Install SUSE as usual–Select pattern SAP HANA Server Base.–SLES for SAP install minimal network services.Register at SUSE Customer Center (SCC) and applyupdates to prevent well-known problem and bugs.– 14Updates size 500MBSAPHanaSR is available only on SLES for SAP:–Provide SAPHanaTopology and SAPHana resource agents–Provide Hawk wizard templates

2) Configure network interfaces

Configure network interfaces16 Define how your network communication will work. Define interfaces for user access, heartbeat, datareplication, SAP remote support, STONITH, IPMI etc.

Network throughout and redundancy17 Use bonding for aggregation or redundancy. (802.3ad,balance-rr, active-backup etc) Make use of 10GE network interfaces and Infiniband56 GB. High Availability requires redudant paths for networkswitches, fibre switches, Infiniband switches etc. Monitor your environment.

3) Configure NTP and timezone

Configure NTP and timezone All nodes must be in time sync. Cluster could fail if clock are skewed. Make use of the same timezone on all nodes or SAPcould misbehavior. Trace events on logscould be hard.19

4) Setup disk layout

Setup disk layout21

Data throughput and redundancy 22Put /hana/log on Fusion-IO for performance.–7200 RPMs SATA 100 IOPS–15000 RPMs SAS 200 IOPS–SSD disks 20,000 IOPS–Fusion-IO 140.000 IOPS/hana/data e /hana/shared on some RAID layout (1,5, 6 etc).

5) Check hostname and IP Addresses

Check hostnames and IP addresses Hostname should be defined before starting SAPHANA installation.–SAP HANA stores this information on sapstart service profiles–Altering hostame after installation will require some changesin files such as/usr/sap/ SID /HDB instance number / hostname /sapprofile.iniCheck /etc/hosts consistency.– 24All nodes must know other nodes’ IPs to hostname mapping.Assign a virtual IP and hostname for the master nodein cluster.

6) Install SAP HANA Database

Install SAP HANA Database26

Install SAP HANA Database27

Install SAP HANA Database28

Install SAP HANA Database29

Install SAP HANA Database30

Install SAP HANA Database31

Install SAP HANA Database32

Install SAP HANA Database33

Install SAP HANA Database34

Install SAP HANA Database35

Install SAP HANA Database36

Install SAP HANA Database37

7) Setup HANA

Setup HANA (part I) ####Create user for data synchronization on all nodes:exporthdbsqlhdbsqlhdbsql PATH " PATH:/usr/sap/HDB/HDB00/exe"-u system -i 00 'CREATE USER slehasync PASSWORD Password1'-u system -i 00 'GRANT DATA ADMIN TO slehasync'-u system -i 00 'ALTER USER slehasync DISABLE PASSWORD LIFETIME'Set password on all nodes:# hdbuserstore SET slehaloc localhost:30015 slehasync Password139

Setup HANA (part II) Verify user creation on all nodes:# hdbuserstore listDATA FILE: /root/.hdb/hana01/SSFS HDB.DATKEY SLEHALOCENV : localhost:30015USER: slehasync Verify query working without asking for password onall nodes:# hdbsql -U slehaloc "select * from dummy"DUMMY"X"1 row selected (overall time 2733 usec; server time 115 usec)40

Setup HANA (part III) Defining primary node with user hdbadm:hana01:/usr/sap/HDB/HDB00 hdbnsutil -sr enable --name SITE001checking for active nameserver .nameserver is active, proceeding .successfully enabled system as system replication source sitedone. Verifying node state with user hdbadm:hana01:/usr/sap/HDB/HDB00 hdbnsutil -sr statechecking for active or inactive nameserver .System Replication State mode: primarysite id: 1site name: SITE001Host Mappings: done.41

Setup HANA (part IV) Do first backup:hana01: # hdbsql -u system -i 00 "BACKUP DATA USING FILE ('backup')"Password:0 rows affected (overall time 46.986124 sec; server time 46.984819 sec) Verify replication status:hana01: # hdbsql -U slehaloc 'select distinct REPLICATION STATUS fromSYS.M SERVICE REPLICATION’REPLICATION STATUS0 rows selected (overall time 1701 usec; server time 401 usec)42

Setup HANA (part V) Define secondary node with user hdbadm:hana02:/usr/sap/HDB/HDB00 hdbnsutil -sr register --remoteHost hana01 -remoteInstance 00 --mode sync --name SITE002adding site .checking for inactive nameserver .nameserver hana02:30001 not responding.collecting information .updating local ini files .done. Check secondary node status with user hdbadm:hana02:/usr/sap/HDB/HDB00 hdbnsutil -sr statechecking for active or inactive nameserver .System Replication State mode: syncsite id: 2site name: SITE002active primary site: 143

Setup HANA (part VI) Check primary node status with user hdbadm:hana01:/usr/sap/HDB/HDB00 hdbnsutil -sr statechecking for active or inactive nameserver .System Replication State mode: primarysite id: 1site name: SITE001Host Mappings: hana01 - [SITE001] hana01hana01 - [SITE002] hana02done.44

8) Configure SLES HA Extension

Configure SLES HA Extension46 Install pattern “High Availability”. Install package SAPHanaSR. sleha-init on first node. Change /etc/corosync/corosync.conf if necessary.–udp (multicast) vs udpu (unicast).–Enable redundant channel and rrp mode.–Enable security auth. sleha-join on second node. Keep STONITH disabled during configuration.

HA Configuration Default / global propertiesproperty id "cib-bootstrap-options" \no-quorum-policy "ignore" \stonith-action "poweroff"rsc defaults id "rsc-options" \resource-stickiness "1000" \migration-threshold 3 \failure-timeout 60op defaults id "op-options" \timeout "600”47

HA Configuration SAPHanaTopology:primitive rsc SAPHanaTopology HDB HDB00ocf:suse:SAPHanaTopology \params SID "HDB" InstanceNumber "00" \op monitor interval "10" timeout "600" \op start interval "0" timeout "600" \op stop interval "0" timeout "300"clone cln SAPHanaTopology HDB HDB00rsc SAPHanaTopology HDB HDB00 \meta is-managed "true" clone-node-max "1"interleave "true"48

HA Configuration SAPHana:primitive rsc SAPHana HDB HDB00 ocf:suse:SAPHana \params SID "HDB" InstanceNumber "00" PREFER SITE TAKEOVER "yes"AUTOMATED REGISTER "true" DUPLICATE PRIMARY TIMEOUT "7200" \op start interval "0" timeout "3600" \op stop interval "0" timeout "3600" \op promote interval "0" timeout "3600" \op monitor interval "60" role "Master" timeout "700" \op monitor interval "61" role "Slave" timeout "700" \meta target-role "Started"ms msl SAPHana HDB HDB00 rsc SAPHana HDB HDB00 \meta clone-max "2" clone-node-max "1" interleave "true"order ord SAPHana HDB HDB00 2000: cln SAPHanaTopology HDB HDB00msl SAPHana HDB HDB0049

HA Configuration Virtual IP:primitive rsc ip HDB HDB00 ocf:heartbeat:IPaddr2 \params ip "" iflabel "0" \op start interval "0" timeout "20" \op stop interval "0" timeout "20" \op monitor interval "10" timeout "20"colocation col saphana ip HDB HDB00 2000:rsc ip HDB HDB00:Started msl SAPHana HDB HDB00:Master50

HA Configuration STONITH IPMI:primitive stonith ipmi hana01 stonith:external/ipmi \params hostname "hana01" ipaddr "" userid "admin"passwd "admin" \op monitor enabled "true" interval "300" start-delay "5"timeout "20"location stonith ipmi hana01 not on hana01 stonith ipmi hana01-inf: hana01primitive stonith ipmi hana02 stonith:external/ipmi \params hostname "hana02" ipaddr "" userid "admin"passwd "admin" \op monitor enabled "true" interval "300" start-delay "5"timeout "20"location stonith ipmi hana02 not on hana02 stonith ipmi hana02-inf: hana0251

Hawk template 52Created custom Hawk template including IPMI asSTONITH. Available late.tar.gz.

Hawk template53

Hawk template54

Hawk template55

9) Testing takeover

Manual takeover Secondary become primary with user hdbadm:hana02:/usr/sap/HDB/HDB00 hdbnsutil -sr takeoverchecking local nameserver .done. Verify new state with user hdbadm:hana02:/usr/sap/HDB/HDB00 hdbnsutil -sr statechecking for active or inactive nameserver .System Replication State mode: primarysite id: 2site name: SITE002Host Mappings: hana02 - [SITE001] hana01hana02 - [SITE002] hana02done.57

Cluster takeover58 Set AUTOMATED REGISTER ”true”. Take attention to STONITH. Prefer shutdown insteadof reboot. Take attention to timeout (start, stop, migration etc)

9) Stress test

Stress test Detect problem during stress. Most of time due to lower timeout. HanaStress y -v --host localhost -i 00 u SYSTEM -p P@ssword1 -g anarchy --tables100 --rows 100000 --threads 10(This will create 100 tables with 100000 rows ofinformation each, using 10 threads)60

Cleanup after stress test Remove database fragmentation:–ALTER SYSTEM RECLAIM DATAVOLUME 120 DEFRAGMENT–ALTER SYSTEM RECLAIM LOGForce flushing log data to disk:–61ALTER SYSTEM SAVEPOINT

References62 ap hana system replication on sles for sap applications.pdf

Going you.63

65Corporate Headquarters 49 911 740 53 0 (Worldwide)Maxfeldstrasse 590409 NurembergGermanywww.suse.comJoin us

Unpublished Work of SUSE 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 oftheir 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 DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market aproduct. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in makingpurchasing 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 solediscretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, atany time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced inthis presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. Allthird-party trademarks are the property of their respective owners.

Fujitsu Brazil Case: Sap HANA Appliances Fujitsu offers Primergy RX600 S6 and PRIMEQUEST machines with SAP HANA. SAP HANA HA studies took place at Fujitsu Platform Solution Center (PSC). Integration between S-SYS and Fujitsu teams. Knowledge transfer allowed Fujitsu to delivery SAP HANA integrated with SUSE High Availability.

Related Documents:

SAP ERP SAP HANA SAP CRM SAP HANA SAP BW SAP HANA SAP Runs SAP Internal HANA adoption roadmap SAP HANA as side-by-side scenario SAP BW powered by SAP HANA SAP Business Suite powered by SAP HANA Simple Finance 1.0 2011 2013 2014 2015 Simple Finance 2.0 S/4 HANA SAP ERP sFin Add-On 2.0

c. SAP HANA Rules Framework; d. SAP HANA, data privacy option; e. SAP HANA, predictive option; f. SAP HANA, spatial and graph option; g. SAP HANA, search and text option; h. SAP HANA, Smart Data Quality ("SDQ "); i. SAP Smart Data Integration ("SDI "); and j. SAP HANA, native storage extension. 3.2. SAP HANA Platform includes the HANA Studio .

Customer Roadmap to SAP Simple Finance - Example " Adopting SAP Simple Finance is a journey - start early" Side-by-side SAP HANA Acceleration SAP HANA accelerators, BW, BPC, GRC SAP Business Suite on SAP HANA SAP ERP on SAP HANA SAP ERP in SAP HANA Enterprise Cloud SAP Accounting Powered By SAP HANA Simple Finance add-on/

1. Introduction: SAP Solution Manager and SAP HANA 2. How to connect SAP HANA to SAP Solution Manager? 3. Monitoring of SAP HANA via SAP Solution Manager 4. Doing Root Cause Analysis of SAP HANA with SAP Solution Manager 5. Extend your Change Control Management towards SAP HANA 6. Even More Valuable Features of SAP Solution Manager

For detailed information about the SAP HANA backup and recovery solution see TR-4614: SAP HANA Backup and Recovery with SnapCenter. SAP HANA disaster recovery SAP HANA disaster recovery (DR) can be done either on the database layer by using SAP HANA system replication or on the storage layer by using storage replication technologies.

SAP PowerDesigner, Enterprise Architecture Designer SAP HANA Web IDE SAP HANA smart data integration and SAP HANA smart data quality SAP HANA extended application services information management option SAP HANA . SAP HANA Vora HANA-optimized re .

SAP NW 7.4 SAP BW 7.4 SPS12 SAP BPC 10.1 RHEL 6.6x SAP HANA SP10 SAP NW 7.5 SAP ECC 6 EHP8 SAP Portal/SolMan RHEL 6.6x SAP HANA SP11 S/4 HANA SAP Fiori BI on HANA BW Simplification HANA Journey –Client Example

SAP HANA supports the following DDR4 DRAM memory configurations: SAP HANA 2.0 memory up to 2 TB for SAP NetWeaver Business Warehouse (BW) and DataMart. SAP HANA 2.0 memory up to 4 TB for SAP Business Suite on SAP HANA (SoH) Operating system The Cisco X210c M6 server is certified for SAP HANA starting with the RHEL for SAP Solutions 8.2