Synonyms
Backward recovery; Failure handling; Media recovery; Online recovery; Restart processing; System recovery
Definition
In contrast to transaction aborts, a crash is typically a major failure by which the state of the current database is lost or parts of storage media are unrecoverable (destroyed). Based on log data from a stable log, also called temporary log file, and the inconsistent and/or outdated state of the permanent database, system recovery has to reconstruct the most recent transaction-consistent database state. To limit the amount of redo steps after a crash, some form of periodic checkpointing is mandatory. Nevertheless, DBMS restart may take too long to be masked for the user; hence, a denial of service may be observed. Recovery from media failures relies on the availability of (several) backup or archive copies of earlier DB states – organized according to the generation principle – and archive logs (often duplexed) covering the processing intervals from the points...
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsRecommended Reading
Bernstein PA, Hadzilacos V, Goodman N. Concurrency control and recovery in database systems. Reading: Addison-Wesley; 1987.
Davies CT. Data processing spheres of control. IBM Syst J. 1978;17(2):179–98.
Graefe G, Kuno HA. Definition, detection, and recovery of single-page failures, a fourth class of database failures. Proc VLDB Endowment; 2012;5(7):646–55.
Gray J, Reuter A. Transaction processing: concepts and techniques. San Francisco: Morgan Kaufmann; 1993.
Gray J, McJones P, Blasgen M, Lindsay B, Lorie R, Price T, Putzolu F, Traiger IL. The recovery manager of the System R database manager. ACM Comput Surv. 1981;13(2):223–42.
Gray J. Notes on data base operating systems. Advanced course: operating systems. Berlin: Springer; 1978. p. 393–481. LNCS 60.
Härder T. DBMS architecture – still an open problem. In: Proceedings of the German National Database Conference; 2005. p. 2–28.
Härder T, Reuter A. Principles of transaction-oriented database recovery. ACM Comput Surv. 1983;15(4):287–317.
Hvasshovd S-O. Recovery in parallel database systems. 2nd ed. Burlington: Morgan Kaufmann; 1999.
Mohan C, Haderle DJ, Lindsay BG, Pirahesh H, Schwarz PM. ARIES: a transaction recovery method supporting fine-granularity locking and partial rollbacks using write-ahead logging. ACM Trans Database Syst. 1992;17(1):94–162.
Pelley S, Wenisch TF, Gold BT, Bridge B. Storage management in the NVRAM era. Proc VLDB Endowment; 2013;7(2):121–32.
Reuter A. Fehlerbehandlung in Datenbanksystemen. Munich: Carl Hanser; 1981. p. 456.
Sauer C, Graefe G, Härder T. An empirical analysis of database recovery costs. In: Proceedings of the Sigmod Workshops: RDSS; 2014.
Sauer C, Härder T. A simple recovery mechanism enabling fine-granular locking and fast, REDO-only recovery. CoRR abs/1409.3682, 2014.
Weikum G, Vossen G. Transactional information systems: theory, algorithms, and the practice of concurrency control and recovery. San Francisco: Morgan Kaufmann; 2002.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Section Editor information
Rights and permissions
Copyright information
© 2018 Springer Science+Business Media, LLC, part of Springer Nature
About this entry
Cite this entry
Härder, T. (2018). Crash Recovery. In: Liu, L., Özsu, M.T. (eds) Encyclopedia of Database Systems. Springer, New York, NY. https://doi.org/10.1007/978-1-4614-8265-9_88
Download citation
DOI: https://doi.org/10.1007/978-1-4614-8265-9_88
Published:
Publisher Name: Springer, New York, NY
Print ISBN: 978-1-4614-8266-6
Online ISBN: 978-1-4614-8265-9
eBook Packages: Computer ScienceReference Module Computer Science and Engineering