TL;DR
Get office and shipping supplies 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 reports tests on a simulated landscape, not a customer deployment, and says the software connects to SAP through read-only interfaces.
Rymvard released version 0.23 on October 4, adding SAP HANA memory tracking, placement proposals and replication takeover checks to its data center capacity ledger, as described in the original analysis. The early-access release is aimed at SAP hosting providers and operations teams that need to assess whether hosts and replication partners have enough memory for workloads and failovers.
The software divides each HANA host’s physical memory among the operating-system reserve, memory used by HANA systems, allocated but unused capacity, capacity reserved for replicas from other sites, and memory still free. Unless a host has a different setting, the reserve is 10% of the first 64 GiB and 3% of the remaining memory. System usage is based on its 30-day peak. Allocations beyond physical memory are shown 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 a takeover. It reports whether capacity fits, fits after named systems are stopped, falls short by a stated number of GiB, or is unknown. Production systems belonging to other customers are not considered stoppable. A replication status older than one hour or a memory reading older than 24 hours results in an unknown status, not a passing check. 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 memory runway by site and quarter, using planned go-lives weighted by their probability. Rymvard says HANA instances are mirrored into its compute view for use 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 addresses a particular planning constraint: a data center may have capacity in its wider infrastructure while an individual HANA host or replication partner lacks the memory needed for a workload or takeover. Showing overbooking separately from free capacity, and identifying potential takeover shortfalls, could help operators see these limits before placing a system or relying on a failover plan.
The practical value depends on the quality and freshness of the measurements and landscape information supplied to the ledger. Rymvard’s decision to mark stale data as unknown rather than available avoids treating an outdated reading as evidence that a takeover will work. Placement proposals and quarterly runway estimates may support site-level planning, but the release provides no customer results establishing savings, improved reliability or other operational outcomes.
For hosting providers, the features bring memory capacity into a shared view alongside compute and customer planning information. That could make cross-site planning easier to discuss, particularly where HANA memory is a tighter constraint than other infrastructure resources. It remains a description of intended product functionality, however, rather than evidence that deployments have already produced those benefits.
As an affiliate, we earn on qualifying purchases.
Read-Only Connections and Test Scope
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 read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. Rymvard lists these as supported sources; the release does not say that customers must connect all of them together.
Rymvard reports testing version 0.23 against a simulated landscape 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 an actual customer, site or outcome.
“Nothing is ever written to SAP.”
— Rymvard
Customer Results Remain Unreported
Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or supplied customer outcomes for the release. Its reported test results come from a simulated environment. They do not establish performance across live customer landscapes, unusual SAP configurations or workloads that change over time.
The release description does not provide independent evaluation results or detail how integrations are validated in each customer’s environment. It also does not give a broader update cadence beyond the stated age thresholds that trigger an unknown result. Rymvard has not published a price list, saying terms are agreed with early-access partners, and has not announced a general availability date.
Early-Access Evaluations Ahead
The immediate next step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. Further evidence from live environments would be needed to show how the memory ledger and takeover checks perform across different customer landscapes and operating conditions.
Rymvard has not announced when the software will become broadly available, named an early-access customer, or published pricing. Until it releases those details or customer deployment results, the scale of adoption and the product’s real-world operational impact remain open questions.
Key Questions
What did Rymvard add in version 0.23?
Version 0.23 adds SAP HANA memory accounting, system placement proposals, replication takeover checks and a workspace showing selected HANA capacity indicators. Rymvard released it on October 4, 2026, as early-access software.
How does the software assess a replication takeover?
It checks whether the secondary host can accommodate the primary system’s allocation after takeover. Results can show that capacity fits, fits after named systems are stopped, falls short by a stated amount, or is unknown. A replication status older than one hour or a memory reading older than 24 hours produces an unknown result.
Does Rymvard write data to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The release lists read operations for the SAP Host Agent and a separate monitoring connection using SELECT queries.
Were the reported tests conducted at a customer site?
No customer deployment is identified in the release. Rymvard says its reported test used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs, and that its screens show an illustrative estate.
When will Rymvard 0.23 be generally available, and what will it cost?
The company has not announced a general availability date or public pricing. It says early-access terms are agreed directly with partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
