You're welcome! :-)
My recommendations:
1) I think the 2 GB file is symptomatic, as the journal db will "break" if
the file exceeds 2 GB in size. This is suspicious, and if the behavior
repeats itself, please open a call with support so that we can do more
in-depth diagnostics.
2) Make sure you following *all* the recommendations in the README file
with regard to NAV, including the NotifyFilter settings.
3) Sorry, I meant to add this in my prior response, but forgot: Change the
NotifyBufferSize from the default value of 0x01000000 to 0x04000000.
3) Yes, you should shut down the journal service, delete the *jdb* files,
then restart the journal service. Again, the first backup will be a full,
but then let's see how it goes from there. Also keep an eye on the *jdb*
files. Unless you have a *huge* number of files that change on a daily
basis, the journal database should not grow so large. And if you have that
many files changing daily, then journal-based backup is probably not a
viable solution.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Kamp, Bruce" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
03/03/2003 08:17
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Journal Service Question
FIRST THANKS!!
How large are the journal db files (named like *jdb*)?
Between 1k & over 2 Gig
I am using NAV 7.60 & made the registry change
Also I added the PreserveDbOnExit=1 per the readme!
Do I need to restart any services?
