In addition to my earlier comments on this, it is possible that you are
looking at IC41440:

ABSTRACT:
TSM 5.2.2.9 CLIENT ON WIN2003 SHOWS ALL FILES "FAILED" IN ITS
STATISTICS WHEN ANS1228E ERROR IS RECEIVED FOR C:\ADSM.SYS

ERROR DESCRIPTION:
The dsmsched.log file shows that during backup of the "System
services" an error occured. The client was not able to sent the
"c:\adsm.sys" directory because this directory was changed
during backup. For example :

ANS1228E Sending of object 'C:\adsm.sys' failed
ANS4037E File 'C:\adsm.sys' changed during processing.
         File skipped.

The client backup summary indicates that all files failed to
backup although only c:\adsm.sys failed. For example :

Total number of objects inspected:       22
Total number of objects backed up:        0
Total number of objects updated:          0
Total number of objects rebound:          0

related to System State/Services, fails, nothing is backed up.
In such case, the client does not indicate that the system state
service backup failed and the client statistics are incorrect.

This problem occurs regardless of type of backup. An incrmental
backup of whole client or just system objects is subject to same
error.

This behavior was not present in previous versions of the
client.The problem appeared at 5.2.2.9 version.

LOCAL FIX:
Setting the "serialization" to 'SHRStatic' will avoid getting
wrong statistics when following error is received :
 ANS1228E Sending of object 'C:\adsm.sys' failed

The APAR has been opened recently, and so no fix is yet available.

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.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/07/2004
14:12:06:

> Hello everyone.  I have an interesting scenario to ask you about.  We
have
> the TSM Client v5.2.1 or v5.2.2 installed on over 700 Windows servers
> including versions 4.0, 2000 and recently 2003.  The TSM host runs on
AIX
> v5.1 and TSM server v5.1.7.3.  It also happens on another of our TSM
severs
> running v5.1.9.0.  We have noticed that all of the W2003 servers give us
> this similar log:
>
> ********************************************************
>
> 07/03/2004 03:05:16 --- SCHEDULEREC STATUS BEGIN
> 07/03/2004 03:05:16 Total number of objects inspected:  336,096
> 07/03/2004 03:05:16 Total number of objects backed up:        0
> 07/03/2004 03:05:16 Total number of objects updated:          2
> 07/03/2004 03:05:16 Total number of objects rebound:          0
> 07/03/2004 03:05:16 Total number of objects deleted:          0
> 07/03/2004 03:05:16 Total number of objects expired:      5,834
> 07/03/2004 03:05:16 Total number of objects failed:     336,096
> 07/03/2004 03:05:16 Total number of bytes transferred:    11.27 GB
> 07/03/2004 03:05:16 Data transfer time:                27,299.99 sec
> 07/03/2004 03:05:16 Network data transfer rate:          433.11 KB/sec
> 07/03/2004 03:05:16 Aggregate data transfer rate:        409.58 KB/sec
> 07/03/2004 03:05:16 Objects compressed by:                   35%
> 07/03/2004 03:05:16 Elapsed processing time:           08:01:08
> 07/03/2004 03:05:16 --- SCHEDULEREC STATUS END
> 07/03/2004 03:05:16 --- SCHEDULEREC OBJECT END WEEKEND_ONLY 07/02/2004
> 19:00:00
> 07/03/2004 03:05:16 Scheduled event 'WEEKEND_ONLY' completed
successfully.
> 07/03/2004 03:05:16 Sending results for scheduled event 'WEEKEND_ONLY'.
> 07/03/2004 03:05:17 Results sent to server for scheduled event
> 'WEEKEND_ONLY'.
>
> 07/03/2004 03:05:17 ANS1483I Schedule log pruning started.
> 07/03/2004 03:05:21 Schedule Log Prune: 340699 lines processed.  224732
> lines pruned.
> 07/03/2004 03:05:21 ANS1484I Schedule log pruning finished successfully.
> 07/03/2004 03:05:21 Querying server for next scheduled event.
> 07/03/2004 03:05:21 Node Name: BNDPSFP01
> 07/03/2004 03:05:22 Session established with server SPOK_TSMSERVER:
> AIX-RS/6000
> 07/03/2004 03:05:22   Server Version 5, Release 1, Level 7.3
> 07/03/2004 03:05:22   Data compression forced on by the server
> 07/03/2004 03:05:22   Server date/time: 07/03/2004 03:01:17  Last
access:
> 07/03/2004 03:01:08
>
> 07/03/2004 03:05:22 --- SCHEDULEREC QUERY BEGIN
> 07/03/2004 03:05:22 --- SCHEDULEREC QUERY END
> 07/03/2004 03:05:22 Next operation scheduled:
> 07/03/2004 03:05:22
> ------------------------------------------------------------
> 07/03/2004 03:05:22 Schedule Name:         WEEKEND_ONLY
> 07/03/2004 03:05:22 Action:                Incremental
> 07/03/2004 03:05:22 Objects:
> 07/03/2004 03:05:22 Options:
> 07/03/2004 03:05:22 Server Window Start:   19:00:00 on 07/09/2004
> 07/03/2004 03:05:22
> ------------------------------------------------------------
> 07/03/2004 03:05:22 Waiting to be contacted by the server.
>
> ***********************************************************
>
> Notice that it fails as exactly as many objects as it inpects, but
transfers
> a lot of data.  And we can restore anything.  As far as we can tell, the
> data is there and the TSM server's filespace jives against what we see
on
> the clients.  Does anyone have any idea what is going on? We don't see
that
> many failures in the log at all - most of it are successful [sent]'s.
>
>
> With regards,
> _______________________________________________
>
> Jon R. Adams
> Systems Engineer II
> Infrastructure Technical Support, OSS
> Premera Blue Cross
> Work: 425-918-5770 / mailto:jon.adams AT premera DOT com
> <mailto:jon.adams AT premera DOT com>
>
>
> "There are only 10 kinds of people in this world - those that know
binary
> and those that do not."
>
> -author unknown