TL;DR
Get the little things that make your day 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
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 tested the early-access software on a simulated landscape; it has not supplied customer deployment results for this release.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting, system placement proposals and replication takeover checks to its data center capacity ledger, as detailed in the original analysis. The early-access release is aimed at SAP hosting providers and operations teams, but the company’s reported test results came from a simulated landscape, not a customer deployment.
The software divides each HANA host’s physical memory among the operating-system reserve, HANA system usage, allocated but unused memory, capacity set aside for replicas from other sites, and free capacity, a key consideration in data center capacity planning. By default, it reserves 10% of the first 64 GiB and 3% of memory above that level for the operating system, unless a host has a different reserve specified. System usage is calculated using its 30-day peak. Allocations that exceed physical memory are shown as overbooking rather than hidden as negative free capacity.
For systems using HANA system replication, the ledger checks whether a secondary host could take over the primary system’s allocation. It can treat named test or development systems as stoppable, but does not assume that other customers’ production systems can be stopped. Results are categorized as fitting, fitting after named systems are stopped, not fitting with a shortfall measured in GiB, or unknown. A replication status older than one hour, or a memory reading older than 24 hours, results in an unknown status rather than a pass. Scale-out systems are assessed as a whole, based on 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, using planned go-lives weighted by probability, complementing detailed data center deployment tracking. Rymvard says HANA instances are mirrored into its compute view so the memory figures can be included in customer showback and lifecycle planning. A new SAP Operations workspace displays free HANA memory, production systems without replication, takeovers that would fail and hosts above 90% utilization.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Making HANA Failover Capacity Visible
The release focuses on a planning problem for providers whose limiting resource is memory rather than power. A facility may have capacity across its wider infrastructure while an individual HANA host or replication partner lacks enough memory for a system allocation. Separating overbooking from free capacity, and showing takeover shortfalls, could make those constraints easier for operations teams to identify before placing a system or relying on failover.
The usefulness of those views depends on the accuracy and freshness of the underlying readings. Rymvard’s rule that outdated measurements produce an unknown result avoids treating stale information as evidence that a takeover will work. Placement suggestions and quarterly runway estimates may help teams compare planned deployments with capacity at each site, but the release materials do not establish that the features reduce costs, improve reliability or produce other customer outcomes.
As an affiliate, we earn on qualifying purchases.
Read-Only SAP Data Connections
Rymvard says its collector connects to the SAP Host Agent over HTTPS and is limited to four read operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. A separate monitoring connection uses TLS and a fixed set of six 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 product can also read system, customer and environment information through interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. The release lists these as supported sources; it does not say that customers must connect all of them. Rymvard describes the product as early access, with commercial terms agreed directly with early-access partners rather than published prices.
“Nothing is ever written to SAP.”
— Rymvard
Customer Results Remain Unreported
Rymvard reports testing version 0.23 against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the software identified one production system without replication, a takeover short by 512 GiB, a host overbooked by 128 GiB, and a replication in an error state. The company says the displayed screens use an illustrative estate, not a customer environment, and do not represent a real customer, site or outcome.
The release does not identify a customer deployment or provide customer results, independent evaluations or performance data from live environments. It also does not describe how the software handles every SAP configuration, how integrations are validated in each environment, or how frequently readings update beyond the stated thresholds. The reported scenario shows what the software found in a simulation; it does not establish how the checks perform with real workloads or unusual configurations.
Early-Access Partner Evaluations
Rymvard says the next step is evaluation with early-access partners, with pricing arranged directly rather than through a public price list. The company has not announced a broader availability date or named a customer deployment. Further information about live deployments, configuration coverage and performance in customer environments would help establish how the simulated results translate to operational use.
Key Questions
What did Rymvard add in version 0.23?
Version 0.23 adds SAP HANA memory accounting, placement proposals for new systems, replication takeover-capacity checks, and memory runway estimates by site and quarter.
How does the software report whether a takeover can fit?
It reports whether the allocation fits, fits after named test or development systems are stopped, does not fit with a shortfall in GiB, or is unknown. A replication status older than one hour or a memory figure older than 24 hours produces an unknown result.
Does Rymvard write to SAP systems?
Rymvard says its SAP connections use read-only operations and states, “Nothing is ever written to SAP.” The release describes connections to SAP Host Agent and several other landscape-information sources.
Has the software been tested at a customer site?
The test results described in the release came from a simulated landscape of 200 hosts, 161 systems and 39 replicated pairs. Rymvard has not identified a customer deployment or provided customer outcomes for this release.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
