Scroll to navigation

SAPHanaSR-angi-scenarios(7) SAPHanaSR-angi SAPHanaSR-angi-scenarios(7)

NAME

SAPHanaSR-angi-scenarios - SAP HANA system replication scenarios.

DESCRIPTION

SAPHanaSR-angi covers two topologies, scale-up and scale-out. On each topology, several scenarios are supported. Finally, for most scenarios, two variants are possible.

* Scenarios overview

The table shows the known SAPHanaSR-angi HA scenarios for HANA system replication for the two HANA topologies. The current support status is also shown.

Topology Scenario Status
Scale-Up perf-opt Supported
perf-opt, 2nd site read-enabled
perf-opt, multi-target, 3rd site outside cluster
perf-opt, multi-SID Undocumented
perf-opt, w. S/4 ENSA2 in same cluster
cost-opt
cost-opt, multi-target
perf-opt, multi-target, 3rd site inside cluster Non-supported
two perf-opt clusters connected
Scale-Out perf-opt, up to 12 nodes, no standby (BW) Supported
perf-opt, 4 nodes, 2nd site read-enabled (ERP)
perf-opt, multi-target, 3rd site outside cluster
perf-opt, up to 30 nodes w. standby (BW) Undocumented
perf-opt, multi-target, 3rd site inside cluster Non-supported
perf-opt, multi-SID
cost-opt
two perf-opt clusters connected

Note: One additional Linux cluster node at 3rd site is needed for all scale-out scenarios.

Supported - the scenario is known to work for the given topology. The setup has been tested and is documented in a setup guide. It is supported by SUSE.

Undocumented - the scenario is expected to work for the given topology. The setup is currently not documented in a setup guide. SUSE services are prepared to help with implementation. Once the setutp is working, it could be supported by SUSE.

Non-supported - the scenario is expected not to work. It is not supported by SUSE.

For details on requirements and configuration of the scenarios, please refer to manual pages SAPHanaSR-angi(7), SAPHanaSR(7) and SAPHanaSR-ScaleOut(7), as well as the respective setup guides.

* Scenario notation

It might help to describe scenarios in a pseudo-visualising notation.

Symbol Meaning
[ ] Linux cluster
A B C master nameserver node
a b c worker node
_ standby node
=> synchronous replication
-> asynchronous replication
IP address
" secondary (read-enabled) IP address

The scale-up performance-optimised multi-target scenario can be noted as:
[ A' => B ] -> C

* Variants overview

SAPHanaSR-angi allows to define different variants of reaction on failures.

Conservative – default configuration
The cluster is patient, it prefers stopping HANA over fencing nodes. It does not react on filesystem failures.

Progressive – alternative configuration
The cluster reacts on failures of HANA or filesystem with fencing all nodes of the affected site. Takeover time might be further reduced by using diskless SBD.

For details on configuration of the variants, please refer to manual pages ocf_suse_SAPHanaController(7), ocf_suse_SAPHana(7), ocf_suse_SAPHanaFilesystem(7), SAPHanaSR-alert-fencing(8), susChkSrv.py(7), SAPHanaSR_basic_cluster(7), SAPHanaSR-ScaleOut_basic_cluster(7).

EXAMPLES

* Examples for supported scenarios

[ A' => B ] -> C
[ A' => B,Q ]
[ 'Aa => "Bb ] -> Cc -> Dd
[ 'Aaaaaaa_ => Bbbbbbb_ ]

* Examples for non-supported scenarios

[ A' => B => C ]
[ 'Aa => Bb ] -> [ 'Cc => Dd ]

BUGS

In case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com.

SEE ALSO

SAPHanaSR-angi(7) , SAPHanaSR(7) , SAPHanaSR-ScaleOut(7) , ocf_suse_SAPHanaController(7) , ocf_suse_SAPHana(7) , ocf_suse_SAPHanaFilesystem(7) , SAPHanaSR-alert-fencing(8) , susChkSrv.py(7) , SAPHanaSR_basic_cluster(7) , SAPHanaSR-ScaleOut_basic_cluster(7) ,
https://documentation.suse.com/sles-sap/sap-ha-support/html/sap-ha-support/article-sap-ha-support.html ,
https://documentation.suse.com/sbp/sap-15/

AUTHORS

A.Briel, F.Herschel, L.Pinne.

COPYRIGHT

(c) 2024 SUSE LLC
The package SAPHanaSR-angi comes with ABSOLUTELY NO WARRANTY.
For details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html

05 Nov 2024