TL;DR
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
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 software is in early access, and the company’s reported test results came from a simulated landscape, not a customer deployment.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger, as described in the original analysis. The early-access software is aimed at SAP hosting providers and operations teams, but the company’s reported tests used a simulated estate rather than a customer deployment.
The release tracks memory across each HANA host, dividing physical capacity into the operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and free memory. The default operating-system 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. When allocations exceed physical memory, the ledger shows overbooking rather than presenting a negative free-capacity figure.
For systems using SAP HANA system replication, the software checks whether the secondary host could accommodate the primary system’s allocation after a takeover. Results are reported as “fits,” “fits after stopping named systems,” a shortfall in GiB, or “unknown.” 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 produces an unknown result rather than a pass. 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 quarterly memory runway by site, using planned go-lives weighted by probability. A new SAP Operations workspace shows free HANA memory, production systems without replication, takeovers expected to fail, and hosts above 90% utilization. Rymvard says HANA instances are mirrored into its compute view for customer showback and lifecycle planning.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Making HANA Failover Capacity Visible
Memory can be the constraint that determines whether a HANA system can be placed or recovered, even when a data center has room in other parts of its infrastructure. A host may appear available at the site level while lacking enough memory for a particular allocation; a replication partner may face the same limit during a takeover. Rymvard’s ledger aims to expose those constraints as host-level overbooking and takeover shortfalls, rather than treating general infrastructure capacity as proof that HANA capacity is available.
The age thresholds matter because a capacity check is only useful if its inputs are current. By returning “unknown” for stale status or memory data, the software avoids treating outdated measurements as confirmation that a failover will fit. Placement proposals and runway estimates could also help teams compare expected deployments with capacity across sites. However, those are intended planning uses: the release materials do not establish that the product has reduced costs, improved reliability or produced measurable customer outcomes.
SAP HANA memory monitoring hardware
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Read-Only Connections and Test Scope
Rymvard says its SAP Host Agent collector connects 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. It also lists read-only sources for landscape information, including SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa; the release does not say customers must connect all of them.
Rymvard reports testing version 0.23 against a simulated estate of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it 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 that the examples do not represent a real customer, site or outcome. Those results describe the test scenario, not measured performance in a live SAP landscape.
“Nothing is ever written to SAP.”
— Rymvard
Customer Results Remain Unreported
Rymvard describes version 0.23 as early-access software and has not named a customer deployment or provided customer outcome data for the release. Its simulated test does not establish how the checks perform across live customer landscapes, unusual SAP configurations or workloads that change between readings. Independent evaluations are not included in the supplied release information.
The company also has not published prices, saying terms are arranged with early-access partners. The release specifies how old data must be before the software returns an unknown result, but does not provide further detail on update speed or how integrations are validated in each customer environment. Broader availability and a public price list have not been announced.
Early-Access Partner Evaluations
The next stated step is evaluation by early-access partners, with commercial terms negotiated directly with Rymvard. Those evaluations may provide evidence about performance in customer environments, but the company has not announced named participants, a broader release date or a public price list. Until it provides such details or customer results, version 0.23’s published test findings remain limited to the simulated estate described for the release.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA host-memory accounting, placement proposals, quarterly capacity-runway estimates and checks of whether replication partners could accommodate a takeover.
Has Rymvard tested the release in a customer data center?
The reported test used a simulated landscape of 200 hosts, 161 systems and 39 replicated pairs. Rymvard says the example screens do not show a customer environment, and it has not reported customer deployment outcomes.
How does the software handle old capacity data?
It returns an unknown takeover result if replication status is more than one hour old or a memory figure is more than 24 hours old. It does not count stale data as evidence that capacity is sufficient.
Does the Rymvard collector write to SAP?
Rymvard says its connections are read-only and that the software does not write to SAP. The release lists specific Host Agent operations and monitoring queries used to collect information.
When will the product be generally available?
No broader availability date has been announced. Rymvard says the immediate next step is evaluation with early-access partners; pricing is arranged directly with those partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
