Lomet, D. Application recovery using generalized redo recovery. IntT Conference on Data Engineering, Orlando, FL (February, 1998). Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Measuring and Optimizing a System for Persistent Database.. - Barga, Lomet Self-citation (Lomet) (Correct)
No context found.
Lomet, D. Application recovery using generalized redo recovery. IntT Conference on Data Engineering, Orlando, FL (February, 1998).
High Speed On-line Backup When Using Logical Log Operations - Lomet Self-citation (Lomet) (Correct)
....the operation can read one or more objects (pages) and write (potentially different) multiple objects. Some examples of how logical logging can substantially reduce the logging required during normal execution are: Application Recovery: Logical log operations for recovering application # s state [8] are: ######: # reads # into its input buffer, transforming its state to a new state # # . Unlike page oriented operations, the values of # and # # are not logged. # # ### ##: # writes # from its output buffer. # s state is unchanged. Unlike page oriented operations, we do not log the new ....
....This is essentially the same problem that we have for full backup. Its solution should be similar as well, involving ##### logging and tracking backup progress. Hence, much of the efficiency of [13] also holds for backup with logical log operations. 6. 2 Application Read Operations and Backup In [8], we introduced log operations that permit efficient logging for application recovery. The only logical log operation we pursued there was application read (#### ##) This avoided physically logging the value of # or #, but required that # be flushed before a change to # was flushed. In all ....
Lomet, D. Application recovery using generalized redo recovery. Intl. Conf. on Data Eng., Orlando (Feb. 1998) 154-163.
Logical Logging to Extend Recovery to New Domains - David Lomet (1999) (4 citations) Self-citation (Lomet) (Correct)
....for understanding redo recovery. Two factors motivated us. First, we wanted to explain existing recovery technology. Second, we wanted to generalize recovery technology to enable its exploitation in domains other than database recovery. We showed how to exploit more powerful log operations in [7] to reduce recovery cost for applications. Our focus here is on redo recovery using logical operations that permit cost effective recovery for new areas like applications and file systems. For this, we need to understand how the choice of log operations impacts logging cost, cache management, and ....
....savings. Logging logical operations, however, can have a profound impact on cache management and recovery. The goal of this paper is to reduce this impact. We give some examples of how logical logging can substantially reduce the logging required during normal execution. Application Recovery: In [7], we provided logical operations for recovering application state. Relating these to operations A and B of Figure 1, Y plays the role of application state and X the object that is being read and written . Application read (R(X,Y) Application Y reads object X into its input buffer, transforming ....
[Article contains additional citation context not shown here]
Lomet, D. Application recovery using generalized redo recovery. Int'l. Conf. on Data Engineering , Orlando, FL (February, 1998) 154-163.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC