3744123 - Initialize the Secondary with Storage Copy to avoid a full data shipping while initializing replication (HSR)

This document outlines the procedure for utilizing a storage copy (snapshot) to streamline the initialization of SAP HANA System Replication (HSR). By leveraging this method, you can significantly reduce network load and setup time by avoiding a full data shipping process.

Efficient Initialization via Persistence Matching

When the secondary system is started following its registration, HANA executes several initialization optimizations to determine the most efficient sync method:

• Compatibility Check: The secondary system automatically verifies whether its current persistence (data files) is compatible with the persistence of the primary system.
• Delta Data Shipping: If the check confirms that the data on the secondary system is a valid point-in-time match (e.g., from a recently restored storage snapshot), the system bypasses the full data transfer. Instead, it requests only the delta data shipping—transferring only the changes that occurred since the snapshot was taken.

• SAP HANA Platform Edition
• SAP HANA Backup & Recovery
• SAP HANA Replication (HSR)
• SAP HANA Scale-Out

scale-out, storage copy, system replication, hsr initialization, coordinator node, worker nodes, delta data shipping, full replica, database snapshot, storage snapshot, xfs_freeze, redo log position 0, log reinitialized, close snapshot, backup data for full system , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , How To