Rymvard Brings SAP HANA Memory Into Data Center Resource Accounting

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

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

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

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 early-access product uses read-only SAP connections; the company’s test results came from a simulated environment, and no customer deployment or outcomes were identified.

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 release is aimed at SAP hosting providers and operations teams seeking to track memory constraints by host and site; the company’s reported test results are from a simulated landscape, not a customer deployment.

For each HANA host, Rymvard divides 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 memory. Unless a host has a different reserve configured, the default is 10 percent of the first 64 GiB and 3 percent of memory above that. System usage is based on its 30-day peak. Allocations that exceed physical memory are shown as overbooking, rather than being hidden as negative free capacity.

For systems using HANA system replication, the software checks whether a secondary host could accommodate the primary system’s allocation after a takeover. It reports whether the system fits, fits only after named systems are stopped, does not fit and by how many GiB, or cannot be assessed. Named test or development systems may be counted as stoppable; production systems belonging to other customers are not. If replication status is more than an hour old or memory data is more than 24 hours old, the result is marked unknown rather than treated as a passing check. 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 using planned go-lives weighted by their probability. Rymvard says HANA instances are mirrored into its compute view so that SAP memory can appear 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 percent utilization.

Making HANA Failover Capacity Visible

The release addresses a specific capacity-planning issue: a data center may have room in its wider infrastructure while an individual HANA host or replication partner lacks enough physical memory for a planned allocation or takeover. Separating free capacity, overbooking and replica reservations could help operations teams spot those constraints before placing a system or relying on a failover plan.

The takeover checks may also help providers distinguish a configured replication relationship from one whose secondary host appears able to accept the primary system’s allocation. That distinction matters to capacity planning, but the software’s result depends on current, accurate source data. Rymvard’s unknown outcome for stale readings avoids presenting old measurements as evidence that a takeover will fit; it also means teams may need to refresh data or investigate before relying on a check.

The placement and runway views could support discussions about where to put incoming systems and when a site may need additional capacity. However, the release description does not establish cost savings, improved reliability or customer outcomes. The stated functionality and simulated test results show what Rymvard says the product can assess, not how it performs across live customer estates or changing workloads.

Read-Only SAP Data Connections

Rymvard says its collector connects to the SAP Host Agent over HTTPS and permits 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 system, customer and environment information: SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard presents these as supported sources for landscape details alongside the HANA memory view; it does not say that customers must connect all of them.

Rymvard says version 0.23 was tested against a simulated estate with 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, 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. The company says the screens use an illustrative estate, not a customer environment, and do not imply a real customer, site or outcome.

“Nothing is ever written to SAP.”

— Rymvard

Customer Evidence Is Still Pending

Rymvard describes version 0.23 as early-access software and has not identified a customer deployment or provided customer outcomes for this release. The reported findings come from a simulated landscape. No independent evaluation or live-world performance data is included in the supplied release description.

The company describes the connection methods and the age thresholds that make some results unknown, but has not detailed how the software handles every possible SAP configuration or how integrations are validated in individual environments. Further information about update speed beyond those thresholds is also not provided. Rymvard has not published pricing, saying commercial terms are arranged with early-access partners.

Early-Access Partner Evaluations

The immediate next step is evaluation by early-access partners, with commercial terms agreed directly with Rymvard. The company has not announced a broader availability date or public price list, and no named customer has been disclosed. Further evidence from partner use would be needed to establish how the accounting and takeover checks perform against live SAP landscapes and operational workloads.

Key Questions

What did Rymvard add in version 0.23?

It added SAP HANA memory accounting, placement proposals, replication takeover checks, site-level runway estimates and a SAP Operations workspace to its data center capacity ledger.

Has Rymvard shown results from a customer deployment?

No customer deployment or outcome was identified. Rymvard’s reported test used a simulated estate of 200 HANA hosts, 161 systems and 39 replicated pairs.

How does the software assess a replication takeover?

It checks whether the secondary host could accommodate the primary system’s allocation, with named test or development systems potentially treated as stoppable. A stale replication status or memory reading produces an unknown result rather than a pass.

Does Rymvard write data to SAP?

Rymvard says its connections are read-only and states, “Nothing is ever written to SAP.” The described SAP Host Agent collector uses four read operations, alongside a separate monitoring connection.

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 terms are arranged directly with early-access partners.

Primary source: Rymvard · via ThorstenMeyerAI.com