3730741 - Takeover to secondary site triggered full replica with operation mode 'Logreplay'

After the takeover triggered to secondary site full replica started with operation mode 'Logreplay' which should not be the case as it should have started synchronize from the last known point — not a complete full copy. 

Traces mentioned below confirms that full replica should not be triggered:

0;2026-03-20 10:15:28.556599;a6d9fc37-a504-9949-b390-def9c2fdbc06;1;sr_register;online FullReplica=false Mode=syncmem Registrator=xxx;;yes;ok;yes;ok;;;xxx;;;;;worker;worker;1;1;;;;;;1;

But after the takeover full replica traces found on secondary site:

[2025757]{-1}[-1/-1] 2026-03-20 11:32:22.471103 i sr_dataaccess    DisasterRecoveryProtocol.cpp(09513) : Full Replica: 0 % (0/18056 GB)
[1994378]{-1}[-1/-1] 2026-03-20 11:33:54.036735 i TraceContext     TraceContext.cpp(01371) : UserName=, StatementExecutionID=844438330182994
[1994378]{-1}[-1/-1] 2026-03-20 11:33:54.036735 i Savepoint        SavepointImpl.cpp(03274) : Savepoint current savepoint version: 999228, restart redo log position: 0x20a3e48d4af9, next savepoint version: 999229, last snapshot SP version: 999227
[2138962]{-1}[-1/-1] 2026-03-20 11:37:22.474749 i sr_dataaccess    DisasterRecoveryProtocol.cpp(09513) : Full Replica: 2 % (443/18056 GB)

SAP HANA PLATFORM EDITION 2.0

SAP HANA REPLICATION

Replication, Full Replica, Failover, GUID, Missing logs, syncmem , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem