Thanks for your response.  Jounaled backups appear to be a service needed
when the backup window is restricted (better than a partial backup but not
as comprehensive as an incremental) .  This could be a reason to move to
4.2.  I included the following section from the TSM for Windows Using BA
Client for others to get a feel for what it does.

If you install the journal engine service and it is running, then by default
the incremental command performs a journal-based incremental backup on any
journaled file systems. Tivoli Storage Manager does not use the journaling
facility inherent in Windows NTFS 5 file systems or any other journaled file
system.

The journal engine service records changes to an object or its attributes in
a journal database. During a journal-based backup, the client obtains a list
of files that are eligible for backup from the journal database.
Journal-based backup can increase backup performance because the client does
not scan the local file system or contact the server to determine which
files to process. Journal-based backup also reduces network traffic between
the client and server.

Tivoli Storage Manager filters the list based on the current include-exclude
list and processes, expires, and updates the resulting files according to
policy constraints, such as serialization. You can use the copy frequency
attribute during a traditional full incremental backup. However, Tivoli
Storage Manager ignores this management class attribute during a
journal-based backup.

The journal engine service does not record changes in specific system files,
such as pagefile, registry, etc., in the journal. Therefore, journal-based
backup will not back up these files. See the journal service configuration
file tsmjbbd.ini in the Tivoli Storage Manager installation directory for
excluded system files. See the Appendix in Tivoli Storage Manager Installing
the Clients, SH26-4119, for more information about the journal service
configuration file tsmjbbd.ini.

To support journal-based backup, you must install the journaling engine
service background process as a service on Windows NT and 2000 using the
dsmcutil command or the client GUI setup wizard. See Tivoli Storage Manager
Installing the Clients, SH26-4119, for more information about using the
dsmcutil command to install the journal engine service.

To install and configure this service using the client GUI setup wizard,
perform the following steps:

Select the Utilities menu> Setup Wizard item.
Select the Help me configure the TSM Journal Engine checkbox.
Follow the instructions on the screen to configure and use the journal
engine.
See Incremental for more information about journal-based backup.

Notes:


The Journal Service is not supported in a Microsoft Cluster Server
environment. Only one Journal Service may be installed on a machine and the
Journal Service cannot dynamically start or stop monitoring shared disks.

When using anti-virus software, there are limitations to journal-based
backup. Refer to the README file that is shipped on the product installation
media for more information.

Al