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?

For ABAP zero-downtime SAP HANA maintenance you create the trigger file hdb_quiesce.dat but connections are never suspended. What setup step was skipped?

getTakeoverRecommendation.py returns "Cannot decide" for your SAP HANA pair. What does that actually mean, and why is it not a green light to take over?

With SAP HANA storage replication, why is the secondary HANA instance not even started — and what does that cost you at failover versus HANA system replication?

You want to use SAP HANA system replication to migrate to new hardware. Which target difference is hard-blocked, versus the many that are allowed?

Your landscape has both ABAP and Java application servers on SAP HANA. Why can you do a zero-downtime maintenance window for one stack but not the other?

SAP HANA system replication can't resolve the partner site's hostname. Why is editing DNS or /etc/hosts the wrong fix, and where do you actually fix it?

In a 3-tier SAP HANA replication chain, why must enable_log_retention be force_on_takeover rather than just on to avoid a full sync of the third system?

What is the correct order and precondition to cleanly disable SAP HANA system replication, and what breaks if you start on the primary?

On an SAP HANA active/active read-enabled secondary, your big analytic read fails on memory even though the host has plenty of RAM. What default cap explains this?

When configuring SAP HANA replication networking, how do you choose between listeninterface = .internal and .global, and what must accompany .global?

After recovering an SAP HANA primary, what single property decides whether the secondary just resumes or must be re-registered?

An admin tries to set up SAP HANA system replication for only one tenant database in a multi-tenant instance. Why isn't that how it works?

Reads on an SAP HANA active/active read-enabled secondary can lag the primary. Given that, what consistency does a query there actually get — and which workloads must NOT use it?

You configure multiple read-enabled secondaries in SAP HANA to spread read load. What limitation of hint-based routing constrains your design?

After an SAP HANA takeover, how do you fail back to the original primary — and why is there no dedicated "failback" command?

SYNC and SYNC with full sync (enable_full_sync) both persist the log to disk on both SAP HANA nodes before commit. What is the one behavioral difference — and why is full sync dangerous for OLTP?

When does the default value of SAP HANA's allowed_sender become a real exposure, and how do you close it?

Active/active read-enabled won't open your SAP HANA secondary for reads even though replication is healthy on SYNC. Which setting actually controls it?

Between SAP HANA operation modes delta_datashipping and logreplay, which gives the faster takeover and why?

At takeover, what one capability lets SAP HANA system replication recover with far less performance impact than storage replication?

Why must you stop relying on active/active read-enabled reads during an SAP HANA release upgrade, and what's the correct upgrade order?

Which SAP HANA monitoring view/command shows system-replication status, and which view columns confirm a read-enabled secondary?

What exactly does SAP HANA SYNCMEM wait for before commit, and how does that distinguish it from plain SYNC?

Which non-obvious prerequisite, beyond identical installs, will silently block SAP HANA multitier system replication if missed?

When the SAP HANA secondary stops responding, what does the primary do after logshipping_timeout (default 30s) — and why is that the safe behavior?

What time-bomb does deregistering an SAP HANA secondary from system replication start on its license?

What does adding --suspendPrimary to hdbnsutil -sr_takeover change, and when does that justify a planned takeover over a plain one?

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

Why can setting SAP HANA logshipping_max_retention_size = 0 cause a log-full on the primary, and what should you do if the secondary will be down a long time?

In delta_datashipping mode, why can a secondary that reconnects after only a few minutes still trigger a full SAP HANA data shipping?