cancel
Showing results for 
Search instead for 
Did you mean: 

HANA Replication Duration, Resync between Sites

SAPSupport
Employee
Employee
0 Kudos
330

We are going to perform HANA upgrade in Production in the next few days, we had recently performed another maintenance activity few weeks back where we had to perform failover and failback between Primary and HA to ensure that failover & failback are intact after the maintenance activity where we noticed that the replication duration between sites is increased massively which is close to 3 hrs because of the size of data that is grown exponentially.

As we are performing upgrade, we again want to perform failover/failback to check if it's working intact after the upgrade however we don't want to wait for 3 hours of duration from A --> B and 3 hours of duration again from B-->A during our checks. Can you please let us know if there is advanced way to avoid the full data to be shipped and can we just have the delta changes to be shipped between sites because if we de-attach secondary and attach it back then the full data sync will start by default.


------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

Accepted Solutions (1)

Accepted Solutions (1)

SAPSupport
Employee
Employee
0 Kudos

The possibilities regarding your question are below:

To avoid the full data shipment, you can initialize the secondary with a binary storage copy from the primary system as explained in SAP HANA System Replication - Initialize the Secondary with Storage Copy from Primary at:https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/a209b098c97d4a1fa0e3c1f...

Result:

When the secondary system is started after the new registration, the initialization optimizations are carried out. The system checks if the persistence of the secondary system is compatible with the persistence of the primary system. The secondary system checks if its persistence is compatible with the persistence of the primary system. If this check succeeds, the secondary system requests only a delta data shipping.

See also the below information about how the Resync works:

1. SAP HANA System Replication - Initializing the Secondary at:https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/e3218c27ef364eb9afc0041...

2. SAP HANA Administration Guide for SAP HANA Platform - Resync Optimization at:https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/41f5c470abc943ad9ae3882...

Answers (1)

Answers (1)

0 Kudos

Hi,

We have opened the link given above and have some open questions.

1) Is there any defined procedure on taking an consistent binary storage copy from the primary system for the persistence of all services?

2) Reg "Replace the persistence of the secondary system with the storage copy from the primary system", can we know which file and in which location in secondary is the storage copy is supposed to be replaced?