TL;DR
Rymvard released early-access version 0.23 on October 4, 2026, adding SAP HANA host-memory accounting, system placement proposals and replication takeover checks to its data center capacity ledger. Its reported test results came from a simulated landscape of 200 hosts, not a customer deployment, and real-world outcomes have not been provided.
Rymvard released version 0.23 of its early-access data center capacity ledger on October 4, adding tools to track SAP HANA memory, propose system placements and check whether a replication partner could host a system after takeover, as described in the original analysis. The company’s reported tests used a simulated landscape, not a customer deployment, so performance and operational outcomes in live environments have not been established.
The release accounts for memory on each HANA host by separating the operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity set aside for replicas from other sites, and memory still free. Rymvard says a system’s memory use is based on its 30-day peak. The default operating-system reserve is 10 percent of the first 64 GiB and 3 percent of the remainder, unless a host has a different reserve specified. If allocations exceed physical memory, the ledger marks the host as overbooked rather than reporting negative free capacity.
For HANA system replication, the software checks whether the secondary host can take the primary system’s allocation. Its result can say the system fits, fits after named systems are stopped, does not fit with a shortfall shown in GiB, or has an unknown status. Rymvard says named test or development systems may count as stoppable, while other customers’ production systems do not. A replication status older than an hour or a memory reading older than 24 hours results in unknown, rather than a passing check. Scale-out deployments 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. Rymvard says HANA instances are mirrored into its compute view for customer showback and lifecycle planning, considerations that can inform data center hardware replacement planning. A new SAP Operations workspace displays free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90 percent utilization.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
HANA Memory and Failover Planning
The release addresses a capacity-planning issue for SAP hosting providers and operations teams: overall data center capacity can appear available even when a particular HANA host or replication partner lacks enough memory for a system. Tracking memory allocation and takeover shortfalls separately may help teams identify those constraints before placement or failover, rather than relying on a broad view of facility capacity.
The practical value depends on the quality and freshness of the data feeding the ledger. Rymvard’s policy of returning an unknown result for stale readings avoids treating outdated information as proof that a takeover will work. Its placement and runway estimates could help teams compare planned deployments against capacity by site, but the release does not provide evidence of cost savings, improved reliability or 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 product does not write to SAP.
The release also lists read-only sources for landscape information: SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. These integrations are described as supported sources, not as a requirement to connect all of them. Rymvard says its test covered a simulated estate of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the software identified one production system without replication, a takeover short by 512 GiB, a host overbooked by 128 GiB and one replication in an error state. The company says its displayed screens are illustrative and do not depict a customer environment.
„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 Unknown
Rymvard describes version 0.23 as early access and has not identified a customer deployment or supplied customer results for the release. The reported findings come from a simulated landscape and do not show how the software performs across live customer environments, unusual SAP configurations or changing workloads.
The release explains the freshness thresholds and connection limits but does not provide independent evaluations or detailed evidence about validation in individual environments. Pricing is not public; Rymvard says terms are arranged with early-access partners. A broader availability date and named customers have not been announced.
HANA system replication failover tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early-Access Partner Evaluations
The next step is evaluation by early-access partners, with commercial terms agreed directly with Rymvard. Those evaluations may provide evidence about how the memory ledger and takeover checks perform in real SAP landscapes, but the company has not announced a timetable for publishing results.
Rymvard has not provided a date for broader availability or a public price list. Until it shares customer deployments or further testing, readers should treat the release’s reported scenario as a description of simulated testing rather than evidence of performance in production.
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-planning views to its data center ledger.
Were the reported results from a customer deployment?
No. Rymvard says it tested version 0.23 against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. It has not identified a customer deployment or provided customer outcomes for this release.
How does the software handle old capacity readings?
Rymvard says a replication status older than one hour, or a memory reading older than 24 hours, produces an unknown takeover status rather than a pass.
Does Rymvard say the software writes to SAP?
No. The company describes its SAP connections as read-only and says the product does not write to SAP.
When will the product be generally available, and what will it cost?
Rymvard has not announced a broader availability date or public price list. It says pricing terms are arranged directly with early-access partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
