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 forei
Author: Mark Bertrand <Mark.Bertrand AT USUNWIRED DOT COM>
Date: Tue, 16 Apr 2002 09:34:59 -0500
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 sc
Author: Denis L'Huillier <dlhuillier AT PERSHING DOT COM>
Date: Tue, 16 Apr 2002 10:28:39 -0400
What's your environment? Is your TSM Server running on UNIX/390/NT? If it's unix then this is what I do..... I created a script which checks many things out on the server but one of those things is t
I have the following script as a POSTSCHEDCMD option in the dsm.sys. This works real well. I receive a mail every night immediatly after the backup ran. in the dsm.sys: POSTSCHEDULECMD /audit_logs/sc
Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>
Date: Tue, 16 Apr 2002 10:40:10 -0400
Be very carefull with the EX=YES. There is a status of an event of '(?)' that doesn't show as an exception. This condition can occur when a backup schedule starts for a node, and then due to either t
Author: Burak Demircan <burak.demircan AT DAIMLERCHRYSLER DOT COM>
Date: Tue, 16 Apr 2002 16:50:51 +0200
Does anybody have a bash or ksh script for it? Regards, Burak bill.boyer AT VERIZON DOT NET Sent by: ADSM-L AT VM.MARIST DOT EDU 16.04.2002 17:45 Please respond to ADSM-L To: A
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 16 Apr 2002 11:07:07 -0400
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", an
Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>
Date: Tue, 16 Apr 2002 11:20:48 -0400
Another approach - arguably better, and the way Servergraph/TSM does it - is to do a "query filespace f=d" on all your clients and see which ones have not been backed up in a long time. -- Mr. Lindsa
Author: Denis L'Huillier <dlhuillier AT PERSHING DOT COM>
Date: Tue, 16 Apr 2002 11:23:06 -0400
Are you sure.... When an incremental schedule is kicked off the TSM Server scheduler waits for a return code to be sent back to the server from the client... If rc=0 then the backup completed success
Author: Bill Boyer <bill.boyer AT VERIZON DOT NET>
Date: Tue, 16 Apr 2002 11:41:08 -0400
Couldn't you just pipe the output of your Q EV EX=NO command into GREP to exclude any lines that have 'Completed' as the status? This should give you everything else included 'Started', 'Pending', 'M
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 16 Apr 2002 12:06:34 -0400
Sorry folks, for the last sentence below that sort of trails off at the end. I meant to delete it before hitting "send". Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client De
Author: "Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA>
Date: Tue, 16 Apr 2002 13:04:36 -0500
And it depends on what you mean by a "successful" backup... We use Bill's method below to report on all events taht do not have a status of completed. (We only used to report on exceptions also ...)
Author: Mark Bertrand <Mark.Bertrand AT USUNWIRED DOT COM>
Date: Tue, 16 Apr 2002 14:29:06 -0500
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 proble
so how do you track failures Mark Bertrand <Mark.Bertrand@USUN To: ADSM-L AT VM.MARIST DOT EDU WIRED.COM> cc: Sent by: "ADSM: Subject: Re: Daily Backup Report Dist Stor Manager" <[email protected] D
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 16 Apr 2002 15:57:36 -0400
Historically (since ADSM V1), "successful" incremental backups had not taken skipped files into account. The rationale was that when processing entire file systems, you are very likely to run into on
Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>
Date: Tue, 16 Apr 2002 17:06:18 -0400
try this , I use this as a startingpoint to search for failures SELECT ACTLOG.DATE_TIME, ACTLOG.MESSAGE, ACTLOG.SEVERITY FROM ACTLOG ACTLOG WHERE (ACTLOG.SEVERITY='E') and (ACTLOG.DATE_TIME>{ts (curr
Author: "Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA>
Date: Tue, 16 Apr 2002 17:05:25 -0500
We use something similar, but only report on client errors (for this particular report). select MESSAGE,DOMAINNAME,NODENAME,DATE_TIME from actlog where - SEVERITY='E' - ORDER BY DOMAINNAME,NODENAME A
Author: StorageGroupAdmin StorageGroupAdmin <StorageGroupAdmin AT SYDNEYWATER.COM DOT AU>
Date: Wed, 17 Apr 2002 08:51:47 +1000
I had thought I had put my two cents worth in on this subject but when searching the archives I failed to see my comments so here goes I agree with Lindsay Morris that simply monitoring the most rece