SAP Knowledge Base Article - Preview

3059109 - HANA DB After System Replication takeover a failback initialises with full data shipping

Symptom

After HDB cluster failover its observed that during a failback former primary was syncing with new primary with full replica. Why is former primary doing full replica instead of using retained log.

Nameserver trace of the former primary (new secondary) contains info messages like:

i PersistenceManag PersistenceManager.cpp(00341) : no valid replication snapshot found -> sync primary and secondary with full data shipping!


Read more...

Environment

SAP HANA Platform 2.0

Product

SAP HANA, platform edition 2.0

Keywords

Log Retention, snapshot, savepoints, sync , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.