You probably missed all the fun a few weeks ago...   :-)

...so please allow me to set the record straight.

The "failed" status when files are skipped is a *bug* in 4.2.1.0, and
there is no debate about it. This problem is documented in APAR IC31844
and fixed in patch 4.2.1.15 for the NT-based Windows clients. There is
also a patch 4.2.1.16 (which also includes the patch) for Win98 and WinMe.

As to having a means of identifying files that were open or otherwise
could not be backed up.... you make a valid point. But that is another
matter for another release....   ;-)

I'm not sure whether the other platforms have patches for this problem.
You can check the patches directory at the ftp site, and look for patches
at 4.2.1.15 or higher, which should include the fix.

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.




Dmitri Pasyutin <pasyutin AT CLUB-INTERNET DOT FR>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/21/2001 12:35
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: winNT client failure



It seems that as of version 4.2.1 the entire backup session is "Failed"
if some objects fail to back up (for all client platforms). Whether it's
abnormal or not is subject to debate. One advantage is that it is easier
to spot files that are open during backup and take action (e.g. put them
in the exclude list).

Dmitri