sap-ase-hadrlisted

SAP ASE (Sybase) HADR / Always-On built on SAP Replication Server — the RMA command surface (sap_status, sap_failover, sap_materialize), setuphadr, the Fault Manager, split-brain and when `force` is legitimate, sync vs async, the three-node DR topology. Use for "ASE HADR", "Sybase high availability", "Always-On", "ASE failover", "companion server", "split-brain ASE", "setuphadr". NOT HANA System Replication.
adam0thman/sap-basis-ops · ★ 0 · AI & Automation · score 72

Install: claude install-skill adam0thman/sap-basis-ops

# SAP ASE HADR (Always-On) **Source.** *SAP ASE HADR Users Guide*, **SAP Adaptive Server Enterprise 16.0 SP04**, Document Version 1.0 – 2022-09-16 **[V]** — downloaded and read directly. Marks: **[V]** verified against the live source, **[G]** cited but not re-read in full. > ## ⚠️ This is not HANA System Replication > > ASE HADR and HANA HSR solve the same *problem* with entirely different *technology*. Nothing in > `sap-hana-system-replication` transfers: there is no `hdbnsutil`, no `sr_register`, no operation > mode. **ASE HADR is built on SAP Replication Server** and is driven through the **RMA (Replication > Management Agent)** with `sap_*` commands. Do not carry HSR vocabulary across. > **Licence gate.** The Always-On option that provides HADR **requires the `ASE_ALWAYS_ON` > licence**. **[V]** Without it, none of this is available regardless of version. --- ## 1. Topology — and the version gate that decides it **[V]** | Version | Supported topology | |---|---| | Before **16.0 SP03 PL03** | **Single companion only** — one primary, one companion | | **SP03 PL03 and later** | **Three-node**: primary + companion + **disaster-recovery (DR) node** | The two-node pair provides HA (fast, optionally zero-data-loss failover); the third **DR node** provides geographic DR. Check the PL level before promising a customer a DR node. **Roles:** - **Primary** — the member where user transaction processing is allowed. - **Companion / Standby** — holds replicated copies, availa