Skip to Content
Technical Articles

SAP Workloads going Green

How to add more SAP instances to an existing SUSE cluster for S/4HANA or NetWeaver?

Back from SAP TechEd India I was able to continue my work on a new Best Practices document for making SAP workloads highly available. We received great feedback from SAP TechEd, SAPPHIRE and SUSECON this year and we’re doing our best take account of this feedback into continuously improving our Best Practices guides for our customers and partners.

I would also like to announce a new upcoming Best Practice guide for next year (2020) which will describe how to extend the SUSE HA cluster configuration with more than one SAP instance or SAP HANA DB. Here’s a small sneak preview for you of what’s coming. Since we don’t have a formal name yet we’ll just call it “multi-SID paper” here. This fits nicely into the slogan “SAP go green” in multiple ways. Firstly, use compute resources much more efficient. Secondly, using SUSE as OS to install the SAP application on top of it.

Running more than one S/4HANA or NetWeaver central instances in the same cluster!

For SAP central instances (ASCS/ERS) we have published multiple Best Practices:

https://documentation.suse.com/sbp/all/single-html/SAP_HA740_SetupGuide_AWS/

sap_netweaver_availability_cluster_740_setup_guide

https://documentation.suse.com/sbp/all/single-html/SAP_S4HA10_SetupGuide-SLE12/

https://documentation.suse.com/sbp/all/single-html/SAP_S4HA10_SetupGuide-SLE15/

Such a cluster looks like this simplified picture:

The question which has reached us is if we would support like the setup below?

The answer is simple: Yes we do.

What could you expect in 2020 for your SAP workloads?

Therefore we started together with Azure to prove and verify multiple scenarios for SAP central instances running in one SUSE HA cluster. The document is mostly finished and is currently in a final draft status. We still need to do some chapter restructuring and adding necessary general information before we can publish it though.

Examples topics that we will cover:

  • Multi-SID setups for ENSA1 in a two node cluster
  • Multi-SID setups for ENSA1 in a multi node cluster
  • Multi-SID setups for ENSA2 in a two node cluster
  • Multi-SID setups for ENSA2 in a multi node cluster
  • Multi-SID setups for ENSA1 and ENSA2 in a two node cluster
  • Multi-SID setups for ENSA1 and ENSA2 in a multi node cluster
  • Multiple HANA SR DB pairs running in one cluster (not planed for the first release)

 

As you may know from all our other documentation this will be freely and openly available on our SUSE Best Practices website. In other words the SUSE “generic” Best Practice can be easily adapted to all infrastructure platforms. As a result most of our partner will adapt this and provide their own documentation or have a joint documentation with us. In summary the new paper describes the additional step needed to extend a running SUSE HA cluster for ASCS / ERS with additional installed ASCS / ERS instances. In other words you will see that the guide is repeating the steps which we have done for the first instance with less adaptions. In short I hope this guide will clearly allow you to differentiate between the points for the first instance and the new points you should take care of for the additional instances.

This is Bernd for SAP LinuxLab St. Leon-Rot Germany

2 Comments
You must be Logged on to comment or reply to a post.