Sorry to hear that you are having problems.

Generally, the "unable to communicate with journal service" means that
the session between the backup client and the journal daemon has
ended for some reason.

Note that this isn't really a "crash" as you mention as the process
doesn't terminate with an error, it is a controlled reaction to an
error which causes the journal backup session to terminate.

A number of problems which caused the the client and/or the journal
daemon to abend were fixed in 5.32 but there apparantly is still a problem

which can occasionally cause a journal session to terminate in the
middle of a journal backup (and generate the above message).

This problem will only occur when a domain backup is being done
by the client and multiple journal backup sessions are running
concurrently via the ResourceUtilization client option.

When the problem occurs the backup of the particular drive in
the domain will end (and error messages will be written to both
the journal and client error logs) and backup of other drives in
the domain will continue.

The problem has been reported by one customer as being somewhat
sporadic and unpredictable, meaning that doesn't happens during
every backup.

I am currently working on fix for this problem and hope to have it
available soon.

If this is the problem, the easiest work around until the fix is
available is to run/schedule backups of individual drives or to
reduce the ResourceUtilization setting to 2.

If you could post (or send to me directly) portions of your errorlogs
(both dsmerror.log and jbberror.log) I should be able to verify if this
is indeed the problem.


Hope this helps ....



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
11/22/2005 11:04 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:        Journaling (again)


Hi,

Is there anyone out there who has a working journal db back-up.

Setup: ITSM 5.3.2.0 server + ITSM 5.3.2.0 client (upgraded from 5.3.0.15
because of instable journal backups) on Windows 2003 cluster server.
Cluster has 4 virtual servers on 2 cluster controlers (active /active or
dual active/passive whatever you prever...).

Virtual server on which journaling is enabled is a profile server.
Normal inspect 17.000.000 objecten

Journal inspect: up to 700.000 objecten to inspect
Normal journal backup: 300.00 object for in total +/- 3 GB

Journal inspect time (if it works) up to 4 hour. Normal incremental
backup up to 26 hours.

Journal backup keeps crashing with "unable to communicate with journal
service". This is during the inspects (5.3.0.15 client) or while
starting the journal backup (5.3.2.0 client)and loading the tsmjbbd
service up to 180 MB of mem (taskmanager/processes).

Can anyone who solved this sort of problem email me the journal .ini
file

Regards,

Karel