SAP Hana System Replication
SAP HANA system replication allows you to copy and synchronisea SAP HANA database to a secondary location within or outside of the same data centre. System replication is commonly used to ensure high availability and disaster recovery.
This approach ensures that your SAP HANA system is always available. The SAP recommended configuration for reducing SAP HANA outages due to planned maintenance, faults, and disasters is system replication. It has a recovery time target (RTO) of minutes and a recovery point objective (RPO) of 0 seconds.
Each server process on the secondary system establishes a connection with its primary system counterpart and requests a snapshot of the data when you enable SAP HANA system replication. SAP HANA then replicates all logged changes in the primary system in real time. The system transmits logs to the secondary system at the same time as it writes logs to the log volumes of each service, persisting the logs.
After replicating the redo logs, the primary system commits a transaction. This process is determined by the replication mode you chose while setting up system replication.
SAP Hana LT Replication
The SAP Landscape Transformation (SAP LT) Replication Server is a SAP technology that allows you to load and replicate data from ABAP and non-ABAP source systems into a SAP HANA environment in real time. To transmit data from the source system to the destination system, the SAP LT Replication Server uses a trigger-based replication mechanism.
You can build transformation rules to selectively filter the data (selective data replication) or to enable additional transformations throughout the data replication process if not all data records in a database should be transmitted.
In addition to new functionalities, SAP HANA matures and enhances the security and stability of the data with each release. SAP HANA includes a replication solution named SAP HANA System Replication for High Availability and Disaster Recovery.
SAP HANA System Replication allows you to copy and synchronise a HANA database to a secondary location in the same or a different data centre on a regular basis. This technique may be confused with SAP HANA LT Replication Server (SLT. LT = Landscape Transformation), which allows data to be put into SAP HANA Database from both ABAP and non-ABAP systems.
Considerations for a SAP HANA Database replication system:
Both the primary and secondary systems must be operational, self-contained, and have an equal number of active nodes.
The master node is where you configure everything.
The secondary system’s version and update must be equal to or greater than the primary system’s.
The SID and instance number of the secondary system must match those of the primary system.
Changes to INI files on one machine must be manually applied to the other.
Before turning on the replication system, it’s a good idea to establish a backup.
The secondary system may be used for development or testing, while the primary system is used for production. If this is the case, it should be noted that the replication system consumes 10% of the secondary system’s resources.
The replication mechanisms employed will be determined by the distance between the data centres.