jBASE Transaction Journaling

TEMENOS EDUCATION CENTRE

NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the TEMENOS group of companies
(The Copyright Owner). The training materials contain protected logos, graphics and images. Use of the training materials is restricted solely for
use by licensed end users, partners and employees. Any un-licensed reproduction by any means, redistribution, editing, transformation,
publishing, distribution, or public demonstration of the training materials whether for commercial or personal gain is expressly prohibited by law,
and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum extent possible. Such training materials shall
not be represented, extracted into or included in part, or in whole, as part of any other training documentation without the express permission of
the Copyright Owner, which must given in writing by an authorised agent of the Copyright Owner to be valid. Where such permission is given a
clear and prominent notice must be displayed on any and all documentation accrediting the Copyright Owner with having copyright over the
materials. End-user licenses will in no event contain permissions extending the use of these training materials to third parties for commercial
training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever or location for further
reproduction or redistribution is expressly prohibited, unless such reproduction is expressly licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA
Objectives

After completing this learning unit, you will be able to:

 Differentiate between multiple implementation setup.

 Analyze jBASE Transaction journaling with T24 – NS installed.
 State the need for hot standby in the event of crash
 Explain the usage of utilities like jbackup, jrestore.

Slide 3
Let us check TJ being implemented in different system configurations!

Slide 4
Single system with single database server

App Server

T24/jBASE

Database
Server Tape
device
jlogdup
Process

Database files Transaction log

Slide 5
Multiple Application Server and a Single Database Server

Message Clustering Server

App Server 1 App Server 2 App Server 3

T24/jBASE T24/jBASE T24/jBASE

Tape
Database device
Server jlogdup
Process

Database files Transaction log

Slide 6
Hot Standby with a jBASE Database server

Message Clustering Server

App Server 1 App Server 2 App Server 3

T24/jBASE T24/jBASE
T24/jBASE

Hot standby/Disaster recovery

Database
Server
Database jlogdup jlogdup jlogdup DB Node 2
DB Node 1
Server Process Process Process

DB Node 1 DB Node 1 DB Node 2 DB Node 2

Database files Transaction log Transaction log Database files

Slide 7
Real-time Scenarios

An insight into choosing the right transaction journaling

Slide 8
Option A

Log the database updates to a file in the same server

as T24; in the event of system crash, restore backup
after the last COB apply the data from the log file and
bring the system online

Slide 9
Option A – Sunny day Scenario

Before COB After COB

Stop Journaling Take a backup

Take backup Set current log set to 1

Clear log sets

Start journaling

Slide 10
Option A – Event of crash

Online Crash Crash During COB

Stop journaling
Restore pre COB backup

Restore post COB backup

Restore using jlogdup from log set

Slide 11
Option B

Log the updates to a file in the same server; Continuously replay

the updates onto an external device like tape; in the event of
system crash, restore the backup taken after the last COB
replay the data from the tape

Slide 12
Option B – Sunny day Scenario

After COB
Before COB

Take a backup

Stop Journaling
Set current log set to 1

Stop jlogdup writing to external Clear log sets

device

Start journaling
Take backup

Start jlogsync

Start jlogdup – write to external

device

Slide 13
Option B – Event of crash

Online Crash Crash During COB

Stop journaling
Restore pre COB backup

Restore post COB backup

Restore using jlogdup from

external device

Slide 14
Option C

Log the updates to a file in the same server (production); Continuously

replay the updates onto a log file on a remote (backup) machine;
Simultaneously, replay the data from the log on the remote machine on
to the database on the remote machine; in the event of a crash, let the
users start using the remote (backup) machine; before COB, after all
the users are out of the system, assuming the production is up again,
restore the backup server database over the production database and
continue with COB.

Slide 15
Option C – Sunny day scenario

Restore this backup

After COB - Take a backup
Machines are now in sync
Start Hot
Production
Journaling Server Standby

Start jlogdup
Log Files

T24 T24
Database Database

Before COB Before COB

Stop Journaling Stop jlogdup
Take backup

Slide 16
Option C – Event of crash

Hot
Production Connectivity Standby
Server Lost
Stop
Journaling Switch to
next log set
Start
journaling
Log Files
T24
Database

Slide 17
Non Stop

Transaction Journaling

With T24 - NS

Slide 18
Transaction Journaling with T24-NS
Online Online
Start
Journaling Hot
Production Standby
Server
Machines are in sync

Start jlogdup Log Files

T24 T24
Database Database

Stop journaling jlogsync & jlogdup Stop journaling jlogsync & jlogdup
Initiate COB Once COB is initiated on
Production Server
Start journaling, jlogsync & jlogdup
Start journaling, jlogsync & jlogdup

After COB Stop Journaling, jlogsync &

Stop Journaling, jlogsync & jlogdup jlogdup
Machines are back in
Take backup Restore backup
sync for start of
business
Slide 19
T24 – NS – Journaling - Concerns

Event of crash?

Slide 20
jbackup

 jBASE provides jbackup to backup data

 jbackup has been tuned in jBASE 5 to support online backup
 Backup the database even while connections to the database exist (Hot
backup in Oracle)

Slide 21
jbackup - illustration

 Let’s understand jbackup with this commands mentioned below

jsh..>pwd
/glosoft/training/room1/R11/bnk/bnk.run
Jsh..>sh
$cd ..
$find . –name bnk.data –print | jbackup –W –V –f >
201012.bak

 This command will switch to the next log set (Log set 2)
 Performs a checkpoint so that log file and database are in sync
and writes a backup started identifier to the jediLoggerConfig
 Once the backup is complete, it also performs another checkpoint ,
log file and database are in sync.
 Writes a backup ended identifier to the jediLoggerConfig
 Switches to the next log set (Log set 3)
 Backup jediLoggerConfig & log set 2

Slide 22
jbackup - options

Slide 23
jrestore

 jrestore is used to restore the backup taken using the jbackup utility.
 While a jrestore is performed the database will be in offline mode.

Let us understand the working of jrestore with this command.

jsh..>pwd
/glosoft/training/room1/R11/bnk/bnk.run
jsh..>sh
$jrestore –W -V –f 201012.bak

 This command will

 Restore the backup (Backup + log set 2 + jEDILoggerConfig file)
 Save a copy of the current jediLoggerConfig file (Holds the information that
the current log set used is 3)
 Automatically invoke the jlogdup process to restore the database and roll
forward data in log set 2
 Restore the saved jediLoggerConfig file

Slide 24
jrestore - options

Slide 25
Quiz

Slide 26
Summary

In this learning unit, you learnt about the …….

You will now be able to:

Differentiate between multiple implementation setup.

Analyze jBASE Transaction journaling with T24 – NS installed.
State the need for hot standby in the event of crash
Explain the usage of utilities like jbackup, jrestore.

Slide 27
 Thank You
TEMENOS EDUCATION CENTRE
NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the TEMENOS group of companies
(The Copyright Owner). The training materials contain protected logos, graphics and images. Use of the training materials is restricted solely for
use by licensed end users, partners and employees. Any un-licensed reproduction by any means, redistribution, editing, transformation,
publishing, distribution, or public demonstration of the training materials whether for commercial or personal gain is expressly prohibited by law,
and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum extent possible. Such training materials shall
not be represented, extracted into or included in part, or in whole, as part of any other training documentation without the express permission of
the Copyright Owner, which must given in writing by an authorised agent of the Copyright Owner to be valid. Where such permission is given a
clear and prominent notice must be displayed on any and all documentation accrediting the Copyright Owner with having copyright over the
materials. End-user licenses will in no event contain permissions extending the use of these training materials to third parties for commercial
training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever or location for further
reproduction or redistribution is expressly prohibited, unless such reproduction is expressly licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA