Troubleshooting
Problem
New configuration for client backup fails to get Journaled
Symptom
Jbberror.log may show the following error:
Bringing Journaled File System '/testjournal online:
Journal Database : '/testjbbfs/tsm_testjournal.jdb
Notification Buffer Size : 0X200000
Preserve Journal On Exit : Yes
Allow Deferred Start : No
Defer Retry Interval : NA
Log File System Errors : Yes
ANS0361I DIAG: jbbtreev.cpp (2826): openBtDb():
Previous process didn't close the database, database may be corrupt.
ANS0361I DIAG: dbfuncsb.cpp ( 502): dbOpen(): Corrupt journal database
'/journaldb/tsm_testjournal.jdbInc.jbbdb' detected, journal will be reset.
Cause
Customer did not run initial full incremental backup that initializes the journal db.
Diagnosing The Problem
The dsmsched.log may show the following incorrect syntax that prevents full incremental from running
------------------------------------------------------------
01/14/14 14:59:14 Schedule Name: TEST_JBB
01/14/14 14:59:14 Action: Incremental
01/14/14 14:59:14 Objects: /testjbbfs/
01/14/14 14:59:14 Options: -SubDir=Yes
The syntax should be "incr /testjbbfs" (without ending slash and subdir option):
The full incremental backup should look like the following in the dsmsched.log:
------------------------------------------------------------
01/14/14 14:59:14 Schedule Name: TEST_JBB
01/14/14 14:59:14 Action: Incremental
01/14/14 14:59:14 Objects: /testjbbfs
01/14/14 14:59:14 Options:
Resolving The Problem
The first backup run after initial journal configuration must be a full incremental. Ensure you are using the correct syntax and that the backup is a full incremental.
[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Client","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Supported Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21664759