Disaster Recovery Evidence for Stateful Cloud Services: A Systematic Review of Test Methods and Reported Performance Metrics

Authors

  • Yuna Kim Department of Computer Science and Cloud Systems, University of Melbourne Author
  • Harun Akhtar Department of Computer Science and Cloud Systems, Cairo University Author

Abstract

Disaster recovery claims for stateful cloud services are difficult to compare because studies use inconsistent failure models, recovery definitions, and measurement intervals. We systematically reviewed empirical studies evaluating recovery of databases, storage-backed services, and other stateful cloud workloads. Searches of computing and engineering databases yielded 2,164 records; 112 studies met inclusion criteria after full-text screening. Recovery time was reported in 84% of studies, recovery-point loss in 46%, and end-to-end application consistency in only 29%. Hardware or node failure dominated the literature, whereas logical corruption, dependency failure, and identity-service outages were substantially underrepresented. Only 18% of studies described repeated recovery trials, and 22% provided sufficient configuration detail to support replication. Studies using fault injection and application-level validation produced more complete evidence than those relying on infrastructure health checks alone. Current evidence supports the technical feasibility of rapid recovery under selected conditions but provides limited insight into repeatability across complex production dependencies. Standard reporting should include fault model, workload state, recovery boundary, validation method, trial count, and both recovery-time and recovery-point outcomes.

References

1. Nazir M. SVM-based disaster recovery for hybrid enterprise storage: effects on recovery time and service availability. Journal of Computing, Intelligence and Information Sciences. 2022. Available from: https://jciis.com/index.php/jciis/article/view/2022-01-05

2. Patterson RH, Manley S, Federwisch M, Hitz D, Kleiman S, Owara S. SnapMirror: file-system-based asynchronous mirroring for disaster recovery. In: Proceedings of the 1st USENIX Conference on File and Storage Technologies. 2002. p. 117-129. Available from: https://www.usenix.org/conference/fast-02/snapmirror-file-system-based-asynchronous-mirroring-disaster-recovery

3. Cully B, Lefebvre G, Meyer D, Feeley M, Hutchinson N, Warfield A. Remus: high availability via asynchronous virtual machine replication. In: Proceedings of the 5th USENIX Symposium on Networked Systems Design and Implementation. 2008. p. 161-174. Available from: https://www.usenix.org/legacy/events/nsdi08/tech/full_papers/cully/cully.pdf

4. Gray J, Lamport L. Consensus on transaction commit. ACM Trans Database Syst. 2006;31(1):133-160. doi:10.1145/1132863.1132867.

5. Gilbert S, Lynch N. Brewer's conjecture and the feasibility of consistent, available, partition-tolerant web services. ACM SIGACT News. 2002;33(2):51-59. doi:10.1145/564585.564601.

6. Ghemawat S, Gobioff H, Leung ST. The Google file system. In: Proceedings of the 19th ACM Symposium on Operating Systems Principles. 2003. p. 29-43. doi:10.1145/945445.945450.

7. DeCandia G, Hastorun D, Jampani M, Kakulapati G, Lakshman A, Pilchin A, et al. Dynamo: Amazon's highly available key-value store. In: Proceedings of the 21st ACM Symposium on Operating Systems Principles. 2007. p. 205-220. doi:10.1145/1294261.1294281.

8. Dean J, Barroso LA. The tail at scale. Commun ACM. 2013;56(2):74-80. doi:10.1145/2408776.2408794.

9. NetApp. Learn about ONTAP SnapMirror asynchronous disaster recovery [Internet]. [cited 2026 Sep 22]. Available from: https://docs.netapp.com/us-en/ontap/data-protection/snapmirror-disaster-recovery-concept.html

10. Swanson M, Bowen P, Phillips AW, Gallup D, Lynes D. Contingency planning guide for federal information systems. Gaithersburg (MD): National Institute of Standards and Technology. 2010;NIST SP 800-34 Rev. 1. doi:10.6028/NIST.SP.800-34r1.

11. Grance T, Nolan T, Burke K, Dudley R, White G, Good T. Guide to test, training, and exercise programs for IT plans and capabilities. Gaithersburg (MD): National Institute of Standards and Technology. 2006;NIST SP 800-84. doi:10.6028/NIST.SP.800-84.

12. Mytkowicz T, Diwan A, Hauswirth M, Sweeney PF. Producing wrong data without doing anything obviously wrong. In: Proceedings of the 14th International Conference on Architectural Support for Programming Languages and Operating Systems. 2009. p. 265-276. doi:10.1145/1508244.1508275.

13. Kalibera T, Jones R. Rigorous benchmarking in reasonable time. In: Proceedings of the 2013 International Symposium on Memory Management. 2013. p. 63-74. doi:10.1145/2464157.2464160.

14. Page MJ, McKenzie JE, Bossuyt PM, Boutron I, Hoffmann TC, Mulrow CD, et al. The PRISMA 2020 statement: an updated guideline for reporting systematic reviews. BMJ. 2021;372:n71. doi:10.1136/bmj.n71.

15. Moher D, Shamseer L, Clarke M, Ghersi D, Liberati A, Petticrew M, et al. Preferred reporting items for systematic review and meta-analysis protocols (PRISMA-P) 2015 statement. Syst Rev. 2015;4:1. doi:10.1186/2046-4053-4-1.

16. Rethlefsen ML, Kirtley S, Waffenschmidt S, Ayala AP, Moher D, Page MJ, et al. PRISMA-S: an extension to the PRISMA Statement for Reporting Literature Searches in Systematic Reviews. Syst Rev. 2021;10:39. doi:10.1186/s13643-020-01542-z.

17. Campbell M, McKenzie JE, Sowden A, Katikireddi SV, Brennan SE, Ellis S, et al. Synthesis without meta-analysis (SWiM) in systematic reviews: reporting guideline. BMJ. 2020;368:l6890. doi:10.1136/bmj.l6890.

18. Wilkinson MD, Dumontier M, Aalbersberg IJ, Appleton G, Axton M, Baak A, et al. The FAIR Guiding Principles for scientific data management and stewardship. Sci Data. 2016;3:160018. doi:10.1038/sdata.2016.18.

Published

2026-06-01