ADSM-L

[ADSM-L] Which is the truth? Inconsistencies between Scheduler Log Summary and collected events

2009-10-26 08:16:54
Subject: [ADSM-L] Which is the truth? Inconsistencies between Scheduler Log Summary and collected events
From: TSM <tsm AT PROFI-AG DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 26 Oct 2009 13:15:05 +0100
Hi,

An incremental client schedule provided the following statistics:

10/18/2009 23:56:38 --- SCHEDULEREC STATUS BEGIN
10/18/2009 23:56:38 Total number of objects inspected: 3,096,554
10/18/2009 23:56:38 Total number of objects backed up:    4,856
10/18/2009 23:56:38 Total number of objects updated:          0
10/18/2009 23:56:38 Total number of objects rebound:          0
10/18/2009 23:56:38 Total number of objects deleted:          0
10/18/2009 23:56:38 Total number of objects expired:     27,290
10/18/2009 23:56:38 Total number of objects failed:           6
10/18/2009 23:56:38 Total number of subfile objects:          0
10/18/2009 23:56:38 Total number of bytes transferred:    5.43 GB
10/18/2009 23:56:38 Data transfer time:                  262.70 sec
10/18/2009 23:56:38 Network data transfer rate:        21,698.41 KB/sec
10/18/2009 23:56:38 Aggregate data transfer rate:        401.75 KB/sec
10/18/2009 23:56:38 Objects compressed by:                    0%
10/18/2009 23:56:38 Subfile objects reduced by:               0%
10/18/2009 23:56:38 Elapsed processing time:           03:56:28

A deeper look into the scheduler log (68496 lines) shows different
results:

 # grep Retry log | grep Directory--   | wc -l      206
 # grep Retry log | grep "Normal File" | wc -l      100
 # grep Retry log | grep Expiring      | wc -l       87

 # grep -v Retry log | grep Directory--   | wc -l  7613
 # grep -v Retry log | grep "Normal File" | wc -l 12472
 # grep -v Retry log | grep Expiring--    | wc -l 47957

I checked twice:
There is only one scheduler protocol in the file

How do these figures fit together??

Thank you

Gernot