# Transaction Journaling - The Manual
Updated: 10/19/2021, 9:29:48 PM
Created: 10/19/2021, 9:29:48 PM
Last Updated By: Kevin Munoz
Read Time: 3 minute(s)
# jBASE resilience features
This document is intended as a guide for system/database administrators in their configuration and maintenance of resilient systems utilising the jBASE database. Knowledge of the administration of and the maintenance of standard systems based on jBASE is assumed.
Traditional jBASE systems essentially comprise three parts: User- and System- related files – “the database”; an application suite of programs to manipulate the data in the database - “the application” and a DBMS system comprising jBASE and user-developed programs to service database requests made by the application. The database is the only component which requires special attention with regard to resilience; the others can merely be reloaded from an archive image. The database is the only fluid component – it changes from day-to-day and probably from second-to-second. This document will describe the features of jBASE which exist in order to protect the database from potential problems which could occur, as well as the methods to use when confronted by each of such circumstances.
The database is the collection of data which supports any business. This valuable commodity must be protected as much as possible and be restored to a known, stable, state when the computer facilities fail to perform normally. The database comprises not only application data, but also configuration data pertaining to: the users of the computer along with their access and restrictions; and peripherals connected to the computer. The configuration data is not part of the data resilience referred to in this document. Any changes to such data should be archived (normally during the O/S archiving procedures).
# Transaction Journaling
Transaction Journaling provides the capability to prevent permanent data loss following a media or system failure. The Transaction Journal is a copy of database updates in a chronological order. In the event of such a failure, the Transaction Journal may be replayed, thus restoring the database to a usable state. Transaction Journaling preserves the integrity of the jBASE database by ensuring that logically related updates are applied to the database in their entirety or not at all.
These are the main transaction journaling administration utilities provided within jBASE:
- jlogadmin This command is provided to configure and start/stop/suspend transaction journaling.
- jlogstatus This command allows the administrator to monitor the activity of transaction journaling.
- jlogdup This command enables the recovery or replication of data.
# Additional Administration Utilities
- jlogsync - synchronizes and flushes log files
- jlogmonitor - monitors the current state of transaction journaling
Failure Conditions and Recovery Remedies
Transaction Journaling on a single system
Transaction Journaling on a single system with two tape decks
Introducing a Hot Standby machine into the configuration
Refinement to Hot Standby Configuration
Resilient T24/jBASE Configurations
Cluster System - multiple application servers and a single database server
Hot Standby database server
# To be updated to reflect current usage
Back to Knowledgebase