Software testing by Unify
Disaster Recovery Testing
Disaster Recovery Testing
The elephant in the room at the start of a project is understanding what the plans are for when things go wrong. This can range from rollback plans to system outages and fail-over processes during Live running – and importantly how this impacts your live data.
This makes disaster recovery (DR) an essential part of test planning and execution so, should the worst happen, that process has also been tested and known to be working.
You might be interested in
Related pages
Some points to consider for DR testing:
Some key points to consider for DR testing:
- The non-functional requirements for DR can form the base to test against.
- The testing should be conducted on an environment that replicates your Live environment as much as possible.
- DR testing quite often needs input from technical and development teams – which should be scheduled.
- Any data latency at the point of failover, and the consideration of data issues during DR.

Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.