Skip to main content
SpringerLink
Log in

Instant recovery with write-ahead logging

  • KURZ ERKLÄRT
  • Published:
Datenbank-Spektrum Aims and scope Submit manuscript

Abstract

Instant recovery improves system availability by reducing the mean time to repair, i.e., the interval during which a database is not available for queries and updates due to recovery activities. Variants of instant recovery pertain to system failures, media failures, node failures, and combinations of multiple failures. After a system failure, instant restart permits new transactions immediately after log analysis, before and concurrent to “redo” and “undo” recovery actions. After a media failure, instant restore permits new transactions immediately after allocation of a replacement device, before and concurrent to restoring backups and replaying the recovery log.

Write-ahead logging is already ubiquitous in data management software. The recent definition of single-page failures and techniques for log-based single-page recovery enable immediate, lossless repair after a localized wear-out in novel or traditional storage hardware. In addition, they form the backbone of on-demand “redo” in instant restart, instant restore, and eventually instant failover. Thus, they complement on-demand invocation of traditional single-transaction “undo” or rollback.

In addition to these instant recovery techniques, the discussion introduces self-repairing indexes and much faster offline restore operations, which impose no slowdown in backup operations and hardly any slowdown in log archiving operations. The new restore techniques also render differential and incremental backups obsolete, complete backup commands on a database server practically instantly, and even permit taking full up-to-date backups without imposing any load on the database server.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2

Similar content being viewed by others

Notes

  1. We use the term “instant” not in an absolute meaning but a relative one, i.e., in comparison to prior techniques. This is like instant coffee, which is not absolutely instantaneous but only relative to traditional techniques of coffee preparation. The reader’s taste and opinion must decide whether instant coffee actually is coffee. Instant recovery, however, is true and reliable recovery from system and media failures, with guarantees as strong as those of traditional recovery techniques.

Literatur

  1. Bruni P, Antonelli M, Goethals D, Kompalka A, Petras M (2010) DB2 9 for z/OS: using the utilities suite. IBM Redbooks, 2nd edn., February 2010—Section 13.10 “Fast log apply”

  2. Gray J (1978) Notes on data base operating systems. In Bayer R, Graham RM, Seegmüller G (eds) Operating systems—an advanced course. LNCS 60. S 393–481, Springer-Verlag, Heidelberg

  3. Graefe G (2004) Write-optimized B-trees. VLDB 672–683

  4. Graefe G, Guy W, Sauer C (2014) Instant recoveryc with write-ahead logging: page repair, system restart, and media restore. Synthesis Lectures on Data Management, Morgan & Claypool Publishers

  5. Graefe G, Kimura H, Kuno HA (2012) Foster B-trees. ACM TODS 37(3):17

  6. Graefe G, Kuno HA, Seeger B (2012) Self-diagnosing and self-healing indexes. DBTest 8

  7. Levy E (1991) Incremental restart. ICDE 640–648

  8. Lehman TJ, Carey MJ (1987) A recovery algorithm for a high-performance memory-resident database system. ACM SIGMOD, pp 104–117

  9. Levy E, Silberschatz A (1992) Incremental recovery in main memory database systems. IEEE TKDE 4(6):529–540

  10. Long R, Harrington M, Hain R, Nicholls G IMS primer. IBM Redbooks, January 2000—Section 15.4.2 “Database change accumulation utility (DFSUCUM0)”

  11. Mohan C, Haderle DJ, Lindsay BG, Pirahesh H, Schwarz PM (1992) ARIES: a transaction recovery method supporting fine-granularity locking and partial rollbacks using write-ahead logging. ACM TODS 17(1):94–162

  12. Oukid I, Lehner W, Kissinger T, Willhalm T, Bumbulis P (2015) Instant recovery for main memory databases. CIDR

Download references

Author information

Authors and Affiliations

  1. TU Kaiserslautern, Kaiserslautern, Germany

    Theo Härder & Caetano Sauer

  2. HP Lab, Palo Alto, US

    Goetz Graefe & Wey Guy

Authors
  1. Theo Härder
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Caetano Sauer
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Goetz Graefe
    View author publications

    You can also search for this author in PubMed Google Scholar

  4. Wey Guy
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Theo Härder.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Härder, T., Sauer, C., Graefe, G. et al. Instant recovery with write-ahead logging. Datenbank Spektrum 15, 235–239 (2015). https://doi.org/10.1007/s13222-015-0204-3

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s13222-015-0204-3

Keywords

Search

Navigation