I am almost certain that this change in behavior is not deliberate. The
APAR is going to be handled as a code defect, not a doc issue. Skipped
files are not cause to fail an incremental backup.

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.




Jeff Connor <connorj AT NIAGARAMOHAWK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/09/2001 08:08
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Windows client behavior change at 4.2.1.0



Not sure how much of an issue this will be for some of you but I thought
I'd pass
along a change we came across in the Windows 4.2.1.0 client.

If you are like us, and don't do a great job of excluding "unimportant"
files
that are regularly missed because they are in use during nightly backups,
then you will probably be affected by the change.  The Windows client
4.2.1.0
now reports a backup schedule failed with a RC=4 if any files are skipped
because they are in use.  The backup does complete but a Q EVENTS
shows the backup schedule failed. Previous versions reported the backup
schedule as completing successfully even if some files were missed.

We are in the process of doing what we should have done already and
building better Exclude lists to omit the non-critical files.  APAR
IC31844
has been
opened for a documentation change so people will be aware of the
new client behavior.

Regards,
Jeff Connor
Niagara Mohawk Power Corp