Term: 2nd Term
Week: 2
Class: Senior Secondary School 3
Age: 17 years
Duration: 40 minutes of 2 periods each
Date:
Subject: Data Processing
Topic:- Crash recovery II
SPECIFIC OBJECTIVES: At the end of the lesson, pupils should be able to
INSTRUCTIONAL TECHNIQUES: Identification, explanation, questions and answers, demonstration, videos from source
INSTRUCTIONAL MATERIALS: Videos, loud speaker, pictures, Data Processing for senior Secondary Education by Hiit Plc, WAPB Computer Studies for Senior Secondary I by Adekunle et al, On-line Materials.
INSTRUCTIONAL PROCEDURES
PERIOD 1-2
PRESENTATION |
TEACHER’S ACTIVITY |
STUDENT’S ACTIVITY |
STEP 1 INTRODUCTION |
The teacher reviews the previous lesson on crash recovery |
Students pay attention |
STEP 2 EXPLANATION |
He explains other recovery related to data structure
|
Students pay attention and participates |
STEP 3 DEMONSTRATION |
He discusses checkpointing and media recovery |
Students pay attention and participate |
STEP 4 NOTE TAKING |
The teacher writes a summarized note on the board |
The students copy the note in their books |
NOTE
OTHER RECOVERY RELATED TO DATA STRUCTURE
Write Ahead Logging (WAL) is family of techniques for providing atomicity and durability (two of the ACID properties) in database systems. In a system using WAL, all modifications are written to a log before they are applied. Usually both redo and undo information is stored in the log. WAL allows updates of a database to be done in one place.
This is the property of transaction processing whereby either all the operations of transactions are executed or none of them are executed (all-or-nothing)
This is the ACID property which guarantees that transactions that have committed will survive permanently.
A transaction log (also transaction journal, database log, binary log or audit trail) is a history of actions executed by a database management system to guarantee ACID properties over crashes or hardware failure. Physically, a log is a file of updates done to the database, stored in stable storage.
CHECK POINTING
Check pointing basically consists of storing a snapshot of the current application state, and later on, use it for restarting the execution in case of failure. A check point record is written into the log periodically at that point when the system writes out to the database on disk all DBMS buffers that have been modified. This is a periodic operation that can reduce the time for recovery from a crash.
Check points are used to make recovery more efficient and to control the reuse of primary and secondary log files. In the case of crash, backup files will be used to recover the database to the point of crash.
MEDIA RECOVERY
Media recovery deals with failure of the storage media holding the permanent database, in particular disk failures. The traditional database approach for media recovery uses archive copies (dumps) of the database as well as archive logs. Archive copies represent snapshots of the database and are periodically taken.
The archive log contains the log records for all committed changes which are not yet reflected in the archive copy. In the event of a media failure, the current database can be reconstructed by using the latest archive copy and redoing all changes in chronological order from the archive log.
A faster recovery from disk failures is supported by disk organizations like RAID (redundant arrays of independent disks) which store data redundantly on several disks. However, they do not eliminate the need for archive based media recovery since they cannot completely rule out the possibility of data loss, e.g when multiple disk fail.
EVALUATION: 1. Explain other recovery related to data structure
CLASSWORK: As in evaluation
CONCLUSION: The teacher commends the students positively