About Us  |  My Account  |  

Journaling Achitecture

The OpenBase SQL multi-file journaling system delivers reliability through completely transparent, automatic and foolproof mechanisms that keep your data safe from all common types of file corruption--including that caused by hardware and software faults, power outages and incomplete writes.

Here's how it works: OpenBase SQL simultaneously maintains both a master and working copies of database data, along with a realtime journal, which tracks all changes. Changes are flushed to the journal as transactions commit, followed soon thereafter by batched flushing of changes to working random access files.

Since an incomplete write can corrupt the middle of random access files, OpenBase SQL uses the journal as a safeguard to ensure that if file corruption occurs, the random access files can be completely rebuilt from scratch.

If a database needs to be rebuilt, OpenBase SQL combines the master copy with the transaction journal to bring your database back up to its present state. In this way, OpenBase SQL offers a redundant and automatic system that keeps data safe.

In addition to maintaining data integrity, the OpenBase SQL multi-file journaling system also eliminates the need to perform many random access writes at commit time. Instead, changes to the work files can be safely batched, resulting in significantly faster database performance.

Instructional Video: OpenBase Journaling Architecture

previous | next