>>> I've been implementing Journal Based Backups for the first time using
the
>>> 5.3 Windows client and thought I'd share some of my experiences and
issues.
>>> According to the Problem Determination Guide, there is a tool called
>>> DBViewB.EXE for testing the validity of a filesystem journal database
file.
>>> The corresponding tool for v5.1 and v5.2 was called DBView.EXE and was
>>> available as part of an unsupported download called JBBTools.zip. A
link to
>>> this is included in the TSM Journal Based Backup FAQ (IBM document
>>> reference 1155524).
>>> However the database structure has changed in 5.3 and the old tools no
>>> longer work. Does anybody know where I can find a copy of DBViewB.EXE
as
>>> this information seems to have been omitted from the Problem
Determination
>>> Guide?
I haven't had a chance to revise the KB article for 5.3 nor has the new
database
viewing utility been placed on the external Tivoli ftp site.
Send me a note and I will send you the new utility directly (I don't think
I can post an exe to the list...).
Hopefully eventually the functionality of this utility will be integrated
into the client as a documented command.
Sorry for the inconvenience ....
>>> While I'm on the subject of the change to the database structure in
5.3,
>>> the new journal files have a '.jbbdb' extension, but these files are
not
>>> part of the default list of files to be excluded from the journaling
in
>>> TSMJBBD.INI. However the old journal database files are excluded.
Surely
>>> this is an omission?
Good point.
Yes, it was definitely an omission, the new db files should have
been added to the exclude list in the sample config file.
I'll make sure that they are added in the first ptf.
>>> Finally, the NLSREPOS entry in the TSMJBBD.INI file defaults to
>>> DSCAMENG.TXT. This causes a warning if you try to run the Journal
Service
>>> as a foreground process (TSMJBBD.EXE i) as this file does not exist in
the
>>> BAClient directory. I was under the impression that DSCAMENG.TXT had
been
>>> superseded since v5.2 by DSMENU.TXT and that the existence of
DSMAMENG.TXT
>>> in the API directory was only for backward compatibility.
Another good point although I will make the obligatory statement that
running
the journal daemon in the foreground isn't officially supported (although
I
do it all the time).
By the way, just curious, but do find it useful running in the foreground,
and
if so, why ?
The call which loads the older message repository was never removed from
the
journal daemon process initialization and I guess nobody notice because
most
people apparently don't pay attention to the foreground messages (I never
did
before reading your note...).
Anyway, I will remove this.
>>> I'll try logging a call with IBM Support but wondered if anybody had
>>> similar experiences
You can have them open a doc apar for the first issue if you like (db
files missing from the sample config file)
and will have to trust me to fix the second one (can't really open an apar
on it because running in the foreground
isn't officially supported).
>>> Don't get me wrong, I think JBB is excellent. I've managed to reduce
the
>>> daily backup of a file system containing 5.6 million files from 9
hours to
>>> 8 seconds!
Thanks, I appreciate the positive feedback.
We did a lot to enhance and improve JBB in 5.3, and hopefully there are
improvements
to come in future releases.
Pete Tanenhaus
Tivoli Storage Manager Client 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/10/2005
10:17 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: Help required on JBB
I've been implementing Journal Based Backups for the first time using the
5.3 Windows client and thought I'd share some of my experiences and
issues.
According to the Problem Determination Guide, there is a tool called
DBViewB.EXE for testing the validity of a filesystem journal database
file.
The corresponding tool for v5.1 and v5.2 was called DBView.EXE and was
available as part of an unsupported download called JBBTools.zip. A link
to
this is included in the TSM Journal Based Backup FAQ (IBM document
reference 1155524).
However the database structure has changed in 5.3 and the old tools no
longer work. Does anybody know where I can find a copy of DBViewB.EXE as
this information seems to have been omitted from the Problem Determination
Guide?
While I'm on the subject of the change to the database structure in 5.3,
the new journal files have a '.jbbdb' extension, but these files are not
part of the default list of files to be excluded from the journaling in
TSMJBBD.INI. However the old journal database files are excluded. Surely
this is an omission?
Finally, the NLSREPOS entry in the TSMJBBD.INI file defaults to
DSCAMENG.TXT. This causes a warning if you try to run the Journal Service
as a foreground process (TSMJBBD.EXE i) as this file does not exist in the
BAClient directory. I was under the impression that DSCAMENG.TXT had been
superseded since v5.2 by DSMENU.TXT and that the existence of DSMAMENG.TXT
in the API directory was only for backward compatibility.
I'll try logging a call with IBM Support but wondered if anybody had
similar experiences.
Don't get me wrong, I think JBB is excellent. I've managed to reduce the
daily backup of a file system containing 5.6 million files from 9 hours to
8 seconds!
Regards
Neil Schofield
Yorkshire Water Services Ltd.
Visit cool-fuel.com to see our fun, interactive website for children
YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD
The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682
|
