so how do you track failures


                    Mark Bertrand
                    <Mark.Bertrand@USUN       To:     [EMAIL PROTECTED]
                    WIRED.COM>                cc:
                    Sent by: "ADSM:           Subject:     Re: Daily Backup Report
                    Dist Stor Manager"
                    <[EMAIL PROTECTED]
                    DU>


                    04/16/02 03:29 PM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"






I hate to correct IBM again... My statement was correct

>>
query event will NOT tell you if your backup was successful.
<<

As Andy so carefully stated in his last comment:

>>
you should not have any problems determining success or failure of the
operation.
<<

The operation and the actual successful backup are two different things. In
referring to a TSM operations (i.e. ACTION=INCREMENTAL), not a script, can
show proof of missed files and errors from reports from my activity log
that
a "success of the operation" does not mean that you had a successful
backup.
I

We currently have a Critsit open with Tivoli and IBM hardware support and
this is one of the major issues.

Just trying to help, I guarantee that if you rely only on a q event to let
your customers know if you have all their files backed up you will get
burned.

----Original Message-----
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 16, 2002 10:07 AM
To: [EMAIL PROTECTED]
Subject: Re: Daily Backup Report


>>
query event will NOT tell you if your backup was successful.
<<

This is true only if the schedule definition launches a script, i.e. DEF
SCH mydomain myschedule ACTION=COMMAND OBJECTS="myscript", and the script
contains commands that run asynchronously; in that case, TSM has no way to
track the actions taken within the script. It can only say, "the script
was launched successfully". In short, the success or failure of the
command depends on the return code issued from the script.

For scheduled TSM operations (i.e. ACTION=INCREMENTAL), you should not
have any problems determining success or failure of the operation. For
ACTION=COMMAND operations where the command

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Mark Bertrand <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
04/16/2002 07:34
Please respond to "ADSM: Dist Stor Manager"


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        Re: Daily Backup Report



We also used "query event * * begindate=today-1 enddate=today ex=yes"
until
I learned that this does not report on clients that were or were not
backed
up successfully, this ONLY reports on if the script or schedule was
successful. To quote straight from the h q event page "Use this command to
check whether schedules were processed successfully."

I will not go into a rant about this, just learn from my mistake, query
event will NOT tell you if your backup was successful.

-----Original Message-----
From: Williams, Tim P {PBSG} [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 16, 2002 9:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Daily Backup Report


we generally run a q event command   ex=yes
you can use begindate begintime parms, etc....
help q event
fYI

-----Original Message-----
From: Orin Rehorst [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 16, 2002 8:48 AM
To: [EMAIL PROTECTED]
Subject: Daily Backup Report


What are some good ways to get an automated daily report on which clients
were or were no backed up successfully?

TIA,

Regards,
Orin

Orin Rehorst
Port of Houston Authority
(Largest U.S. port in foreign tonnage)
e-mail:  [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone:  (713)670-2443
Fax:      (713)670-2457
TOPAS web site: <www.homestead.com/topas/topas.html
<http://www.homestead.com/topas/topas.html> >

Reply via email to