Automated SAP HANA System Replication With Pacemaker On RHEL
Automated SAP HANA SystemReplication with Pacemaker onRHELSetup GuideFrank Danapfel (Red Hat)Dieter Thalmayr (Magnum Opus GmbH)Dieter Jäger (Magnum Opus GmbH)Version 1.0MAY 2015
100 East Davie StreetRaleigh NC 27601 USAPhone: 1 919 754 3700Phone: 888 733 4281Fax: 1 919 754 3701PO Box 13588Research Triangle Park NC 27709 USA.Linux is a registered trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux and the Red Hat"Shadowman" logo are registered trademarks of Red Hat, Inc. in the United States and othercountries.AMD is a trademark of Advanced Micro Devices, Inc.SAP, SAP NetWeaver and SAP HANA are registered trademarks of SAP AG in Germany and severalother countries.ABAP is a trademark of SAP AG in Germany and several other countries.HANA is a trademark of SAP AG in Germany and several other countries.UNIX is a registered trademark of The Open Group.Intel, the Intel logo and Xeon are registered trademarks of Intel Corporation or its subsidiaries in theUnited States and other countries.POSIX is a registered trademark of IEEE.Oracle is a registered trademark of Oracle Corporation.IBM is a registered trademark of International Business Machines in many countries worldwide.VMware, ESX, ESXi, and vSphere, are registered trademarks of VMware, Inc.All other trademarks referenced herein are the property of their respective owners. 2015 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions setforth in the Open Publication License, V1.0 or later (the latest version is presently available athttp://www.opencontent.org/openpub/).The information contained herein is subject to change without notice. Red Hat, Inc. shall not be liablefor technical or editorial errors or omissions contained herein.Distribution of modified versions of this document is prohibited without the explicit permission of RedHat Inc.Distribution of this work or derivative of this work in any standard (paper) book form for commercialpurposes is prohibited unless prior permission is obtained from Red Hat Inc.The GPG fingerprint of the security@redhat.com key is:CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0Ewww.redhat.comiiNDA Required: Do Not Distribute
Table of Contents1 Executive Summary. 12 Concepts and Planning. 22.1 How it works: overview of the basic setup. 22.2 Resource Agents. 22.2.1 SAPHana Resource Agent. 22.2.2 SAPHanaTopology Resource Agent. 32.3 Supported scenarios. 42.4 High Availability Add-On Overview. 52.4.1 CMAN. 52.4.2 Pacemaker. 52.4.3 Fencing/STONITH. 53 Setup and Configuration. 63.1 Introduction. 63.1.1 Conventions. 63.2 Prerequisites. 73.2.1 General preparations. 73.2.2 Storage requirements. 73.2.3 Operating System Installation. 73.2.4 Cluster package installation. 73.3 SAP HANA Installation. 83.4 SAP HANA System Replication Setup. 93.4.1 Primary node. 93.4.2 Secondary Node. 93.4.3 Create a monitoring account in SAP HANA. 103.5 Cluster Setup. 113.5.1 Initialize the cluster. 113.5.2 Configure Fencing (STONITH). 113.5.3 Virtual IP addresses and hostnames. 123.5.4 Create the SAPHanaTopology resource. 123.5.5 Create clone resource for SAPHanaTopology. 123.5.6 Create SAPHana resource. 13NDA Required: Do Not DistributeIIIwww.redhat.com
3.5.7 Create Master/Slave for SAPHana. 133.5.8 Set up constraints. 13Appendix A: Reference Documentation. 14Appendix B: Example Cluster Configuration. 15www.redhat.comivNDA Required: Do Not Distribute
1 Executive SummarySAP HANA provides mechanisms for system replication (redundancy) and clustering (scaleout) while it leaves some parts of clustering to the operating system. That way in case offailure of a single system, the SAP HANA cluster will be able to provide service withoutsignificant service interruptions. Currently, a two-Node-Cluster solution running Red HatEnterprise Linux for SAP HANA with High Availability is supported. The clustering is done withPacemaker and CMAN, two widely used, industry-standard, open source software packages.The following pages list the technical prerequisites for Pacemaker clustering and provide astep-to-step guide on how to set up a working solution using Red Hat Enterprise Linux withthe High Availability Add-On together with SAP HANA.The solution shown here will be a working one. But most certainly the challenge of a realscenario is more complex than the scope of this document can address. Red hatrecommends that setting up and subsequently servicing a cluster should be guided by acertified consultant familiar with both SAP and Red Hat.1www.redhat.com
2 Concepts and PlanningThe SAP HANA System already provides some of the most crucial cluster components ofsystem replication and auto failover of the software, with one active node, and one standbynode, as well as storage replication and system replication. The host system needs to providea mechanisms for monitoring the SAP processes and network resources and to initiate andcontrol the failover process in case of a problem. It also will provide a fencing mechanism tomake sure, that in case of a failover, the cluster will end up in a well defined state.In this document we will focus on the second part, the host system cluster setup. For thesetup of the SAP HANA components, please refer to the SAP HANA How To-Guide (see page14, Appendix A).2.1 How it works: overview of the basic setupSAP HANA provides different kinds of high availability, aiming for a simple but highlycustomizable setup.In this document we describe how to use Pacemaker to automate a SAP HANA Scale-Upsetup with SAP HANA system replication between two nodes. All data is preloaded(in-memory-database). All changes are constantly replicated from the master node to theslave node, so that in case of a failover recovery time can be minimized.2.2 Resource AgentsThe central part of the Pacemaker cluster setup are two Open Cluster Framework (OCF)resource agents: SAPHana SAPHanaTopology2.2.1 SAPHana Resource AgentThe SAPHana resource agent runs on both nodes in a master/slave configuration. Themaster assumes responsibility for the SAP HANA databases running in primary mode, andthe slave is responsible for instances that are operated in synchronous (secondary) status.The SAPHana resource agent understands the following mandatory parameters: SID ”RHE1”: the SID of the SAP HANA system InstanceNumber "00": ID of the SAP HANA Instance PREFER SITE TAKEOVER true: Should cluster/RA prefer to switch over to the slaveinstance instead of restarting the master locally?www.redhat.com2
DUPLICATE PRIMARY TIMEOUT 7200: Time difference needed between twoprimary time stamps, if a dual-primary situation occurs. AUTOMATED REGISTER false: Define whether a former primary shouldautomatically be registered.Other parameters: SAPHanaFilter: Define SAP HANA resource agent messages to be printed2.2.2 SAPHanaTopology Resource AgentThe SAPHanaTopology resource agent runs as a stateless cloned agent on all nodes andgathers information about the status and configuration of all SAP HANA system replications.The SAPHanaTopology agent understands the following mandatory parameters: SID ”RHE1”: the SID of the SAP HANA system InstanceNumber "00": ID of the SAP HANA InstanceOther parameters: SAPHanaFilter: Define type of SAPHanaTopology resource agent messages to beprintedA full description of these parameters can be found on the SAP HANA man page and thesource code at r/SAPHana.3www.redhat.com
2.3 Supported scenariosCurrently the supported scenarios are limited to the following parameters:1. Two-node clustersSAP HANA Scale-Up (single-box to single-box) System Replication2. Both SAP HANA instances have the same SAP Identifier (SID) and Instance-Number.3. There is no other SAP HANA system (like QAS or TST) on the replicating node whichneeds to be stopped during takeover.4. Only one system replication for the SAP HANA database, no replication chains.5. The SAP HOSTAGENT must be installed on all nodes.6. All nodes are in the same network segment (layer 2).7. Technical users and groups such as sidadm are defined locally on all cluster nodes.8. Name resolution of the cluster nodes and the virtual IP address can be done locally onall cluster nodes.9. Time synchronization between the cluster nodes using NTP.10. If the cluster nodes are installed in different datacenters or datacenter areas, theenvironment must match the requirements of the Red Hat Enterprise Linux for SAPHANA High Availability Add-On. This especially refers to the network latencies betweenthe nodes and the recommended maximum distance.www.redhat.com4
2.4 High Availability Add-On OverviewThe Red Hat Enterprise Linux for SAP High Availability add-on provides the followingcomponents to set up HA environments: Cluster Manager (CMAN) Pacemaker STONITH2.4.1 CMANCluster Manager (CMAN) is a Red Hat specific service module that manages the clustercommunication infrastructure. It provides a user API that is used by Red Hat layered clustercomponents. CMAN also provides additional functionality such as APIs for a distributed lockmanger, clustered lvm, conditional shutdown, and barriers.2.4.2 PacemakerPacemaker is the Cluster Resource Manager. Clustered services and resources are definedthere. Pacemaker can control user requests like service start, restart, disable or relocate, aswell as provide fail-over capabilities as necessary.Pacemaker uses OCF-compliant resource agents to control and monitor required resources.2.4.3 Fencing/STONITHAll cluster relevant components are installed locally on all participating nodes so both of thecluster member nodes can perform all services. In case of switching services, thenow-disabled node has to be switched off, which is why there has to be a working powerfencing mechanism in place. In our example setup, we will describe an ipmi fencing. ButPacemaker supports several different fencing methods, and every one of them may beapplied. Since all storage components are exclusively local, there is no need for storagefencing.5www.redhat.com
3 Setup and Configuration3.1 IntroductionThis part of the document describes the entire installation process. It provides somebackground information, describes the necessary steps, and if possible, gives examples onwhich commands to use. Setups will hardly ever be performed exactly the same way as theyare described here; it is the consultant’s job to understand and modify the commands asappropriate to the respective context.Basically, the whole process includes the following steps: Installing and configuring Red Hat Enterprise Linux for SAP HANA on all nodesaccording to the SAP guidelines Installing SAP HANA on all nodes using the same SID and instance number Manually configuring SAP HANA System Replication and verifying that it worksaccording to SAP guidelines Configuring the cluster Performing cluster tests to verify that failover works under all circumstances3.1.1 ConventionsFor readability, we will assume an example setup. The host names and instance names aremeant as examples, and should be changed to your needs. These are the example values weuse:ParameterStorageSIDInstance NoPublic networkCluster networkPublic cluster lusterDescriptionStorage for HDB data and log files isconnected “locally” (per node; not www.redhat.com6
3.2 Prerequisites3.2.1 General preparationsMake sure your environment meets the following requirements: All storage can be local, no shared storage needed Stonith device present Network port 7630/tcp must be available and not blocked by a firewall NTP must be set up properly to have precise time synchronization between the nodes3.2.2 Storage requirementsSAP HANA is an in-memory database. All cluster relevant components are kept in memoryand are replicated to the cluster nodes, so there is no need for shared storage, which simplifies the storage setup very much. The only storage requirement is to have reliable local storage on all cluster systems, with all needed components available to start up the cluster framework.3.2.3 Operating System InstallationPlease follow the guidelines in SAP Note 2009879 (SAP HANA Guidelines for RedHatEnterprise Linux (RHEL) Operating System) to prepare the OS on all cluster nodes.3.2.4 Cluster package installationIn addition please make sure that all cluster nodes are subscribed to the "RHEL Server HighAvailability" channel and install the cluster packages:[root]# yum install cman pacemaker pcs resource-agents-sap-hanaMake sure the cluster will not be started at boot time by switching off the Corosync frameworkdaemon:[root]# chkconfig corosync off7www.redhat.com
3.3 SAP HANA InstallationFor SAP HANA System Replication to work SAP HANA must be installed using the same SIDand Instance Number on all nodes. The installation of SAP HANA is not covered in thisdocument. Please refer to the setup manuals available at the SAP Market Place, downloadthe SAP HANA software and perform the SAP HANA installation following the instructions inthe manual (s. p. 14, Appendix A).After successful installation of the database, verify that SAP HANA is running by using theSAP HDB tool:rh1adm@node1:/usr/sap/RH6/HDB00 HDB infoUSERPID PPID %CPUVSZRSS COMMANDrh1adm4949 4948 1.5 110452 3924 -bashrh1adm5032 4949 0.0 114064 1924\ /bin/sh /usr/sap/RH6/HDB00/HDB inforh1adm5059 5032 0.0 118036 1508\ ps fx -U rh6adm -ouser,pid,ppid,pcpu,vsz,rss,argsrh1adm169181 0.0 22088 1496 sapstartpf /usr/sap/RH1/SYS/profile/RH6 HDB00 node1rh1adm16927 16918 0.0 896912 301692\ /usr/sap/RH1/HDB00/node1/trace/hdb.sapRH1 HDB00 -d -nw-f /usr/sap/RH1/HDB00/node1/daemon.inipf /usr/sap/RH1/SYS/profile/RH1 HDB00 node1rh1adm16947 16927 3.5 9589920 1925852\ hdbnameserverrh1adm16998 16927 0.0 7842256 238936\ hdbpreprocessorrh1adm17001 16927 0.0 7620992 235508\ hdbcompileserverrh1adm17093 16927 4.4 12878916 3763036\ hdbindexserverrh1adm17096 16927 4.4 12475796 4040556\ hdbstatisticsserverrh1adm17099 16927 3.5 11216184 2070452\hdbxsenginerh1adm17535 16927 0.0 930408 72500\ sapwebdisp hdbpf /usr/sap/RH1/HDB00/node1/wdisp/sapwebdisp.pfl-f /usr/sap/RH1/HDB00/node1/trace/dev webdisprh6adm238041 0.0 67850875720 /usr/sap/RH1/HDB00/exe/sapstartsrvpf /usr/sap/RH1/SYS/profile/RH1 HDB00 node1 -D -u rh1admFor the system replication to work, the SAP HANA "log mode" variable must be set to"normal". This can be verified after installation with the following command:[rh1adm]# hdbsql -u system -i 00 "select value from"SYS"."M INIFILE CONTENTS" where key 'log mode'"Password:VALUE "normal"1 row selected (overall time 191.885 msec; server time 188.704 msec)Make sure that SAP HANA is not configured to automatically start after system boot, sincestartup and shutdown of SAP HANA will be controlled by the cluster (must be done on allnodes):[root]# grep Autostart /RH1 HDB00 node1:Autostart 0www.redhat.com8
3.4 SAP HANA System Replication SetupIf SAP HANA System Replication uses a separate network for its traffic, you need to configurethe System Replication hostname resolution as described in Host Name Resolution forSystem Replication3.4.1 Primary nodeThe first step is to prepare the primary node. The SAP HANA system replication will only workafter an initial backup has been performed:[rh1adm]# hdbsql -i 00 -u system -p pw of user system "BACKUP DATA USINGFILE ('/tmp/foo')"0 rows affected (overall time 35.458355 sec; server time 35.426372 sec)After successful backup, replication can be initialized:[rh1adm]# hdbnsutil -sr enable --name DC1checking for active nameserver .nameserver is active, proceeding .successfully enabled system as system replication source sitedone.As a final step, check replication status and make sure it both shows the current node isrunning and the current node as primary.[rh1adm]# hdbnsutil -sr statechecking for active or inactive nameserver .System Replication State mode: primarysite id: 1site name: DC1Host Mappings:3.4.2 Secondary NodeThe second step is to initialize the secondary node. This has only one step: register thesecond node to the SAP HANA cluster[rh1adm]# hdbnsutil -sr register --remoteHost node1 --remoteInstance 00--mode syncmem --name DC2adding site .checking for inactive nameserver .nameserver node2:30001 not responding.collecting information .updating local ini files .done.Make sure that everything has worked as expected by checking the replication status. Youshould now see both nodes, node1 still as primary; the secondary node should show up in“syncmem” mode.[rh1adm]# hdbnsutil -sr statechecking for active or inactive nameserver .System Replication State9www.redhat.com
mode: syncmemsite id: 2site name: DC2active primary site: 1re-setup replication: hdbnsutil -sr register --name DC2 --mode syncmem--remoteHost node1--remoteInstance 00Host Mappings: node2 - [DC1] node1node2 - [DC2] node23.4.3 Create a monitoring account in SAP HANAA technical user with "DATA ADMIN" privileges must exist in SAP HANA for the resourceagents to be able to run queries on the system replication status. Run the followingcommands on primary node to create a technical user "rhelhasync" inside the HANA DB(replace password with your own password):[rh1adm]# hdbsql -i 00 -u system -p pw of system user "create userrhelhasync password password "[rh1adm]# hdbsql -i 00 -u system -p pw of system user "grant DATA ADMIN torhelhasync"[rh1adm]# hdbsql -i 00 -u system -p pw of system user "ALTER USERrhelhasync DISABLE PASSWORD LIFETIME"Then add a userkey "SAPHANA SID SR" for this user to the local HANA user store for theroot user. Run the following command on all nodes:[root]# hdbuserstore SET SAPHANA SID SR localhost:30015 rhelhasync password (replace SID with the SID of the SAP HANA installation; for example if the SID of yourHANA installation is "RH1"; the userkey therefore must be "SAPHANARH1SR")Please verify that it is possible to run hdbsql commands as root using theSAPHANA SID SR userkey without being prompted for a password, e.g.:[root]# /usr/sap/RH1/HDB00/exe/hdbsql -U SAPHANARH1SR -i 00 "select distinctREPLICATION STATUS from SYS.M SERVICE REPLICATION"If you get an error message about issues with the password or are being prompted for apassword please verify with HANAStudio that the password for the user "rhelhaloc" is notconfigured to be changed on first login or that the password has expired.www.redhat.com10
3.5 Cluster Setup3.5.1 Initialize the clusterRun the following command on each cluster node to configure the cluster infrastructure andstart the cluster:[root]# pcs cluster setup --name hanasr --local node1hb node2hb[root]# service pacemaker startCheck if your cluster node is running and connected with the following command:root]# pcs statusCluster name: hanasrLast updated: Thu Dec 4 12:14:34 2014Last change: Mon Dec 1 17:05:31 2014Stack: cmanCurrent DC: node1 - partition with quorumVersion: 1.1.11-97629de2 Nodes configured0 Resources configuredOnline: [ node1hb node2hb ]Full list of resources:[.]The following commands need only to be issued on one of the cluster nodes, as Pacemakerpropagates configuration to all cluster nodes automatically the moment they are committed.Configure some basic cluster parameters. As this is a two-node cluster you have to set“no-quorum-policy” to “ignore”. Adjust resource stickiness and default timeout to values whichare manageable with the SAP HANA pertyresourceresourceresourceset no-quorum-policy "ignore"defaults default-resource-stickness 1000defaults default-migration-threshold 5000op defaults timeout 600s3.5.2 Configure Fencing (STONITH)The following is just an example of how to configure fencing using the ipmi fencing method.Please choose the correct fencing method for your environment.To use IPMI for fencing you can set up STONITH with the following commands:[root]# pcs stonith create st ipmi node1 fence ipmilan \ipaddr ip of management card of node1 \login " user of management card of node1 " \passwd " password of user of management card of node1 " \pcmk host list "node1hb"[root]# pcs stonith create st ipmi node1 fence ipmilan \ipaddr ip of management card of node2 \login " user of management card of node2 " \passwd " password of user of management card of node2 " \pcmk host list "node2hb"[root]# pcs constraint location st-ipmi-node1 avoids node1[root]# pcs constraint location st-ipmi-node2 avoids node211www.redhat.com
Unfortunately "pcs stonith" currently does not provide any information on which node thefencing agent is running, so you have to use "pcs status" to get this information:[root]# pcs statusCluster name: hanasrLast updated: Thu Dec 4 12:14:34 2014Last change: Mon Dec 1 17:05:31 2014Stack: cmanCurrent DC: node1 - partition with quorumVersion: 1.1.11-97629de2 Nodes configured2 Resources configuredOnline: [ node1 node2 ]Full list of resources:st-ipmi-node1 (stonith:fence ipmilan): Started node2hbst-ipm-node2 (stonith:fence ipmilan):Started node1hbTo check if fencing actually works, test the fencing by initializing fencing on node2. Verify iffencing was successful by monitoring node2 activity:pcs stonith fence node23.5.3 Virtual IP addresses and hostnamesNow set up the virtual IP address of the cluster. This address will always be connected to theactive node. Make sure that your switches and network will permit the ip takeover:[root]# pcs resource create rsc ip SAPHana RH1 HDB00 IPaddr2 \ip "192.168.1.10"3.5.4 Create the SAPHanaTopology resourceNow create the primary SAPHanaTopology resource:[root]# pcs resource create rsc SAPHanaTopology RH1 HDB00 SAPHanaTopology \SID RH1 \InstanceNumber 00 \op start timeout 600 \op stop timeout 300 \op monitor \interval 10 timeout 6003.5.5 Create clone resource for SAPHanaTopologyCreate a clone of the primary resource, making sure that SAP HANA will be active on bothnodes:# pcs resource clone rsc SAPHanaTopology RH1 HDB00 \meta is-managed true clone-node-max 1 target-role "Started"www.redhat.com12
3.5.6 Create SAPHana resourceCreate the SAP HANA master resource. This master/slave resource will make sure that theSAP HANA system is running on both nodes, where the master will be the primary activenode1:[root]# pcs resource create rsc SAPHana RH1 HDB00 SAPHana \SID RH1 \InstanceNumber 00 \PREFER SITE TAKEOVER true \DUPLICATE PRIMARY TIMEOUT 7200 \AUTOMATED REGISTER false \op start timeout 3600 \op stop timeout 3600 \op promote timeout 3600 \op demote timeout 3600 \op monitor interval 59 role "Master" timeout 700 \op monitor interval 61 role "Slave" timeout 7003.5.7 Create Master/Slave for SAPHanaMake the SAPHana resource a master/slave resource:root]# pcs resource master msl rsc SAPHana RH1 HDB00 rsc SAPHana RH1 HDB00 \meta is-managed true notify true clone-max 2 clone-node-max 1target-role "Started"3.5.8 Set up constraintsBoth resources, SAPHanaTopology and SAPHana, need to run on the same node. They haveto be started and activated/deactivated in the correct order:[root]# pcs constraint colocation add rsc ip SAPHana RH1 HDB00 with mastermsl rsc SAPHana RH1 HDB00 2000[root]# pcs constraint order rsc SAPHanaTopology RH1 HDB00-clone thenmsl rsc SAPHana RH1 HDB00 symmetrical false1 The timeouts shown below for the start, stop, promote and demote operations are only examples and shouldbe adjusted on the local SAP HANA setup (e. g. large HANA DBs can take longer to start up therefore thestart timeout might have to be increased)13www.redhat.com
Appendix A: Reference DocumentationThe following list includes the existing documentation and articles referenced by thisdocument. SAP Note 2009879 - SAP HANA Guidelines for RedHat Enterprise Linux (RHEL)Operating System SAP Note 2013638 - SAP HANA DB: Recommended OS settings for RHEL 6.5 SAP Note 2001528 - Linux: SAP HANA Database SPS 08 revision 80 (or higher) onRHEL 6 or SLES 11 SAP Note 2063657 - HANA System Replication takeover decision guideline Availability and Scalability - SAP HANA Administration Guide How to Perform System Replication for SAP HANA Automate SAP HANA System Replication with SLES HANA System Replication - Take-over process Configuring the Red Hat High Availability Add-On with Pacemakerwww.redhat.com14
Appendix B: Example ClusterConfigurationHere is the example configuration we used in this document:Cluster Name: hanasrCorosync Nodes:node1hb node2hbPacemaker Nodes:node1hb node2hbResources:Clone: rsc SAPHanaTopology RH1 HDB00-cloneMeta Attrs: is-managed true clone-node-max 1 target-role StartedResource: rsc SAPHanaTopology RH1 HDB00 (class ocf provider heartbeattype SAPHanaTopology)Attributes: SID RH1 InstanceNumber 00Operations: start interval 0 timeout 600(rsc SAPHanaTopology RH1 HDB00-start-timeout-600)stop interval 0 timeout 300(rsc SAPHanaTopology RH1 HDB00-stop-timeout-300)monitor interval 10 timeout 600(rsc SAPHanaTopology RH1 HDB00-monitor-interval-10-timeout-600)Master: msl rsc SAPHana RH1 HDB00Meta Attrs: is-managed true notify true clone-max 2 clone-node-max 1Resource: rsc SAPHana RH1 HDB00 (class ocf provider heartbeattype SAPHana)Attributes: SID RH1 InstanceNumber 00 PREFER SITE TAKEOVER trueDUPLICATE PRIMARY TIMEOUT 7200 AUTOMATED REGISTER falseOperations: start interval 0 timeout 3600(rsc SAPHana RH1 HDB00-name-start-timeout-3600)stop interval 0 timeout 3600(rsc SAPHana RH1 HDB00-name-stop-timeout-3600)promote interval 0 timeout 3600(rsc SAPHana RH1 HDB00-name-promote-timeout-3600)demote interval 0s timeout 3600(rsc SAPHana RH1 HDB00-name-demote-timeout-3600)monitor interval 59 role Master timeout 700(rsc SAPHana RH1 -700)monitor interval 61 role Slave timeout 700(rsc SAPHana RH1 700)Resource: rsc ip SAPHana RH1 HDB00 (class ocf provider heartbeattype IPaddr2)Attributes: ip 192.168.1.10Operations: start interval 0s timeout 20s(rsc ip SAPHana RH1 HDB00-start-timeout-20s)stop interval 0s timeout 20s(rsc ip SAPHana RH1 HDB00-stop-timeout-20s)monitor interval 10s timeout 20s(rsc ip SAPHana RH1 HDB00-monitor-interval-10s)15www.redhat.com
Stonith Devices:Resource: st-ipmi-node1 (class stonith type fence ipmilan)Attributes: ipaddr node1-drac login xxxx passwd yyyypcmk host list node1hbOperations: monitor interval 60s (st-ipmi-node1-monitor-interval-60s)Resource: st-ipmi-node2 (class stonith type fence ipmilan)Attributes: ipaddr node2-drac login xxxx passwd yyyypcmk host list node2hbOperations: monitor interval 60s (st-ipmi-node2-monitor-interval-60s)Fencing Levels:Location Constraints:Resource: st-ipmi-node1Disabled on: node1hb (score:-
SAP HANA Scale-Up (single-box to single-box) System Replication 2. Both SAP HANA instances have the same SAP Identifier (SID) and Instance-Number. 3. There is no other SAP HANA system (like QAS or TST) on the replicating node which needs to be stopped during takeover. 4. Only one system replication for the SAP HANA database, no replication .
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
SAP HANA Appliance SAP HANA DB In-Memory A io BI Client non-ABAP (SAP supported DBs) SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Warehouse SAP HANA DB r In-Memory Source Systems SAP LT Replication Ser
SAP HANA System Replication SAP HANA System Replication works at the database layer. The solution is based on an additional SAP HANA system at the disaster recovery site that receives the changes from the primary system. This secondary system must be identical to the primary system. SAP HANA System Replication can be operated in one of two modes:
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 .
Health and social care services are facing increasing pressures 6. In recent years, demands on health and social care services have been increasing because of demographic changes. People are living longer with multiple long-term conditions and increasingly complex needs. At the same time, NHS boards and councils are facing increasingly difficult financial challenges. There is general .
