Whoever told you that is wrong.

However, journal-based backup does require a 4.2 server, which would =
not=20
help Bob because he is running a 3.7 server.

For Bob's problem, I find 7+ hours a looooong time to process < 300,000 =

files, even with "traditional" incremental backup. However, there could =
be=20
other factors involved as well, such as other activity on client and/or =

server machines, amount of RAM, other hardware issues, etc.

If the amount of memory that TSM is using is causing excessive paging,=20
then that could be related to the problem. 4.2.1.26 should address some =
of=20
the memory issues (as I mentioned earlier this week).

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.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Ehland Ann J <ehland.aj AT MELLON DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/08/2002 11:00
Please respond to "ADSM: Dist Stor Manager"

=20
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:=20
        Subject:        Re: Inspecting over 200,000 objects with =
WinNT2000
client (takes    8 ho=20
urs)

=20

We've been told that journal based backup is not supported for W2K=20
clients.
=20