Principles of transaction-oriented database recovery
ACM Computing Surveys (CSUR)
Concurrency control and recovery in database systems
Concurrency control and recovery in database systems
Management of a remote backup copy for disaster recovery
ACM Transactions on Database Systems (TODS)
ACM Transactions on Database Systems (TODS)
An efficient and flexible method for archiving a data base
SIGMOD '93 Proceedings of the 1993 ACM SIGMOD international conference on Management of data
Recovery mechanisms in database systems
Recovery mechanisms in database systems
Logical logging to extend recovery to new domains
SIGMOD '99 Proceedings of the 1999 ACM SIGMOD international conference on Management of data
The Recovery Manager of the System R Database Manager
ACM Computing Surveys (CSUR)
Transaction Processing: Concepts and Techniques
Transaction Processing: Concepts and Techniques
Persistent Applications Using Generalized Redo Recovery
ICDE '98 Proceedings of the Fourteenth International Conference on Data Engineering
Exploiting A History Database for Backup
VLDB '93 Proceedings of the 19th International Conference on Very Large Data Bases
Redo Recovery after System Crashes
VLDB '95 Proceedings of the 21th International Conference on Very Large Data Bases
Improving Parallelism in Asynchronous Reading of an Entire Database
HiPC '00 Proceedings of the 7th International Conference on High Performance Computing
Parallel on-the-fly reading of an entire database copy
Practical parallel computing
Asynchronous Backup and Initialization of a Database Server for Replicated Database Systems
The Journal of Supercomputing
Online reorganization of databases
ACM Computing Surveys (CSUR)
Hi-index | 0.00 |
Media recovery protects a database from failures of the stable medium by maintaining an extra copy of the database, called the backup, and a media recovery log. When a failure occurs, the database is “restored” from the backup, and the media recovery log is used to roll forward the database to the desired time, usually the current time. Backup must be both fast and “on-line”, i.e. concurrent with on-going update activity. Conventional online backup sequentially copies from the stable database, almost independent of the database cache manager, but requires page-oriented log operations. But results of logical operations must be flushed to a stable database (a backup is a stable database) in a constrained order to guarantee recovery. This order is not naturally achieved for the backup by a cache manager concerned only with crash recovery. We describe a “full speed” backup, only loosely coupled to the cache manager, and hence similar to current online backups, but effective for general logical log operations. This requires additional logging of cached objects to guarantee media recoverability. We then show how logging can be greatly reduced when log operations have a constrained form which nonetheless provides very useful additional logging efficiency for database systems.