A backup only counts as tested once you have actually restored it and verified that the data is correct and complete. A backup that has only been made but never restored is in practice an assumption: you only find out in a real outage whether the file is usable, whether it is complete, and whether the system will restart with it.
For transport companies, this is not a theoretical question. A route plan that is unreachable for a few hours affects not only the company itself but also drivers on the road and the client who expects timely delivery. Anyone who falls under the care duty of the NIS2 Directive, or who is asked by a client to demonstrate how recovery is arranged, must therefore be able to show more than a backup schedule. What is typically requested is evidence of a successful recovery test, with a date and a result.
Why an untested backup does not count
A backup file can become corrupted without anyone noticing, contain a backup of an outdated version, or exist but not be restorable within a system that has since been updated. These are not exceptions, they are the most common reasons why a recovery fails when it is needed. Article 21 of the NIS2 Directive lists backup management and disaster recovery as part of the care duty measures, alongside matters such as access control and incident handling. The Directive does not specify the timeframe or frequency for a test; this is further defined in national legislation and by supervisory authorities. What consistently comes up is the distinction between creating a backup and being able to prove that a backup can be restored.
What this affects in the transport sector
Route planning and routing systems
The planning system often contains the only current version of routes, driver allocation and agreements with clients. In the event of a failure without a tested backup, not only does planning stop, reconstructing it takes time that is rarely available in transport. A recovery test shows whether a plan from yesterday or today can be made usable again within a workable timeframe.
Tracking and track-and-trace
Tracking data is increasingly used by clients for their own accountability, for example in the food or medical goods supply chain. Loss of historical tracking data can therefore also create a problem for the client. A test demonstrates whether historical route data, not just current status, can be retrieved.
Connections with clients
Many transport companies work with EDI connections or client portals where orders, statuses and documents are exchanged automatically. After a recovery, not only must the company's own system work again, the connection must also be back in sync with the client's systems. This is a step that is often overlooked in a test, yet clients specifically ask about it in questionnaires.
What you record in a recovery test
A useful test report contains at minimum the date of the test, which system or dataset was restored, who carried out the test, how long the recovery took, and whether the restored data proved to be complete and current. This is not a legal document, it is a work note that you can show at any time, to a supervisory authority, a client, or yourself after an incident. how other care duty measures have been implemented provides an overview of what is expected from an organization in addition to backups.
What clients want to see from this
A security questionnaire from a shipper or freight forwarder rarely asks for the technical backup schedule itself. More often it asks whether backups are tested periodically, when that was last done, and who is responsible for it. A director or office manager who has that answer ready does not need to explain what a backup is, only demonstrate that it works. a few questions quickly show.
For your own situation, and for the question of which deadline or frequency is usual for your type of service, the regulator or a legal advisor remains the appropriate point of contact; this article describes the background, not advice for a specific case.
If you want to see how a tested recovery fits into a broader dossier alongside the other mandatory measures, see how the platform builds that or start the free quick-scan to see where your organization stands exactly.