Geoff,

Make sure you are not using the QUIET option (just in case you are). QUIET
is nice when things are going well, but it is best to not use it when
diagnosing problems. Assuming that you are not using QUIET, then make sure
you see the 'Using Journal for ...' messages. If the messages are not
there, then a couple of things occur to me:

1) Was this the first incremental backup you ran after turning on
journaling? If so, then this is normal: the first backup will be a full
incremental (not to be confused with full backup) so that the journal
database(s) and server can be synched. Or did you do anything else (like
reboot) that may have caused the journal to require resynchronization?

2) Do you have all desired drives configured to use journaled backup, via
the JournaledFileSystems parameter? What does your tsmjbbd.ini file look
like?

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (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.




"Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/31/2002 10:56
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Journaling Again



>          1. First of all, look in the dsmsched.log file and look to see
if
> you have the message:
>
>                  Using journal for '\\xxx-yyyyyyyy\c$'

It's not there but the service is started.

>          If you see this message, a journaled backup has taken place for
> that filespace. You should see this message
>          at the start of the backup.
>
>          2. Verify that the journal size is adequate. If you see a
message
> like the following in the jbberror.log,  your journal size (specified by
> parameter JournalDBSize in tsmjbbd.ini) is set too low. If you take the
> default (as specified by Pete Tanenhaus
> in previous posts as a recommendation) you should not have this problem.

This is set to the default and there is no error message in this log
I guess I'll stop and restart the service and see what kind of reports I
get
tonight.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 905-7154