🔍 Read the full analysis: Will SAP HANA System Replication Be Ready For A Takeover? on Rymvard
Get privacy and security gear 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
TL;DR
Rymvard is offering an early-access check for SAP HANA System Replication environments that compares a secondary host’s available memory with the primary system’s allocation. In a simulated 200-host landscape, the company says it identified a takeover that would be 512 GiB short even after stopping test systems; no customer result is cited.
Rymvard says its early-access product now checks whether secondary hosts in SAP HANA System Replication environments have enough memory to take over for production databases. The check is intended to flag a capacity gap before a failover is needed, including cases where development or test systems on the replica host would have to be stopped to free memory.
System replication maintains a copy of a production HANA database at another site, but having a replica does not by itself establish that the secondary host can run the production workload. Rymvard’s check compares the primary system’s memory allocation with the capacity available on its paired secondary host. It treats the pair’s own replica as replaced during a takeover and may count test and development systems on the secondary host as stoppable.
The company says production systems belonging to other customers are not treated as stoppable. Each check returns one of four results: the host fits; it fits after named systems are stopped; it does not fit, with the shortfall reported in GiB; or the result is unknown. Rymvard says a replication status older than one hour or a memory measurement older than 24 hours produces an unknown result, rather than a passing assessment.
For scale-out HANA systems, the check evaluates the system as a whole and uses the worst host pair in its assessment. Rymvard says it runs continuously against live data from HANA monitoring views and the SAP Host Agent. A failing takeover is recorded as an urgent finding with the relevant host, memory shortfall and systems involved.
Will SAP HANA System Replication Be Ready for a Takeover?
Rymvard’s early access check compares production memory allocation with capacity on the paired secondary host. It aims to surface a memory gap before a failover is needed.
Simulated HANA estate
After test systems stopped
Older status means unknown
Older measurement means unknown
A replica alone does not guarantee capacity
System replication keeps a copy of a production database at another site. But the secondary host still needs enough available memory to run that workload. Development and test systems may occupy capacity that recovery plans expect to reclaim.
Primary allocation
The check compares the production system’s memory allocation against the paired secondary host’s available capacity.
Stoppable workloads
The pair’s own replica is treated as replaced during takeover. Test and development systems may count as stoppable.
Other production
Rymvard says production systems belonging to other customers are not treated as stoppable.
From confirmed fit to unknown
Each result distinguishes capacity that is ready now, capacity that depends on named systems stopping, a measured shortfall, or data too stale for a confident assessment.
Fits
Available memory is sufficient for the takeover assessment.
Fits after stops
Capacity is sufficient if specified test or development systems are stopped.
Does not fit
The finding reports the shortfall in GiB and the systems involved.
Unknown
Replication status older than one hour or memory data older than 24 hours prevents a pass assessment.
How the capacity check works
Rymvard says the check runs continuously on live data from HANA monitoring views and the SAP Host Agent. For scale-out systems, it evaluates the system as a whole and uses the weakest host pair in its assessment.
Collect replication status and memory measurements.
Match production allocation with secondary capacity.
Account for workloads that may be stopped for takeover.
Flag fit, required stops, shortfall, or unknown data.
A large gap surfaced in a simulation
Designed to reveal hidden capacity risk
Rymvard says its check found one production system in a simulated landscape of 200 HANA hosts that would remain 512 GiB short even after all test systems on the secondary host were stopped. This illustrates the issue the product targets; it is not a reported customer incident or independently verified result.
Customer outcomes not published
Memory fit is one recovery prerequisite
A finding can help teams see a capacity risk and the systems that may need to stop. It does not create memory capacity or demonstrate that a complete recovery will succeed.
Operational signal
Failing takeovers are recorded as urgent findings with the relevant host, memory shortfall, and systems involved. Freshness rules turn stale inputs into an unknown result.
Customer validation
No customer names, deployment counts, independent validation, or measured customer outcomes are provided. Illustrative screens do not establish performance across live estates.
Stop rules must match reality
The assessment depends on accurate monitoring data and correct classification of which secondary-host workloads can actually stop under recovery procedures.
Runbooks still matter
Teams should evaluate findings alongside takeover runbooks and capacity plans. The available information does not establish that every failover condition is tested.
Testing and pricing are partner-led
Rymvard says the check is running in early access. Pricing is agreed with participating partners; no general-release date, partner list, or customer-results schedule has been announced.
Source · RymvardWhat administrators should know
What does the check measure?
It compares a production HANA system’s memory allocation with capacity on its secondary replication host, accounting for systems that may be stopped to free memory.
What did the 512 GiB example show?
In a simulated 200-host landscape, one takeover remained 512 GiB short after test systems were stopped. Rymvard did not describe it as a customer result.
Is the product generally available?
No general-release date is provided. Rymvard says the product is in early access and pricing is arranged with participating partners.
What should a team verify?
Confirm the check can use its HANA monitoring data and reflects which workloads can be stopped under its own recovery procedures.
Memory Gaps Can Defeat a Failover
The check focuses on a gap between replication status and takeover readiness. A database copy may be maintained at a secondary site, yet the host could lack the memory required to run the production system if other workloads occupy its capacity. If those workloads cannot safely or quickly be stopped, a planned recovery path may not work as expected.
For administrators, an explicit result and named systems to stop can make capacity risks easier to identify and address before an outage. A finding marked unknown also matters: it signals that the underlying measurements are too old to support a confident fit assessment. The check does not itself create memory capacity or demonstrate that a full recovery will succeed; it assesses one operational prerequisite using the data available to it.
Rymvard reports that, in a simulated landscape of 200 HANA hosts, its check found one production system whose takeover would be 512 GiB short even after all test systems on the secondary host were stopped. That example indicates the kind of issue the product is designed to surface, but it is not a reported customer incident or independently verified performance result.
SAP HANA memory capacity testing tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
How the Capacity Check Works
In SAP HANA System Replication, a secondary system is kept in sync with a primary database so it can be used in a takeover. That arrangement supports recovery planning, but the memory available at the secondary site can change as workloads are added or grow. Rymvard describes test and development workloads on replica hosts as a common cost-saving arrangement, with those systems expected to be stopped if production needs the capacity.
The product’s assessment distinguishes between workloads it considers stoppable and other production systems that must remain accounted for. Its four outcomes are designed to separate a confirmed fit from a fit that depends on stopping specific systems, a measured shortfall, and an assessment that cannot be made from sufficiently recent data. For scale-out deployments, it assesses the weakest host pair rather than relying on an aggregate view that could obscure a local capacity deficit.
Rymvard says the product is in early access and running. It says screens shown for the product use an illustrative example estate, not a customer deployment, and that the scenarios do not imply any particular customer, site or outcome. The company has not published prices; it says pricing is agreed with early-access partners.
“A replication status older than one hour or a memory figure older than 24 hours makes the result unknown — never fine.”
— Rymvard
As an affiliate, we earn on qualifying purchases.
Customer Results Remain Unreported
The 512 GiB shortfall comes from a simulated 200-host landscape; Rymvard has not identified it as a customer finding. The company says its product is running in early access, but it has not provided customer names, deployment numbers, independent validation, or measured outcomes from customer environments. Its illustrative screens do not establish how the check has performed across live customer estates.
The assessment also depends on the accuracy and freshness of the monitoring data and on which secondary-host workloads can actually be stopped during a takeover. Rymvard describes its rules for test and development systems and other customers’ production systems, but has not provided details here about how organizations configure or verify those classifications. The check addresses memory fit; the available information does not establish that it tests every other condition needed for a successful failover.
enterprise database replication hardware
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early-Access Testing and Pricing
Rymvard says the check is available through its early-access program and that pricing is arranged with participating partners rather than publicly listed. The company has not announced a general-release date, partner list, or schedule for publishing customer results. Further evidence about performance in customer environments would help clarify how the simulated example compares with operational deployments.
For teams considering the check, the immediate question is whether it can use their HANA monitoring data and accurately reflect which workloads could be stopped under their recovery procedures. Any finding should be evaluated alongside the organization’s own takeover runbooks and capacity planning; an assessment of memory fit is not, on its own, proof that a complete recovery will succeed.
Source: Rymvard
high availability server memory modules
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What does Rymvard’s SAP HANA check measure?
It compares a production HANA system’s memory allocation with capacity on its secondary replication host, accounting for systems that may be stopped to free memory.
What results can the check return?
Rymvard describes four outcomes: fits; fits after named systems are stopped; does not fit, with the shortfall in GiB; or unknown when the required data is too old.
What did the 512 GiB example show?
In a simulated landscape of 200 HANA hosts, Rymvard says it found a production system that would remain 512 GiB short for takeover even after all test systems on the secondary host were stopped. The company did not describe this as a customer result.
Is the product generally available?
No general-release date is provided. Rymvard says the product is running in early access and that pricing is agreed with early-access partners.
Source: Rymvard
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
