Re: 6.3.3.000 server wont HALT
This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: 6.3.3.000 server wont HALT
Have you tried a -console session prior to issuing halt? Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, December 03, 2012 7:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 6.3.3.000 server wont HALT This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person.
Re: 6.3.3.000 server wont HALT
Not sure what you mean by console session. I use TSMManager and issue the halt via it's console/monitor window, if that is what you are referring to - and yes, it shows the halt is issued and then the server goes non-responsive, as suspected. Then from ssh/Linux the process dsmserv never halts/stops. On Mon, Dec 3, 2012 at 9:00 AM, Schneider, Jim jschnei...@ussco.com wrote: Have you tried a -console session prior to issuing halt? Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, December 03, 2012 7:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 6.3.3.000 server wont HALT This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: 6.3.3.000 server wont HALT
Hi Zoltan, Looks like we have one or two other customers reporting this. My recommendation would be for you to open a PMR. Optionally, if you want to be as pro-active as possible, perform the following steps in advance (this is the current set of doc being requested for this issue): 1. Stop TSM, kill if necessary. 2. Start dsmserv in the foreground. 3. Wait for TSM to come completely up. 4. In the TSM server console, enable tracing by issuing: trace enable ADM DB THREAD TM ADDMSG trace begin /tmp/tsmhalttrace.out (for the trace begin command, specify whatever directory and trace file name if you want) 5. Issue the HALT command on the TSM server console 6. Wait 10 minutes. 7. Open a root terminal on the system where TSM is running and issue the following commands (and save the output): ps -ef | grep dsmserv ps -ef | grep db2 8. Locate the process ID (PID) for dsmserv AND db2sysc from the ps output. 9. Issue the pstack command against the dsmserv PID and save the output, e.g.: $ procstack 1234 10. Issue the pstack command against the db2sysc PID and save the output, e.g.: $ procstack 1235 10. Wait 10 minutes. 11. Repeat steps 7, 8, 9, and 10. Save the output. 13. Repeat steps 7, 8, 9, and 10 again, saving the output. 14. Copy and save all of the on-screen output from the TSM console. 15. Restart TSM. 16. Login as instance owner, issue db2support -d tsmdb1 -c -g -s, save the db2support.zip generated Once you have the PMR created, you can send in the doc that you collected: 1.The TSM server console output 2. The TSM server trace file 3. The three iterations of the ps output 4. The three iterations of pstack output against dsmserv 5. The three iterations of pstack output against db2sysc 6. The db2support.zip file Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2012-12-03 08:45:17: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2012-12-03 08:55 Subject: Re: 6.3.3.000 server wont HALT Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Stable Version of TSM 6
Charles, Generally speaking version 6.x is stable, the sweet spot for me is 6.3.2. When you debate between Windows vs. AIX I would consider anticipated workload. My servers run Win2008-r2 (x64) and handle 250-300 clients each comfortably. IMHO, just as critical as the platform you select is the underlying hardware (disks, NIC, memory, CPU). Opt for the fastest disks you can afford and pad the memory recommendations for an optimal system. Also, spreading the DB2 database and logs across dedicated LUNS is a must for good performance. In reference to question #2 and VM's I am testing it now for DR and should be able to provide details in a week or two if you're interested. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Welton, Charles Sent: Friday, November 30, 2012 7:35 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Stable Version of TSM 6 Hello: I have a few questions about TSM 6. # 1: Is there a STABLE version of 6 that would be recommended? Right now, we are running TSM at version 5.5.2.0, but we are thinking about upgrading. I am not interested in getting to the latest and greatest version. I am interested in getting to a supported, stable version. # 2: Based on the recommendation in question # 1, can we run that version of TSM 6 on Windows? What about a VM? Thank you... Charles This email contains information which may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE and is intended only for the use of the addresses(s) named above. If you have received this email in error, please contact the sender immediately.
Re: 6.3.3.000 server wont HALT
Thanks Andy. Glad to know I am not the only one. Will collect the info and open a PMR. Just another reason they call it the bleeding edge ;--) On Mon, Dec 3, 2012 at 9:34 AM, Andrew Raibeck stor...@us.ibm.com wrote: Hi Zoltan, Looks like we have one or two other customers reporting this. My recommendation would be for you to open a PMR. Optionally, if you want to be as pro-active as possible, perform the following steps in advance (this is the current set of doc being requested for this issue): 1. Stop TSM, kill if necessary. 2. Start dsmserv in the foreground. 3. Wait for TSM to come completely up. 4. In the TSM server console, enable tracing by issuing: trace enable ADM DB THREAD TM ADDMSG trace begin /tmp/tsmhalttrace.out (for the trace begin command, specify whatever directory and trace file name if you want) 5. Issue the HALT command on the TSM server console 6. Wait 10 minutes. 7. Open a root terminal on the system where TSM is running and issue the following commands (and save the output): ps -ef | grep dsmserv ps -ef | grep db2 8. Locate the process ID (PID) for dsmserv AND db2sysc from the ps output. 9. Issue the pstack command against the dsmserv PID and save the output, e.g.: $ procstack 1234 10. Issue the pstack command against the db2sysc PID and save the output, e.g.: $ procstack 1235 10. Wait 10 minutes. 11. Repeat steps 7, 8, 9, and 10. Save the output. 13. Repeat steps 7, 8, 9, and 10 again, saving the output. 14. Copy and save all of the on-screen output from the TSM console. 15. Restart TSM. 16. Login as instance owner, issue db2support -d tsmdb1 -c -g -s, save the db2support.zip generated Once you have the PMR created, you can send in the doc that you collected: 1.The TSM server console output 2. The TSM server trace file 3. The three iterations of the ps output 4. The three iterations of pstack output against dsmserv 5. The three iterations of pstack output against db2sysc 6. The db2support.zip file Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2012-12-03 08:45:17: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2012-12-03 08:55 Subject: Re: 6.3.3.000 server wont HALT Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software
Re: Stable Version of TSM 6
Anyone running TSM 6.4 in production? How does it look? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Saturday, December 01, 2012 11:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Stable Version of TSM 6 # 1: Is there a STABLE version of 6 that would be recommended? Right now, we are running TSM at version 5.5.2.0, but we are thinking about upgrading. I am not interested in getting to the latest and greatest version. I am interested in getting to a supported, stable version. Ive got several customers running 6.3.2 on AIX and Windows. Some were done as new servers, some as upgrades, no difference. I have been very impressed with stability. Really. # 2: Based on the recommendation in question # 1, can we run that version of TSM 6 on Windows? Sure. But: a) make sure you have the recommended quality of hardware (For example, RAM requirements are much higher for V6 than V5. Check the web site for recommendations) b) you can't convert from one platform to the other as part of upgrading a 5.5 DB, so if you're upgrading the server you have, it will be on the same platform. c) whether you choose Windows as your platform for a new server, depends on how much I/O you have to move per day, can you get enough HBA's in the box, etc. I've got no problems with somebody asking me to move 5-8 TB per day on say, a relatively new Windows box, at least 4 cores, Win2K8 64, 32G RAM, good disk array. More than that, I question whether Windows is suitable. Everybody else on this list will have their own opinions about that. #2a: What about a VM? TSM server is not supported as a Windows VM (VMware or the MS equivalent) if there are tape drivers involved. That means if you are doing all disk backups, it's supported. If you have physical tape or a VTL attached, the answer is no. Hope that helps! W
Re: 6.3.3.000 server wont HALT
Can anyone say whether this problem is limited to Linux, or does it exhibit itself on other server platforms? Thanks. At 09:34 AM 12/3/2012, Andrew Raibeck wrote: Hi Zoltan, Looks like we have one or two other customers reporting this. My recommendation would be for you to open a PMR. Optionally, if you want to be as pro-active as possible, perform the following steps in advance (this is the current set of doc being requested for this issue): 1. Stop TSM, kill if necessary. 2. Start dsmserv in the foreground. 3. Wait for TSM to come completely up. 4. In the TSM server console, enable tracing by issuing: trace enable ADM DB THREAD TM ADDMSG trace begin /tmp/tsmhalttrace.out (for the trace begin command, specify whatever directory and trace file name if you want) 5. Issue the HALT command on the TSM server console 6. Wait 10 minutes. 7. Open a root terminal on the system where TSM is running and issue the following commands (and save the output): ps -ef | grep dsmserv ps -ef | grep db2 8. Locate the process ID (PID) for dsmserv AND db2sysc from the ps output. 9. Issue the pstack command against the dsmserv PID and save the output, e.g.: $ procstack 1234 10. Issue the pstack command against the db2sysc PID and save the output, e.g.: $ procstack 1235 10. Wait 10 minutes. 11. Repeat steps 7, 8, 9, and 10. Save the output. 13. Repeat steps 7, 8, 9, and 10 again, saving the output. 14. Copy and save all of the on-screen output from the TSM console. 15. Restart TSM. 16. Login as instance owner, issue db2support -d tsmdb1 -c -g -s, save the db2support.zip generated Once you have the PMR created, you can send in the doc that you collected: 1.The TSM server console output 2. The TSM server trace file 3. The three iterations of the ps output 4. The three iterations of pstack output against dsmserv 5. The three iterations of pstack output against db2sysc 6. The db2support.zip file Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2012-12-03 08:45:17: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2012-12-03 08:55 Subject: Re: 6.3.3.000 server wont HALT Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- Paul ZarnowskiPh: 607-255-4757 CIT Infrastructure / Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: 6.3.3.000 server wont HALT
I meant 'dsmadmc -id=id -pass=pass -console' from a telnet/ssh session. It displays all console messages as they are generated. I use it to monitor the progress of long-running processes (deletion of filespaces, macros that update volume access, etc.). Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, December 03, 2012 8:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 6.3.3.000 server wont HALT Not sure what you mean by console session. I use TSMManager and issue the halt via it's console/monitor window, if that is what you are referring to - and yes, it shows the halt is issued and then the server goes non-responsive, as suspected. Then from ssh/Linux the process dsmserv never halts/stops. On Mon, Dec 3, 2012 at 9:00 AM, Schneider, Jim jschnei...@ussco.com wrote: Have you tried a -console session prior to issuing halt? Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, December 03, 2012 7:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 6.3.3.000 server wont HALT This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person.
Re: 6.3.3.000 server wont HALT
Hi I did a test to my new TSm Server windows V6.3.3.0 , I halt the server check in the manage console the service is stop , check in task manager the services (tsm and db2) shut down Regards Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: Monday, December 03, 2012 4:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 6.3.3.000 server wont HALT Hi Zoltan, Looks like we have one or two other customers reporting this. My recommendation would be for you to open a PMR. Optionally, if you want to be as pro-active as possible, perform the following steps in advance (this is the current set of doc being requested for this issue): 1. Stop TSM, kill if necessary. 2. Start dsmserv in the foreground. 3. Wait for TSM to come completely up. 4. In the TSM server console, enable tracing by issuing: trace enable ADM DB THREAD TM ADDMSG trace begin /tmp/tsmhalttrace.out (for the trace begin command, specify whatever directory and trace file name if you want) 5. Issue the HALT command on the TSM server console 6. Wait 10 minutes. 7. Open a root terminal on the system where TSM is running and issue the following commands (and save the output): ps -ef | grep dsmserv ps -ef | grep db2 8. Locate the process ID (PID) for dsmserv AND db2sysc from the ps output. 9. Issue the pstack command against the dsmserv PID and save the output, e.g.: $ procstack 1234 10. Issue the pstack command against the db2sysc PID and save the output, e.g.: $ procstack 1235 10. Wait 10 minutes. 11. Repeat steps 7, 8, 9, and 10. Save the output. 13. Repeat steps 7, 8, 9, and 10 again, saving the output. 14. Copy and save all of the on-screen output from the TSM console. 15. Restart TSM. 16. Login as instance owner, issue db2support -d tsmdb1 -c -g -s, save the db2support.zip generated Once you have the PMR created, you can send in the doc that you collected: 1.The TSM server console output 2. The TSM server trace file 3. The three iterations of the ps output 4. The three iterations of pstack output against dsmserv 5. The three iterations of pstack output against db2sysc 6. The db2support.zip file Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2012-12-03 08:45:17: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2012-12-03 08:55 Subject: Re: 6.3.3.000 server wont HALT Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal
issue with offsite reclamation
I noticed that I wasn't getting as many tapes back that though I should get and I dug a little deeper and found an error popping up in the activity log: ANRD Thread32 issued message from: ANRD Thread32 07FEF7A56A99 OutDiagToCons()+159 ANRD Thread32 07FEF7A504EC outDiagfExt()+fc ANRD Thread32 07FEF74D63DC AfRclmOnsiteVols()+20fc ANRD Thread32 07FEF74D6B5F AfRclmVolumeThread()+1bf ANRD Thread32 07FEF72782A4 startThread()+124 ANRD Thread32 73211D9F endthreadex()+43 ANRD Thread32 73211E3B endthreadex()+df ANRD Thread32 76D5652D BaseThreadInitThunk()+d ANRD Thread32 76E8C521 RtlUserThreadStart()+21 ANRD_1147918115 RclmOffsiteVols(afrclm.c:2975) Thread32: Error 3051 queuing storage pool volumes for offsite reclamation. Offsite reclamation processing may be incomplete. I get this error whenever i kick off the process. Im running TSM 6.3.1.0 on Windows 2008 R2. David Tyree Interface Analyst South Georgia Medical Center 229.333.1155
Re: 6.3.3.000 server wont HALT
Doesn't it figure. Now that I ran the server interactively to setup the trace, it is halting just fine. Don't know what to think, now. On Mon, Dec 3, 2012 at 10:28 AM, Zoltan Forray zfor...@vcu.edu wrote: Thanks Andy. Glad to know I am not the only one. Will collect the info and open a PMR. Just another reason they call it the bleeding edge ;--) On Mon, Dec 3, 2012 at 9:34 AM, Andrew Raibeck stor...@us.ibm.com wrote: Hi Zoltan, Looks like we have one or two other customers reporting this. My recommendation would be for you to open a PMR. Optionally, if you want to be as pro-active as possible, perform the following steps in advance (this is the current set of doc being requested for this issue): 1. Stop TSM, kill if necessary. 2. Start dsmserv in the foreground. 3. Wait for TSM to come completely up. 4. In the TSM server console, enable tracing by issuing: trace enable ADM DB THREAD TM ADDMSG trace begin /tmp/tsmhalttrace.out (for the trace begin command, specify whatever directory and trace file name if you want) 5. Issue the HALT command on the TSM server console 6. Wait 10 minutes. 7. Open a root terminal on the system where TSM is running and issue the following commands (and save the output): ps -ef | grep dsmserv ps -ef | grep db2 8. Locate the process ID (PID) for dsmserv AND db2sysc from the ps output. 9. Issue the pstack command against the dsmserv PID and save the output, e.g.: $ procstack 1234 10. Issue the pstack command against the db2sysc PID and save the output, e.g.: $ procstack 1235 10. Wait 10 minutes. 11. Repeat steps 7, 8, 9, and 10. Save the output. 13. Repeat steps 7, 8, 9, and 10 again, saving the output. 14. Copy and save all of the on-screen output from the TSM console. 15. Restart TSM. 16. Login as instance owner, issue db2support -d tsmdb1 -c -g -s, save the db2support.zip generated Once you have the PMR created, you can send in the doc that you collected: 1.The TSM server console output 2. The TSM server trace file 3. The three iterations of the ps output 4. The three iterations of pstack output against dsmserv 5. The three iterations of pstack output against db2sysc 6. The db2support.zip file Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2012-12-03 08:45:17: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2012-12-03 08:55 Subject: Re: 6.3.3.000 server wont HALT Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done. However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this issue before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray zfor...@vcu.edu wrote: Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 (RH Linux) While the install and startup went fine, it won't HALT. After the install/upgrade, I got in via dsmadmc just fine. Checked the actlog - saw all the schema changes/upgrades. Updated/registered the licenses and then issued HALT. Got the usually warning and said YES. Now it has been sitting for 25-minutes since the halt. Can't get back in via dsmadmc. Top shows dsmserv using 200% CPU. I tried standard kills, with no luck. I hate to do a kill -9 but will if I don't have a choice. What the heck is it doing? Should I wait longer or just kill it with extreme prejudice? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email
-snapdiff incremental backups on Windows and include/exclude
Do: include exclude exclude.dir Work when you are doing an incremental with -snapdiff ? (Netapp Vfiler, TSM 6.4 client on Win2K8, Ontap 8.1, TSM 6.3.0 server on Win2K8) Thanks! Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
SV: -snapdiff incremental backups on Windows and include/exclude
Hi Wanda, If you are using multiple vFiler, you can't run Snapdiff. The issue was a NetApp problem and not a IBM problem. But I sow some news about NetApp in TSM 6.4 but no one could tell me what news it is. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Säkra återläsningar. -Ursprungligt meddelande- Från: Prather, Wanda [mailto:wanda.prat...@icfi.com] Skickat: den 4 december 2012 07:38 Till: ADSM-L@VM.MARIST.EDU Ämne: -snapdiff incremental backups on Windows and include/exclude Do: include exclude exclude.dir Work when you are doing an incremental with -snapdiff ? (Netapp Vfiler, TSM 6.4 client on Win2K8, Ontap 8.1, TSM 6.3.0 server on Win2K8) Thanks! Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
Re: -snapdiff incremental backups on Windows and include/exclude
Hi Christian, Yes, look at the TSM 6.4 Windows client manual, in the section New for IBM Tivoli Storage Manager Version 6.4 The 6.4 code does support vFilers and also SnapMirror replication target volumes. So far it appears to work on the vFilers, I'm just getting weird errors on a handful of files that I'm trying to resolve about invalid file handle, ans4013E. (78 failures out of 5.5. million files is not too bad for the first try!) Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Christian Svensson Sent: Tuesday, December 04, 2012 1:47 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: -snapdiff incremental backups on Windows and include/exclude Hi Wanda, If you are using multiple vFiler, you can't run Snapdiff. The issue was a NetApp problem and not a IBM problem. But I sow some news about NetApp in TSM 6.4 but no one could tell me what news it is. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Säkra återläsningar. -Ursprungligt meddelande- Från: Prather, Wanda [mailto:wanda.prat...@icfi.com] Skickat: den 4 december 2012 07:38 Till: ADSM-L@VM.MARIST.EDU Ämne: -snapdiff incremental backups on Windows and include/exclude Do: include exclude exclude.dir Work when you are doing an incremental with -snapdiff ? (Netapp Vfiler, TSM 6.4 client on Win2K8, Ontap 8.1, TSM 6.3.0 server on Win2K8) Thanks! Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
