System Replication (HA/DR)

How does SAP HANA ASYNC replication behave, and what is its main trade-off?

In SAP HANA active/active read-enabled, how is read-access memory capped, and what is the default?

What constraint does the active/active read-enabled option place on SAP HANA version upgrades?

In SAP HANA system replication, what mode does the secondary run in, and what does each secondary service do?

What is storage replication in the SAP HANA context, and why is the secondary HANA instance inactive during it?

In SAP HANA system replication, when does the secondary need to re-register after the primary is recovered?

Which SAP HANA script gives a takeover recommendation, and what three results can it return?

In SAP HANA multitier (multitarget) system replication, how are the replication modes typically arranged across three data centers?

What does the SAP HANA SYNCMEM (synchronous in-memory) replication mode wait for before committing?

Which SAP HANA parameter caps how much log space is kept for resyncing a secondary, and what is its default?

In SAP HANA, what consideration applies to making backups in a system-replication landscape?

What is the order of operations to disable SAP HANA system replication, and what is the precondition?

What two ways can read queries be directed to the secondary in an SAP HANA active/active read-enabled setup?

What is the key performance advantage of SAP HANA system replication over storage replication at takeover?

Why is the SAP HANA `enable_log_retention` parameter disabled by default on the secondary, and what does it do?

In SAP HANA, how can the system views of a closed secondary be queried from the primary?

Which SAP HANA parameter caps the retention of the last data-shipping snapshot for resync, and what is its default?

What does the SAP HANA active/active read-enabled option provide, and which operation mode enables it?

What is the difference between the SAP HANA replication mode and the operation mode?

How are database connections suspended for SAP HANA zero-downtime maintenance with ABAP?

How does an SAP HANA system map hostnames to IP addresses for replication, given it doesn't use DNS or the hosts file?

What is SAP HANA system replication, and at what level does it operate?

What are the three SAP HANA system-replication operation modes?

Which command performs an SAP HANA takeover from the command line, and what does the `--suspendPrimary` option add?

What is SAP HANA secondary time travel, and what does it solve that ordinary system replication cannot?

In an SAP HANA multitier setup, why must `enable_log_retention` be set to `force_on_takeover` rather than just `on`?

Which SAP HANA parameter restricts which hosts may send system-replication traffic, and where is it set?

What is SAP HANA zero-downtime maintenance with SAP solutions, and which stack does it support?

What does the SAP HANA `listeninterface` parameter (`.local` / `.internal` / `.global`) control for system replication networking?

After an SAP HANA takeover, how do you fail back to the original primary?

What does the SAP HANA `logshipping_timeout` parameter do, and what is its default?

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

Which two parameters configure SAP HANA secondary time travel, and what are their defaults?

What hardware constraint applies when using SAP HANA system replication to exchange hardware?

How does SAP HANA SYNC replication differ from SYNC with the full sync option (`enable_full_sync`)?

What happens to the SAP HANA license on the secondary after deregistering it from system replication?

Can multiple secondaries be used for read access in SAP HANA active/active read-enabled, and with what limitation?

What are the prerequisites for SAP HANA multitier system replication?