Persistent applications using generalized redo recovery

We describe how to recover applications after system crashes using database recovery. Earlier efforts, based on frequent application checkpoints and/or logging values read, are very expensive. We treat application state as a cached object and log application execution as operations in the recovery f...

Full description

Saved in:
Bibliographic Details
Published inProceedings 14th International Conference on Data Engineering pp. 154 - 163
Main Author Lomet, D.B.
Format Conference Proceeding
LanguageEnglish
Published IEEE 1998
Subjects
Checkpointing
Computer crashes
Computer languages
Costs
Database systems
Humans
Silicon compounds
Tiles
Transaction databases
Online AccessGet full text

Cover

More Information
Summary:We describe how to recover applications after system crashes using database recovery. Earlier efforts, based on frequent application checkpoints and/or logging values read, are very expensive. We treat application state as a cached object and log application execution as operations in the recovery framework of D. Lomet and M. Tuttle (1995). Logging application execution does not require logging the application state. Further logged application reads are mostly logical operations in which only the data source identity is logged. We describe a cache manager that handles the flush order dependencies introduced by these log operations and a recovery process that restores application state by replaying the application.
ISBN:0818682892
9780818682896
ISSN:1063-6382
2375-026X
DOI:10.1109/ICDE.1998.655771