第 1 章 Introduction to SAP HANA scale-up system replication HA
Configuring the SAP HANA system replication between two identical HANA instances enables a basic resiliency of the database. You can configure these two instances in a Pacemaker cluster for advanced high availability that automatically handles the service recovery in the case of a failure on the primary instance side.
1.1. Terminology 复制链接链接已复制到粘贴板!
node
One host or system in a HA cluster setup, also called a cluster member.
cluster
Cluster is the high-availability setup using the Pacemaker cluster manager from the RHEL HA Add-On. It consists of two or more members, or nodes.
instance
One set of SAP HANA systems that belong to one HANA site. In single-host (scale-up) HANA environments, one HANA site consists of a single HANA instance. In multiple-host (scale-out) HANA configurations, each HANA site consists of two or more HANA instances.
primary
The primary HANA instance or primary site refers to the instance which is the active HANA instance or site. In single-host setups (scale-up), this is one system. In multiple-host (scale-out) setups, the primary instance stretches across multiple systems of one HANA site and the systems have different roles in the HANA environment to distribute load.
secondary
The secondary HANA instance or secondary site refers to the SAP HANA instance or site which is configured to be synced with the primary HANA instance through the SAP HANA system replication mechanism. This instance preloads the in-memory data of the primary instance and is ready to take over if the primary instance fails.