🔍 Read the full analysis: DORA Puts SAP Takeovers On The Auditor's Agenda on Rymvard
Get the latest gadgets 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 added a check on 4 October 2026 to assess whether a SAP HANA secondary host can carry production workloads after a system takeover. The early-access feature reports whether capacity fits, fits after stopping named systems, falls short, or cannot be determined; its example estate is illustrative, not a customer deployment.
Rymvard added an early-access check on 4 October 2026 that evaluates whether a secondary host in a SAP HANA system-replication setup can carry the primary system’s production allocation after a takeover. The feature is aimed at providers serving financial institutions subject to the EU’s Digital Operational Resilience Act (DORA), which has applied since 17 January 2025 and requires financial entities to manage ICT risks, including those involving third-party providers.
The check compares the memory capacity available on the secondary host with the primary system’s allocation. Rymvard says the system being replicated is accounted for by replacing its own replica. Test and development systems on the secondary host may be marked as stoppable to free capacity, but production systems belonging to other customers are not treated as stoppable.
Each system receives one of four outcomes: fits; fits after named systems are stopped; does not fit, with the shortfall stated in GiB; or unknown. Rymvard says a replication status more than one hour old, or a memory figure more than 24 hours old, makes the result unknown rather than a pass. For scale-out systems, the assessment covers the system as a whole and uses the worst-performing host pair.
Rymvard says results can be exported for each system, allowing a provider to present an assessment to an auditor and identify capacity gaps before a resilience test. The company illustrates the feature with a managed SAP provider scenario in Luxembourg, but says the scenario and screens use an illustrative estate, not a customer. Rymvard is in early access and does not publish prices; terms are agreed with early-access partners.
Digital resilience · SAP HANA · Early access
DORA Puts SAP Takeovers On The Auditor’s Agenda
Rymvard’s new capacity check asks a practical recovery question: can a secondary SAP HANA host carry the primary system’s production allocation after a takeover?
Compare available secondary-host memory with the production allocation, using current replication and memory data.
01 / Why this matters
Replication alone does not prove recovery capacity
For regulated financial firms, recovery depends on a secondary site having room to run the workloads that matter when a primary system is taken over.
DORA brings supplier risk into view
Regulation (EU) 2022/2554 has applied since 17 January 2025. It addresses ICT risk management and digital operational resilience, including risks linked to technology providers.
Will the secondary host fit the load?
A replica may share its host with other workloads. The assessment compares available memory with the primary system’s production allocation after takeover.
A capacity check has a defined scope
It can surface gaps and assumptions. It does not establish successful live recovery or prove compliance with every DORA requirement.
02 / The result set
Four outcomes, with stale data marked unknown
Rymvard says the check accounts for the replicated system by replacing its own replica. Named test and development systems may be stoppable; other customers’ production systems are not.
Fits
Available secondary-host memory covers the production allocation.
Fits after stops
Capacity works if specifically named stoppable systems are stopped.
Does not fit
The result states the memory shortfall in GiB.
Unknown
Data outside the freshness limits cannot produce a passing result.
“A replication status older than one hour or a memory figure older than 24 hours makes the result unknown — never fine.”
Rymvard · stated freshness rule03 / How the assessment works
From host data to an auditable capacity view
The result is a technical snapshot that providers can review, act on and export for each system.
Read current data
Check replication status and host memory freshness.
Compare allocation
Relate available secondary capacity to production memory.
Account for stops
Allow named non-production workloads to free capacity.
Export per system
Use results to investigate gaps ahead of resilience testing.
“Production systems of other customers are never counted as stoppable.”
Rymvard · workload handling04 / Scope & evidence
Useful signal, with important limits
Rymvard describes itself as a capacity ledger for data centers. It says the check is running in its early-access product and that results can be exported for each system. For scale-out SAP HANA, the assessment covers the system as a whole and uses the worst-performing host pair.
The company’s Luxembourg managed-provider scenario and displayed screens use an illustrative estate. No customer, deployment site, audit result or real-world recovery outcome is identified.
The announcement does not specify every supported HANA configuration, required integrations or validation steps. Providers remain responsible for interpreting results, addressing shortfalls and conducting resilience tests suited to their operations.
05 / Key questions
What providers and auditors should know
What did Rymvard add?
An early-access check of whether a SAP HANA secondary host has enough capacity for the primary system’s production allocation after takeover.
How does this relate to DORA?
DORA addresses ICT risk, including third-party provider risk, and the resilience of critical services. This check covers one technical capacity question; it does not establish DORA compliance.
Has a customer used the feature?
No customer use or audit outcome is disclosed. The Luxembourg provider scenario is illustrative and does not identify a customer or site.
Is it generally available, and what does it cost?
It is in early access. Pricing is not published and is agreed with partners; no general-release date has been announced.
Primary source: Regulation (EU) 2022/2554 (DORA), with feature details and scenario statements attributed to Rymvard.
Evidence for SAP Recovery Capacity
DORA has applied since 17 January 2025, bringing ICT risk management and operational resilience into the compliance responsibilities of banks, insurers and other financial entities. Their obligations include risks linked to services supplied by ICT third parties. For institutions relying on managed SAP systems, a recovery plan depends not only on replication being configured but also on the secondary site having sufficient capacity to run the required production workload.
Rymvard’s feature focuses on that practical capacity question. A documented result can help a provider identify when non-production systems are consuming memory needed for recovery, and can make the assumptions behind a takeover assessment more visible. It does not, on the information provided, establish that a system will recover successfully in a live incident or satisfy every DORA requirement. Rather, it reports a bounded technical check based on the capacity and status data available to it.
The distinction between a failed assessment and an unknown result also matters for audit evidence. Stale measurements do not count as a passing outcome under Rymvard’s stated rules. That approach makes data freshness part of the assessment, while leaving providers responsible for interpreting the result, addressing shortfalls and conducting the resilience testing required for their own operations.
As an affiliate, we earn on qualifying purchases.
DORA and HANA Replication
Regulation (EU) 2022/2554, commonly called DORA, applies to financial entities and addresses digital operational resilience, including the management of ICT risks and the resilience of services provided by technology suppliers. The regulation has applied since 17 January 2025. Its requirements make third-party technology and recovery arrangements relevant to the resilience work of regulated institutions, not just their direct IT operations.
SAP HANA system replication maintains a secondary system that can be used in a takeover. Having a replica alone does not show that the secondary host has enough memory for the production allocation: other workloads may also be running there. Rymvard’s announced check evaluates that capacity relationship and distinguishes systems that can be stopped to free space from production workloads that must remain accounted for.
Rymvard describes itself as a capacity ledger for data centers. The company says the feature is running in its early-access product, but the published Luxembourg provider scenario is illustrative. No customer, deployment site or real-world outcome is identified, so the announcement does not establish how the check has performed in a customer audit or resilience exercise.
“A replication status older than one hour or a memory figure older than 24 hours makes the result unknown — never fine.”
— Rymvard
SAP HANA replication capacity check software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Customer Use and Audit Outcomes
No customer deployment or audit result is identified in the announcement. Rymvard says the displayed screens come from its running product but use an illustrative example estate, and that the Luxembourg scenario does not imply a customer, site or outcome. It is not clear how many providers are testing the feature, when early access might end, or whether the company plans broader availability.
The published details also do not specify how the check handles every possible HANA configuration beyond the stated scale-out rule, or what data integrations and validation steps customers need. The check is described as a capacity assessment; there is no claim that it replaces a full recovery exercise, an independent audit or other DORA controls. Pricing is not public and is negotiated with early-access partners.
IT resilience testing tools for SAP systems
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early Access and Provider Testing
Rymvard says the check is available now through its early-access programme. Providers interested in using it would need to assess their own system data, review any reported shortfalls or stoppable workloads, and determine how exported per-system results fit into their audit and resilience processes. The company has not announced a general-release date or a timetable for additional features.
The next material evidence will be whether providers use the check in customer environments and how its assessments compare with recovery tests and audit requirements. Until such deployments or outcomes are disclosed, the announcement establishes the feature’s stated operation and availability, not its adoption or effectiveness across financial-sector SAP estates.
Primary source: Regulation (EU) 2022/2554 (DORA) · via Rymvard
Data center capacity management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add?
It added an early-access check that assesses whether a SAP HANA system’s secondary host has enough capacity to take over the primary system’s production allocation.
What results can the check return?
The result is fits, fits after named systems are stopped, does not fit with a shortfall in GiB, or unknown. Rymvard says stale replication or memory data produces an unknown result.
How does this relate to DORA?
DORA requires financial entities to manage ICT risk, including risks tied to third-party providers, and to test recovery of critical services. The check addresses one technical capacity question for SAP HANA recovery; it does not by itself establish compliance with DORA.
Has a customer used the feature?
No customer use or audit outcome is disclosed. Rymvard says its Luxembourg managed-provider scenario is illustrative and does not refer to a customer, site or real-world result.
Is the feature generally available, and what does it cost?
Rymvard says the feature is running in early access. The company publishes no prices and says pricing is agreed with early-access partners; a general-release date has not been announced.
Primary source: Regulation (EU) 2022/2554 (DORA) · via Rymvard
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
