After completing this section, you should be able to describe the necessary steps and configuration parameters to deploy SAP HANA system replication and which roles can be used.
SAP HANA system replication is the built-in high availability function. To enable system replication between two servers, the servers must be installed identically. You must now name one server as the primary and the other one as the secondary.
The corresponding role is available on Automation Hub as part of the redhat.sap_install collection v1.1.0+ (supported), or on Ansible Galaxy as part of the community.sap_install collection (upstream, unsupported).
The following parameters are common to the other roles to prepare and install HANA, and they are also required and reused in this role:
| Name | Description |
|---|---|
sap_domain
| The domain name of the SAP systems (defaults to ansible_domain) |
sap_hana_sid
| The SID of the HANA system (such as RHE) |
sap_hana_instance_number
| The instance number of the HANA system (such as 00) |
sap_hana_install_master_password
| The database system password of both SAP HANA systems |
The following dictionary defines the HANA system replication, and is also used in the cluster roles to configure the Pacemaker cluster:
sap_hana_cluster_nodes: - node_name:HANA node 1node_ip:ÌP of node1 used for system replicationnode_role: [primary|secondary] hana_site:name of site[...]
The dictionary must contain two or three node definitions, where exactly one node must have the primary role. All other nodes have the secondary role.
The default replication mode is sync, and uses the log_replay operation mode.
You can change this behavior with the following variables:
| Name | Description |
|---|---|
sap_ha_install_hana_hsr_rep_mode
| Replication mode (defaults to sync) |
sap_ha_install_hana_hsr_oper_mode
| Operation mode (defaults to logreplay) |