In almost all cases, the worst case scenario is that Journal Based Backup
will revert to a traditional
progressive incremental backup and no additional objects will be backed up.

The one possible exception is when virus protection (or potentially other)
software saves objects object attributes
(for example, last access date/time stamp), modifies them, and then resets
them to their original value.

In this scenario objects processed by the virus protection software will
not be backed up again by traditional
incremental backup because candidates for backup are selected based on
attribute comparison between
the local copy of the object and the copy of the object on the TSM server.

Since the Journal service monitors real-time change activity to the
filesystem,  each object processed by the
anti-virus software will generate a change notification and will cause an
entry to be added to the journal
database, and since Journal Based Backup selects backup candidates based
solely on the contents of
the journal every object process by the virus protection software (usually
the entire filesystem) will be
backed up again.

Symantec has a fix available for Norton Anti-Virus which allows the
caching/resetting of attributes to be
turned off during Nav scan processing (please see the TSM readme file for
details about obtaining the
fix).

Anyway, you might want to try turning off any virus protection software
(Symantec or otherwise).

Hope this helps .....


Pete Tanenhaus
Tivoli Storage Solutions Software 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
03/22/2002 11:02 AM ---------------------------
03/22/2002 11:02 AM ---------------------------

Andrew Raibeck/Tucson/IBM@IBMUS AT VM.MARIST DOT EDU> on 03/22/2002 09:29:43 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: Why are all my NT files getting backed up again?



I've never heard of a journal-based backup causing a backup of the entire
machine.... do we even know whether James is running the journal service?

It might help to know how often these full backups occur, and if there is
any pattern. Also, is it possible that someone is altering any copygroup
settings, perhaps changing the MODE from MODIFIED to ABSOLUTE? Maybe the
file space is getting renamed or deleted?

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.





"Remeta, Mark" <MRemeta AT SELIGMANDATA DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/21/2002 15:40
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Why are all my NT files getting backed up
        again?



Yes but it keeps the list locally and sometimes I think it gets confused
so
it just backs everything up again...