TL;DR
Get tech for your team 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 capacity-planning software. Its reported results came from a simulated landscape of 200 hosts, not a customer deployment, and real-world performance remains unverified.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger. The early-access software is intended to help hosting providers and operations teams identify memory constraints when placing HANA systems or planning failover, but the company’s reported tests used a simulated estate rather than a customer deployment.
The release breaks down each HANA host’s physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity reserved for replicas from other sites, and remaining free capacity, supporting data center planning. The default operating-system reserve is 10% of the first 64 GiB and 3% of the rest, unless a host has a different reserve configured. System usage is based on its 30-day peak. Allocations that exceed physical memory appear as overbooking, rather than being hidden as negative free capacity.
For systems using HANA system replication, Rymvard checks whether the secondary host could accommodate the primary system’s allocation after takeover. It returns one of four results: fits, fits after stopping named systems, does not fit with 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 an hour or a memory reading older than 24 hours leads to an unknown result. Scale-out systems are assessed as a whole, with the weakest host pair determining the outcome.
The software also proposes a host and replication-site partner for a new HANA system and estimates site-level memory runway by quarter, weighting planned go-lives by probability. A new SAP Operations workspace displays free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90% utilization. Rymvard says HANA instances are mirrored into its compute view so that SAP memory can appear in customer showback and lifecycle planning.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Why HANA Memory Can Limit Placement
The release addresses a planning problem that can be obscured by broader data center capacity figures: a site may have room in its overall infrastructure while a particular HANA host or replication partner lacks enough physical memory for a workload or failover. By showing host overbooking separately from free capacity, the ledger is designed to make those constraints more visible before a placement decision or takeover.
The checks may also help teams distinguish a genuine capacity pass from an outdated reading. Treating stale data as unknown rather than available avoids presenting old measurements as proof that a replication target can support a system. That is a feature of the stated rules, not evidence that the product improves availability or prevents outages in customer environments.
For providers managing planned deployments across sites, quarterly runway estimates and placement proposals could support comparisons between expected demand and available memory. However, the release provides no customer outcomes or independent evaluation establishing savings, reliability gains or operational impact. The practical value will depend on the quality of the source data and how well the software fits each customer’s landscape.
SAP HANA memory capacity planning software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
How the Ledger Gets SAP Data
Rymvard says its collector connects to the SAP Host Agent over HTTPS and permits 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 release also lists read-only connections for landscape information from SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard names these as supported sources; the release does not say that customers must use all of them together.
Version 0.23 was tested against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, Rymvard reports that the software 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 the displayed screens use an illustrative estate, not a customer environment.
“Nothing is ever written to SAP.”
— Rymvard
Customer Performance Remains Unverified
Rymvard describes version 0.23 as early access and has not identified a customer deployment or supplied customer outcomes for the release. The reported test findings come from a simulated landscape, so they do not establish how the product performs across live customer environments, unusual SAP configurations or workloads that change over time.
The release explains the data-age thresholds and query limits, but does not provide independent validation of its integrations or detail how quickly readings update in every environment. Rymvard has also not published prices, saying terms are arranged with early-access partners. A broader availability date and named customers have not been announced.
Early-Access Evaluations Ahead
The next step is evaluation by early-access partners, with pricing arranged directly with Rymvard. The company has not announced a public price list, a broader release date or named participants. Those evaluations could provide the customer evidence that is absent from the current simulated test results, but no outcomes or schedule have been disclosed.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA host-memory accounting, placement proposals, replication takeover checks, quarterly memory-runway estimates and an SAP Operations workspace.
Has the software been tested at a customer site?
Rymvard’s reported test used a simulated landscape of 200 hosts, 161 systems and 39 replicated pairs. The company says its example screens do not show a customer environment and has not identified a customer deployment for this release.
How does the software handle old capacity readings?
It reports a takeover result as unknown if replication status is more than an hour old or a memory figure is more than 24 hours old. It does not treat those stale readings as a passing result.
Does Rymvard write to SAP systems?
The company says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The release describes specific permitted Host Agent operations and a separate monitoring connection.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
