Your errorlog indicates that the journal service was shut down because an
i/o error occurred while updating a journal entry.
The precise meaning of return code 27 is that a seek was attempted to an
offset greater than 2 gig in the journal db file,
which essentially means that the journal db grew too large (the supported
maximum of the journal db manager is 2 gig).
Can you verify that the journal actually grew this large (look at the size
of journal db files in the journal directory) ?
Keep in mind that the number of journal entries corresponds with the amount
of file system change activity
and that the size of journal entries depends primarily on the fully
qualified path length of objects which change
(so file systems with very deeply nested dir structures will use more
space).
Also keep in mind the every journal entry is unique, meaning that there can
only be one entry per file/directory
of the file system being journaled (each entry represents that the last
change activity of the object).
When a journal based backup is performed and journal entries are processed
by the b/a client (backed up or expired),
the space the processed journal db entries occupy are marked as free and
will be reused, but the actual disk size of the
journal db file never shrinks.
I noticed that your notify buffer size was only 1 meg so I'm a bit
surprised that the journal was able to grow
this large without a notify buffer overflow occurring.
It's possible (doesn't seem likely, but possible) that if enough unique
objects changed in a long enough period of time
(before a Journal Based Backup was performed) that the journal db file
could grow large enough to exceed
the 2 gig limit without overflowing the small buffer.
Anyway, I suggest doing the following to get Journal Based Backup up and
running again:
1. Stop the journal service if it is running
2. Delete entire contents of the journal directory
del c:\TSM_Journal\*.*
3. restart the journal service
4. Perform a complete incremental backup of journal file systems
Note that this backup MUST update the Last Incr Backup Date for the
filespace on the server,
so you must backup the entire filespace (command like dsmc incr c:\*.*
WILL NOT do this).
5. Verify that Last Incr Backup Date was update by issuing the following
command:
dsmc query filespace
6. Verify that the journal is valid and that Journal Based Backup can be
used by
backing up a single file of a journal filespace:
dsmc sel c:\somefile
You should see the "Using Journal" message.
Also note that when Journal Based Backup is used the "Number of
Objects" inspected statistic
will be roughly equal to the actual number of objects backed up and
expired, as opposed to normal
incremental backup where the number of objects inspected is actual the
number of objects that
match the backup specification (the entire file system for dsmc incr c:
....).
7. Perform backup of the journal filesystem as you normally would.
Backup must be to the same server with same node name as was used in
steps 4/6 for the journal
to be valid and for jbb to work.
.
If you are still experiencing problems please append again to the list or
email me directly.
Regards, Pete
Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: tanenhau AT us.ibm DOT com
tieline: 320.8778, external: 607.754.4213
"Those who refuse to challenge authority are condemned to conform to it"
---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on
03/03/2003 10:56 AM ---------------------------
"Kamp, Bruce" <bkamp AT MHS DOT NET>@VM.MARIST.EDU> on 03/03/2003 07:48:48 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Journal Service Question
I installed the Journal Service on a Win 2k SP2 server (for the E drive)
with TSM client 5.1.5.9.
My TSM server is at 5.1.1.6 on AIX 4.3.3.
Once this is installed should it still show these messages in the
dsmsched.log?
03/03/2003 02:55:47 ANS1898I ***** Processed 879,500 files *****
03/03/2003 02:55:48 ANS1898I ***** Processed 889,000 files *****
03/03/2003 02:55:49 ANS1898I ***** Processed 898,500 files *****
03/03/2003 02:55:50 ANS1898I ***** Processed 908,500 files *****
03/03/2003 02:55:51 ANS1898I ***** Processed 918,000 files *****
03/03/2003 02:55:52 ANS1898I ***** Processed 927,500 files *****
03/03/2003 02:55:53 ANS1898I ***** Processed 937,000 files *****
03/03/2003 02:55:54 ANS1898I ***** Processed 947,000 files *****
03/03/2003 02:55:55 ANS1898I ***** Processed 957,000 files *****
03/03/2003 02:55:56 ANS1898I ***** Processed 966,500 files *****
03/03/2003 02:55:57 ANS1898I ***** Processed 976,500 files *****
03/03/2003 02:55:58 ANS1898I ***** Processed 985,500 files *****
03/03/2003 02:55:59 ANS1898I ***** Processed 995,500 files *****
03/03/2003 02:56:00 ANS1898I ***** Processed 1,005,500 files *****
03/03/2003 02:56:01 ANS1898I ***** Processed 1,015,000 files *****
03/03/2003 02:56:02 ANS1898I ***** Processed 1,024,500 files *****
03/03/2003 02:56:03 ANS1898I ***** Processed 1,034,000 files *****
03/03/2003 02:56:04 ANS1898I ***** Processed 1,043,000 files *****
03/03/2003 02:56:05 ANS1898I ***** Processed 1,053,000 files *****
03/03/2003 02:56:06 ANS1898I ***** Processed 1,055,500 files *****
03/03/2003 02:56:06 Successful incremental backup of '\\api-sql\e$'
To me it looks like it is still scanning the file system for files to
backup!
I installed it using the setup wizard & only selected this one file system.
I received this error in the jbberror.log the first night after installing
the service but none since.
03/01/2003 07:47:05 jnlDbCntrl(): Error updating the journal for fs 'E:',
dbUpdEntry() rc = -1, last error = 27
03/01/2003 07:47:06 JbbMonitorThread(): DB Access thread, tid 17732 ended
with return code 215.
This is my tsmjbbd.ini file:
[JournalSettings]
Nlsrepos=dscameng.txt
Errorlog=jbberror.log
JournalDir=C:\PROGRA~1\Tivoli\TSM\baclient
[JournaledFileSystemSettings]
;
; List of journaled filesystems
;
JournaledFileSystems=E:
;
; Default journal db size
; Allows journal to grow, limited only by space available
JournalDBSize=0x00000000
;
; What events to monitor
;
;
; File & Dir Name, Size, Attrib, Last Write, Security
NotifyFilter=0x0000011f
; Notification Buffer Size
;
NotifyBufferSize=0x00100000
[JournaledFileSystemSettings.E:\]
JournalDBSize=0x00000000
Thanks,
--------------------------------------
Bruce Kamp
Midrange Systems Analyst II
Memorial Healthcare System
E: bkamp AT mhs DOT net <mailto:bkamp AT mhs DOT net>
P: (954) 987-2020 x4597
F: (954) 985-1404
---------------------------------------
|
