I'm guessing that the problem is that your initial backup command doesn't
update the last backup completed time on the TSM server so the journal
isn't set to the valid state and therefore won't be used for future
backups.

Changes are not tracked in journals which are not in the valid state.

Note that the command dsmc incr e:\ -subdir=yes  IS NOT
considered a full backup by the TSM client (even though conceptually it
is)
and therefore will not update the last backup completed date,
you must use the command dsmc incr e:.

Once the full incremental backup successfully completes the next backup
should use the journal.

This information and more is described in detail in my JBB FAQ technote:

http://www-01.ibm.com/support/docview.wss?
rs=203&context=SWI00&context=
SWJ00&context=SWK00&q1=
Journal+Based+Backup&uid=
swg21155524&loc=en_US&cs=utf-8&lang=en+en


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
01/17/2010 07:01 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:        Re: JBB problem


This is exactly what I did. I made an initial incremental backup of the
whole filesystem. But as you see in the details, journal database is not
updated when something changes or added.