I spent one week explaining Our DBA`s that TSM is backing up your 
databases and all data is safe regardless of dsmerror..log file errors 
they see everyday .
Had to prove them by restoring some of the data. 
Can't do restore test on weekly basis to prove them that TSM is backing up 
your data. That's why I asked this question on list, and found out that I 
am not alone who is having this problem. Hopefully IBM will address this 
issue. 
 
Thank You 

SD






Kathleen Hallahan <Kathleen_Hallahan AT FREDDIEMAC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/30/2002 11:24 AM
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        Re: TSM Scheduler shows backups  completed successfully 
dsmerror. log  
shows backups failed ?


I might try running this for a few days to see what kind of results I get.
However, we have filespaces added and removed pretty frequently, so I'm 
not
sure yet if my results would be valid.  I will see what it does, though.

What I'd really like to see, of course, is the TSM server report the 
actual
status of backups more accurately, rather than having to devise
workarounds.  So far that functionality doesn't seem to be planned for the
product, however, at least based on my discussions with IBM/Tivoli.





"Nelson, Doug"
<DNelson@CHITT       To:     ADSM-L AT VM.MARIST DOT EDU
ENDEN.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/30/2002
10:56 AM
Please respond
to "ADSM: Dist
Stor Manager"






We have a script that runs as part of our morning report that shows file
spaces that have not been backed up in the last 24 hrs. It has been very
successful in catching the ones that say "completed" but didn't really do
it.

select node_name,filespace_name,backup_end from -
filespaces where 1 < -
days(current_timestamp) - days(backup_end) or -
backup_end is null


Douglas C. Nelson
Distributed Computing Consultant
Alltel Information Services
Chittenden Data Center
2 Burlington Square
Burlington, Vt. 05401
802-660-2336



-----Original Message-----
From: Kathleen Hallahan [mailto:Kathleen_Hallahan AT FREDDIEMAC DOT COM]
Sent: Monday, December 30, 2002 10:36 AM
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)