Re: SQL/scripts
One that we've added to our daily 'health' check is query the actlog for: ANR8443E Command: Volume volume name in library library name cannot be assigned a status of SCRATCH. messages. We had some tapes brought back that were not scratch and inserted into the 3494 library. The library put them away, but TSM didn't check them in. They were still valid offsite tapes that TSM still thought were offsite. We went on a disaster recovery test and didn't have a tape volume we needed for a restore. Found out it was in the library in limbo. For a SCSI library they would still be in the I/O port (if you have one). Once bitten... Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Rushforth, Tim Sent: Thursday, May 30, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: SQL/scripts I'm not prepared to post our scripts yet but will tell you some of the things that we run daily: Report on failed client schedules - q event * * enddate=today begintime=NOW-23:59 endtime=NOW f=d - filter and report on anything other than completed Report on Client errors (mostly failed files) - select MESSAGE,DOMAINNAME,NODENAME,DATE_TIME from actlog where - (date_timecurrent_timestamp - 1 days and originator='CLIENT' AND SEVERITY='E') - ORDER BY DOMAINNAME,NODENAME - Report on file spaces not backed up in over x days q fi f=d - filter and report on specific nodes and days, depending on complexity could be easier done with SQL - Report on all server error messags and some warning messages reported over last 24 hours - we just do a q actlog then filter for specific messages - we stated with all error messages then slowly filtered out ones we didn't want - we started with no warning\informational and then slowly added ones we wanted - this might be easier with sql but we are using a perl script! - we also run an online error monitor that emails, net sends, or pages us on various errors throughout the day - Daily\weekly processing report - client report from accounting log, reports on gb, transfer rate, media wait ... for backup/restore, archive/retrieve - TSM Health Check every 5 minutes - email and page if TSM is down - TSM System check - checks for things like DB %utilization, # of scratch tapes, stgpool %, db and log volumes synched, db cache hit 98%, log %, disk volumes all online and available, no tapes in error state or specific ones in read only that should not be, cleaning cart close to no uses - report of tapes not written to in over x amount of time (we then reclaim these) Tim Rushforth City of Winnipeg -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 11:33 AM To: [EMAIL PROTECTED] Subject: SQL/scripts Hello! I don't have a reporting package and I was wondering if any on you could tell me some useful scripts that you run on a daily basis? Thanks!!! Joni Moyer Associate Systems Programmer [EMAIL PROTECTED] (717)975-8338
Re: SQL/scripts
We've found it easier to include all errors in our check (which covers this one) then just filter out any errors you don't want as you go along. We get this happening also, get the error right away in email, also in next days error check of previous 24 hours. -Original Message- From: Bill Boyer [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 9:51 AM To: [EMAIL PROTECTED] Subject: Re: SQL/scripts One that we've added to our daily 'health' check is query the actlog for: ANR8443E Command: Volume volume name in library library name cannot be assigned a status of SCRATCH. messages. We had some tapes brought back that were not scratch and inserted into the 3494 library. The library put them away, but TSM didn't check them in. They were still valid offsite tapes that TSM still thought were offsite. We went on a disaster recovery test and didn't have a tape volume we needed for a restore. Found out it was in the library in limbo. For a SCSI library they would still be in the I/O port (if you have one). Once bitten... Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Rushforth, Tim Sent: Thursday, May 30, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: SQL/scripts I'm not prepared to post our scripts yet but will tell you some of the things that we run daily: Report on failed client schedules - q event * * enddate=today begintime=NOW-23:59 endtime=NOW f=d - filter and report on anything other than completed Report on Client errors (mostly failed files) - select MESSAGE,DOMAINNAME,NODENAME,DATE_TIME from actlog where - (date_timecurrent_timestamp - 1 days and originator='CLIENT' AND SEVERITY='E') - ORDER BY DOMAINNAME,NODENAME - Report on file spaces not backed up in over x days q fi f=d - filter and report on specific nodes and days, depending on complexity could be easier done with SQL - Report on all server error messags and some warning messages reported over last 24 hours - we just do a q actlog then filter for specific messages - we stated with all error messages then slowly filtered out ones we didn't want - we started with no warning\informational and then slowly added ones we wanted - this might be easier with sql but we are using a perl script! - we also run an online error monitor that emails, net sends, or pages us on various errors throughout the day - Daily\weekly processing report - client report from accounting log, reports on gb, transfer rate, media wait ... for backup/restore, archive/retrieve - TSM Health Check every 5 minutes - email and page if TSM is down - TSM System check - checks for things like DB %utilization, # of scratch tapes, stgpool %, db and log volumes synched, db cache hit 98%, log %, disk volumes all online and available, no tapes in error state or specific ones in read only that should not be, cleaning cart close to no uses - report of tapes not written to in over x amount of time (we then reclaim these) Tim Rushforth City of Winnipeg -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 11:33 AM To: [EMAIL PROTECTED] Subject: SQL/scripts Hello! I don't have a reporting package and I was wondering if any on you could tell me some useful scripts that you run on a daily basis? Thanks!!! Joni Moyer Associate Systems Programmer [EMAIL PROTECTED] (717)975-8338
SQL/scripts
Hello! I don't have a reporting package and I was wondering if any on you could tell me some useful scripts that you run on a daily basis? Thanks!!! Joni Moyer Associate Systems Programmer [EMAIL PROTECTED] (717)975-8338
Re: SQL/scripts
You should try the archives (http://www.adsm.org) and also the Scripts Depot at Coderelief (http://www.coderelief.com/depot.htm) Lots of good stuff people on this list have posted there. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joni Moyer Sent: Wednesday, May 29, 2002 12:33 PM To: [EMAIL PROTECTED] Subject: SQL/scripts Hello! I don't have a reporting package and I was wondering if any on you could tell me some useful scripts that you run on a daily basis? Thanks!!! Joni Moyer Associate Systems Programmer [EMAIL PROTECTED] (717)975-8338
Re: SQL/scripts
I'm not prepared to post our scripts yet but will tell you some of the things that we run daily: Report on failed client schedules - q event * * enddate=today begintime=NOW-23:59 endtime=NOW f=d - filter and report on anything other than completed Report on Client errors (mostly failed files) - select MESSAGE,DOMAINNAME,NODENAME,DATE_TIME from actlog where - (date_timecurrent_timestamp - 1 days and originator='CLIENT' AND SEVERITY='E') - ORDER BY DOMAINNAME,NODENAME - Report on file spaces not backed up in over x days q fi f=d - filter and report on specific nodes and days, depending on complexity could be easier done with SQL - Report on all server error messags and some warning messages reported over last 24 hours - we just do a q actlog then filter for specific messages - we stated with all error messages then slowly filtered out ones we didn't want - we started with no warning\informational and then slowly added ones we wanted - this might be easier with sql but we are using a perl script! - we also run an online error monitor that emails, net sends, or pages us on various errors throughout the day - Daily\weekly processing report - client report from accounting log, reports on gb, transfer rate, media wait ... for backup/restore, archive/retrieve - TSM Health Check every 5 minutes - email and page if TSM is down - TSM System check - checks for things like DB %utilization, # of scratch tapes, stgpool %, db and log volumes synched, db cache hit 98%, log %, disk volumes all online and available, no tapes in error state or specific ones in read only that should not be, cleaning cart close to no uses - report of tapes not written to in over x amount of time (we then reclaim these) Tim Rushforth City of Winnipeg -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 11:33 AM To: [EMAIL PROTECTED] Subject: SQL/scripts Hello! I don't have a reporting package and I was wondering if any on you could tell me some useful scripts that you run on a daily basis? Thanks!!! Joni Moyer Associate Systems Programmer [EMAIL PROTECTED] (717)975-8338
Server identification in SQL/scripts
What table/field contains the server name that is consistent across all configurations/OS of the TSM server?
Re: Server identification in SQL/scripts
I'm not exactly sure what your question is asking for, but have you looked at the SERVER_NAME column in the STATUS table? 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. Jolliff, Dale [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 04/16/2002 08:02 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Server identification in SQL/scripts What table/field contains the server name that is consistent across all configurations/OS of the TSM server?
Re: Server identification in SQL/scripts
That's what I was looking for -- thanks. I had been flailing around looking through syscat.columns and somehow missed it. -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 10:53 AM To: [EMAIL PROTECTED] Subject: Re: Server identification in SQL/scripts I'm not exactly sure what your question is asking for, but have you looked at the SERVER_NAME column in the STATUS table? 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. Jolliff, Dale [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 04/16/2002 08:02 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Server identification in SQL/scripts What table/field contains the server name that is consistent across all configurations/OS of the TSM server?
