SAPHanaTopology - SAP HANA on Amazon
SAPHanaRHEL 7.xRHEL 8.xOverlay IP
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

SAPHanaTopology

The SAPHanaTopology resource gathers the status and configuration of SAP HANA System Replication on each node. Configure the following attributes for SAPHanaTopology.

Run the following command to create the SAPHANATopology resource: 


[root@prihana~]# pcs resource create SAPHanaTopology_HDB_00 SAPHanaTopology \
SID=HDB InstanceNumber=00 \
op start timeout=600 \
op stop timeout=300 \
op monitor interval=10 timeout=600 \
clone clone-max=2 clone-node-max=1 interleave=true

SAPHana

The SAPHana resource is responsible for starting, stopping, and relocating the SAP HANA database. This resource must be run as a primary/secondary cluster resource. To create this resource, run the following command:

RHEL 7.x


[root@prihana~]# pcs resource create SAPHana_HDB_00 SAPHana \
SID=HDB InstanceNumber=00 PREFER_SITE_TAKEOVER=true \
DUPLICATE_PRIMARY_TIMEOUT=7200 AUTOMATED_REGISTER=true \
op start timeout=3600 \
op stop timeout=3600 \
op monitor interval=61 role="Slave" timeout=700 \
op monitor interval=59 role="Master" timeout=700 \
op promote timeout=3600 \
op demote timeout=3600 \
master notify=true clone-max=2 clone-node-max=1 interleave=true

RHEL 8.x


[root@prihana~]# pcs resource create SAPHana_HDB_00 \
SAPHana SID=HDB InstanceNumber=00 PREFER_SITE_TAKEOVER=true \
DUPLICATE_PRIMARY_TIMEOUT=7200 AUTOMATED_REGISTER=true \
op start timeout=3600 \
op stop timeout=3600 \
op monitor interval=61 role="Slave" timeout=700 \
op monitor interval=59 role="Master" timeout=700 \
op promote timeout=3600 \
op demote timeout=3600 \
promotable meta notify=true clone-max=2 clone-node-max=1 interleave=true
Note

If the AUTOMATED_REGISTER parameter is set to true, the secondary instance will automatically register after startup, and start the replication.

Overlay IP

Add the Overlay IP (OIP) address to the primary node using the following command: 

[root@prihana ~]# ip address add <overlay IP address>/32  dev eth0

To route the traffic to your primary SAP HANA database with Overlay IP, you must update the route table and map the Overlay IP address to the primary SAP HANA database instance-id. 


[root@prihana ~]# aws ec2 create-route --route-table-id rtb-xxxxxxxx \
--destination-cidr-block <overlay IP address> --instance-id i-xxxxxxxx

pcs resource create hana-oip \
aws-vpc-move-ip ip=<overlay IP address> interface=eth0 routing_table=rtb-dbexxxxx

If you are using different route tables for subnet in each Availability Zone where you are deploying the SAP HANA instances, you need to update the OIP in the route table associated with both the subnets. To create the resource in such scenario, you can use the previous command and mention both the route table IDs separated by a comma. See the following example: 


[root@prihana ~]# pcs resource create hana-oip aws-vpc-move-ip \
ip=<overlay IP address>  \
interface=eth0 \
routing_table=rtb-xxxxxxx,rtb-yyyyyyyy