TL;DR
Get school and study 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 early-access 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’s reported results came from a simulated estate, and it has not identified a customer deployment or provided real-world outcomes.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger, as detailed in the original analysis. The early-access release is aimed at SAP hosting providers and operations teams, but the company’s reported test results came from a simulated environment, 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 memory, capacity reserved for replicas from other sites, and remaining free memory, complementing precise rack deployment tracking for data center operations. Unless a host has a different setting, the default operating-system reserve is 10% of the first 64 GiB and 3% of the memory above that. System usage is calculated from its 30-day peak. If allocations exceed physical memory, the ledger shows overbooking rather than concealing it as negative free capacity.
For systems using HANA system replication, Rymvard checks whether a secondary host could accommodate the primary system’s allocation after a takeover. It reports whether the capacity fits, fits after specified systems are stopped, falls short by a stated number of GiB, or cannot be determined. 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 produces an unknown result, not a pass. Scale-out systems are assessed 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, weighting planned go-lives by their probability. A new SAP Operations workspace displays indicators for 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 for 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
For providers running SAP workloads, a data center’s overall capacity can mask a more specific constraint: a HANA host or replication partner may lack the memory needed for an allocation or takeover. By separating free memory, overbooking and replication shortfalls, Rymvard’s ledger is designed to make those limitations visible during placement and capacity planning, rather than treating general facility capacity as a proxy for HANA readiness.
The stale-data rules are also relevant to how operators interpret the checks. Rymvard’s stated policy is to mark a result unknown when the underlying replication or memory information exceeds its age thresholds. That avoids presenting old readings as proof that a takeover will fit, although the value of the check still depends on the accuracy and timeliness of the data collected in each environment.
The release describes planning features, not demonstrated business outcomes. The material supplied does not establish that the product reduces costs, prevents outages or improves reliability in customer use. Its potential usefulness will depend on whether its views reflect real configurations and workload changes accurately enough for operational decisions.
SAP HANA memory monitoring software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Read-Only SAP Data Connections
Rymvard says its collector communicates with 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 release also lists read-only access to landscape information from SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard presents these as supported sources; the release material does not say that customers must connect all of them.
For its reported test, the company used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it says 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. Rymvard says the screens use an illustrative estate, not a customer environment, and do not represent a real customer, site or outcome.
“Nothing is ever written to SAP.”
— Rymvard
data center capacity planning tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Customer Results Remain Unreported
Rymvard describes version 0.23 as early-access software and has not named a customer deployment or supplied customer outcomes for the release. Its reported findings are from a simulated landscape, so they do not establish how the checks perform across live customer systems, unusual configurations or changing workloads.
The release material also does not provide independent evaluations, pricing, a date for broader availability or details on validation in individual customer environments. Rymvard says terms are arranged with early-access partners. Beyond the stated one-hour replication-status and 24-hour memory-reading thresholds, it is not clear how quickly measurements update in practice or how the product handles every possible SAP configuration.
HANA replication takeover capacity software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early-Access Partner Evaluations
The stated next step is evaluation by early-access partners, with pricing arranged directly with Rymvard. The company has not announced a wider release date or public price list, and the supplied material names no customer deployment. Further announcements or partner experience would be needed to judge how the capacity and takeover checks perform in live environments.
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 an SAP Operations workspace to its data center capacity ledger.
Has Rymvard reported results from a customer deployment?
No customer deployment or customer outcomes were identified in the release material. The company’s reported test used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs.
How does the software handle old capacity data?
Rymvard says a replication status more than an hour old or a memory reading more than 24 hours old results in an unknown status, rather than a passing takeover check.
Does Rymvard say the software writes to SAP?
No. The company says its SAP connections are read-only and states,
Nothing is ever written to SAP.
When will the software be broadly available?
Rymvard has not announced a broader availability date. It says the immediate 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.
