Define the Recovery Point
An RPO describes how far back in time the restored data may be after an incident. A one-hour RPO concerns the acceptable gap in updates; it does not mean the service must resume within one hour. The related RTO answers the separate question of restoration time.
Define the data sets and service boundaries carefully. Transactional data may need a different objective from archives or rarely changed configuration records.
Connect Data Loss to Real Consequences
Analyse the effect of losing transactions, missing records or introducing inconsistencies across interconnected systems. Where records can be reconstructed reliably from independent evidence, the acceptable gap may differ from data that cannot be recovered elsewhere.
Consult business and data owners when setting objectives. Backup administrators can advise on feasibility, but they should not unilaterally decide the organisation's tolerance for information loss.
Choose Suitable Protection Mechanisms
Backups, snapshots and transaction logs can provide different recovery points. Continuous replication may improve currency but can carry malicious changes or accidental deletions into secondary environments. Independent historical copies can remain valuable.
Confirm that the selected configuration and backup frequency can deliver the agreed recovery point under realistic failure conditions. Monitor failures and access to retained copies.
Test Completeness and Consistency
Restore representative data into a segregated environment, establish the age of recovered data and test its integrity. For interdependent databases, snapshots taken at inconsistent moments can produce a service that starts but returns contradictory information.
Document the actual recovery point achieved and compare it with the approved objective. Record missing dependencies, failed verification checks and remediation responsibilities.
Retain Approvals and Check Specific Requirements
Article 21 explicitly covers backup management but does not require hourly backups for every NIS2 organisation. Check national implementing provisions and additional requirements for the entities covered by Regulation (EU) 2024/2690.
Keep the RPO rationale, assigned data owner, supporting technical design, test evidence and exceptions. Review after changes to transaction volumes, critical systems or suppliers.
Questions on the text
Are hourly backups mandatory under NIS2?
No universal hourly backup requirement applies to all NIS2-covered organisations under Article 21.
Does real-time replication guarantee no data loss?
Not necessarily. Data corruption, administrative errors or malicious changes may replicate too, so restoration design and independent recoverable copies matter.