SAP HANA disaster recovery and SAP Business One environments engineered for African operating conditions.
912 designs, implements, and tests SAP HANA disaster recovery for SAP Business One environments — using HANA System Replication in asynchronous mode with a deliberately manual failover gate. ETIMS-ready, runbook-documented, and tested.
What 912 Deploys
The specific SAP capabilities we scope.
Product names identify technologies in scope. They do not by themselves imply partnership, authorization, certification, or a universal recommendation.
SAP HANA System Replication (Async)
Primary-to-DR HANA database replication over MPLS. Asynchronous mode is the deliberate choice — protects production performance while exposing only seconds-to-minutes of data loss in normal link conditions.
SAP Business One DR Application Server
Production-grade SAP Business One application server at the DR site, sized for all production users at full load. Ready to assume operations on takeover.
Mainserver File Replication
Replicates attachments, notes, report files, and Crystal Reports templates. The data outside the HANA database that still has to fail over with the business.
KRA ETIMS DR Configuration
ETIMS installed, configured, and tested at the DR site so tax-compliant invoicing continues after failover. Mandatory for Kenyan operations.
Why SAP
How the technology fits an operating decision.
The fit depends on the estate, licences, prerequisites, integrations, people, support responsibilities, and alternatives.
Manual failover prevents split-brain corruption
Automatic failover under flapping MPLS links is where SAP environments lose data permanently. We use a manual failover gate — hdbnsutil -sr_state check, stakeholder notification, then hdbnsutil -sr_takeover — to guarantee data integrity over a few extra minutes of recovery time.
Honest RPO framing
Asynchronous replication exposes seconds-to-minutes of data loss in normal conditions. We document that exposure rather than promising zero data loss we cannot deliver synchronously without crippling daily performance.
ETIMS continuity is not optional
A SAP DR plan that doesn't ship with ETIMS at the DR site is broken for any Kenyan business — tax-compliant invoicing breaks the moment you fail over. We treat ETIMS configuration as part of the base DR scope, not an add-on.
Engagement Model
How 912 deploys SAP, step by step.
The cadence we follow on every SAP engagement. Slots into the broader 912 six-phase engagement model — see How We Work for the full delivery cadence.
Step 01Architecture & sizing
DR HANA server sized to match primary class (typically 2 sockets, 256 GB RAM, 4 TB storage minimum). DR application server sized for full production load. MPLS latency benchmarked from the carrier.
Step 02Build & configure
SUSE Linux Enterprise Server for SAP installed. HANA System Replication configured in async mode. SAP Business One DR application server provisioned. ETIMS installed and tested at DR. Mainserver file replication wired.
Step 03Runbook documentation
Step-by-step failover procedure: confirm outage → check replication state → notify stakeholders → takeover on DR node → update DNS → start SAP Business One services → verify invoice posting + ETIMS. Same for failback during maintenance window.
Step 04Daily HANA backups
Last-resort protection against corruption or total loss. Daily HANA backups to offsite storage in addition to the replication architecture.
Proof Points
Source-backed specifics, not vague claims.
These figures and terms are explicitly attributed in the review note below. Final commercial terms depend on the current vendor quote and the signed 912 scope.
HANA replication mode (deliberate choice for performance + integrity)
Failover gate — split-brain prevention by design
KRA-compliant invoicing post-failover
Proposal validity standard on SAP DR engagements
Architecture based on an anonymized SAP HANA DR engagement for a Kenyan manufacturer. SAP Business One DR permission, HANA DR licence, and SUSE Linux Enterprise Server for SAP subscriptions remain client-side per standard SAP commercial terms.
Related 912 Services
The 912 service pages that lean on SAP.
Each service brief includes the SAP components, the broader engagement model, and the FAQs around scope, pricing, and support.
Scope your SAP engagement in one call.
We’ll walk through your environment, recommend the right product set, and produce a written proposal you can hold us to.