TL;DR
Get hardware and tech essentials 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 host-memory accounting, placement proposals and replication takeover checks to its data center capacity ledger. The company reports tests on a simulated landscape of 200 hosts, not a customer deployment, so real-world performance and outcomes remain unreported.
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 update is aimed at SAP hosting providers and operations teams, but the company’s reported test results come from a simulated estate, not a customer deployment.
The software breaks down each HANA host’s physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and capacity still free. Its 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. When allocations exceed physical memory, the ledger reports overbooking rather than presenting the remaining capacity as a negative free-memory figure.
For HANA systems using system replication, version 0.23 checks whether a secondary host could accommodate the primary system’s allocation after a takeover. Rymvard reports one of four results: fits; fits after named systems are stopped; does not fit, with the shortfall shown in GiB; or unknown. A named test or development system 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, leads to an unknown result rather than a passing check. Scale-out systems are assessed as a whole, using the weakest host pair.
The release also proposes a host and replication-site partner for a new HANA system and estimates memory runway by site and quarter, weighting planned go-lives by their probability. A new SAP Operations workspace displays four indicators: 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 so their memory can feed 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
The update focuses on a planning problem for providers whose immediate constraint is memory capacity, not the broader availability of data center space or power. A site may have room in its wider infrastructure while a particular HANA host—or the secondary host expected to take over—lacks enough memory for an allocation. Showing host overbooking and replication shortfalls separately could help operations teams spot those limits before placing a system or relying on a failover plan.
The freshness rules also matter operationally. Treating stale data as unknown rather than available capacity avoids presenting an outdated status as evidence that a takeover will fit. Placement proposals and quarterly runway estimates may help teams compare planned deployments against capacity across sites. Those are described product functions, however, not demonstrated savings or proven improvements in reliability. The practical value will depend on how accurate and current the input data is, and on performance in live customer environments.
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 product 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 presents these as supported information sources; it does not say that customers must connect all of them. The company describes version 0.23 as early-access software, with terms arranged directly with early-access partners rather than a published price list.
For its reported test, Rymvard used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. The company says the scenario surfaced one production system without replication, one takeover short by 512 GiB, one host overbooked by 128 GiB, and one replication in an error state. Rymvard says the displayed screens use an illustrative estate and do not represent 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.
Live Customer Results Remain Unreported
Rymvard has not identified a customer deployment or provided customer outcomes for version 0.23. Its reported test findings are from a simulated landscape, so they do not establish how the checks perform across real customer environments, unusual SAP configurations or changing workloads. The release describes the product’s rules and query limits, but does not include independent evaluation results.
The company has not published pricing, a broader availability date or details about how quickly readings are refreshed beyond the stated age thresholds for replication and memory data. It is also unclear how integrations are validated within each customer’s environment or how the product handles every possible SAP configuration. No customer-specific savings, reliability gains or operational outcomes are stated.
HANA failover capacity check tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early-Access Partner Evaluations
Rymvard says the next stage is evaluation by early-access partners, with commercial terms arranged directly. The company has not announced a public price list, a broader release date or named customers. Further evidence from live deployments would be needed to show how the ledger’s capacity readings, takeover checks and placement suggestions perform under real operating conditions.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA host-memory accounting, placement proposals, replication takeover checks, and a workspace showing selected capacity and replication indicators.
Does the software write data to SAP?
Rymvard says its SAP connections are read-only and that the product does not write to SAP. Its described Host Agent access uses four read operations.
What happens when capacity data is stale?
The takeover result becomes unknown if replication status is more than one hour old or a memory figure is more than 24 hours old. Rymvard says the ledger does not treat stale information as a passing capacity check.
Were the reported test results from a customer?
No. Rymvard reports testing against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. It says the illustrative screens do not show a customer environment.
When will the product be generally available?
Rymvard has not announced a broader availability date. The release is in early access, with evaluations by partners expected as the next step.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
