#Journaling

4 Followers · 45 Posts

Global journaling records all global update operations performed on a database, and used in conjunction with backup makes it possible to restore a database to its state immediately before a failure or crash.

While backup is the cornerstone of physical recovery, it is not the complete answer. Restoring a database from backup does not recover global updates made since that backup, which may have been created a number of hours before the point at which physical integrity was lost. These post-backup updates can be restored to the database from journal files after the database is restored from backup, bringing the database up to date. Any transactions open at the time of the failure are rolled back to ensure transaction integrity.

Documentation.

InterSystems staff + admins Hide everywhere
Hidden post for admin
New
InterSystems Official Daniel Palevski · 3 hr ago

Summary

Alert Id Product & Versions Affected Risk Category & Score Explicit Requirements
DP-449126 InterSystems IRIS® data platform 
InterSystems IRIS® for Health 
InterSystems Health Connect™ 
versions 2024.1.0 – 2024.1.5, 2024.2.0, 2024.3.0, 2025.1.0 – 2025.1.3, 2025.2.0, 2025.3.0
Data Integrity: Low Risk  Database updates executed as part of custom logic for CSP session events may not be journaled.

 

Issue

An issue has been corrected that prevented global sets and kills in custom logic from being journaled.

0
1 12
Question Malaya Acharya · Mar 2

I had configured the environment as follows:

OS: Redhat Linux 9.4

IRIS 2025.2 installed on local directory

IRIS Database: One LVM is created with 20 Storage luns and the LVM is mounted on a mount point. IRIS database is created on that

Primary and Alternate Journal: One LVM is created with 5 Storage luns and the LVM is mounted on a mount point. IRIS database is created on that.

WIJ: One LVM is created with 5 Storage luns and the LVM is mounted on a mount point. IRIS database is created on that.

So Data, WIJ and Journal is mounted on 3 separate mount point.

2
0 86
Question Scott Roth · Jun 1, 2025

I am attempting to failover my TEST environment to the Backup, and I keep getting an error stating that 

06/01/25-18:47:54:516 (11864) 1 [Utility.Event] Primary startup failed, failed to read header of /archive/journal/MIRROR-IRISTEST-20250513.007 (file #63653)

however, when I go to /archive/journal/, I am not finding any record of MIRROR-IRISTEST-20250513.007 (file #63653)

to get out of this error message I have to restart what was the Primary and restart the Backup to get it back into a state that we can use it.

1
0 95