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 company says it tested the early-access software on a simulated landscape, not a customer deployment, and has not provided customer outcome data.
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 update is aimed at SAP hosting providers and operations teams, but the company’s published test results are from a simulated estate rather than a customer deployment, as detailed in the original analysis.
The software divides each HANA host’s physical memory among the operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity reserved for replicas from other sites, and remaining free capacity, supporting the kind of data center capacity tracking used in infrastructure planning. Rymvard’s 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 calculated from its 30-day peak. If allocations exceed physical memory, the ledger displays overbooking rather than presenting a negative free-capacity figure.
For systems using HANA system replication, version 0.23 checks whether a 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 treated as stoppable, but production systems belonging to other customers are not. A replication status older than one hour or a memory reading older than 24 hours yields an unknown result. Scale-out systems are assessed as a whole using the weakest host pair.
The update 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. Rymvard says HANA instances are mirrored into its compute view for 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 addresses a planning problem for providers whose constraint is memory capacity rather than power or overall facility space. A data center may have room in its wider infrastructure while a particular HANA host, or a replication partner, lacks enough memory for a workload. Separating overbooking and takeover shortfalls in a capacity ledger could help operations teams identify those constraints before placing a system or relying on failover.
The stale-data rules also affect how teams should interpret the checks: an old measurement is marked unknown, not available. That is a cautious distinction for planning, but its practical value depends on the accuracy and freshness of the source data. Rymvard’s placement and runway views may support comparisons between planned deployments and site capacity; the release materials do not establish savings, improved reliability or 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 uses 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 access to system, customer and environment information through SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. These are described as supported information sources, not as tools that must all be connected together. The company characterizes version 0.23 as early-access software.
For its reported test, Rymvard used a simulated landscape containing 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it identified one production system without replication, one takeover with a 512 GiB shortfall, one host overbooked by 128 GiB, and one replication in an error state. Rymvard says the displayed screens use an illustrative estate, not a customer environment; those examples do not identify a real customer, site or outcome.
“Nothing is ever written to SAP.”
— Rymvard
data center capacity planning software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Customer Evidence Is Still Pending
Rymvard has not named a customer deployment or supplied customer outcomes for version 0.23. The reported findings come from a simulated landscape, so they do not show how the software performs across live customer environments, unusual SAP configurations or workloads that change over time. The release describes its accounting rules and data-age thresholds, but does not provide an independent evaluation or real-world performance results.
Other details remain undisclosed, including public pricing, a date for broader availability, and how integrations are validated in individual environments. Rymvard says early-access terms are agreed directly with partners. The release also does not establish how quickly capacity readings update beyond the stated thresholds or how every possible SAP configuration is handled.
As an affiliate, we earn on qualifying purchases.
Early-Access Partner Evaluations
The stated next step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. The company has not announced a broader release date, public price list or named customer. Further evidence from live deployments would be needed to assess how the memory ledger and takeover checks perform in operational environments.
Until such information is available, version 0.23’s documented functions and simulated test results describe the product’s current capabilities as presented by Rymvard, rather than verified customer results. Prospective users will need to assess whether their SAP data sources, configurations and monitoring practices meet the product’s stated requirements.
HANA system replication failover tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA memory accounting, system placement proposals, replication takeover checks and related capacity views to its data center ledger.
Were the reported tests run at a customer site?
No. Rymvard says its test used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. It has not supplied customer outcomes for this release.
How does the software handle stale capacity data?
It reports a takeover result as unknown when replication status is more than one hour old or a memory figure is more than 24 hours old.
Does Rymvard write data to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.”
When will the software be generally available?
The company has not announced a broader availability date. Its stated next step is evaluation by early-access partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
