ADSM-L

Re: SQL Query Challenge

2004-03-19 08:21:48
Subject: Re: SQL Query Challenge
From: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 19 Mar 2004 08:21:09 -0500
Just realize that "Success" in that context only means the backup
session ended "normally", not that all the files were successfully
backed up.

David

>>> Jack.Coats AT BANKSTERLING DOT COM 3/18/2004 4:10:03 PM >>>
Sorry, I should have been more explicit.

Currently I run a query that is:

  QUERY EVENT * * BEGINDATE=TODAY-1 BEGINTIME=08:00 ENDDATE=TODAY
ENDTIME=NOW EXCEPTIONSONLY=YES FORMAT=STANDARD

Todays report came back:

Thu 03/18/2004
 8:00a
.
.
Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 1, Level
6.0
(C) Copyright IBM Corporation 1990, 2003 All Rights Reserved.

ANS8000I Server command: 'QUERY EVENT * * BEGINDATE=TODAY-1
BEGINTIME=08:00
ENDDATE=TODAY ENDTIME=NOW EXCEPTIONSONLY=YES FORMAT=STANDARD'

Scheduled Start      Actual Start         Schedule Name Node Name
Status

-------------------- -------------------- ------------- -------------
---------
03/17/2004 20:00:00  03/18/2004 04:17:28  DAILY         HOUCYPRSTA
Failed

03/17/2004 20:00:00  03/18/2004 04:16:01  DAILY         HOUNORTHSHORE
Failed

03/17/2004 20:00:00  03/17/2004 21:01:28  DAILY         HOUSARBOX
Failed

03/17/2004 20:00:00  03/17/2004 20:36:53  DAILY         HOUENDPOINT
Failed

03/18/2004 00:00:00                       SERVER-MIDNI- HOUCORP1
Missed

                                           GHT


ANS8002I Highest return code was 0.

.
Thu 03/18/2004
 8:00a

And the Status comes back as "Completed", "Failed" (backup started but
for
any reason did not complete sucessfully"),
"Missed" (did not connect to server ... typically the scheduler service
was
not running), or "In Progress" (the backup is running backing up).

I guess for this purpose, the "In Progress" should be considered the
same as
"Failed", even though it really hasn't.

Oh yes, this is answering an 'audit requirement' from one of the many
groups
that audits us regularly.

... Jack

> -----Original Message-----
> From: David E Ehresman [SMTP:deehre01 AT LOUISVILLE DOT EDU]
> Sent: Thursday, March 18, 2004 2:48 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: SQL Query Challenge
>
> Define "failed".
>
> 1)  did not run
> 2) ran but did missed some files
> 3) ran but missed some filespaces
> 4) all of the above
> 5) some combination of the above
>
> >>> Jack.Coats AT BANKSTERLING DOT COM 3/18/2004 3:41:26 PM >>>
> Ok, this is really something I don't quite know how to do.
>
> My boss wants a report daily that has the name of nodes that failed
on
> their
> last backup attempt, and and the last time they has a successful
> completion
> (or when the first started failing).
>
> And, for those that failed last in their previous backup attempt,
but
> were
> successful on the latest backup, when did they first fail (in a row)
> and
> when were they successful finally.
>
> Of course I want to automate it so I don't want to pass any
parameters
> and I
> will be running it as a saved query (administrative script) from the
> command
> line, so I can pipe the output to a mail client.
>
> What I have is what failed during the last night, but this is beyond
my
> SQL
> basis.

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