Counting SAP HANA Memory In Data Center Capacity With Rymvard

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get the latest gadgets delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Rymvard released version 0.23 on October 4, 2026, adding SAP HANA memory accounting, placement proposals and replication takeover checks to its data center capacity ledger. The company reports testing on a simulated 200-host landscape; it has not disclosed customer deployment results for this release.

Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication-capacity checks to its data center capacity ledger, as detailed in the original analysis. The early-access software is aimed at SAP hosting providers and operations teams, but the test results disclosed with the release came from a simulated estate, not a customer deployment.

The release divides each HANA host’s physical memory among an operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity set aside for replicas from other sites, and remaining free memory. The default reserve is 10% of the first 64 GiB and 3% of the remainder, unless a host has a different reserve configured. System usage is based on its 30-day peak. If allocations exceed physical memory, the ledger flags overbooking instead of representing the excess as negative free capacity.

For systems using SAP HANA system replication, Rymvard checks whether a secondary host could take over the primary system’s allocation. It reports whether the takeover fits, fits after named systems are stopped, falls short by a stated amount of memory, or cannot be assessed. Named test or development systems may be counted as stoppable; production systems belonging to other customers are not. A replication status older than one hour or a memory reading older than 24 hours results in an unknown status, not a passing result. Scale-out systems are evaluated as a whole, using the weakest host pair.

Version 0.23 also proposes a host and replication-site partner for a new HANA system and estimates memory runway by site and quarter, based on planned go-lives weighted by probability. Rymvard says HANA instances are mirrored into its compute view for customer showback and lifecycle planning. A new SAP Operations workspace shows free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90% utilization.

Making HANA Failover Capacity Visible

The release addresses a specific capacity-planning problem: a data center may have room across its broader infrastructure while an individual HANA host or replication partner lacks enough memory for a workload or takeover. Separating free memory, reserved replica capacity and overbooking could help operators spot those constraints before placing a system or relying on a failover.

The checks are relevant to service providers responsible for multiple customer systems, because Rymvard’s rules do not treat another customer’s production workload as something that can simply be stopped to make room. The stale-data thresholds also limit what the software claims to know: outdated measurements produce an unknown result, rather than evidence that a takeover will succeed. The announced features describe planning and monitoring functions, however; the supplied information does not establish savings, improved reliability or other customer outcomes.

Read-Only SAP Data and Test Scope

Rymvard says its collector connects to the SAP Host Agent over HTTPS and uses four read operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. A separate monitoring connection uses TLS and six fixed SELECT queries, with a 60-second limit per system and no more than eight systems queried at once. The company says the software does not write to SAP.

The release also lists read-only connections to SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. These sources can supply landscape information alongside HANA memory data; Rymvard does not say that customers must use all of them together.

For its reported test, Rymvard used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it identified one production system without replication, one takeover short by 512 GiB, one host overbooked by 128 GiB, and one replication in an error state. The company says displayed screens use an illustrative estate, not a customer environment, and do not represent a real customer, site or outcome.

“Nothing is ever written to SAP.”

— Rymvard

Customer Evidence Is Still Pending

Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or provided customer outcomes for this release. The disclosed test is simulated, so it does not show how the system performs across live customer landscapes, unusual SAP configurations or workloads that change over time.

The release explains some query limits and data-age thresholds, but does not provide independent evaluation results or detail how every supported integration is validated in a particular environment. Rymvard has also not published prices, saying terms are arranged with early-access partners. A broader release date and a named customer have not been announced.

Early-Access Evaluations Ahead

The next stated step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. The company has not announced a public price list, broader availability date or named customer. Evidence from live deployments, if disclosed, would help establish how the ledger’s memory readings and takeover checks perform beyond the simulated scenario.

Key Questions

What did Rymvard add in version 0.23?

It added SAP HANA memory accounting, host and replication-site placement proposals, and checks of whether a secondary host can accommodate a system takeover.

Was the reported test conducted at a customer site?

No. Rymvard says its results came from a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. It did not report a customer deployment for this release.

What happens when the capacity data is old?

The result becomes unknown if replication status is more than one hour old or a memory figure is more than 24 hours old. Rymvard does not count stale data as proof that a takeover will fit.

Does Rymvard write data to SAP?

The company says its SAP connections are read-only and states that the software does not write to SAP.

When will the software be generally available?

Rymvard has not announced a broader availability date. The stated next step is evaluation by early-access partners.

Primary source: Rymvard · via ThorstenMeyerAI.com