[email protected] +91-120-6025102
Submit

Avail Best discounts

Please fill in the form below and we will contact you within 24 hours.

How to do System Replication for SAP HANA?

The replication of SAP HANA ships all the data to secondary system situated at a website -

When SAP HANA system replication is allowed, every server functioning on secondary system makes a connection through the primary counterpart as well as requests data snapshot. Then, all the logged changes within primary system get replicated constantly. Every continued redo log within primary system has been sent to secondary.

Transaction within primary system is not dedicated prior redo logs are simulated. In addition, SAP HANA Multitenant Data Center Containers can too run in the SAP HANA system replication configuration. The whole system is replicated1 that is System DB as well as tenant DBs. When system replication is functioning, secondary system, configured similarly to primary would be on the standby till the takeover is done.

Replication Modes-

SAP HANA provides various replication modes as per the customer needs.

  1. Synchronous - The secondary system gives the acknowledgement to the primary when the data is persisted and received to the disk.
  2. Synchronous in-memory - The secondary system directs the acknowledgement back the moment data is received (it might result in the performance increase based on the disk speed).
  3. Asynchronous - According to the asynchronous replication' design, primary system do not have to wait till the time secondary sends the acknowledgement.

In addition, the SYNC (Synchronous Replication Mode) could run with enabling the "full sync". It make sure that none of the transaction could be dedicated locally with no redo log buffers' shipping to secondary site.

Operation Modes -

SPS11 SAP HANA system replication could function in two operation modes -

  1. Delta Data Shipping - Along with constant redo logo shipping, secondary system make a request to delta data shopping with the time (in every 10 minutes). During the takeover, redo log has to be replayed until last delta data shipment arrived. (It is considered as 'classical' operation mode.)
  2. Logreplay - Within operation mode, redo log shipping is ended post system replication was set up initially with the complete data shipping. Redo log is repeated on secondary directly post arrival making the step unnecessary during the takeover that shortens RTO via factors. In addition, the data amount that has to be transferred to secondary website is minimized drastically as no delta data shipping is needed.

Utilizing Logreplay operation mode makes the secondary website in SAP HANA system replication as HotStandby system.

Data moved to secondary -

HANA database directs the three kinds of data packages on the network to secondary side (as per configured operation mode) the moment system replication is constituted-

  1. Complete data shipping - The complete set of data is made as HANA snapshot over disk of primary is sent once the system replication is done.
  2. Delta data shipping - In this operation mode, the data increment (the data changed since last delta data shipping) transported time-to-time (in every 10 minutes) through primary data area to secondary data area.
  3. Redo log shipping - Each write transaction over primary makes redo log buffers, which constantly sent to secondary site.

Takeover -

Takeover is basically a name given to this process of switching the active system through present primary system in the secondary system2. When takeover runs, the earlier secondary system turns into new primary system.

Was this answer helpful? #0 #0
 

Submit Query

Please fill in the form below and we will contact you within 24 hours.