Re: offsite tapes 'reclamation'
Hi, I suggest reading this chapter from the Administrator's Guide: Reclaiming Space in Sequential Access Storage Pools Especially these parts: Reclamation for Copy Storage Pools and Reclamation of Offsite Volumes. Regards, Imre -Original Message- From: Hegedus Gyrgy [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 9:54 PM To: [EMAIL PROTECTED] Subject: offsite tapes 'reclamation' Hi All, I would like to copy the primary storage pools to a copy storage pool, then take the tapes offsite. The 'backup stgpool' command make incremental backups, so every day I should take some tapes offsite. And will be more and more offsite tapes. How can I initiate the reclamation process? Should I take back all tapes to the library? I have no idea. What should I do? Could you help me? Regards, Gyorgy Hegedus Megatrend 2000 Rt.
delete filespace takes 24hours
Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf
Re: delete filespace takes 24hours
Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
AW: delete filespace takes 24hours
some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: DSM server 5.1.0.7 hangs during night backup.
Hi Yury! Before even starting to investigate, I would urge you to upgrade to a proper server level. You are running a 1,5 year old patch release! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Yury Us [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 17:20 To: [EMAIL PROTECTED] Subject: DSM server 5.1.0.7 hangs during night backup. Hi all, I have very unpleasant situation with my DSM server. It hangs 1 or 2 times a week during the night backup. Every single client (I have 500 nodes) hangs too. So After rebooting the server all client nodes have to be restarted. We fixed all suspicious hardware problems, installed latest AIX4.3.3 patches and DSM server patch, all installations did not help. I ran auditdb during this weekends. It found a few discrepancies and fixed them. But last night server hangs again. There is no any suspicious messages or errors in the actlog. On some clients in dsmerror file I see the following error: 10/27/03 22:26:48 ANS1005E TCP/IP read error on socket = 7, errno = 73, reason : 'A connection with a remote socket was reset by that socket.'. But most nodes don't have even that. My environment is as follows: AIX 4.3.3 DSM Server 5.1.0.3 Nodes mixture of versions from 4.2 to 5.2 versions. Have you ever had or heard of such a problem and what would you recommend to do next? With respect, Yuriy Us. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
TDP for Oracle works with Oracle 8.1.6 ?
Hi all. I´m close to install the TDP for Oracle 5.2.0 over HPUX 11.0, so I wonder if does works with Oracle 8.1.6. Anyboby have experience with this software conbination ? Thanks. Juanma ING National Netherlanden Madrid - SPAIN Cloudy, Raining and 12 ºC
Re: TDP for MSSQL - huge problem
In dsmserv.opt increase the value of two parameters 1. commtimeout 3000 2. idletimeout some suitable value. Regards Alkina L ADSM: Dist Stor Manager wrote: gt;4 more than one week I've been receiving the error code listed below during gt;my night backup process on MS SQL 7 (NT 4.0): gt; gt;28-10-2003 07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. gt;Return code = -1073741510. gt;28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket = 1320, errno = gt;10054, reason : 'Unknown error'. gt;28-10-2003 07:58:45 ANS1005E TCP/IP read error on socket = 656, errno = gt;10054, reason : 'Unknown error'. gt; gt;The scheduled backup completes just few databases but always stop on msdb. gt;The problem doesn't occur when I start up backup manualy. gt;Yesterday I upgraded the TDP client to the latest 5.2.1 version. It didn't gt;solve this problem. gt;What can I do next? Have u evere had similar problem? gt;Waitin' for some suggestion from ya wizards:-) Sebastian - The 10054 TCP/IP errno reflects a connection being reset by peer, which in TSM terms means that the server terminated the session with the client. Thus, the place to look is in the server Activity Log, which should explain why it did so. It may be that server timeout values are too low. Richard Sims, BU Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets on Air Sahara Flights. For Best Deals, log on to http://airsahara.indiatimes.com and Bid Now !
RESET PASSEXP (for a node)?
(TSM server 5.1.6.5 on AIX) Did anyone find a way to clear a client node's PASSwordEXPiration time (once it's inadvertently set by some admin), so as to re-establish the server-wide default value? A commands like the following doesn't work for me: UPDATE NODE ... PASSEXP= Strangely, the server's HELP in 5.1.6.5 mentions RESET PASSEXP under both SET PASSEXP and HELP RESET; unfortunately, the server doesn't recognize that as a valid command. ((And while on the topic of undocumented [line-mode] commands - does FLUSH LOG, which I once entered in despair, have any useful purpose? Be careful ... :-()) Wolfgang J. Moeller, Tel. +49 551 201-1516/-1510, [EMAIL PROTECTED] GWDG, D-37077 Goettingen, F.R.Germany |Disclaimer: No claim intended! http://www.gwdg.de/~moeller/ [EMAIL PROTECTED] [EMAIL PROTECTED]
ODP: TDP for MSSQL - huge problem
Hi folks, current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that : Beginning full backup for database model, 13 of 21. Full: 0 Read: 867840 Written: 867840 Rate: 617.71 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 357.81 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 251.70 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 194.13 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 157.99 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 133.20 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 115.13 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 101.38 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 90.56 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 81.83 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 74.63 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 68.60 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 63.47 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 59.05 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 55.21 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 51.84 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 48.86 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 46.20 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 43.81 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 41.66 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 39.71 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 37.94 Kb/Sec ... Full: 0 Read: 869104 Written: 869104 Rate: 0.74 Kb/Sec so as u can see, the transfer is going lower and lower so the backup operation couldn't finish proper. all the time it stops on database model (msdb). manualy i can backup it without any problems. what's wrong? have u seen similar problem? p.s. oh i almoust forget - i'm using storageagent in version 5.1.7.0. this database server is connected to the san. -Wiadomo oryginalna- Od: alkina [mailto:[EMAIL PROTECTED] Wysano: 29 paYdziernika 2003 10:44 Do: [EMAIL PROTECTED] Temat: Re: TDP for MSSQL - huge problem In dsmserv.opt increase the value of two parameters 1. commtimeout 3000 2. idletimeout some suitable value. Regards Alkina L ADSM: Dist Stor Manager wrote: gt;4 more than one week I've been receiving the error code listed below during gt;my night backup process on MS SQL 7 (NT 4.0): gt; gt;28-10-2003 07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. gt;Return code = -1073741510. gt;28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket = 1320, errno = gt;10054, reason : 'Unknown error'. gt;28-10-2003 07:58:45 ANS1005E TCP/IP read error on socket = 656, errno = gt;10054, reason : 'Unknown error'. gt; gt;The scheduled backup completes just few databases but always stop on msdb. gt;The problem doesn't occur when I start up backup manualy. gt;Yesterday I upgraded the TDP client to the latest 5.2.1 version. It didn't gt;solve this problem. gt;What can I do next? Have u evere had similar problem? gt;Waitin' for some suggestion from ya wizards:-) Sebastian - The 10054 TCP/IP errno reflects a connection being reset by peer, which in TSM terms means that the server terminated the session with the client. Thus, the place to look is in the server Activity Log, which should explain why it did so. It may be that server timeout values are too low. Richard Sims, BU Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets on Air Sahara Flights. For Best Deals, log on to http://airsahara.indiatimes.com and Bid Now !
Re: AW: delete filespace takes 24hours
Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 09:31:25 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes 24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
AW: AW: delete filespace takes 24hours
what means an o.k. expiration performance? why should it go faster to delete volumes(in 3 pools)? thanks joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 11:21 An: [EMAIL PROTECTED] Betreff: Re: AW: delete filespace takes 24hours Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 09:31:25 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes 24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
backupsetcontents
Hello, we use TSM Server 4.2.2.0 on Windows NT. We created a backupset on LTO Volume. When we try to query the contents of this backupset (q backupsetcontents) the operation takes up to 24 hours. Is this normal for a query? We know that the information is read from the tape, but such a long time for it? Who can help or give me some inputs? Mit freundlichen Grüßen Sascha Bräuning DB/DC C/S-Systeme/Überwachungsverfahren FE/KA Sparkassen Informatik GmbH Co.KG Wilhelm-Pfitzer-Straße 1 70736 Fellbach Telefon: 0711/5722-2144 Telefax: 0711/5722-2147 Notes: Sascha Bräuning/6322/FE/SI/[EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED]
Re: AW: AW: delete filespace takes 24hours
Just trying a few ideas. An ok expiration performance is one that you are happy with, so would be a lot less than 24 hours (say under 4 hours) The discard data with the volumes was just a thought, that maybe your database was nearly full, so did not have enough free space to build up the table for the full 160,000 delete You did not provide database statistics Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 10:54:02 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: AW: delete filespace takes 24hours what means an o.k. expiration performance? why should it go faster to delete volumes(in 3 pools)? thanks joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 11:21 An: [EMAIL PROTECTED] Betreff: Re: AW: delete filespace takes 24hours Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 09:31:25 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes 24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
AW: AW: AW: delete filespace takes 24hours
yes on this TSM server runs the expire about 5 hours, the database should have enough space q db f=d: Available Space (MB): 20,784 Assigned Capacity (MB): 20,784 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,644 Page Size (bytes): 4,096 Total Usable Pages: 5,320,704 Used Pages: 3,536,071 Pct Util: 66.5 Max. Pct Util: 67.1 Physical Volumes: 34 Buffer Pool Pages: 24,576 Total Buffer Requests: 349,306,341 Cache Hit Pct.: 98.03 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 1,119.86 Percentage Changed: 8.11 Last Complete Backup Date/Time: 28.10.2003 16:08:19 thank you and regards joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 12:42 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: delete filespace takes 24hours Just trying a few ideas. An ok expiration performance is one that you are happy with, so would be a lot less than 24 hours (say under 4 hours) The discard data with the volumes was just a thought, that maybe your database was nearly full, so did not have enough free space to build up the table for the full 160,000 delete You did not provide database statistics Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 10:54:02 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: AW: delete filespace takes 24hours what means an o.k. expiration performance? why should it go faster to delete volumes(in 3 pools)? thanks joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 11:21 An: [EMAIL PROTECTED] Betreff: Re: AW: delete filespace takes 24hours Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 09:31:25 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes 24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group.
Re: AW: AW: AW: delete filespace takes 24hours
Joachim, Not sure where to look further. I do think your cache hit rate is a bit low. My database statistics show Available Space (MB): 27,936 Assigned Capacity (MB): 27,936 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,064 Page Size (bytes): 4,096 Total Usable Pages: 7,151,616 Used Pages: 5,453,023 Pct Util: 76.2 Max. Pct Util: 77.1 Physical Volumes: 24 Buffer Pool Pages: 12,288 Total Buffer Requests: 112,683,745 Cache Hit Pct.: 99.06 This was after running expiration in 4 hours 50 minutes which deleted q uite a lot of objests ANR0812I Inventory file expiration process 3 completed: examined 3750451 objects, deleting 415022 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. My region size is 768 mb. but my bufferpool is only half as big with a larger database. There was a thread about bufferpool and region sizes a while ago, which might be worth looking at. Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 11:54:30 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: AW: AW: delete filespace takes 24hours yes on this TSM server runs the expire about 5 hours, the database should have enough space q db f=d: Available Space (MB): 20,784 Assigned Capacity (MB): 20,784 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,644 Page Size (bytes): 4,096 Total Usable Pages: 5,320,704 Used Pages: 3,536,071 Pct Util: 66.5 Max. Pct Util: 67.1 Physical Volumes: 34 Buffer Pool Pages: 24,576 Total Buffer Requests: 349,306,341 Cache Hit Pct.: 98.03 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 1,119.86 Percentage Changed: 8.11 Last Complete Backup Date/Time: 28.10.2003 16:08:19 thank you and regards joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 12:42 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: delete filespace takes 24hours Just trying a few ideas. An ok expiration performance is one that you are happy with, so would be a lot less than 24 hours (say under 4 hours) The discard data with the volumes was just a thought, that maybe your database was nearly full, so did not have enough free space to build up the table for the full 160,000 delete You did not provide database statistics Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 10:54:02 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: AW: delete filespace takes 24hours what means an o.k. expiration performance? why should it go faster to delete volumes(in 3 pools)? thanks joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 11:21 An: [EMAIL PROTECTED] Betreff: Re: AW: delete filespace takes 24hours Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 09:31:25 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes 24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: delete filespace takes 24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 16 Files in size. How work the TSM DB? One select, one commit, one select one commit? If
Re: TDP for MSSQL - huge problem
Hi,
Let's first start from simple principles.
Open up query analyzer, login as an account with sa privs and run the
following:
Dbcc checkdb ('msdb')
Note any errors and repair them. Then try a to disk backup of the msdb
database. If both of these are fine, it is a tsm problem, but it just
sounds like database corruption to me.
Michael Wheelock
Integris Health of Oklahoam
-Original Message-
From: Sebastian Szumczyk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 4:22 AM
To: [EMAIL PROTECTED]
Subject: ODP: TDP for MSSQL - huge problem
Hi folks,
current vaules for commtimeout and idletimout are 1200 and 180. i don't
think that increasing these vaules solve my problem. maybe it will stop
writing in logs that kind of errors but please remember that i cannot backup
up my whole database (ms sql) environment. log for that operation (for
scheduled operations only) looks like that :
Beginning full backup for database model, 13 of 21.
Full: 0 Read: 867840 Written: 867840 Rate: 617.71 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 357.81 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 251.70 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 194.13 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 157.99 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 133.20 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 115.13 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 101.38 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 90.56 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 81.83 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 74.63 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 68.60 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 63.47 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 59.05 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 55.21 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 51.84 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 48.86 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 46.20 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 43.81 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 41.66 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 39.71 Kb/Sec
Full: 0 Read: 869104 Written: 869104 Rate: 37.94 Kb/Sec
...
Full: 0 Read: 869104 Written: 869104 Rate: 0.74 Kb/Sec
so as u can see, the transfer is going lower and lower so the backup
operation couldn't finish proper. all the time it stops on database model
(msdb). manualy i can backup it without any problems. what's wrong? have u
seen similar problem? p.s. oh i almoust forget - i'm using storageagent in
version 5.1.7.0. this database server is connected to the san.
-Wiadomo oryginalna-
Od: alkina [mailto:[EMAIL PROTECTED]
Wysano: 29 paYdziernika 2003 10:44
Do: [EMAIL PROTECTED]
Temat: Re: TDP for MSSQL - huge problem
In dsmserv.opt increase the value of two parameters
1. commtimeout 3000
2. idletimeout some suitable value.
Regards
Alkina L
ADSM: Dist Stor Manager wrote:
gt;4 more than one week I've been receiving the error code listed below
during gt;my night backup process on MS SQL 7 (NT 4.0): gt; gt;28-10-2003
07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. gt;Return code
= -1073741510. gt;28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket
= 1320, errno = gt;10054, reason : 'Unknown error'. gt;28-10-2003 07:58:45
ANS1005E TCP/IP read error on socket = 656, errno = gt;10054, reason :
'Unknown error'. gt; gt;The scheduled backup completes just few databases
but always stop on msdb. gt;The problem doesn't occur when I start up
backup manualy. gt;Yesterday I upgraded the TDP client to the latest 5.2.1
version. It didn't gt;solve this problem. gt;What can I do next? Have u
evere had similar problem? gt;Waitin' for some suggestion from ya
wizards:-)
Sebastian - The 10054 TCP/IP errno reflects a connection being reset by
peer, which in TSM terms means that the server terminated the session with
the client. Thus, the place to look is in the server Activity Log, which
should explain why it did so. It may be that server timeout values are too
low.
Richard Sims, BU
Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com
Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
Bid for Air Tickets on Air Sahara Flights. For Best Deals, log on to
http://airsahara.indiatimes.com and Bid Now !
This e-mail may contain identifiable health information that is subject to protection
under state and federal law. This information is intended to be for the use of the
individual named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this information is
prohibited
and may be punishable by law. If you have received this electronic
Re: ODP: TDP for MSSQL - huge problem
Sebastian, We have seen a hang like this recently when service has been applied to the operating system. The fix for this has been to apply and/or reapply the latest service packs to SQL Server. In most cases, this has been to apply SP3 or SP3a to SQL Server 2000. I see that you are on NT4 and SQL 7. So, you should make sure the latest service packs are applied to the NT 4 and to the SQL 7 Server. If the problem still persists after doing so, please call IBM support. Thanks, Del current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that :
TSM 5.2 Sun Solaris - Language Format problems.!??!!!
Had TSM 5.1 installed with no problems in this environment before. Using Solaris 8, and TSM 5.2 Upon installing the TSM 5.2 server code I get the following errors: Error opening catalog /opt/tivoli/tsm/server/bin/dsm/en_IE.ISO8859-15/en_IE.ISO8 859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/C.cat, for language /e n_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859 -15/C ANR0915E Unable to open language /EN_IE.ISO8859-15/EN_IE.ISO8859-15/EN_IE.ISO8 8859-15/EN_IE.ISO8859-15/EN_IE.ISO8859-15/C for message formatting. I assumed that these would just be warning errors, but after using DSMFMT to format my database and log volumes I cannot use the DSMSERV FORMAT commant as it comes back with a message saying that the format parameters are missing!!!??!!! Anyone else having this problem? I'm using: DSMSERV FORMAT 1 /opt/tivoli/tsm/server/bin/log1.dsm 1 /opt.tivoli/tsm/server/bin/db1.dsm The DSMFMT command was tried first, but no joy. Is the error in relation to the language the one causing the problems? if so, I'm gonna have a problem as the locale on all these servers has to stay EN_IE (Irish). Anyone? Maybe one for the SUN gurus! R.
Re: ODP: TDP for MSSQL - huge problem
Hi Del, any ideas as to what gets fixed by reapplying the SP? I am trying to see if there's anything else we need to fix after installing TDP. Thanks, yi [EMAIL PROTECTED] 10/29/03 08:39AM Sebastian, We have seen a hang like this recently when service has been applied to the operating system. The fix for this has been to apply and/or reapply the latest service packs to SQL Server. In most cases, this has been to apply SP3 or SP3a to SQL Server 2000. I see that you are on NT4 and SQL 7. So, you should make sure the latest service packs are applied to the NT 4 and to the SQL 7 Server. If the problem still persists after doing so, please call IBM support. Thanks, Del current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that :
Re: TSM 5.2 Sun Solaris - Language Format problems.!??!!!
On Wed, 29 Oct 2003 12:21:51 + Rowan O'Donoghue [EMAIL PROTECTED] wrote: Had TSM 5.1 installed with no problems in this environment before. Using Solaris 8, and TSM 5.2 Upon installing the TSM 5.2 server code I get the following errors: Error opening catalog /opt/tivoli/tsm/server/bin/dsm/en_IE.ISO8859-15/en_IE.ISO8 859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/C.cat, for language /e n_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/en_IE.ISO8859-15/en_IE. ISO8859-15/C ANR0915E Unable to open language /EN_IE.ISO8859-15/EN_IE.ISO8859-15/EN_IE.ISO8 8859-15/EN_IE.ISO8859-15/EN_IE.ISO8859-15/C for message formatting. I assumed that these would just be warning errors, but after using DSMFMT to format my database and log volumes I cannot use the DSMSERV FORMAT commant as it comes back with a message saying that the format parameters are missing!!!??!!! Anyone else having this problem? I'm using: DSMSERV FORMAT 1 /opt/tivoli/tsm/server/bin/log1.dsm 1 /opt.tivoli/tsm/server/bin/db1.dsm The DSMFMT command was tried first, but no joy. Is the error in relation to the language the one causing the problems? if so, I'm gonna have a problem as the locale on all these servers has to stay EN_IE (Irish). Anyone? Maybe one for the SUN gurus! R. Did you install the irisch language options with the TSM server? -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
delete filespace takes 24hours
Thank you John we have 3 times more buffereqests? with a smaller bufferpool i had less cache hits! Regards Joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 14:15 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: AW: delete filespace takes 24hours Joachim, Not sure where to look further. I do think your cache hit rate is a bit low. My database statistics show Available Space (MB): 27,936 Assigned Capacity (MB): 27,936 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,064 Page Size (bytes): 4,096 Total Usable Pages: 7,151,616 Used Pages: 5,453,023 Pct Util: 76.2 Max. Pct Util: 77.1 Physical Volumes: 24 Buffer Pool Pages: 12,288 Total Buffer Requests: 112,683,745 Cache Hit Pct.: 99.06 This was after running expiration in 4 hours 50 minutes which deleted q uite a lot of objests ANR0812I Inventory file expiration process 3 completed: examined 3750451 objects, deleting 415022 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. My region size is 768 mb. but my bufferpool is only half as big with a larger database. There was a thread about bufferpool and region sizes a while ago, which might be worth looking at. Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 11:54:30 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: AW: AW: delete filespace takes 24hours yes on this TSM server runs the expire about 5 hours, the database should have enough space q db f=d: Available Space (MB): 20,784 Assigned Capacity (MB): 20,784 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,644 Page Size (bytes): 4,096 Total Usable Pages: 5,320,704 Used Pages: 3,536,071 Pct Util: 66.5 Max. Pct Util: 67.1 Physical Volumes: 34 Buffer Pool Pages: 24,576 Total Buffer Requests: 349,306,341 Cache Hit Pct.: 98.03 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 1,119.86 Percentage Changed: 8.11 Last Complete Backup Date/Time: 28.10.2003 16:08:19 thank you and regards joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 12:42 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: delete filespace takes 24hours Just trying a few ideas. An ok expiration performance is one that you are happy with, so would be a lot less than 24 hours (say under 4 hours) The discard data with the volumes was just a thought, that maybe your database was nearly full, so did not have enough free space to build up the table for the full 160,000 delete You did not provide database statistics Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 10:54:02 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: AW: delete filespace takes 24hours what means an o.k. expiration performance? why should it go faster to delete volumes(in 3 pools)? thanks joachim -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 11:21 An: [EMAIL PROTECTED] Betreff: Re: AW: delete filespace takes 24hours Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 09:31:25 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes 24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is 98.5% ! -Ursprüngliche Nachricht- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes 24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 08:52:53 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM:
Re: offsite tapes 'reclamation'
And the TSM Admin Guide can be found online at http://publib.boulder.ibm.com/tividd/td/tdprodlist.html#S David Ehresman [EMAIL PROTECTED] 10/29/2003 2:19:45 AM Hi, I suggest reading this chapter from the Administrator's Guide: Reclaiming Space in Sequential Access Storage Pools Especially these parts: Reclamation for Copy Storage Pools and Reclamation of Offsite Volumes. Regards, Imre -Original Message- From: Hegedus György [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 9:54 PM To: [EMAIL PROTECTED] Subject: offsite tapes 'reclamation' Hi All, I would like to copy the primary storage pools to a copy storage pool, then take the tapes offsite. The 'backup stgpool' command make incremental backups, so every day I should take some tapes offsite. And will be more and more offsite tapes. How can I initiate the reclamation process? Should I take back all tapes to the library? I have no idea. What should I do? Could you help me? Regards, Gyorgy Hegedus Megatrend 2000 Rt.
ODP: ODP: TDP for MSSQL - huge problem
Del, so why manual start backup process finished proper? by the way i have got all latest sp's applied. -Wiadomo oryginalna- Od: Del Hoobler [mailto:[EMAIL PROTECTED] Wysano: 29 paYdziernika 2003 14:40 Do: [EMAIL PROTECTED] Temat: Re: ODP: TDP for MSSQL - huge problem Sebastian, We have seen a hang like this recently when service has been applied to the operating system. The fix for this has been to apply and/or reapply the latest service packs to SQL Server. In most cases, this has been to apply SP3 or SP3a to SQL Server 2000. I see that you are on NT4 and SQL 7. So, you should make sure the latest service packs are applied to the NT 4 and to the SQL 7 Server. If the problem still persists after doing so, please call IBM support. Thanks, Del current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that :
Re: ODP: TDP for MSSQL - huge problem
yi, Microsoft has not yet been able to identify for us what was changed that caused this. IBM support is still working with Microsoft to try to identify specifically why this was happening. It seems that after (re)applying the latest service packs, this problem is resolved. And for most customers, they are so busy, after the problem is resolved, they no longer wish to spend more time on it. I can't blame them. I have some suspicions that it could be related to some of the security hotfixes put out lately by Microsoft... ... but can't confirm it yet. If you see any problems, please call support. Thanks, Del any ideas as to what gets fixed by reapplying the SP? I am trying to see if there's anything else we need to fix after installing TDP.
Re: ODP: ODP: TDP for MSSQL - huge problem
Sebastian, I don't know for sure. I haven't seen the configuration of your system. It could have something to do with the default network path connection to the SQL server... which may be different when running from a different userid... if you have set it up that way on your system. Maybe it uses pipes in one case and TCP/IP in another. I really think the best way for you to get this resolved is to place a call with IBM support. It is very difficult to solve something like this without getting more details about your setup and configuration. Thanks, Del so why manual start backup process finished proper? by the way i have got all latest sp's applied.
Re: ODP: TDP for MSSQL - huge problem
Thanks Del, that's good enough answer for me. Yi [EMAIL PROTECTED] 10/29/03 09:10AM yi, Microsoft has not yet been able to identify for us what was changed that caused this. IBM support is still working with Microsoft to try to identify specifically why this was happening. It seems that after (re)applying the latest service packs, this problem is resolved. And for most customers, they are so busy, after the problem is resolved, they no longer wish to spend more time on it. I can't blame them. I have some suspicions that it could be related to some of the security hotfixes put out lately by Microsoft... ... but can't confirm it yet. If you see any problems, please call support. Thanks, Del any ideas as to what gets fixed by reapplying the SP? I am trying to see if there's anything else we need to fix after installing TDP.
ODP: ODP: ODP: TDP for MSSQL - huge problem
Del - u're completely right that it's very difficult to solve this problem in the way i'm trying to do it. But this list is the best knowledge base I have ever seen. So that's why I'm trying to ask u guys about problems I have just seen. by the way below is result of dbcc checkdb : CHECKDB found 0 allocation errors and 0 consistency errors in database 'msdb'. According to Richard recomendation I have changed COMMtimeout values. we will see thanks for all the replies. sebastian -Wiadomo oryginalna- Od: Del Hoobler [mailto:[EMAIL PROTECTED] Wysano: 29 paYdziernika 2003 15:17 Do: [EMAIL PROTECTED] Temat: Re: ODP: ODP: TDP for MSSQL - huge problem Sebastian, I don't know for sure. I haven't seen the configuration of your system. It could have something to do with the default network path connection to the SQL server... which may be different when running from a different userid... if you have set it up that way on your system. Maybe it uses pipes in one case and TCP/IP in another. I really think the best way for you to get this resolved is to place a call with IBM support. It is very difficult to solve something like this without getting more details about your setup and configuration. Thanks, Del so why manual start backup process finished proper? by the way i have got all latest sp's applied.
High Number of Storage Agent Sessions
We have the following environment: 5.1.6.2 TSM Server 5.1.6.2 Storage Agents 5.1.6 BA Clients There are a high number of storage agent idle sessions on the TSM Server. This didn't exist in the 5.1.1 environment. Wondering if someone can point me to the solution for resolving this. Thomas L. Fought (E-mail).vcf Thomas L. Fought (E-mail).vcf Description: Binary data
Re: delete filespace takes 24hours
On Wed, 29 Oct 2003 15:00:02 +0100 Schaub Joachim Paul ABX-SECE-ZH [EMAIL PROTECTED] wrote: Thank you John we have 3 times more buffereqests? with a smaller bufferpool i had less cache hits! Regards Joachim Total buffer requests means shit.. this is like an uptime counter... it wraps every so many days (1.5 in my case iirc) -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: delete filespace takes 24hours
Gosh, That's the first four letter word I've seen on this list for a long time. Excuse me whilst I blush and faint from shock... ;o) David McClelland Global Management Systems Reuters Ltd, London -Original Message- From: Remco Post [mailto:[EMAIL PROTECTED] Sent: 29 October 2003 14:52 To: [EMAIL PROTECTED] Subject: Re: delete filespace takes 24hours Joachim Total buffer requests means shit.. this is like an uptime counter... it wraps every so many days (1.5 in my case iirc) -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams - Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
Re: delete filespace takes 24hours
David, you must have led a sheltered life gosh is pretty mild where I come from David McClelland [EMAIL PROTECTED]@vm.marist.edu on 10/29/2003 03:15:54 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: delete filespace takes 24hours Gosh, That's the first four letter word I've seen on this list for a long time. Excuse me whilst I blush and faint from shock... ;o) David McClelland Global Management Systems Reuters Ltd, London -Original Message- From: Remco Post [mailto:[EMAIL PROTECTED] Sent: 29 October 2003 14:52 To: [EMAIL PROTECTED] Subject: Re: delete filespace takes 24hours Joachim Total buffer requests means shit.. this is like an uptime counter... it wraps every so many days (1.5 in my case iirc) -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams - Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Domino backups going to wrong storagepool
Back a while ago, when we first started doing Domino TDP backups, due to lack of disk space, the backups were directed straight to tape. Since then, lots of SSA disk (can we say CHEAP.) was added and I changed the management classes to point to the new disk storage pool. However, the backups are still going to tape. I see lots of sessions waiting for MEDIA. What gives ? Does Domino remember where it was going and keeps going there ? ALL of the backupcopygroups for this policy set/domain point to the disk storage pool. Del, your thoughts on this ?
Re: Domino backups going to wrong storagepool
On Wed, 29 Oct 2003 11:13:16 -0500 Zoltan Forray/AC/VCU [EMAIL PROTECTED] wrote: Back a while ago, when we first started doing Domino TDP backups, due to lack of disk space, the backups were directed straight to tape. Since then, lots of SSA disk (can we say CHEAP.) was added and I changed the management classes to point to the new disk storage pool. However, the backups are still going to tape. I see lots of sessions waiting for MEDIA. What gives ? Does Domino remember where it was going and keeps going there ? ALL of the backupcopygroups for this policy set/domain point to the disk storage pool. Del, your thoughts on this ? maxsize settings? -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
help needed desperately - reinstall TSM client v5.1
Hi, I am a newbie here. Just join the list and sent the message but didn't shown on the list. (must have done wrong) I am sending it again. University TSM server was updated to 5.1.6 several months ago, I noticed about a month ago that our client v4.2 didn't work right.(Don't really know how long it had been malfunctioning, log file was overwritten.) The dsmsched.log message is Sending of object '\\imlab-win\appleshare' failed 10/23/2003 13:03:40 ANS1063E Invalid path specification 10/23/2003 13:03:40 ANS1228E Sending of object '\\imlab-win\wwwroot' failed 10/23/2003 13:03:40 ANS1063E Invalid path specification 10/23/2003 13:03:44 Scheduled event '1300' completed successfully. We could not figure what was wrong. and decided to upgrade the client. I am upgrading the TSM client from 4.2 to 5.2. As recommended in the README file, I stopped the scheduler from the system. Then removed the scheduler through TSM utility menu. And then uninstalled the old version of TSM from control panel, add/remove program panel. Then downloaded new version. The installShield Wizard was interrupted and installation failed. the message I got is as follows: The wizard was interrupted before Tivoli could be completely installed. your system has not been modified. To complete installation at another time I also tried to run the setup after I disable the firewall. It failed with the same message. Does anyone known what was wrong? Is there anything(component) else that I need to remove before installation? Thanks in advance for any advice! Lan Lan Wu-Cavener PennState
Re: Domino backups going to wrong storagepool
Did you update the management class (and activate the policy domain in question)? Ted At 11:13 AM 10/29/2003 -0500, you wrote: Back a while ago, when we first started doing Domino TDP backups, due to lack of disk space, the backups were directed straight to tape. Since then, lots of SSA disk (can we say CHEAP.) was added and I changed the management classes to point to the new disk storage pool. However, the backups are still going to tape. I see lots of sessions waiting for MEDIA. What gives ? Does Domino remember where it was going and keeps going there ? ALL of the backupcopygroups for this policy set/domain point to the disk storage pool. Del, your thoughts on this ?
Re: Domino backups going to wrong storagepool
... ALL of the backupcopygroups for this policy set/domain point to the disk storage pool. Just be sure that the Active policy set reflects this, not just the named policy sets, which is to say that Activate Policyset would have needed to be done. Richard Sims, BU
Re: Remove disk pool volume, it won't die!!
Mike - I had this happen many years and releases ago when I was moving the diskpool from one device to another. I got rid of the problem volumes by doing a restore volume on them; of course this assumes you are using copypools. Do 'restore v volume_name preview=yes' and get the tapes back from offsite. Mark the tapes onsite and do the restore without preview=yes. When the restore is done tsm will delete the volume. At least that is how it worked for me. Bill Colwell At 03:29 PM 10/22/2003, you wrote: I run TSM 4.2 on Solaris 8. I was in the process of converting all of the diskpool volumes from OS mounted files to raw partitions to fix some performance issues we have been experiencing with backups when I hit a little problem. I disabled sessions and allowed migration to run to completion. All volumes in the diskpool were listed at 0% util. I was able to delete all volumes except 1, it claimed there was still data in it. Still showed 0% for the volume doing a q vol, but I ran an audit on the volume, it said that there was no data in it. I restarted the server, still claimed there was data in there. I tried del vol /tsmdata1/data1 discardd=yes, no effect, guess that option does not work for devices of type DISK? Now comes the point where I did something I probably shouldn't have. I stopped TSM again, deleted the file at the OS level, unmounted the partition, restarted TSM, and defined this last volume using the raw partition (others I had already done). This all worked fine, but I still have this dangling volume that it of course can't mount so it's offline.Still getting ANS8001I Return code 13 when I try to delete the volume. Log says: 10/22/03 20:26:51 ANR2406E DELETE VOLUME: Volume /tsmdata4/data1 still contains data. Any suggestions on how I can nuke this volume once and for all. I realize I might have lost a few files if this volume did in fact contain some data, but I am not that concerned abou that right now. Thanks! Michael French Savvis Communications IDS01 Santa Clara, CA (408)450-7812 -- desk (408)239-9913 -- mobile -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Re: Domino backups going to wrong storagepool
Zoltan, I think Remco, Richard, and Ted probably covered the things that could be wrong... if not.. let me know. Thanks, Del Back a while ago, when we first started doing Domino TDP backups, due to lack of disk space, the backups were directed straight to tape. Since then, lots of SSA disk (can we say CHEAP.) was added and I changed the management classes to point to the new disk storage pool. However, the backups are still going to tape. I see lots of sessions waiting for MEDIA. What gives ? Does Domino remember where it was going and keeps going there ? ALL of the backupcopygroups for this policy set/domain point to the disk storage pool. Del, your thoughts on this ?
Re: High Number of Storage Agent Sessions
Hi Tom, sounds like the issue described in APAR IC36510. The problem appears also on the STA's side and should be fixed in 5.1.8.0. Best regards, Wolfgang Bayrhof - Original Message - From: Fought,Tom [EMAIL PROTECTED] Date: Wed, 29 Oct 2003 09:31:25 -0500 To: [EMAIL PROTECTED] Subject: High Number of Storage Agent Sessions We have the following environment: 5.1.6.2 TSM Server 5.1.6.2 Storage Agents 5.1.6 BA Clients There are a high number of storage agent idle sessions on the TSM Server. This didn't exist in the 5.1.1 environment. Wondering if someone can point me to the solution for resolving this. Thomas L. Fought (E-mail).vcf Thomas L. Fought (E-mail).vcf
Re: delete filespace takes 24hours
From: Remco Post [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Total buffer requests means shit.. this is like an uptime counter... it wraps every so many days (1.5 in my case iirc) From: David McClelland [mailto:[EMAIL PROTECTED] Gosh, That's the first four letter word I've seen on this list for a long time. Excuse me whilst I blush and faint from shock... Well, you know those excitable Dutch... -- Mark Stapleton ([EMAIL PROTECTED])
Re: RESET PASSEXP (for a node)?
Did anyone find a way to clear a client node's PASSwordEXPiration time (once it's inadvertently set by some admin), so as to re-establish the server-wide default value? A commands like the following doesn't work for me: UPDATE NODE ... PASSEXP= You can choose between two things: reset passexp node=... This will clear the node-specific password expiration flag, and the common password expiration period (set using 'set passexp') will take effect for the node (which is what you want). Or: update node ... passexp=0 This will mean that the node's password never expires, regardless of what the global password expiration period is. ((And while on the topic of undocumented [line-mode] commands - does FLUSH LOG, which I once entered in despair, have any useful purpose? Be careful ... :-()) Very good question, I'd also like to know the answer to that one :-) Cheers Dmitri
