SAP HANA 2.0 Administration · System Replication (HA/DR)

A reconnecting SAP HANA secondary keeps triggering full data shipping. How does enable_log_retention fix that, and why is it off by default?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in System Replication (HA/DR)

A colleague wants to connect SAP HANA Cockpit directly to the standby secondary in a system replication pair to confirm it is healthy. Why does this fail by default, and what does that imply for verification?

To offload backup I/O from the production SAP HANA primary, an admin schedules data and log backups on the system-replication secondary. Why is this wrong, and when does it become possible?

You are picking the replication mode for the long-haul DR link between SAP HANA in two geographically distant data centers. Why is ASYNC the right choice here but the wrong choice for a nearby pair?

An admin sets timetravel_snapshot_creation_interval and assumes SAP HANA secondary time travel is now protecting them. Why might no recovery point actually exist?

Since a closed SAP HANA secondary accepts no sessions, how do you actually read its monitoring views (e.g. its data volumes) — and from where?

A user accidentally deletes a table on the SAP HANA primary. Why won't the system-replication secondary save you, and what feature would?

Start learning today

Free to start — download the app or use it in your browser.