ADSM-L

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

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

First item sent: 10/17/2009 20:00:49
Last item sent: 10/18/2009 23:56:35
Elapsed processing time:           03:56:28

In deed, there are two sessions in the log. I missed checking the fist and
the last item sent.
Scheduler Log Summary and collected events correspond perfectly.

Sorry for the set up.

and thank you

Gernot







Lindsay Morris <lindsay AT TSMWORKS DOT COM>
Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
26.10.2009 15:07
Bitte antworten an "ADSM: Dist Stor Manager"

        An:     ADSM-L AT VM.MARIST DOT EDU
        Kopie:
        Thema:  Re: Antwort: Re: Which is the truth? Inconsistencies
between Scheduler Log Summary and collected events


You would not be able to match up "Objects inspected" by scanning the log;
You SHOULD  be able to match up "objects backed up" and "objects expired";
The log numbers are larger than the client statistics, and that makes
sense if the log has a lot of sessions, say, over the course of a
week.
The client statistics are for one particular session only.

I don't have time to look through your log, but are you quite sure it only
has the one session in it, that matches the statistics?
I bet it has many sessions, like David said.  Look at the dates in it.


Lindsay Morris
Principal
TSMworks
Tel. 1-859-539-9900
lindsay AT tsmworks DOT com


On Mon, Oct 26, 2009 at 9:37 AM, TSM <tsm AT profi-ag DOT de> wrote:

> Hi Andrew,
>
> you are right:
>
> Client: this is Windows
> TSM Backup-Archive Client Version 5, Release 5, Level 2.2
>
> Server: this is AIX
> Session established with server TSM01: AIX-RS/6000
> Server Version 5, Release 5, Level 3.0
>
>
> the log file can be dowloaded from
>
> http://rapidshare.com/files/298151011/logWith1Session.zip.html     MD5:
> B56F02BA5E6968A98B10BF4A24E1D8E0
>
> Thank you
>
> Gernot
>
>
>
>
>
> Andrew Raibeck <storman AT US.IBM DOT COM>
> Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 26.10.2009 14:10
> Bitte antworten an "ADSM: Dist Stor Manager"
>
>         An:     ADSM-L AT VM.MARIST DOT EDU
>        Kopie:
>        Thema:  Re: Which is the truth? Inconsistencies between Scheduler
> Log Summary and collected events
>
>
> I think we'd need to see your log file to truly validate the numbers.
You
> also don't mention what client version or platform this is.
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
>
>
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

>
>
>
> 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 10/26/2009
> 08:15:05 AM:
>
> > [image removed]
> >
> > Which is the truth? Inconsistencies between Scheduler Log Summary
> > and collected events
> >
> > TSM
> >
> > to:
> >
> > ADSM-L
> >
> > 10/26/2009 08:16 AM
> >
> > Sent by:
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Please respond to "ADSM: Dist Stor Manager"
> >
> > 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
>

<Prev in Thread] Current Thread [Next in Thread>