That is a good idea, although as you mentioned, would be difficult to
implement here.  Just finding one place to move all those files to, plus
working out access to all of the clients across multiple platforms in order
to get them, would be prohibitive.  But hopefully it will be helpful to
someone else in their environment.

Thanks,

Kathleen




                    Halvorsen
                    Geirr Gulbrand       To:     ADSM-L AT VM.MARIST DOT EDU
                    <gehal@WMDATA.       cc:
                    COM>                 Subject:     Re: TSM Scheduler shows 
backups  completed successfully
                    Sent by:              dsmerror. log         shows backups 
failed ?
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MAR
                    IST.EDU>


                    01/02/2003
                    04:09 AM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






Hello Kathleen, and a happy new year to everyone on the list.

One of our customers, resolved this by copying (!) all dsmsched.log and
dsmerror.log files to one server, and ran a script through all of them, to
get the actual status of the backup's. I can see that for 800+ clients,
this
would probably not be the best solution. The good thing about it is, it
will
always give the correct status.
Another idea just popped into my head... If you daily rename/move/delete
the
dsmsched.log and dsmerror.log from the clients, it would reduce the data to
copy/scan for errors.

Rgds.
Geirr G. Halvorsen

-----Original Message-----
From: Kathleen Hallahan [mailto:Kathleen_Hallahan AT FREDDIEMAC DOT COM]
Sent: 30. december 2002 16:36
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Scheduler shows backups completed successfully
dsmerror.log shows backups failed ?


This is an issue we have raised with Tivoli ourselves recently, even
requesting--and being turned down for-- a Design Change Request.  Their
recommendation was to check the dsmsched.logs on the clients.  This is
impossible for us and presumably for anyone in a large envorinment; we have
over 800 clients and I know there are organizations out there with many
more.  As it is, we've had to write an AIX script to catch the ones that
report as "In Progress," considering that they are rarely, if ever,
actually in progress at that time.  I have no idea how to chase down the
ones reporting as "Completed" when in fact they have not, on a daily basis
across our entire environment.  If anyone has any workable solutions I'd be
very interested in hearing them; I'm at a bit of a loss myself.





                    Mark Stapleton
                    <stapleto@BERB       To:     ADSM-L AT VM.MARIST DOT EDU
                    EE.COM>              cc:
                    Sent by:             Subject:     Re: TSM Scheduler
shows backups  completed successfully
                    "ADSM: Dist           dsmerror.log         shows
backups
failed ?
                    Stor Manager"
                    <ADSM-L AT VM DOT MAR
                    IST.EDU>


                    12/29/2002
                    09:58 PM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






On Fri, 2002-12-27 at 14:07, shekhar Dhotre wrote:
>  q eve * * shows all backups are completing successfully but  clients
> dsmerror.log  file shows  schedule command failed ,How I can verify that
> these backups are completing successfully other than restore test?
>
> 26-12-2002 20:45:08 ANS1909E The scheduled command failed.
> 26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.

Remember that the *schedule* itself completed successfully. You're far
better off looking for the message numbers that appear in the summaries
that appear in the server activity log at the end of a successsful
backup. (I'm not within reach of a TSM server tonight, so I can't look
them ATM.)

This is a much better indicator of successful backups than the event
list.

--
Mark Stapleton (stapleton AT berbee DOT com)