Re: TSM scheduler service issue
Issue got fixed by changing scheduler service to dsmcad , By Sarav +65-82284384 On 19 Jul, 2014, at 10:53 pm, Dmitry Dukhov dem...@gmail.com wrote: On 19.07.2014 16:44, Saravanan wrote: Hi, TSM scheduler service is running as root user in the background But when we trigger oracle job from TSM it doesn't work su - oracle -c /opt/tsm/ora.0.sh But when we trigger TSM scheduler service in foreground it works well Has anybody seen this issue ? By Sarav +65-82284384 try so run first script db_bkf.sh su - orarnd -c /usr/tivoli/tsm/client/scripts/db_full_backup which run second script db_full_backup cd /usr/tivoli/tsm/client/scripts /oracle/db102/bin/rman /usr/tivoli/tsm/client/scripts/db_bkf.rman -- Dmitry Dukhov Siberia Software SL http://www.s-iberia.com
TSM scheduler service issue
Hi, TSM scheduler service is running as root user in the background But when we trigger oracle job from TSM it doesn't work su - oracle -c /opt/tsm/ora.0.sh But when we trigger TSM scheduler service in foreground it works well Has anybody seen this issue ? By Sarav +65-82284384
Re: TSM scheduler service issue
Start by excluding TSM, does it run from a cron or at job? It's most likely a variable thats set when you run it as a user that isn't when run from TSM On 19 July 2014 13:44, Saravanan evergreen.sa...@gmail.com wrote: Hi, TSM scheduler service is running as root user in the background But when we trigger oracle job from TSM it doesn't work su - oracle -c /opt/tsm/ora.0.sh But when we trigger TSM scheduler service in foreground it works well Has anybody seen this issue ? By Sarav +65-82284384
Re: TSM scheduler service issue
On 19.07.2014 16:44, Saravanan wrote: Hi, TSM scheduler service is running as root user in the background But when we trigger oracle job from TSM it doesn't work su - oracle -c /opt/tsm/ora.0.sh But when we trigger TSM scheduler service in foreground it works well Has anybody seen this issue ? By Sarav +65-82284384 try so run first script db_bkf.sh su - orarnd -c /usr/tivoli/tsm/client/scripts/db_full_backup which run second script db_full_backup cd /usr/tivoli/tsm/client/scripts /oracle/db102/bin/rman /usr/tivoli/tsm/client/scripts/db_bkf.rman -- Dmitry Dukhov Siberia Software SL http://www.s-iberia.com
Re: TSM scheduler service issue
Yes it's running from root crontab but not starting from TSM sched By Sarav +65-82284384 On 19 Jul, 2014, at 9:15 pm, Steven Langdale steven.langd...@gmail.com wrote: Start by excluding TSM, does it run from a cron or at job? It's most likely a variable thats set when you run it as a user that isn't when run from TSM On 19 July 2014 13:44, Saravanan evergreen.sa...@gmail.com wrote: Hi, TSM scheduler service is running as root user in the background But when we trigger oracle job from TSM it doesn't work su - oracle -c /opt/tsm/ora.0.sh But when we trigger TSM scheduler service in foreground it works well Has anybody seen this issue ? By Sarav +65-82284384
Re: TSM scheduler service issue
Op 19 jul. 2014, om 15:15 heeft Steven Langdale steven.langd...@gmail.com het volgende geschreven: Start by excluding TSM, does it run from a cron or at job? It's most likely a variable thats set when you run it as a user that isn't when run from TSM my thoughts exactly, the init environment is usually far more limited than a normal user environment. Also, make sure that you include the #!/bin/sh as the first line of your script and it actually points to the shell that you are depending on... On 19 July 2014 13:44, Saravanan evergreen.sa...@gmail.com wrote: Hi, TSM scheduler service is running as root user in the background But when we trigger oracle job from TSM it doesn't work su - oracle -c /opt/tsm/ora.0.sh But when we trigger TSM scheduler service in foreground it works well Has anybody seen this issue ? By Sarav +65-82284384 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Restart TSM Scheduler on Ubuntu
Hi people , First i kill all the process with dsmcad (5 dsmcad launch...) After that i do dsmcad sched start And i have this message test@node_name#58;~# dsmcad sched startd 28.02.2014 09#58;27#58;15 #40;dsmcad#41; ANSE amsgrtrv.cpp#40;3087#41;#58; Message No 11000 could not be found. 28.02.2014 09#58;27#58;15 #40;dsmcad#41; ANSE amsgrtrv.cpp#40;3087#41;#58; Message No 11000 could not be found. 28.02.2014 09#58;27#58;15 #40;dsmcad#41; ANS0102W Unable to open the message repository /opt/tivoli/tsm/client/ba/bin/fr_FR/dsmclientV3.cat. The American English repository will be used instead. But on my TSM Server i see the ANR0406I Session 28037 started for node NODE_NAME #40;Linux86#41; #40;Tcp/Ip blabla.fr#40;60250#41;#41;. ANR0403I Session 28037 ended for node NODE_NAME #40;Linux86#41;. But each day the node was missed anybody (nothing in the dsmerror.log and in the dsmsched.log).. Best regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Restart TSM Scheduler on Ubuntu
Hi everybody, What is the command i have to do to restart the tsm scheduler on Ubuntu (client missed 2days..) Regards, Mickael +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Restart TSM Scheduler on Ubuntu
That all depends on what the name of the scheduler service or process is? On RedHat Linux the script is usually in /etc/init.d and most people just call it dsmc or dsmcad. So you could do a dsmc restart (if the script supports it) or stop/start. 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 On Feb 11, 2014 3:32 AM, mik tsm-fo...@backupcentral.com wrote: Hi everybody, What is the command i have to do to restart the tsm scheduler on Ubuntu (client missed 2days..) Regards, Mickael +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
TSM Scheduler problem with Windows 2008
Hello All, We are having a issue with a Windows 2008 client backing up thru a firewall I believe someone had issues Windows 2008 clients due to a firewall were there any executables added to the firewall? Or just ports? Thanks in advance
Re: TSM Scheduler problem with Windows 2008
Only way I can make the firewall and tsm play nice is to specify as follows: * tcpip client port tcpclientport 1501 *dsmcad dsmagent ports, Webport 1552 1553 *web client HTTPport HTTPport 1581 * TSM server port TCPport 1500 Then specify port openings in the firewall for 1501 1552 and 1553. We never use the web client. Works like a champ then. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, June 09, 2011 1:39 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Scheduler problem with Windows 2008 Hello All, We are having a issue with a Windows 2008 client backing up thru a firewall I believe someone had issues Windows 2008 clients due to a firewall were there any executables added to the firewall? Or just ports? Thanks in advance
Re: TSM Scheduler problem with Windows 2008
Thanks Gary! Regards! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Thursday, June 09, 2011 2:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Scheduler problem with Windows 2008 Only way I can make the firewall and tsm play nice is to specify as follows: * tcpip client port tcpclientport 1501 *dsmcad dsmagent ports, Webport 1552 1553 *web client HTTPport HTTPport 1581 * TSM server port TCPport 1500 Then specify port openings in the firewall for 1501 1552 and 1553. We never use the web client. Works like a champ then. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, June 09, 2011 1:39 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Scheduler problem with Windows 2008 Hello All, We are having a issue with a Windows 2008 client backing up thru a firewall I believe someone had issues Windows 2008 clients due to a firewall were there any executables added to the firewall? Or just ports? Thanks in advance
Re: TSM Scheduler problem with Windows 2008
Just in case you don't like GUIs: netsh advfirewall firewall add rule name=IBM Tivoli Storage Manager CAD dir=in program=C:\program files\tivoli\tsm\baclient\dsmcad.exe action=allow Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Thursday, June 09, 2011 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler problem with Windows 2008 Only way I can make the firewall and tsm play nice is to specify as follows: * tcpip client port tcpclientport 1501 *dsmcad dsmagent ports, Webport 1552 1553 *web client HTTPport HTTPport 1581 * TSM server port TCPport 1500 Then specify port openings in the firewall for 1501 1552 and 1553. We never use the web client. Works like a champ then. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, June 09, 2011 1:39 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Scheduler problem with Windows 2008 Hello All, We are having a issue with a Windows 2008 client backing up thru a firewall I believe someone had issues Windows 2008 clients due to a firewall were there any executables added to the firewall? Or just ports? Thanks in advance This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
TSM Scheduler problem with Windows 2008
tjackson5512 wrote: Good Afternoon, I am having trouble configuring TSM Backup Client on Windows 2008 clients. The version ont he server is TSM 5.4.5.1 and the Windows Client is 5.5.2.12. After scheduling a test backup with the TSM server, the Client does not start at the sscheduled time. When I refresh the TSM services on the client the backup starts till completed. I have removed and re-installed the TSM Backup Client at least 3-4 times. I am not sure if it is a McAfee Virus scanner problem or a Windows 2008 firewall problem. Has anyone seen this problem with Win 2008 before? [Shocked] I have submitted a ticket to IBM software support and to date haven't gotten much help. Does TSM 6.1 have better luck with Windows 2008? [Question] Any help would be much appreciated. Solution Found - I had setup a test backup on four of the Windows 2008 clients that weren't backing up and low and behold it was the Windows 2008 Firewall. I had added all of the dsm commands and also added port 1501. The backups kicked off on time and I did not have to refresh the TSM Services. The backups ran without issue. [Laughing] +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
TSM Scheduler problem with Windows 2008
Good Afternoon, I am having trouble configuring TSM Backup Client on Windows 2008 clients. The version ont he server is TSM 5.4.5.1 and the Windows Client is 5.5.2.12. After scheduling a test backup with the TSM server, the Client does not start at the sscheduled time. When I refresh the TSM services on the client the backup starts till completed. I have removed and re-installed the TSM Backup Client at least 3-4 times. I am not sure if it is a McAfee Virus scanner problem or a Windows 2008 firewall problem. Has anyone seen this problem with Win 2008 before? [Shocked] I have submitted a ticket to IBM software support and to date haven't gotten much help. Does TSM 6.1 have better luck with Windows 2008? [Question] Any help would be much appreciated. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Scheduler problem with Windows 2008
Which SCHEDMODE are you using? PROMPTED or POLLING? If you use SCHEDMODE PROMPTED, have you checked the TSM server activity log for messages showing that it tries to prompt the client? If the scheduled backup begins when you restart the scheduler within its window, then perhaps the server is otherwise having a difficult time prompting the client. This might be a firewall issue. Are you using the CAD to manage the scheduler? If so, check out APAR IC65313, that might explain the trouble. Issue the DSMCUTIL LIST command to see the installed services. Make a note of the name of the TSM scheduler service. Then issue DSMCUTIL QUERY /NAME:cadschedname (where cadschedname is the name of the CAD, probably TSM Client Acceptor), and look at the CAD Schedule Service field. Does it match the name of the TSM scheduler service? Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/i...@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 The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2010-05-03 12:14:34: TSM Scheduler problem with Windows 2008 tjackson5512 to: ADSM-L 2010-05-03 12:21 Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Please respond to ADSM-L Good Afternoon, I am having trouble configuring TSM Backup Client on Windows 2008 clients. The version ont he server is TSM 5.4.5.1 and the Windows Client is 5.5.2.12. After scheduling a test backup with the TSM server, the Client does not start at the sscheduled time. When I refresh the TSM services on the client the backup starts till completed. I have removed and re-installed the TSM Backup Client at least 3-4 times. I am not sure if it is a McAfee Virus scanner problem or a Windows 2008 firewall problem. Has anyone seen this problem with Win 2008 before? [Shocked] I have submitted a ticket to IBM software support and to date haven't gotten much help. Does TSM 6.1 have better luck with Windows 2008? [Question] Any help would be much appreciated. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Scheduler problem with Windows 2008
Have installed 6.1.3 on several servers without any issue... --- Julien Malghem Ingénieur Système / Spécialiste Stockage julien.malg...@rbs.fr 2 Ter rue Marcel Doret 31700 Blagnac www.rbs.fr RBS Solutions Tél. : +33 (0)5 34 47 76 77 • Portable : +33 (0)6 60 26 61 52 • Fax : +33 (0)5 34 47 14 14 Un problème ? Contactez le Centre de Support RBS au 0892 70 12 12 (0,34€/mn) ou écrivez à supp...@rbs.fr -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de tjackson5512 Envoyé : lundi 3 mai 2010 18:15 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] TSM Scheduler problem with Windows 2008 Good Afternoon, I am having trouble configuring TSM Backup Client on Windows 2008 clients. The version ont he server is TSM 5.4.5.1 and the Windows Client is 5.5.2.12. After scheduling a test backup with the TSM server, the Client does not start at the sscheduled time. When I refresh the TSM services on the client the backup starts till completed. I have removed and re-installed the TSM Backup Client at least 3-4 times. I am not sure if it is a McAfee Virus scanner problem or a Windows 2008 firewall problem. Has anyone seen this problem with Win 2008 before? [Shocked] I have submitted a ticket to IBM software support and to date haven't gotten much help. Does TSM 6.1 have better luck with Windows 2008? [Question] Any help would be much appreciated. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
TSM Scheduler problem with Windows 2008
Thank you for replying back. Currently SCHEDMODE is set to PROMPTED. Cannot change the TSM Server to POLLING. I believe this problem deals with McAfee anti-virus software. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Scheduler problem with Windows 2008
A schedule that runs when the service is restarted but not otherwise sounds like a classic firewall issue. When the service is restarted on the client, the client starts communication with the server and the schedule can run. But when then next cycle comes around TSM initiates the communication and can not make it thru the firewall. This results in a cannot contact message in the TSM service actlog and no messages in the dsmwebcl/dsmsched logs. David tjackson5512 tsm-fo...@backupcentral.com 5/3/2010 12:14 PM Good Afternoon, I am having trouble configuring TSM Backup Client on Windows 2008 clients. The version ont he server is TSM 5.4.5.1 and the Windows Client is 5.5.2.12. After scheduling a test backup with the TSM server, the Client does not start at the sscheduled time. When I refresh the TSM services on the client the backup starts till completed. I have removed and re-installed the TSM Backup Client at least 3-4 times. I am not sure if it is a McAfee Virus scanner problem or a Windows 2008 firewall problem. Has anyone seen this problem with Win 2008 before? [Shocked] I have submitted a ticket to IBM software support and to date haven't gotten much help. Does TSM 6.1 have better luck with Windows 2008? [Question] Any help would be much appreciated. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Scheduler problem with Windows 2008
We are facing exactly the same problem with TSM Client 6.2.0, SCHEDMODE PROMPTED and standalone scheduler. I have found in TSM Server activity log it is impossible to reach scheduler by port 1501. I have asked Windows 2008 Admin to allow communication TSM Server --- 1501 on node in Win2008 firewall. This night we will see results. From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of tjackson5512 [tsm-fo...@backupcentral.com] Sent: Monday, May 03, 2010 7:14 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Scheduler problem with Windows 2008 Good Afternoon, I am having trouble configuring TSM Backup Client on Windows 2008 clients. The version ont he server is TSM 5.4.5.1 and the Windows Client is 5.5.2.12. After scheduling a test backup with the TSM server, the Client does not start at the sscheduled time. When I refresh the TSM services on the client the backup starts till completed. I have removed and re-installed the TSM Backup Client at least 3-4 times. I am not sure if it is a McAfee Virus scanner problem or a Windows 2008 firewall problem. Has anyone seen this problem with Win 2008 before? [Shocked] I have submitted a ticket to IBM software support and to date haven't gotten much help. Does TSM 6.1 have better luck with Windows 2008? [Question] Any help would be much appreciated. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
TSM Scheduler service stops by itself
I am having a problem with the TSM Scheduler of a windows server. It stops sometimes by itself in the middle of a backup of files. The weird thing is that in the same server I have a scheduled TDP SQL backup, but the scheduler service works without problem. +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Scheduler service stops by itself
On Feb 18, 2009, at 7:32 AM, admbackup wrote: I am having a problem with the TSM Scheduler of a windows server. It stops sometimes by itself in the middle of a backup of files. The weird thing is that in the same server I have a scheduled TDP SQL backup, but the scheduler service works without problem. You need to look for evidence. Inspect the dsmerror.log on the client, and the Activity Log on the TSM server for indications of cause. On a Windows box you can also check its Event Log, to see if the process is crashing, etc. Richard Sims
Re: TSM Scheduler service stops by itself
We are having problems here with scheduled backups hanging. It happened on rare occassions prior to upgrading to 5.5.1, but it began happening with great frequency on certain Windows boxes after the upgrade. W2k3 servers with SP2, Broadcom NICs with the Advanced Control Suite, and a particular microsoft hotfix, 91. Management determined that we were not going to roll back the hotfix. The workaround that we used was to deselect the Advanced Control Suite TCP Chimney setting. Typically, our Windows folks blamed TSM because everything else was working fine, while we blamed Microsoft because TSM wasn't what changed, and TSM worked fine on unaltered Windows servers. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Wednesday, February 18, 2009 8:23 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler service stops by itself On Feb 18, 2009, at 7:32 AM, admbackup wrote: I am having a problem with the TSM Scheduler of a windows server. It stops sometimes by itself in the middle of a backup of files. The weird thing is that in the same server I have a scheduled TDP SQL backup, but the scheduler service works without problem. You need to look for evidence. Inspect the dsmerror.log on the client, and the Activity Log on the TSM server for indications of cause. On a Windows box you can also check its Event Log, to see if the process is crashing, etc. Richard Sims IMPORTANT: E-mail sent through the Internet is not secure and timely delivery of Internet mail is not guaranteed. Legg Mason therefore, recommends that you do not send any action-oriented or time-sensitive information to us via electronic mail, or any confidential or sensitive information including: social security numbers, account numbers, or personal identification numbers. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: TSM Scheduler service stops by itself
If you need ammo for scrapping with your Windows brethren, remind them that TSM uses no OS APIs that aren't supplied by Windows itself. If they changed something in the OS, that's what broke. -- Mark Stapleton System engineer, CDW -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebschman, George J. Sent: Wednesday, February 18, 2009 8:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler service stops by itself We are having problems here with scheduled backups hanging. It happened on rare occassions prior to upgrading to 5.5.1, but it began happening with great frequency on certain Windows boxes after the upgrade. W2k3 servers with SP2, Broadcom NICs with the Advanced Control Suite, and a particular microsoft hotfix, 91. Management determined that we were not going to roll back the hotfix. The workaround that we used was to deselect the Advanced Control Suite TCP Chimney setting. Typically, our Windows folks blamed TSM because everything else was working fine, while we blamed Microsoft because TSM wasn't what changed, and TSM worked fine on unaltered Windows servers. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Wednesday, February 18, 2009 8:23 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler service stops by itself On Feb 18, 2009, at 7:32 AM, admbackup wrote: I am having a problem with the TSM Scheduler of a windows server. It stops sometimes by itself in the middle of a backup of files. The weird thing is that in the same server I have a scheduled TDP SQL backup, but the scheduler service works without problem. You need to look for evidence. Inspect the dsmerror.log on the client, and the Activity Log on the TSM server for indications of cause. On a Windows box you can also check its Event Log, to see if the process is crashing, etc. Richard Sims IMPORTANT: E-mail sent through the Internet is not secure and timely delivery of Internet mail is not guaranteed. Legg Mason therefore, recommends that you do not send any action-oriented or time-sensitive information to us via electronic mail, or any confidential or sensitive information including: social security numbers, account numbers, or personal identification numbers. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you. No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.10.25/1957 - Release Date: 17-Feb-09 7:07 AM No virus found in this outgoing message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.10.25/1957 - Release Date: 17-Feb-09 7:07 AM
Re: TSM Scheduler service stops by itself
When Windows 2003 SP2 hangs during backups I first verify it has patch KB948496. Having you tried blaming the network? : Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebschman, George J. Sent: Wednesday, February 18, 2009 8:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler service stops by itself We are having problems here with scheduled backups hanging. It happened on rare occassions prior to upgrading to 5.5.1, but it began happening with great frequency on certain Windows boxes after the upgrade. W2k3 servers with SP2, Broadcom NICs with the Advanced Control Suite, and a particular microsoft hotfix, 91. Management determined that we were not going to roll back the hotfix. The workaround that we used was to deselect the Advanced Control Suite TCP Chimney setting. Typically, our Windows folks blamed TSM because everything else was working fine, while we blamed Microsoft because TSM wasn't what changed, and TSM worked fine on unaltered Windows servers. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Wednesday, February 18, 2009 8:23 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler service stops by itself On Feb 18, 2009, at 7:32 AM, admbackup wrote: I am having a problem with the TSM Scheduler of a windows server. It stops sometimes by itself in the middle of a backup of files. The weird thing is that in the same server I have a scheduled TDP SQL backup, but the scheduler service works without problem. You need to look for evidence. Inspect the dsmerror.log on the client, and the Activity Log on the TSM server for indications of cause. On a Windows box you can also check its Event Log, to see if the process is crashing, etc. Richard Sims IMPORTANT: E-mail sent through the Internet is not secure and timely delivery of Internet mail is not guaranteed. Legg Mason therefore, recommends that you do not send any action-oriented or time-sensitive information to us via electronic mail, or any confidential or sensitive information including: social security numbers, account numbers, or personal identification numbers. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
TSM Scheduler Hang
We have started seeing the Scheduler service on Windows hang. The backup stops processing, the Schedule stays started, but nothing happens. The fix for now is to stop the scheduler and restart the acceptor. This is only happening on a few of the servers and they do not seem to have much in common, they are running different apps. Versions: Windows 2000 and 2003 (32bit) Agent 5.3.2.2 and 5.3.4.8 TSM 5.4.2.0 (AIX) We plan on upgrading the agents to 5.4.2.3 and 5.3.6.0, but this process will take some time. Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Scheduler Hang
Since you are investing time in upgrading the client, why not go with the 5.3.6 on the w2K boxes, and 5.5.1 on the 2003 boxes? A 5.4 server will handle 5.5 clients, and you will not have to go back to the 2003 servers when you upgrade your TSM server. I remember having this problem on some boxes, before I upgraded, where it was like everything on the server and client thought the backups were running, but a query of the sessions on the server showed idlew, and no increase of data flow. The only thing that resolved our issues was the client upgrade. So, since I was having to touch the box anyway, I started upgrading the clients as I found the problem, and wound up saving more time than it cost. See Ya' Howard -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Friday, September 26, 2008 10:25 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Scheduler Hang We have started seeing the Scheduler service on Windows hang. The backup stops processing, the Schedule stays started, but nothing happens. The fix for now is to stop the scheduler and restart the acceptor. This is only happening on a few of the servers and they do not seem to have much in common, they are running different apps. Versions: Windows 2000 and 2003 (32bit) Agent 5.3.2.2 and 5.3.4.8 TSM 5.4.2.0 (AIX) We plan on upgrading the agents to 5.4.2.3 and 5.3.6.0, but this process will take some time. Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
I hope it works for you. We recently upgraded to 5.5.1 server on a z/OS platform, after which most of our scheduled backups failed, apparently because of some perceived discrepancy found by reverse lookup. We added the DNSLOOKUP NO parameter as suggested by IBM support (it is undocumented for z/OS) and by itself, it did not solve our problems. We also had to restart the client acceptors on all the clients. In a few cases we had to perform manual backups before the new server software was satisfied. - Margaret Clark Systems Programmer, San Diego Data Proc4essing Corporation -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 4:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. TSM will populate field TCP_ADDRESS in table NODES with the numeric address of the client when it connects, so not having name lookups performed is really no loss in functionality... And now that I know about that option, it's going in next restart, because it will cut latency, which will matter for things like when an RMAN client deletes its old backups in a flurry of hundreds of separate sessions in sequence. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD
TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
John - The ANR8213W message is conspicuously deficient in not parenthetically including the IP address along with the network name that it's reporting, such that you don't know for certain what address the TSM server is using in making the connection attempt. With DNS awry at your location, it may be that in the last client-server interaction that an address was obtained for the next interaction, where that address is no longer valid. IBM Technote 1296826 goes into other aspects of this situation. I would not fault TSM in the missed schedule: I would not want my server to be interacting with dubious network addresses where supposedly secured host data is involved. Flakey DNS is a very bad situation, and needs to get permanently fixed there. If you have good Security people there, they should be railing on people about the ramifications of erroneous network addresses being given out by your DNS servers. You can look into the DNSLOOKUP option for your TSM server, but there remains the larger issue of bad addresses being given out in the environment in general. Richard Sims
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately. This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
No, the problem is that the node TSM is trying to reach is stlo-mpvadm.company.com but the machine that's responding is stlo-mpvadm.smrcy.com and TSM knows there's a difference. You MUST correct the DNS problem because TSM uses it in some way to verify authentication. I've seen this a dozen or so times before. When I've seen it the worse is where they have moved the machine to a new domain, but didn't update the machine's node and domain name info. So the machine was reporting nodename.olddomain.com while the DNS was saying nodename.newdomain.com and TSM would not allow the schedule to proceed. Once we corrected the domain info, the backups proceeded normally. See Ya' Howard -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo- mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately. This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix this is to fix the Active Directory root cause, but sometimes that requires a reboot of the client which can taken a week or more to schedule. Is the schedmode setting at fault? Would changing it to polling get around this until a reboot can be scheduled? If I don't hear anything better I will try that tonight. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
Richard Thanks for your post. It seems odd to me too that it doesn't spell out the IP address when it tries to connect, but when you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 ... However, it may attempt to do a DNS resolve anyway, or a reverse resolve on the IP address, and that is when it gets into trouble. The DNS inconsistency only exists for this one client, and because of how Active Directory works, I will have to reboot the client to fix it, which will take a few days to plow through the bureaucracy. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Thursday, September 18, 2008 11:15 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. John - The ANR8213W message is conspicuously deficient in not parenthetically including the IP address along with the network name that it's reporting, such that you don't know for certain what address the TSM server is using in making the connection attempt. With DNS awry at your location, it may be that in the last client-server interaction that an address was obtained for the next interaction, where that address is no longer valid. IBM Technote 1296826 goes into other aspects of this situation. I would not fault TSM in the missed schedule: I would not want my server to be interacting with dubious network addresses where supposedly secured host data is involved. Flakey DNS is a very bad situation, and needs to get permanently fixed there. If you have good Security people there, they should be railing on people about the ramifications of erroneous network addresses being given out by your DNS servers. You can look into the DNSLOOKUP option for your TSM server, but there remains the larger issue of bad addresses being given out in the environment in general. Richard Sims This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
John - One last thought: A 10-net is in use there (private net - no routing). As such fussy firewall rules may be in force, which with the DNS happening may be a further impediment to reaching that TSM client through the server. Some basic network tracing (Wireshark, et al) in conjunction with a TSM server Define Clientaction simple interaction may illuminate what's going on. Richard
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
I specify this on almost all my TSM servers and haven't seen any adverse effects. Bypasses the DNS issues like what you have right now. It is a documented option in the Admin Reference. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 3:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What difference does it make that the reverse resolve doesn't match? Or is the problem with the client? Is it not responding? The client's dsmwebcl.log and dsmerror.log show no evidence that it is getting contacted at all. The right way to fix
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
TSM will populate field TCP_ADDRESS in table NODES with the numeric address of the client when it connects, so not having name lookups performed is really no loss in functionality... And now that I know about that option, it's going in next restart, because it will cut latency, which will matter for things like when an RMAN client deletes its old backups in a flurry of hundreds of separate sessions in sequence. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for node STLO-MPVADM has missed its scheduled start up window. In looking into it, what seems to be happening is that it's forward resolve in DNS doesn't match it's reverse resolve. Here is an example: W:\nslookup stlo-mpvadm Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.smrcy.com Address: 10.52.27.204 W:\nslookup 10.52.27.204 Server: stl-pdcp001.smrcy.com Address: 10.2.215.158 Name:stlo-mpvadm.company.com Address: 10.52.27.204 W:\ Notice that the domain name of the host is different on the forward and the reverse resolve. That is a mistake. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So what is TSM's problem here? It knows the correct IP address. What
TSM Scheduler Service in 'Stopping' state
Hi All, I had a Windows 2003 client (with TSM client 5.3.2)rebooted last week. Since the reboot, the TSM (client) stopped working. I tried to restart the service but it went on STOPPING state and wouldn't respond. Even the TSM GUI doesn't start. Due to the criticality of the client, I am not able to perform the reboot. Is there anyway, I can make TSM work again with out a reboot ? Would really appreciate your help. Regards, Dinesh Pahari (PS. The client is backing up to a TSM server 5.3.1)
Re: TSM Scheduler Service in 'Stopping' state
On Mar 16, 2008, at 5:59 PM, Pahari, Dinesh P wrote: Hi All, I had a Windows 2003 client (with TSM client 5.3.2)rebooted last week. Since the reboot, the TSM (client) stopped working. I tried to restart the service but it went on STOPPING state and wouldn't respond. Even the TSM GUI doesn't start. Due to the criticality of the client, I am not able to perform the reboot. Is there anyway, I can make TSM work again with out a reboot ? Would really appreciate your help. Tell us what diagnosis you've done... What's in the dsmerror.log and dsmwebcl.log files. Any indications of problems in the Windows Event Log? (There may be more wrong in the system than just TSM executability after that reboot.) Evaluate the circumstances of the reboot: if it was actually a crash, or forced reboot after a hang, there can be prevailing issues. Is the dsmerror.log writable, in a writable directory, as directed by your options file? (If not, you'll have problems.) Richard Sims
Re: TSM Scheduler Service in 'Stopping' state
Thank you for your swift response. The server was rebooted intentionally after a regular maintenance. There are no significant errors reported in the event viewer. Similarly, TSM activity log has recorded nothing since the reboot and no errors are reported for the error occurred. FYI below Event Viewer: Source: AdsmClientServiceTSM Message: Scheduler halter right after the reboot. Dsmerror.log: 03/02/2008 04:03:14 ConsoleEventHandler(): Caught Shutdown console event . 03/02/2008 04:03:14 ConsoleEventHandler(): Cleaning up and terminating Process ... 03/02/2008 05:09:46 ConsoleEventHandler(): Caught Shutdown console event . 03/02/2008 05:09:46 ConsoleEventHandler(): Cleaning up and terminating Process ... Dsmsched.log: Process Interrupted!! Severing connection. Regards, Dinesh Pahari -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Monday, 17 March 2008 9:05 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Scheduler Service in 'Stopping' state Importance: High On Mar 16, 2008, at 5:59 PM, Pahari, Dinesh P wrote: Hi All, I had a Windows 2003 client (with TSM client 5.3.2)rebooted last week. Since the reboot, the TSM (client) stopped working. I tried to restart the service but it went on STOPPING state and wouldn't respond. Even the TSM GUI doesn't start. Due to the criticality of the client, I am not able to perform the reboot. Is there anyway, I can make TSM work again with out a reboot ? Would really appreciate your help. Tell us what diagnosis you've done... What's in the dsmerror.log and dsmwebcl.log files. Any indications of problems in the Windows Event Log? (There may be more wrong in the system than just TSM executability after that reboot.) Evaluate the circumstances of the reboot: if it was actually a crash, or forced reboot after a hang, there can be prevailing issues. Is the dsmerror.log writable, in a writable directory, as directed by your options file? (If not, you'll have problems.) Richard Sims
Re: TSM Scheduler Service in 'Stopping' state
On Mar 16, 2008, at 6:47 PM, Pahari, Dinesh P wrote: The server was rebooted intentionally after a regular maintenance. There are no significant errors reported in the event viewer. Similarly, TSM activity log has recorded nothing since the reboot and no errors are reported for the error occurred. FYI below Event Viewer: Source: AdsmClientServiceTSM Message: Scheduler halter right after the reboot. Dsmerror.log: 03/02/2008 04:03:14 ConsoleEventHandler(): Caught Shutdown console event . 03/02/2008 04:03:14 ConsoleEventHandler(): Cleaning up and terminating Process ... 03/02/2008 05:09:46 ConsoleEventHandler(): Caught Shutdown console event . 03/02/2008 05:09:46 ConsoleEventHandler(): Cleaning up and terminating Process ... Dsmsched.log: Process Interrupted!! Severing connection. Unfortunately, those are very vague and general messages, which seem to be suggesting that something external to TSM is whacking the process when it tries to start. Without specific diagnostics presenting themselves, you'll have to work toward uncovering the cause. I would start by taking a look at what's also running on that system, and in particular if there's any kind of new facility on the system which has the power to kill processes, home-grown or commercial. You might compare what's running on that system relative to similar systems in your shop. I would also check for reduced boundary conditions which might keep things from running, such as full file systems or loss of memory or swap space (though these should show up in the OS Event Log). I would then perform some escalating experiments to try to attract the cause... Use the CLI to run some increasingly consumptive commands, starting with 'dsmc q sess, a 'dsmc i' of a directory, and so on, to see when things start failing. If you can't achieve a session, then you may be having networking problems or a prohibitor of some kind. If you can get a dsmc to work, then try manually starting the scheduler while watching the dsmwebcl.log. If the scheduler will start, then try a simple DEFine CLIENTAction from the TSM server, to run a simple OS command, and see what happens, then see if it can run a 'dsmc i' of the directory you tried before. And if this is happening to the TSM process, I would expect it to be happening to some other system processes, too: look for other things which can't run. You have a clear demarcation as to when this all started, at the reboot. A reboot can put into effect a bunch of changes which had been planted in the days and weeks prior to that event...things which could have been forgotten over time. It's also possible for a bad OS patch to be put into effect which is causing problems. Check your site records of system changes. Richard Sims
PROBLEM WITH THE TSM SCHEDULER
Please I need help, with TSM installed in Windows 2003, I have a Problem with the Scheduler in this platform, I put the TSM Scheduler services to do automatically but, it falls, it stops and the schedule can´t do automatically, please tell me what I have to do. Thanks and regards Wladimir Benavides. El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se encuentra libre de Virus.
Re: PROBLEM WITH THE TSM SCHEDULER
Check that the node correctly connects and authenticates manually to the server first. Also ensure the service is running under an account with the correct privileges. What version of TSM Client is it? Ian Smith Wladimir Benavides [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 12/11/2007 15:29 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] PROBLEM WITH THE TSM SCHEDULER Please I need help, with TSM installed in Windows 2003, I have a Problem with the Scheduler in this platform, I put the TSM Scheduler services to do automatically but, it falls, it stops and the schedule can´t do automatically, please tell me what I have to do. Thanks and regards Wladimir Benavides. El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se encuentra libre de Virus. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
Re: PROBLEM WITH THE TSM SCHEDULER
The server and the client are on the same server. The version of the client is : Cliente: Ver 5. Release 4 Level 1.3. Thanks and Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian-IT Smith Sent: Monday, November 12, 2007 10:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] PROBLEM WITH THE TSM SCHEDULER Check that the node correctly connects and authenticates manually to the server first. Also ensure the service is running under an account with the correct privileges. What version of TSM Client is it? Ian Smith Wladimir Benavides [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 12/11/2007 15:29 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] PROBLEM WITH THE TSM SCHEDULER Please I need help, with TSM installed in Windows 2003, I have a Problem with the Scheduler in this platform, I put the TSM Scheduler services to do automatically but, it falls, it stops and the schedule can´t do automatically, please tell me what I have to do. Thanks and regards Wladimir Benavides. El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se encuentra libre de Virus. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se encuentra libre de Virus.
Re: PROBLEM WITH THE TSM SCHEDULER
So what is the error? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Wladimir Benavides Sent: November 12, 2007 11:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] PROBLEM WITH THE TSM SCHEDULER The server and the client are on the same server. The version of the client is : Cliente: Ver 5. Release 4 Level 1.3. Thanks and Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian-IT Smith Sent: Monday, November 12, 2007 10:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] PROBLEM WITH THE TSM SCHEDULER Check that the node correctly connects and authenticates manually to the server first. Also ensure the service is running under an account with the correct privileges. What version of TSM Client is it? Ian Smith Wladimir Benavides [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 12/11/2007 15:29 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] PROBLEM WITH THE TSM SCHEDULER Please I need help, with TSM installed in Windows 2003, I have a Problem with the Scheduler in this platform, I put the TSM Scheduler services to do automatically but, it falls, it stops and the schedule can´t do automatically, please tell me what I have to do. Thanks and regards Wladimir Benavides. El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se encuentra libre de Virus. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se encuentra libre de Virus.
Re: Adding the TSM Scheduler to a run level on SUSE 9 for Zseries
Hello, just look at the example init script /etc/init.d/skeleton. Copy it to /etc/init.d/tsm_sched Edit it (you only need the start and stop section) it's really easy... And then use chkconfig tsm_shed on to activate it. Then the script will be executed when you boot into runlevel 3 or 5. if you want to use the rc-mimik. You can also create a symbolic link in /sbin: ln -s /etc/init.d/tsm_sched /sbin/rctsm_sched Then you can start and stop the scheduler with: rctsm_sched start rctsm_sched stop Volker PS: I can send you the script I use if you like - I couldn't send it to the list, because shell script attachments are not accepted. Am Montag, den 29.08.2005, 11:52 -0400 schrieb Peter Rothman: I am new to this list and to TSM. I just installed TSM on SUSE9 running under z/VM 510. How do I add the TSM scheduler to one of the run levels so that it starts whenever we reboot the system. Is there a script - do not find one in the install doc. Thanks Peter.
Re: Adding the TSM Scheduler to a run level on SUSE 9 for Zseries
Thanks. I would appreciate the script - please send. Volker Maibaum [EMAIL PROTECTED] BERSPAECHER.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: [ADSM-L] Adding the TSM Scheduler to a run level on SUSE 9 for Zseries 08/30/2005 02:28 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hello, just look at the example init script /etc/init.d/skeleton. Copy it to /etc/init.d/tsm_sched Edit it (you only need the start and stop section) it's really easy... And then use chkconfig tsm_shed on to activate it. Then the script will be executed when you boot into runlevel 3 or 5. if you want to use the rc-mimik. You can also create a symbolic link in /sbin: ln -s /etc/init.d/tsm_sched /sbin/rctsm_sched Then you can start and stop the scheduler with: rctsm_sched start rctsm_sched stop Volker PS: I can send you the script I use if you like - I couldn't send it to the list, because shell script attachments are not accepted. Am Montag, den 29.08.2005, 11:52 -0400 schrieb Peter Rothman: I am new to this list and to TSM. I just installed TSM on SUSE9 running under z/VM 510. How do I add the TSM scheduler to one of the run levels so that it starts whenever we reboot the system. Is there a script - do not find one in the install doc. Thanks Peter.
Adding the TSM Scheduler to a run level on SUSE 9 for Zseries
I am new to this list and to TSM. I just installed TSM on SUSE9 running under z/VM 510. How do I add the TSM scheduler to one of the run levels so that it starts whenever we reboot the system. Is there a script - do not find one in the install doc. Thanks Peter.
5.2.2 or upgrade was [ADSM-L] TSM Scheduler
Regarding your note about whether to stay at 5.2.2 or upgrade, I have the same question. We've recently went to 5.2.2 and had a consultant in here for the better part of last week helping us out. We are running it on OS/400 PASE (and have discovered some limitations with that). We may be going to Linux on the i5 - iSeries - AS/400. However, my boss heard from somewhere to stay on 5.2.2 as it's a bit more stable. Those in the iSeries world know us as people who like to stay on the bleeding edge with the latest OS releases and fixes. But maybe my boss has been bled out a little too often lately, or, we don't have the experience with TSM that we do with OS/400. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Jones, Eric J [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03/23/2005 06:59 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] TSM Scheduler Good Evening. I'm running TSM 5.2.2 server on a AIX 5.2 machine. I have clients running AIX 5.2, Windows 2000 and Windows 2003 with TSM 5.2.2 client. What I'm seeing is occasionally the clients that are running with a client schedule on the server don't kick off. All I see in the server activity log is that the clients missed their schedule, nothing about contacting the clients. Nothing shows up in the client logs so I assume they were never contacted. If I stop and start TSM it starts they all start running again. It does not happen often but 1 day when I 'm doing my daily checks none of the scheduled clients run. All the clients that don't run scheduled events run fine(cron job or windows scheduled event). Is there an easy way to get the scheduler running when it gets into this mode without stopping and starting TSM? On another note. Should we consider upgrading the server to a later version than 5.2.2 or stay at this version since it seems to be running well for the most part. I know in the past they tended to stay with 1 version and at some point TSM became unsupported which I don't want to get to that point. Also is their a later version of TSM(5.2.3, 5.2.4, other) that the clients should be running at, at this point. I know the question is some what general and open to personal preference but I was just looking for input. We are looking to bring in SOLARIS 10 and Linux and would like to avoid problems down the road. Thanks for all your help, Eric
Setting up TSM Scheduler service remotely
Hi All, I am working in a Windows 2k3 non-cluster environment running TSM Server 5.2.3 with clients TSM 5.2.2. What I am trying to do is to install the scheduler service remotely from another computer. I am using the following commands: dsmcutil install sched /name:TSMScheduler /machine:%1 /node:%2 /password:%3 /optfile:C:\Program Files\Tivoli\TSM\BAClient\dsm.opt /clientdir:C:\Program Files\Tivoli\TSM\BAClient dsmcutil updatepw /machine:%1 /node:%2 /oldpassword:%3 /password:password /updateonserver:yes After issuing these commands, I get the responses: Connecting to registry on remote machine Authenticating current password Password authentication successful The registry password for node X has been updated However, after all this happens, the scheduler quits and when I go to the remote system and start the TSM Client, it prompts me for a password. My question is How do I get the remote system to accept the new service and password without having to physically go over to the machine and log in? According to the documentation I have found on the Tivoli website, the above commands should be sufficient. Also, I have made sure that I am using an account with Admin rights on the remote system and there are no errors related to windows authentication or permissions. One last note is that if I run the dsmcutil showpw command, it returns the correct password from the remote system's registry. Thanks in Advance! Jim Neal System Engineer Lockheed Martin/ODIN MS T28D-4 Moffett Field, Ca 94035 (650) 604-1283
TSM Scheduler
Good Evening. I'm running TSM 5.2.2 server on a AIX 5.2 machine. I have clients running AIX 5.2, Windows 2000 and Windows 2003 with TSM 5.2.2 client. What I'm seeing is occasionally the clients that are running with a client schedule on the server don't kick off. All I see in the server activity log is that the clients missed their schedule, nothing about contacting the clients. Nothing shows up in the client logs so I assume they were never contacted. If I stop and start TSM it starts they all start running again. It does not happen often but 1 day when I 'm doing my daily checks none of the scheduled clients run. All the clients that don't run scheduled events run fine(cron job or windows scheduled event). Is there an easy way to get the scheduler running when it gets into this mode without stopping and starting TSM? On another note. Should we consider upgrading the server to a later version than 5.2.2 or stay at this version since it seems to be running well for the most part. I know in the past they tended to stay with 1 version and at some point TSM became unsupported which I don't want to get to that point. Also is their a later version of TSM(5.2.3, 5.2.4, other) that the clients should be running at, at this point. I know the question is some what general and open to personal preference but I was just looking for input. We are looking to bring in SOLARIS 10 and Linux and would like to avoid problems down the road. Thanks for all your help, Eric
Re: TSM Scheduler
Yes, you can create an admin schedule that runs a TSM script that tests the date, and decides yes/no force the client backup schedule on that day. Cleverer people than I have figured it out: http://msgs.adsm.org/cgi-bin/get/adsm0208/900.html -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Savva Sent: Wednesday, January 12, 2005 2:38 AM To: ADSM-L@VM.MARIST.EDU Subject: TSM Scheduler Importance: Low Hi to all, I am running a TSM server version 5.1.5.0 and TSM client version 5.1.5.0 on Windows 2000 platform. I have one question regarding Client Schedules. Is there any capability to schedule a client backup job to run the last day of every Month, Year via TSM scheduler? Thanks in advance Nicos Savva TSM Administrator
TSM Scheduler
Hi to all, I am running a TSM server version 5.1.5.0 and TSM client version 5.1.5.0 on Windows 2000 platform. I have one question regarding Client Schedules. Is there any capability to schedule a client backup job to run the last day of every Month, Year via TSM scheduler? Thanks in advance Nicos Savva TSM Administrator
Re: TSM Scheduler
schedule it thru the OS scheduler and call dsmc thru scripts Nicolas Savva [EMAIL PROTECTED] To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU TSM Scheduler 01/12/2005 15:07 Please respond to ADSM: Dist Stor Manager Hi to all, I am running a TSM server version 5.1.5.0 and TSM client version 5.1.5.0 on Windows 2000 platform. I have one question regarding Client Schedules. Is there any capability to schedule a client backup job to run the last day of every Month, Year via TSM scheduler? Thanks in advance Nicos Savva TSM Administrator
Re: TSM Scheduler
On Jan 12, 2005, at 9:37 AM, Nicolas Savva wrote: Is there any capability to schedule a client backup job to run the last day of every Month, Year via TSM scheduler? Download and read through the TSM 5.3 Technical Guide redbook, which describes the enhanced scheduling capabilities available in that release of the server. Until you get to 5.3, trying to accomplish that through classic scheduling isn't realistic. Richard Sims
0 bytes on optical drive when tsm scheduler service starts
Anyone has any experience with this? This is bit bizarre to me! Client tsm version 5.2, tsm server 5.2 Running on windows Apparently user experiencing problems everytime tsm scheduler service starts and their reports are written as 0 bytes, we disabled the snapshot agent on this This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et protege. L'expediteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) designe(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immediatement, par retour de courriel ou par un autre moyen.
TSM scheduler using the wrong IP address for a node
Hi there, we're using TSM 5.2.2.2 on AIX 5.2. The client is at 5.2.2.5, also on AIX 5.2. (Both 64 bit) I cloned a machine using mksysb. On the clone, I changed the IP address. I accidentally started the dsmcad process with an unchanged configuration. This caused the TSM server to update the information it has for that node. This was shown in a q nod tridev1 f=d. I stopped and disabled the TSM installation on the clone, and did a manual backup with the original machine. This worked fine, and both 'q nod tridev1 f=d' and select * from nodes where node_name='TRIDEV1' now show the correct IP address. However: the scheduler still insist on using the wrong IP address. Given the output of select * from nodes where node_name='TRIDEV1' below, how is this possible? NODE_NAME: TRIDEV1 PLATFORM_NAME: AIX DOMAIN_NAME: PD_TRIAS PWSET_TIME: 2003-10-29 14:27:10.00 INVALID_PW_COUNT: 0 CONTACT: COMPRESSION: CLIENT ARCHDELETE: YES BACKDELETE: NO LOCKED: NO LASTACC_TIME: 2004-04-23 09:22:21.00 REG_TIME: 2001-06-11 13:43:07.00 REG_ADMIN: MM LASTSESS_COMMMETH: Tcp/Ip LASTSESS_RECVD: 15210894 LASTSESS_SENT: 17493 LASTSESS_DURATION: +3.960900E+001 LASTSESS_IDLEWAIT: +1.43906687873968E-001 LASTSESS_COMMWAIT: +4.57724254588603E+000 LASTSESS_MEDIAWAIT: +0.00E+000 CLIENT_VERSION: 5 CLIENT_RELEASE: 2 CLIENT_LEVEL: 2 CLIENT_SUBLEVEL: 5 CLIENT_OS_LEVEL: 5.2 OPTION_SET: AGGREGATION: YES URL: http://tridev1.trias.nl:1581/ NODETYPE: CLIENT PASSEXP: KEEP_MP: NO MAX_MP_ALLOWED: 3 AUTO_FS_RENAME: NO VALIDATEPROTOCOL: NO TCP_NAME: tridev1 TCP_ADDRESS: 172.17.1.42 GUID: 05.50.1b.d0.d8.9e.11.d7.9b.74.08.63.ac.11.01.8b TXNGROUPMAX: 0 DATAWRITEPATH: ANY DATAREADPATH: ANY SESSION_INITIATION: ClientOrServer CLIENT_HLA: CLIENT_LLA: Only after executing UPD NOD TRIDEV1 HLADDRESS='172.17.1.42' LLADDRESS='1500', the scheduler used the correct address. There's also something wrong with UPDATE NODE: if you issue UPD NOD TRIDEV1 HLADDRESS='172.17.1.41' the response is Node updated, but that is in fact not the case. In the actlog an error is reported: 04/23/04 10:39:07 ANR2017I Administrator JOSKAM issued command: UPDATE NODE tridev1 hladdress=172.17.1.42 (SESSION: 26308) 04/23/04 10:39:07 ANR4739E Either the high level address ( 172.17.1.42 ), l ow level address( ? ), or both were entered in error. ( SESSION: 26308) 04/23/04 10:39:07 ANR2063I Node TRIDEV1 updated. (SESSION: 26308) You don't get to see the ANR4739E unless you look in the actlog. -- Jurjen Oskam Avoid putting a paging file on a fault-tolerant drive, such as a mirrored volume or a RAID-5 volume. Paging files do not need fault-tolerance. - 308417
TSM Scheduler under Windows XP
We have noticed that for at least some of our XP machines, the TSM scheduler does not appear to run unless the user is logged on. Because users here are asked to logoff before they go home once a week in order for windows security patches to be pushed to their machines, that means their pcs are not getting backed up that night (most backups here are scheduled for right before midnight). We have noticed similar behavior for McAfee antivirus -- scheduled virus checks don't occur unless the user is logged on, so it might not be a tsm specific issue. Has anyone else run into this, or is there something wrong with the way we have the scheduler service set up on our xp machines? Thanks.
Re: TSM Scheduler under Windows XP
Try reinstalling - logged in as the administrator. Try both domain and local administrator see if that clears up both problems. I've seen even when a user was in the administrator group but not the administrator that programs were run at the users security level. Sal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Klein, Robert (NIH/CIT) Sent: Wednesday, March 17, 2004 11:04 AM To: [EMAIL PROTECTED] Subject: TSM Scheduler under Windows XP We have noticed that for at least some of our XP machines, the TSM scheduler does not appear to run unless the user is logged on. Because users here are asked to logoff before they go home once a week in order for windows security patches to be pushed to their machines, that means their pcs are not getting backed up that night (most backups here are scheduled for right before midnight). We have noticed similar behavior for McAfee antivirus -- scheduled virus checks don't occur unless the user is logged on, so it might not be a tsm specific issue. Has anyone else run into this, or is there something wrong with the way we have the scheduler service set up on our xp machines? Thanks.
/ /OREF:CPT18245 Tsm Scheduler
I need with my tsm scheduler. It seems to be wasting alot of time... I am running TSM 5.1.6 across fibre, with 8 clients backing up to a 3583 LTO with 2 drives on a SAN. I stop and start my client schedulers the storage agents from cron. Often a scheduled event, which is due to start at 15:00 will only begin at 16:30 - despite the fact that it is the first scheduled event of the day and is not waiting for drives or resources. Here are my some settings taken from the dsm.sys on the client: errorlogretention 10,D PASSWORDACCESS GENERATE nodenamesapdev schedmode polling schedlogname/usr/tivoli/tsm/logs/dsmsched.log schedlogretention 4,D maxcmdretries 3 retryperiod10 queryschedperiod 1 Can anyone help? Cecily Hewlett AIX and TSM Administrator Cape Town
Re: / /OREF:CPT18245 Tsm Scheduler
Change schedmode to prompted on the client and restart the scheduler. With schedmode polling the start of schedule is dependent on the randomization setting on the TSM server (q sys). -Original Message- From: Cecily Hewlett [mailto:[EMAIL PROTECTED] Sent: vrijdag 5 maart 2004 10:09 To: [EMAIL PROTECTED] Subject: / /OREF:CPT18245 Tsm Scheduler I need with my tsm scheduler. It seems to be wasting alot of time... I am running TSM 5.1.6 across fibre, with 8 clients backing up to a 3583 LTO with 2 drives on a SAN. I stop and start my client schedulers the storage agents from cron. Often a scheduled event, which is due to start at 15:00 will only begin at 16:30 - despite the fact that it is the first scheduled event of the day and is not waiting for drives or resources. Here are my some settings taken from the dsm.sys on the client: errorlogretention 10,D PASSWORDACCESS GENERATE nodenamesapdev schedmode polling schedlogname/usr/tivoli/tsm/logs/dsmsched.log schedlogretention 4,D maxcmdretries 3 retryperiod10 queryschedperiod 1 Can anyone help? Cecily Hewlett AIX and TSM Administrator Cape Town
TSM SCHEDULER
Hi All, I have to schedule a periodic archive via http graphic interface in the description field I want to write: Title_of_Archive date where Title_of_Archive is a costant word date is the date at startup archive. how can I do it? Simone
Re: AIX startup of TSM scheduler
Hi, we also use only dsmcad as starter for the tsm scheduler. Here a script
that could help you for stopping, starting and restarting:
#!/usr/bin/sh
# rc.dsmcad , version 1.1
#
# description: start or restart client acceptor daemon
# constraints: must be run as root
# it will start dsmcad client acceptor daemon
#
# author : sh
# jesús muiño conde
#
# modifications:
# 23/06/2003 initial creation
# 23/06/2003 v1.1 Routed the log to /dev/null (PAN)
# ***
# some vars
# ---
YO=$(basename $0)
DSMCAD=dsmcad
DSM_DIR=/usr/tivoli/tsm/client/ba/bin
PS=/usr/bin/ps
KILL=/usr/bin/kill
#DSMCADLOG=/usr/tivoli/tsm/client/ba/bin/dsmwebcl.log
DSMCADLOG=/dev/null
NOHUP=/usr/bin/nohup
SLEEP=/usr/bin/sleep
# some funcs
# ---
stop_dsmcad()
{
while check_if_running
[[ -n $DSMCADPROC ]]
do
echo ${YO}: Killing TSM client acceptor daemon with signal KILL.
/usr/bin/kill -9 $DSMCADPROC
done
}
start_dsmcad()
{
echo ${YO}: Starting TSM client acceptor daemon ...
$NOHUP ${DSM_DIR}/$DSMCAD $DSMCADLOG 21
$SLEEP 5
check_if_running
echo ${YO}: ... scheduling will start in 1 minute.
}
check_if_running()
{
DSMCADPROC=$(ps -efo pid,command | awk '/'$DSMCAD'/ {print$1}' |
xargs)
if [[ -n $DSMCADPROC ]] then
echo ${YO}: TSM client acceptor daemon is running: PIDs
${DSMCADPROC}
fi
}
cmd_usage()
{
print \n\t$YO must be used as follows:
print \t$YO -[ s | q | r ]
print \t-s Starts the TSM client acceptor daemon.
print \t Should only be used through inittab
print \t Use in inittab: \dsmcad:2:once:/usr/local/bin/rc.dsmcad
-start /dev/console 21\
print \t-q Stops the TSM client acceptor daemon
print \t-r Stops and starts the TSM client acceptor daemon.\n
}
# main starts here
# ---
if [[ $# != 1 || $1 != '-'[sqr] ]] then
cmd_usage
exit 2
fi
while getopts sqr i
do
case $i in
s )
# just starts the TSM client acceptor daemon should only be used
when the system boots
# or in /etc/inittab
start_dsmcad
;;
q )
# just stops the TSM client acceptor daemon
stop_dsmcad
;;
r )
# the TSM client acceptor daemon is stopped and
# then re-started
stop_dsmcad
start_dsmcad
;;
? )
# short description how to use the command
cmd_usage
exit 2
;;
esac
done
exit 0
***
-Original Message-
From: Thomas Rupp, Vorarlberger Illwerke AG
[mailto:[EMAIL PROTECTED]
Sent: Thursday,8. January 2004 09:14
To: [EMAIL PROTECTED]
Subject: AW: AIX startup of TSM scheduler
All problems went away as soon as we began to let DSMCAD
start the scheduler.
Regards
Thomas Rupp
TSM scheduler not working with W2K Advanced Cluster
We seem to be having trouble with getting the scheduler service to run correctly with an Advanced Server cluster. Are there any guidelines or documents that would be useful, such as lessons learned, hot fixes and common problems that would help in troubleshooting? Thanks, Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell
Re: TSM scheduler not working with W2K Advanced Cluster
Questions, lots of questions. What level of patch are you on for W2K? What level of TSM client are you using? Did you follow the instructions in the TSM client for Windows manual concerning setting up cluster-aware services? Also, stating we're having problems without being specific about what those problems are (error messages, etc.) means that people will not be able to offer you much help. -- Mark Stapleton -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 08:40 To: [EMAIL PROTECTED] Cc: Subject: TSM scheduler not working with W2K Advanced Cluster We seem to be having trouble with getting the scheduler service to run correctly with an Advanced Server cluster. Are there any guidelines or documents that would be useful, such as lessons learned, hot fixes and common problems that would help in troubleshooting? Thanks, Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell
Re: TSM scheduler not working with W2K Advanced Cluster
I'm really looking for documents and general resources for TSM and Windows cluster setups. I will forward the error logs, unfortunately the error logs aren't revealing much in the way of a reason for the problem. We have had IBM working on this for a week now with no solution. Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 9:53 AM To: [EMAIL PROTECTED] Subject: Re: TSM scheduler not working with W2K Advanced Cluster Questions, lots of questions. What level of patch are you on for W2K? What level of TSM client are you using? Did you follow the instructions in the TSM client for Windows manual concerning setting up cluster-aware services? Also, stating we're having problems without being specific about what those problems are (error messages, etc.) means that people will not be able to offer you much help. -- Mark Stapleton -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 08:40 To: [EMAIL PROTECTED] Cc: Subject: TSM scheduler not working with W2K Advanced Cluster We seem to be having trouble with getting the scheduler service to run correctly with an Advanced Server cluster. Are there any guidelines or documents that would be useful, such as lessons learned, hot fixes and common problems that would help in troubleshooting? Thanks, Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell
Re: TSM scheduler not working with W2K Advanced Cluster
Read the TSM client for Windows manual. There is a chapter on cluster-based setups. -- Mark Stapleton ([EMAIL PROTECTED]) -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 09:01 To: [EMAIL PROTECTED] Cc: Subject: Re: TSM scheduler not working with W2K Advanced Cluster I'm really looking for documents and general resources for TSM and Windows cluster setups. I will forward the error logs, unfortunately the error logs aren't revealing much in the way of a reason for the problem. We have had IBM working on this for a week now with no solution. Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 9:53 AM To: [EMAIL PROTECTED] Subject: Re: TSM scheduler not working with W2K Advanced Cluster Questions, lots of questions. What level of patch are you on for W2K? What level of TSM client are you using? Did you follow the instructions in the TSM client for Windows manual concerning setting up cluster-aware services? Also, stating we're having problems without being specific about what those problems are (error messages, etc.) means that people will not be able to offer you much help. -- Mark Stapleton -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 08:40 To: [EMAIL PROTECTED] Cc: Subject: TSM scheduler not working with W2K Advanced Cluster We seem to be having trouble with getting the scheduler service to run correctly with an Advanced Server cluster. Are there any guidelines or documents that would be useful, such as lessons learned, hot fixes and common problems that would help in troubleshooting? Thanks, Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell
Re: TSM scheduler not working with W2K Advanced Cluster
When you state that you are having problems getting the services running, did you: 1) Get the clients installed and running on both machines independently 2) Install the services on each node for the cluster, using the shared storage device and get it running on both nodes 3) Once you add the service to the cluster it will run, but once you fail the cluster to the other node the service fails to come up? Mark -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 9:02 AM To: [EMAIL PROTECTED] Cc: Subject: Re: TSM scheduler not working with W2K Advanced Cluster Read the TSM client for Windows manual. There is a chapter on cluster-based setups. -- Mark Stapleton ([EMAIL PROTECTED]) -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 09:01 To: [EMAIL PROTECTED] Cc: Subject: Re: TSM scheduler not working with W2K Advanced Cluster I'm really looking for documents and general resources for TSM and Windows cluster setups. I will forward the error logs, unfortunately the error logs aren't revealing much in the way of a reason for the problem. We have had IBM working on this for a week now with no solution. Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 9:53 AM To: [EMAIL PROTECTED] Subject: Re: TSM scheduler not working with W2K Advanced Cluster Questions, lots of questions. What level of patch are you on for W2K? What level of TSM client are you using? Did you follow the instructions in the TSM client for Windows manual concerning setting up cluster-aware services? Also, stating we're having problems without being specific about what those problems are (error messages, etc.) means that people will not be able to offer you much help. -- Mark Stapleton -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Fri 1/9/2004 08:40 To: [EMAIL PROTECTED] Cc: Subject: TSM scheduler not working with W2K Advanced Cluster We seem to be having trouble with getting the scheduler service to run correctly with an Advanced Server cluster. Are there any guidelines or documents that would be useful, such as lessons learned, hot fixes and common problems that would help in troubleshooting? Thanks, Kenneth Bradberry Director, Technology and Infrastructure Superior Consultant Company (248) 226-4322 Office (313) 310-2724 Cell
AW: AIX startup of TSM scheduler
All problems went away as soon as we began to let DSMCAD start the scheduler. Regards Thomas Rupp
Re: AIX startup of TSM scheduler
To automate it if you have many tsm client backup schedulers on the same server you can use the: mkssys command to setup a subsystem, this way you can use the: startsrc and stopsrc commands to get the schedulers started and stopped. Thanks!. --Justin Richard Bleistein Unix/TSM Systems Administrator |-+ | | Prather, Wanda | | | [EMAIL PROTECTED]| | | UAPL.EDU| | | Sent by: ADSM: | | | Dist Stor| | | Manager | | | [EMAIL PROTECTED]| | | .EDU| | || | || | | 01/07/2004 04:39 | | | PM | | | Please respond to| | | ADSM: Dist Stor | | | Manager | | || |-+ ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: AIX startup of TSM scheduler | ---| This always works for me: nohup dsmc sched 21 /dev/null /dev/null -Original Message- From: Steven Pemberton [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 4:22 PM To: [EMAIL PROTECTED] Subject: Re: AIX startup of TSM scheduler I've found the following to work pretty well: (dsmc sched 21 /dev/null ) The parenthesis drop it into a sub-shell and cleanly detaches from your current session. Regards, Steven P. -- Steven Pemberton Senior Enterprise Management Consultant IBK, Senetas Group Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907 Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au
Re: AIX startup of TSM scheduler
Jack, Getting a manually invoked nohup-ed TSM scheduler to stick around in AIX has caused a few problems in the past - a look in the archives will probably reveal that. There's some funny thing that I seem to remember about redirected stdout nohup-ed processes dying - I recall that this seemed to work for me in the past: # nohup dsmc sched /dev/null /dev/null 21 Or, manually open a new shell: # ksh # nohup dsmc sched /dev/null 21 # exit And just check with a `ps -ef` to ensure the dsmc sched is still present... Hope this helps, Rgds, David McClelland Global Management Systems Reuters 85 Fleet Street London EC4P 4AJ -Original Message- From: Coats, Jack [mailto:[EMAIL PROTECTED] Sent: 07 January 2004 01:46 To: [EMAIL PROTECTED] Subject: AIX startup of TSM scheduler Ok, I am showing my old age/lack of memory/in-experience in this area, but: I need to reset the passwords for a couple AIX clients. Where do I start up the scheduler on these machines? (AIX 4.3.3) How do I do an elequent kind of thing to do: nohup dsmc sched or whatever to restart the scheduler by hand (rather than rebooting)? ... TIA ... JC --- - 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: AIX startup of TSM scheduler
Hello, Under AIX I don't think I've ever had any trouble with; #nohup dsmc sched 21 /dev/null #exit #bg #exit But I would be interested if anyone can tell me why #nohup dsmc sched 21 /dev/null #bg #exit doesn't work...why do you _have_ to say #exit #bg #exit ? Thanks, Matt. -Original Message- From: David McClelland [EMAIL PROTECTED]@EME Sent: Wednesday, January 07, 2004 9:23 AM To: [EMAIL PROTECTED] Subject: Re: AIX startup of TSM scheduler Jack, Getting a manually invoked nohup-ed TSM scheduler to stick around in AIX has caused a few problems in the past - a look in the archives will probably reveal that. There's some funny thing that I seem to remember about redirected stdout nohup-ed processes dying - I recall that this seemed to work for me in the past: # nohup dsmc sched /dev/null /dev/null 21 Or, manually open a new shell: # ksh # nohup dsmc sched /dev/null 21 # exit And just check with a `ps -ef` to ensure the dsmc sched is still present... Hope this helps, Rgds, David McClelland Global Management Systems Reuters 85 Fleet Street London EC4P 4AJ -Original Message- From: Coats, Jack [mailto:[EMAIL PROTECTED] Sent: 07 January 2004 01:46 To: [EMAIL PROTECTED] Subject: AIX startup of TSM scheduler Ok, I am showing my old age/lack of memory/in-experience in this area, but: I need to reset the passwords for a couple AIX clients. Where do I start up the scheduler on these machines? (AIX 4.3.3) How do I do an elequent kind of thing to do: nohup dsmc sched or whatever to restart the scheduler by hand (rather than rebooting)? ... TIA ... JC --- - 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. ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore the Powergen Group does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Powergen Group. Registered addresses: Powergen UK plc, 53 New Broad Street, London, EC2M 1SL Registered in England Wales No. 2366970 Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: AIX startup of TSM scheduler
Hi, In the past we too have seen problems with the scheduler daemon not honouring a nohup under Solaris, HPUX, and AIX. We have found that using at on unix-type systems causes the least problems. So, our (ksh) startup files tend to look something like this, and can be called during init, or from the command line... if ! pgrep -f dsmc sched -se.*=$server /dev/null 21 then print /bin/dsmc sched -se=$server /dev/null 21 /dev/null | at now print started dsmc sched through 'at' fi (pgrep is Solaris specific. Amend as required) Regards, -=Dave=- Sungard Vaulting Services +44 (0) 20 7608 7140 Warren, Matthew (Retail) To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RGEN.CO.UK Subject: Re: AIX startup of TSM scheduler Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] U 07/01/2004 10:15 Please respond to ADSM: Dist Stor Manager Hello, Under AIX I don't think I've ever had any trouble with; #nohup dsmc sched 21 /dev/null #exit #bg #exit But I would be interested if anyone can tell me why #nohup dsmc sched 21 /dev/null #bg #exit doesn't work...why do you _have_ to say #exit #bg #exit ? Thanks, Matt. -Original Message- From: David McClelland [EMAIL PROTECTED]@EME Sent: Wednesday, January 07, 2004 9:23 AM To: [EMAIL PROTECTED] Subject: Re: AIX startup of TSM scheduler Jack, Getting a manually invoked nohup-ed TSM scheduler to stick around in AIX has caused a few problems in the past - a look in the archives will probably reveal that. There's some funny thing that I seem to remember about redirected stdout nohup-ed processes dying - I recall that this seemed to work for me in the past: # nohup dsmc sched /dev/null /dev/null 21 Or, manually open a new shell: # ksh # nohup dsmc sched /dev/null 21 # exit And just check with a `ps -ef` to ensure the dsmc sched is still present... Hope this helps, Rgds, David McClelland Global Management Systems Reuters 85 Fleet Street London EC4P 4AJ -Original Message- From: Coats, Jack [mailto:[EMAIL PROTECTED] Sent: 07 January 2004 01:46 To: [EMAIL PROTECTED] Subject: AIX startup of TSM scheduler Ok, I am showing my old age/lack of memory/in-experience in this area, but: I need to reset the passwords for a couple AIX clients. Where do I start up the scheduler on these machines? (AIX 4.3.3) How do I do an elequent kind of thing to do: nohup dsmc sched or whatever to restart the scheduler by hand (rather than rebooting)? ... TIA ... JC --- - 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. ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore the Powergen Group does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Powergen Group. Registered addresses: Powergen UK plc, 53 New Broad Street, London, EC2M 1SL Registered in England Wales No. 2366970 Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: AIX startup of TSM scheduler
If you have screen installed just start up a screen session and run: dsmc sched Then Ctrl-A , Ctrl-D If you need to get back into the screen: screen -R Coats, Jack wrote: Ok, I am showing my old age/lack of memory/in-experience in this area, but: I need to reset the passwords for a couple AIX clients. Where do I start up the scheduler on these machines? (AIX 4.3.3) How do I do an elequent kind of thing to do: nohup dsmc sched or whatever to restart the scheduler by hand (rather than rebooting)? ... TIA ... JC
Re: AIX startup of TSM scheduler
I've found the following to work pretty well: (dsmc sched 21 /dev/null ) The parenthesis drop it into a sub-shell and cleanly detaches from your current session. Regards, Steven P. -- Steven Pemberton Senior Enterprise Management Consultant IBK, Senetas Group Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907 Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au
Re: AIX startup of TSM scheduler
This always works for me: nohup dsmc sched 21 /dev/null /dev/null -Original Message- From: Steven Pemberton [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 4:22 PM To: [EMAIL PROTECTED] Subject: Re: AIX startup of TSM scheduler I've found the following to work pretty well: (dsmc sched 21 /dev/null ) The parenthesis drop it into a sub-shell and cleanly detaches from your current session. Regards, Steven P. -- Steven Pemberton Senior Enterprise Management Consultant IBK, Senetas Group Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907 Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au
Re: AIX startup of TSM scheduler
Hot Diggety! Prather, Wanda was rumored to have written:
This always works for me:
nohup dsmc sched 21 /dev/null /dev/null
Alternatively, drop this one liner in /etc/inittab on an AIX system:
dsmc::respawn:/usr/bin/dsmc sched -password=quiet /dev/null 21
(It is usually preferrable to put this at or near the very end of the file)
Then do:
# kill -HUP 1
(to make inittab aware)
Subsequently, if you want to force the scheduler to update, it's just a
matter of kill -9'ing the 'dsmc sched' process ID and inittab would
automatically respawn a fresh copy of the dsmc scheduler.
For instance:
# kill -9 `ps -ef|grep '/usr/bin/dsmc sched'|grep -v grep|awk '{print $2}'`
This general approach works if you've got the client password stored as an
encrypted hash in a file locally... if you have a setup that requires
someone to manually enter the password every time, then this may not be a
suitable approach (use of inittab to respawn).
-Dan
AIX startup of TSM scheduler
Ok, I am showing my old age/lack of memory/in-experience in this area, but: I need to reset the passwords for a couple AIX clients. Where do I start up the scheduler on these machines? (AIX 4.3.3) How do I do an elequent kind of thing to do: nohup dsmc sched or whatever to restart the scheduler by hand (rather than rebooting)? ... TIA ... JC
Re: AIX startup of TSM scheduler
I usually put the startup in /etc/rc.local, but you can put it in /etc/inittab (not respawn), or /etc/rc.tcpip. As root, to restart the sched process and detach it: # sh -c /bin/dsmc sched /dev/null 21 If placing in an rc file, remember to background it '', probably the inittab as well. hope this helps. bob On Tue, Jan 06, 2004 at 07:45:50PM -0600, Coats, Jack wrote: Ok, I am showing my old age/lack of memory/in-experience in this area, but: I need to reset the passwords for a couple AIX clients. Where do I start up the scheduler on these machines? (AIX 4.3.3) How do I do an elequent kind of thing to do: nohup dsmc sched or whatever to restart the scheduler by hand (rather than rebooting)? ... TIA ... JC
Re: TSM Scheduler not contacting clients
I noticed that difference also. I am running AIX 5.1 ML3. The card in question is a gigabit card. Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] [EMAIL PROTECTED] LE.EDU To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: TSM Scheduler not contacting clients EDU 04/10/2003 02:33 Please respond to ADSM-L What version of aix are you running? I'm running aix 5.1. Your netstat -v output is different than mine. After: IBM 10/100 Mbps Ethernet PCI Adapter Specific Statistics: Chip Version: 25 RJ45 Port Link Status : down Media Speed Selected: Auto negotiation Media Speed Running: Unknown I get: Receive Pool Buffer Size: 384 Free Receive Pool Buffers: 128 No Receive Pool Buffer Errors: 0 but I don't see the Receive Pool Buffer lines in your output. Those are the lines that tell you whether you have the error I had. David [EMAIL PROTECTED] 10/3/2003 6:45:22 AM My netstat shows no errors. I'm not sure if it's this particular problem. 1:[EMAIL PROTECTED]:/home/root # netstat -v ent0 - ETHERNET STATISTICS (ent0) : Device Type: IBM 10/100/1000 Base-T Ethernet PCI Adapter (14100401) Hardware Address: 00:06:29:6b:5d:30 Elapsed Time: 19 days 21 hours 1 minutes 59 seconds Transmit Statistics: Receive Statistics: --- Packets: 968722735Packets: 2738698376 Bytes: 122708764323 Bytes: 3883111224538 Interrupts: 5777133 Interrupts: 973619783 Transmit Errors: 0Receive Errors: 0 Packets Dropped: 0Packets Dropped: 0 Bad Packets: 0 Max Packets on S/W Transmit Queue: 126 S/W Transmit Queue Overflow: 0 Current S/W+H/W Transmit Queue Length: 0 Broadcast Packets: 12232 Broadcast Packets: 6240805 Multicast Packets: 2 Multicast Packets: 2 No Carrier Sense: 0 CRC Errors: 0 DMA Underrun: 0 DMA Overrun: 0 Lost CTS Errors: 0Alignment Errors: 0 Max Collision Errors: 0 No Resource Errors: 194 Late Collision Errors: 0 Receive Collision Errors: 0 Deferred: 0 Packet Too Short Errors: 0 SQE Test: 0 Packet Too Long Errors: 0 Timeout Errors: 0 Packets Discarded by Adapter: 0 Single Collision Count: 0 Receiver Start Count: 0 Multiple Collision Count: 0 Current HW Transmit Queue Length: 0 General Statistics: --- No mbuf Errors: 0 Adapter Reset Count: 0 Adapter Data Rate: 2000 Driver Flags: Up Broadcast Running Simplex AlternateAddress 64BitSupport PrivateSegment DataRateSet Adapter Specific Statistics: Additional Driver Flags: Autonegotiate Entries to transmit timeout routine: 0 Firmware Level: 13.0.5 Transmit and Receive Flow Control Status: Disabled Link Status: Up Media Speed Selected: Autonegotiation Media Speed Running: 1000 Mbps Full Duplex Packets with Transmit collisions: 1 collisions: 0 6 collisions: 0 11 collisions: 0 2 collisions: 0 7 collisions: 0 12 collisions: 0 3 collisions: 0 8 collisions: 0 13 collisions: 0 4 collisions: 0 9 collisions: 0 14 collisions: 0 5 collisions: 0 10 collisions: 0 15 collisions: 0 -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: bcc: Subject:Re: TSM Scheduler not contacting clients [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 10/02/2003 12:45 PM AST Please respond to ADSM-Lfont size=-1/font There was a major bug in Aix 5.1 64 bit mode tcp that caused major slowdowns in backups. It was apar IY36925 fixed in bos.net.tcp.client 5.1.0.37. The receive buffer problem occurred with that fix already in place. David Ehresman [EMAIL PROTECTED] 10/2/2003 12:27:02 PM On Thu, 2 Oct 2003 09:56:38 -0400 David E Ehresman [EMAIL PROTECTED] wrote: Now this makes some bells ring over here. IIRC there was some bug in the AIX 5.1 TCP code, which in particular would shouw on TSM servers. I don't know what
Re: TSM Scheduler not contacting clients
devices.pci.bla output:
devices.pci.23100020.diag
5.1.0.35C FIBM PCI 10/100 Mb Ethernet
Adapter (23100020) Diagnostics
no -a output from the server. Most of our clients are Solaris and NT.
hkgiicorep1:/root# goto hkgintsmsp1 no -a
extendednetstats = 0
thewall = 524264
sockthresh = 85
sb_max = 1048576
somaxconn = 1024
clean_partial_conns = 0
net_malloc_police = 0
rto_low = 1
rto_high = 64
rto_limit = 7
rto_length = 13
inet_stack_size = 16
arptab_bsiz = 7
arptab_nb = 25
tcp_ndebug = 100
ifsize = 8
arpqsize = 12
ndpqsize = 50
route_expire = 1
send_file_duration = 300
fasttimo = 200
routerevalidate = 0
dgd_packets_lost = 3
dgd_retry_time = 5
dgd_ping_time = 5
passive_dgd = 0
sodebug = 0
nbc_limit = 393192
nbc_max_cache = 131072
nbc_min_cache = 1
nbc_pseg = 0
nbc_pseg_limit = 524264
strmsgsz = 0
strctlsz = 1024
nstrpush = 8
strthresh = 85
psetimers = 20
psebufcalls = 20
strturncnt = 15
pseintrstack = 12288
lowthresh = 90
medthresh = 95
psecache = 1
subnetsarelocal = 1
maxttl = 255
ipfragttl = 60
ipsendredirects = 1
ipforwarding = 0
udp_ttl = 30
tcp_ttl = 60
arpt_killc = 20
tcp_sendspace = 16384
tcp_recvspace = 16384
udp_sendspace = 9216
udp_recvspace = 42080
tcp_bad_port_limit = 0
udp_bad_port_limit = 0
rfc1122addrchk = 0
nonlocsrcroute = 0
tcp_keepintvl = 150
tcp_keepidle = 14400
bcastping = 0
udpcksum = 1
tcp_mssdflt = 512
icmpaddressmask = 0
tcp_keepinit = 150
ie5_old_multicast_mapping = 0
rfc1323 = 0
pmtu_default_age = 10
pmtu_rediscover_interval = 30
udp_pmtu_discover = 0
tcp_pmtu_discover = 0
ipqmaxlen = 100
directed_broadcast = 0
ipignoreredirects = 0
ipsrcroutesend = 1
ipsrcrouterecv = 0
ipsrcrouteforward = 1
ip6srcrouteforward = 1
ip6_defttl = 64
ndpt_keep = 120
ndpt_reachable = 30
ndpt_retrans = 1
ndpt_probe = 5
ndpt_down = 3
ndp_umaxtries = 3
ndp_mmaxtries = 3
ip6_prune = 2
ip6forwarding = 0
multi_homed = 1
main_if6 = 0
main_site6 = 0
site6_index = 0
maxnip6q = 20
llsleep_timeout = 3
tcp_timewait = 1
tcp_ephemeral_low = 32768
tcp_ephemeral_high = 65535
udp_ephemeral_low = 32768
udp_ephemeral_high = 65535
delayack = 0
delayackports = {}
sack = 0
use_isno = 1
tcp_newreno = 1
tcp_nagle_limit = 65535
rfc2414 = 0
tcp_init_window = 0
tcp_ecn = 0
tcp_limited_transmit = 1
icmp6_errmsg_rate = 10
tcp_maxburst = 0
tcp_nodelayack = 0
tcp_finwait2 = 1200
hkgiicorep1:/root#?
--
Mark Ferraretto
Unix Systems Administrator
Deutsche Bank Hong Kong
w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971
[EMAIL PROTECTED]
[EMAIL PROTECTED]
.NET To: [EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED]Subject: Re: TSM Scheduler not
contacting clients
EDU
Re: TSM Scheduler not contacting clients
Mark, I'd like you to do the following to see if we can fix the problem
you're having:
1. Apply the fix for APAR IY46228. (fileset bos.net.tcp.client
5.1.0.54)
2. I would also make the following changes to your network options:
no -o thewall=1058576
no -o rfc1323=1
no -o tcp_sendspace=65536
no -o tcp_recvspace=65536
no -o tcp_mssdflt=1448
no -o tcp_nodelayack=1
LET ME KNOW IF THIS WORKS (Please).
At 06:15 PM 10/6/2003 +0800, you wrote:
devices.pci.bla output:
devices.pci.23100020.diag
5.1.0.35C FIBM PCI 10/100 Mb Ethernet
Adapter (23100020)
Diagnostics
no -a output from the server. Most of our clients are Solaris and NT.
hkgiicorep1:/root# goto hkgintsmsp1 no -a
extendednetstats = 0
thewall = 524264
sockthresh = 85
sb_max = 1048576
somaxconn = 1024
clean_partial_conns = 0
net_malloc_police = 0
rto_low = 1
rto_high = 64
rto_limit = 7
rto_length = 13
inet_stack_size = 16
arptab_bsiz = 7
arptab_nb = 25
tcp_ndebug = 100
ifsize = 8
arpqsize = 12
ndpqsize = 50
route_expire = 1
send_file_duration = 300
fasttimo = 200
routerevalidate = 0
dgd_packets_lost = 3
dgd_retry_time = 5
dgd_ping_time = 5
passive_dgd = 0
sodebug = 0
nbc_limit = 393192
nbc_max_cache = 131072
nbc_min_cache = 1
nbc_pseg = 0
nbc_pseg_limit = 524264
strmsgsz = 0
strctlsz = 1024
nstrpush = 8
strthresh = 85
psetimers = 20
psebufcalls = 20
strturncnt = 15
pseintrstack = 12288
lowthresh = 90
medthresh = 95
psecache = 1
subnetsarelocal = 1
maxttl = 255
ipfragttl = 60
ipsendredirects = 1
ipforwarding = 0
udp_ttl = 30
tcp_ttl = 60
arpt_killc = 20
tcp_sendspace = 16384
tcp_recvspace = 16384
udp_sendspace = 9216
udp_recvspace = 42080
tcp_bad_port_limit = 0
udp_bad_port_limit = 0
rfc1122addrchk = 0
nonlocsrcroute = 0
tcp_keepintvl = 150
tcp_keepidle = 14400
bcastping = 0
udpcksum = 1
tcp_mssdflt = 512
icmpaddressmask = 0
tcp_keepinit = 150
ie5_old_multicast_mapping = 0
rfc1323 = 0
pmtu_default_age = 10
pmtu_rediscover_interval = 30
udp_pmtu_discover = 0
tcp_pmtu_discover = 0
ipqmaxlen = 100
directed_broadcast = 0
ipignoreredirects = 0
ipsrcroutesend = 1
ipsrcrouterecv = 0
ipsrcrouteforward = 1
ip6srcrouteforward = 1
ip6_defttl = 64
ndpt_keep = 120
ndpt_reachable = 30
ndpt_retrans = 1
ndpt_probe = 5
ndpt_down = 3
ndp_umaxtries = 3
ndp_mmaxtries = 3
ip6_prune = 2
ip6forwarding = 0
multi_homed = 1
main_if6 = 0
main_site6 = 0
site6_index = 0
maxnip6q = 20
llsleep_timeout = 3
tcp_timewait = 1
tcp_ephemeral_low = 32768
tcp_ephemeral_high = 65535
udp_ephemeral_low = 32768
udp_ephemeral_high = 65535
delayack = 0
delayackports = {}
sack = 0
use_isno = 1
tcp_newreno = 1
tcp_nagle_limit = 65535
rfc2414 = 0
tcp_init_window = 0
tcp_ecn = 0
tcp_limited_transmit = 1
icmp6_errmsg_rate = 10
tcp_maxburst = 0
tcp_nodelayack = 0
tcp_finwait2 = 1200
hkgiicorep1:/root#
--
Mark Ferraretto
Unix Systems Administrator
Deutsche Bank Hong Kong
w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971
[EMAIL PROTECTED]
[EMAIL PROTECTED]
.NET To:
[EMAIL PROTECTED]
Sent
by: cc:
[EMAIL PROTECTED]Subject: Re: TSM
Scheduler not contacting clients
EDU
04/10/2003
02:32
Please respond
Re: TSM Scheduler not contacting clients
My netstat shows no errors. I'm not sure if it's this particular problem. 1:[EMAIL PROTECTED]:/home/root # netstat -v ent0 - ETHERNET STATISTICS (ent0) : Device Type: IBM 10/100/1000 Base-T Ethernet PCI Adapter (14100401) Hardware Address: 00:06:29:6b:5d:30 Elapsed Time: 19 days 21 hours 1 minutes 59 seconds Transmit Statistics: Receive Statistics: --- Packets: 968722735Packets: 2738698376 Bytes: 122708764323 Bytes: 3883111224538 Interrupts: 5777133 Interrupts: 973619783 Transmit Errors: 0Receive Errors: 0 Packets Dropped: 0Packets Dropped: 0 Bad Packets: 0 Max Packets on S/W Transmit Queue: 126 S/W Transmit Queue Overflow: 0 Current S/W+H/W Transmit Queue Length: 0 Broadcast Packets: 12232 Broadcast Packets: 6240805 Multicast Packets: 2 Multicast Packets: 2 No Carrier Sense: 0 CRC Errors: 0 DMA Underrun: 0 DMA Overrun: 0 Lost CTS Errors: 0Alignment Errors: 0 Max Collision Errors: 0 No Resource Errors: 194 Late Collision Errors: 0 Receive Collision Errors: 0 Deferred: 0 Packet Too Short Errors: 0 SQE Test: 0 Packet Too Long Errors: 0 Timeout Errors: 0 Packets Discarded by Adapter: 0 Single Collision Count: 0 Receiver Start Count: 0 Multiple Collision Count: 0 Current HW Transmit Queue Length: 0 General Statistics: --- No mbuf Errors: 0 Adapter Reset Count: 0 Adapter Data Rate: 2000 Driver Flags: Up Broadcast Running Simplex AlternateAddress 64BitSupport PrivateSegment DataRateSet Adapter Specific Statistics: Additional Driver Flags: Autonegotiate Entries to transmit timeout routine: 0 Firmware Level: 13.0.5 Transmit and Receive Flow Control Status: Disabled Link Status: Up Media Speed Selected: Autonegotiation Media Speed Running: 1000 Mbps Full Duplex Packets with Transmit collisions: 1 collisions: 0 6 collisions: 0 11 collisions: 0 2 collisions: 0 7 collisions: 0 12 collisions: 0 3 collisions: 0 8 collisions: 0 13 collisions: 0 4 collisions: 0 9 collisions: 0 14 collisions: 0 5 collisions: 0 10 collisions: 0 15 collisions: 0 -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: bcc: Subject:Re: TSM Scheduler not contacting clients [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 10/02/2003 12:45 PM AST Please respond to ADSM-Lfont size=-1/font There was a major bug in Aix 5.1 64 bit mode tcp that caused major slowdowns in backups. It was apar IY36925 fixed in bos.net.tcp.client 5.1.0.37. The receive buffer problem occurred with that fix already in place. David Ehresman [EMAIL PROTECTED] 10/2/2003 12:27:02 PM On Thu, 2 Oct 2003 09:56:38 -0400 David E Ehresman [EMAIL PROTECTED] wrote: Now this makes some bells ring over here. IIRC there was some bug in the AIX 5.1 TCP code, which in particular would shouw on TSM servers. I don't know what it was any more, nor what the fix is (It was just smalltalk with some engeneer once). You might want to check the APAR DB I had that problem and it was a aix tcp tuning issue. Do a netstat -v ent1 | grep Receive Pool Buffer where ent1 is the adaptor that your tsm traffic runs on. If your No Receive Pool Buffer Errors: line is greater than zero you have the same problem I had. We raised our receive pool buffer size up to 2048 and that fixed our problem. The ethernet adaptor has to be down to change the setting. The command is: chdev -l entx -a rxbuf_pool_size=2048 where x is the adaptor name. David Ehresman University of Louisville [EMAIL PROTECTED] 10/1/2003 8:21:01 PM All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. Halting TSM and restarting it seems to fix it for a few days and then it will start again. Checking the actlog, I stop seeing 'Schedule prompter contacting...' messages. And, of course, the following day I see a whole stack of 'Missed' backups. Sometimes the prompter may contact one or two (out of about 100) systems before stopping altogether. We have 100 Nodes - 50 Unix (Solaris
Re: TSM Scheduler not contacting clients
On Fri, 3 Oct 2003 08:21:45 +0800 Mark Ferraretto [EMAIL PROTECTED] wrote: All, Thanks for this info. We'll patch our AIX box and report the results. I'm curious about one thing though. If it's an AIX problem, why does shutting down the TSM server (not AIX) and restarting it fix the problem? Because that was the nature of this bug... Mark -- 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: TSM Scheduler not contacting clients
I had that problem and it was a aix tcp tuning issue. Do a netstat -v ent1 | grep Receive Pool Buffer where ent1 is the adaptor that your tsm traffic runs on. If your No Receive Pool Buffer Errors: line is greater than zero you have the same problem I had. We raised our receive pool buffer size up to 2048 and that fixed our problem. The ethernet adaptor has to be down to change the setting. The command is: chdev -l entx -a rxbuf_pool_size=2048 where x is the adaptor name. David Ehresman University of Louisville [EMAIL PROTECTED] 10/1/2003 8:21:01 PM All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. Halting TSM and restarting it seems to fix it for a few days and then it will start again. Checking the actlog, I stop seeing 'Schedule prompter contacting...' messages. And, of course, the following day I see a whole stack of 'Missed' backups. Sometimes the prompter may contact one or two (out of about 100) systems before stopping altogether. We have 100 Nodes - 50 Unix (Solaris/Linux/AIX) and 50 NT/2000 systems. All are running file-based backups. We also have a single Notes server (NT) that's backed up using TDP. All are in prompted mode. I haven't been able to find any error messages in the TSM log. Just an absence of prompter messages like I said before. Can anyone help? Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: TSM Scheduler not contacting clients
On Thu, 2 Oct 2003 09:56:38 -0400 David E Ehresman [EMAIL PROTECTED] wrote: Now this makes some bells ring over here. IIRC there was some bug in the AIX 5.1 TCP code, which in particular would shouw on TSM servers. I don't know what it was any more, nor what the fix is (It was just smalltalk with some engeneer once). You might want to check the APAR DB I had that problem and it was a aix tcp tuning issue. Do a netstat -v ent1 | grep Receive Pool Buffer where ent1 is the adaptor that your tsm traffic runs on. If your No Receive Pool Buffer Errors: line is greater than zero you have the same problem I had. We raised our receive pool buffer size up to 2048 and that fixed our problem. The ethernet adaptor has to be down to change the setting. The command is: chdev -l entx -a rxbuf_pool_size=2048 where x is the adaptor name. David Ehresman University of Louisville [EMAIL PROTECTED] 10/1/2003 8:21:01 PM All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. Halting TSM and restarting it seems to fix it for a few days and then it will start again. Checking the actlog, I stop seeing 'Schedule prompter contacting...' messages. And, of course, the following day I see a whole stack of 'Missed' backups. Sometimes the prompter may contact one or two (out of about 100) systems before stopping altogether. We have 100 Nodes - 50 Unix (Solaris/Linux/AIX) and 50 NT/2000 systems. All are running file-based backups. We also have a single Notes server (NT) that's backed up using TDP. All are in prompted mode. I haven't been able to find any error messages in the TSM log. Just an absence of prompter messages like I said before. Can anyone help? Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- 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: TSM Scheduler not contacting clients
There was a major bug in Aix 5.1 64 bit mode tcp that caused major slowdowns in backups. It was apar IY36925 fixed in bos.net.tcp.client 5.1.0.37. The receive buffer problem occurred with that fix already in place. David Ehresman [EMAIL PROTECTED] 10/2/2003 12:27:02 PM On Thu, 2 Oct 2003 09:56:38 -0400 David E Ehresman [EMAIL PROTECTED] wrote: Now this makes some bells ring over here. IIRC there was some bug in the AIX 5.1 TCP code, which in particular would shouw on TSM servers. I don't know what it was any more, nor what the fix is (It was just smalltalk with some engeneer once). You might want to check the APAR DB I had that problem and it was a aix tcp tuning issue. Do a netstat -v ent1 | grep Receive Pool Buffer where ent1 is the adaptor that your tsm traffic runs on. If your No Receive Pool Buffer Errors: line is greater than zero you have the same problem I had. We raised our receive pool buffer size up to 2048 and that fixed our problem. The ethernet adaptor has to be down to change the setting. The command is: chdev -l entx -a rxbuf_pool_size=2048 where x is the adaptor name. David Ehresman University of Louisville [EMAIL PROTECTED] 10/1/2003 8:21:01 PM All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. Halting TSM and restarting it seems to fix it for a few days and then it will start again. Checking the actlog, I stop seeing 'Schedule prompter contacting...' messages. And, of course, the following day I see a whole stack of 'Missed' backups. Sometimes the prompter may contact one or two (out of about 100) systems before stopping altogether. We have 100 Nodes - 50 Unix (Solaris/Linux/AIX) and 50 NT/2000 systems. All are running file-based backups. We also have a single Notes server (NT) that's backed up using TDP. All are in prompted mode. I haven't been able to find any error messages in the TSM log. Just an absence of prompter messages like I said before. Can anyone help? Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- 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: TSM Scheduler not contacting clients
All, Thanks for this info. We'll patch our AIX box and report the results. I'm curious about one thing though. If it's an AIX problem, why does shutting down the TSM server (not AIX) and restarting it fix the problem? Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] [EMAIL PROTECTED] LE.EDU To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: TSM Scheduler not contacting clients EDU 03/10/2003 00:45 Please respond to ADSM-L There was a major bug in Aix 5.1 64 bit mode tcp that caused major slowdowns in backups. It was apar IY36925 fixed in bos.net.tcp.client 5.1.0.37. The receive buffer problem occurred with that fix already in place. David Ehresman [EMAIL PROTECTED] 10/2/2003 12:27:02 PM On Thu, 2 Oct 2003 09:56:38 -0400 David E Ehresman [EMAIL PROTECTED] wrote: Now this makes some bells ring over here. IIRC there was some bug in the AIX 5.1 TCP code, which in particular would shouw on TSM servers. I don't know what it was any more, nor what the fix is (It was just smalltalk with some engeneer once). You might want to check the APAR DB I had that problem and it was a aix tcp tuning issue. Do a netstat -v ent1 | grep Receive Pool Buffer where ent1 is the adaptor that your tsm traffic runs on. If your No Receive Pool Buffer Errors: line is greater than zero you have the same problem I had. We raised our receive pool buffer size up to 2048 and that fixed our problem. The ethernet adaptor has to be down to change the setting. The command is: chdev -l entx -a rxbuf_pool_size=2048 where x is the adaptor name. David Ehresman University of Louisville [EMAIL PROTECTED] 10/1/2003 8:21:01 PM All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. Halting TSM and restarting it seems to fix it for a few days and then it will start again. Checking the actlog, I stop seeing 'Schedule prompter contacting...' messages. And, of course, the following day I see a whole stack of 'Missed' backups. Sometimes the prompter may contact one or two (out of about 100) systems before stopping altogether. We have 100 Nodes - 50 Unix (Solaris/Linux/AIX) and 50 NT/2000 systems. All are running file-based backups. We also have a single Notes server (NT) that's backed up using TDP. All are in prompted mode. I haven't been able to find any error messages in the TSM log. Just an absence of prompter messages like I said before. Can anyone help? Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
TSM Scheduler not contacting clients
All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. Halting TSM and restarting it seems to fix it for a few days and then it will start again. Checking the actlog, I stop seeing 'Schedule prompter contacting...' messages. And, of course, the following day I see a whole stack of 'Missed' backups. Sometimes the prompter may contact one or two (out of about 100) systems before stopping altogether. We have 100 Nodes - 50 Unix (Solaris/Linux/AIX) and 50 NT/2000 systems. All are running file-based backups. We also have a single Notes server (NT) that's backed up using TDP. All are in prompted mode. I haven't been able to find any error messages in the TSM log. Just an absence of prompter messages like I said before. Can anyone help? Mark -- Mark Ferraretto Unix Systems Administrator Deutsche Bank Hong Kong w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971 [EMAIL PROTECTED] -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: TSM Scheduler not contacting clients
Hey Mark, Could your TSM server be running out of sessions (as per MAX SESSIONS?) - perhaps you have tape mounts holding running sessions, (thus holding their completion for new sessions)? The prompter will only contact nodes when it has session slots available during the backup startup window. ...deon ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/10/2003 10:21:01 AM: All, I am running TSM 5.1.6.1 on AIX 5.1ML3. In the last few weeks it's started exhibiting a rather strange problem where the scheduler seems not to contact the clients to start the backup schedule. ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli
TSM Scheduler service terminated unexpectedly
I have the 5.1.5.0 client running locally on a W2K (SP3) server. The backup of this client is generally less than 1Gb per day, but the TSM scheduler service on that client regularly terminates unexpectedly with the following error in the W2K event log: Event Type:Error Event Source: Service Control Manager Event Category: None Event ID: 7031 Date: 09/26/2003 Time: 8:04:38 PM User: N/A Computer: FILESERVER Description: The TSM Scheduler service terminated unexpectedly. It has done this 22 time(s). The following corrective action will be taken in 0 milliseconds: No action. ANY IDEAS???
Re: TSM Scheduler service terminated unexpectedly
I started getting this on a W2k server, too, running a 5.1.5.0 client. The server had been successfully backing up since June and the scheduler was still working, just didn't work for backups. I could still run ACT=COMMAND scheduled through it. The GUI and command line would similarly fail when trying to do a backup. I ended up just upgrading to a 5.1.6.7 client version and it's working fine now. But then it was working fine before, too! :-) The owner of the box said that a new application was installed right before the problems started. I thought that a common DLL or something was overlayed. We tried uninstalling the TSM services and re-instlaling them...reboots... nothing worked until I upgraded. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stephan Dinelle Sent: Friday, September 26, 2003 9:09 AM To: [EMAIL PROTECTED] Subject: TSM Scheduler service terminated unexpectedly I have the 5.1.5.0 client running locally on a W2K (SP3) server. The backup of this client is generally less than 1Gb per day, but the TSM scheduler service on that client regularly terminates unexpectedly with the following error in the W2K event log: Event Type:Error Event Source: Service Control Manager Event Category: None Event ID: 7031 Date: 09/26/2003 Time: 8:04:38 PM User: N/A Computer: FILESERVER Description: The TSM Scheduler service terminated unexpectedly. It has done this 22 time(s). The following corrective action will be taken in 0 milliseconds: No action. ANY IDEAS???
Re: TSM Scheduler service terminated unexpectedly
Stephan, Yes, this is a message that happens quite often with Windows clients. I have seen that this happens when the server is rebooted overnight and upon start-up TSM has problems starting the TSM Scheduler service again. Under the Scheduler properties and the 'RECOVERY' tab, set 'First Failure: to Restart the Service' and 'Second Failure: to Restart the Service' as well. Sometimes it will restart the service automatically if it dies. It's a hit-or-miss scenario. Regards, Demetrius Malbrough Tivoli Certified Consultant ---Original Message--- From: Stephan Dinelle [EMAIL PROTECTED] Subject: TSM Scheduler service terminated unexpectedly Sent: 26 Sep 2003 13:09:08 I have the 5.1.5.0 client running locally on a W2K (SP3) server. The backup of this client is generally less than 1Gb per day, but the TSM scheduler service on that client regularly terminates unexpectedly with the following error in the W2K event log: Event Type:Error Event Source: Service Control Manager Event Category: None Event ID: 7031 Date: 09/26/2003 Time: 8:04:38 PM User: N/A Computer: FILESERVER Description: The TSM Scheduler service terminated unexpectedly. It has done this 22 time(s). The following corrective action will be taken in 0 milliseconds: No action. ANY IDEAS??? ---Original Message---
Re: AIX backup command via TSM scheduler
Did some debugging on our backup scripts and it seems that the following lines are the culprit : stty intr '' trap stty intr '' 2 Would anyone know what is the purpose of those two lines ? ( am not familiar with scripts. The backup scripts are provided for by our IBM support ) Thanks Conko, Steven To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: OM Subject: Re: AIX backup command via TSM scheduler Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 06/07/2003 01:57 AM Please respond to ADSM: Dist Stor Manager We have an AIX server, so I dont know if the syntax is different, but we do have AIX clients. we run similar commands but dont use any quotes and dont include the -c, an entry for us is like this: su - oracle /home/oracle/scripts/backup/db_backup.sh It usually runs fine. however, there are isolated instances where it may fail with the rc=1 yet still run from the command line. in each of those cases we have had to step through the entire process with debug statements to find out what the problem is (keeping in mind that with the su -, the profile is sourced first.) usually, there ends up being some problem in the environment or a problem with double sourcing a file. i have no idea why the scheduler has problems when it runs okay from the command line. but that is what we have had to to... debug the process. Steve -Original Message- From: Neilson Lui [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2003 8:45 PM To: [EMAIL PROTECTED] Subject: AIX backup command via TSM scheduler Environment: Server TSM v5.1.5 on W2k Client TSM v5.1.5 on AIX with Oracle running Our backup job is currently being scheduled by the cron daemon on AIX via the command ( issued as root ) su - userid -c 'sh /tsmscript/backup.sh' I was trying to have the same command defined on TSM scheduler. But i was getting a return code of 1 when the same command is issued by the TSM scheduler. Is there a way to let the TSM scheduler use another userid instead of root ? Any suggestions.
Re: AIX backup command via TSM scheduler
Have tried defining it as 'su - userid -c sh /tsmscript/backup.sh'. But still the return code is 1. David Longo [EMAIL PROTECTED]To: [EMAIL PROTECTED] FIRST.ORG cc: Sent by: ADSM: DistSubject: Re: AIX backup command via TSM scheduler Stor Manager [EMAIL PROTECTED] U 06/06/2003 11:51 AM Please respond to ADSM: Dist Stor Manager Most likely the problem is that you need to enclose the ENTIRE command in quotes when putting it in an object parameter on the TSM server schedule. (That's in addition to the quotes that are already in it.) David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 06/05/03 08:44PM Environment: Server TSM v5.1.5 on W2k Client TSM v5.1.5 on AIX with Oracle running Our backup job is currently being scheduled by the cron daemon on AIX via the command ( issued as root ) su - userid -c 'sh /tsmscript/backup.sh' I was trying to have the same command defined on TSM scheduler. But i was getting a return code of 1 when the same command is issued by the TSM scheduler. Is there a way to let the TSM scheduler use another userid instead of root ? Any suggestions. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: AIX backup command via TSM scheduler
We have an AIX server, so I dont know if the syntax is different, but we do have AIX clients. we run similar commands but dont use any quotes and dont include the -c, an entry for us is like this: su - oracle /home/oracle/scripts/backup/db_backup.sh It usually runs fine. however, there are isolated instances where it may fail with the rc=1 yet still run from the command line. in each of those cases we have had to step through the entire process with debug statements to find out what the problem is (keeping in mind that with the su -, the profile is sourced first.) usually, there ends up being some problem in the environment or a problem with double sourcing a file. i have no idea why the scheduler has problems when it runs okay from the command line. but that is what we have had to to... debug the process. Steve -Original Message- From: Neilson Lui [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2003 8:45 PM To: [EMAIL PROTECTED] Subject: AIX backup command via TSM scheduler Environment: Server TSM v5.1.5 on W2k Client TSM v5.1.5 on AIX with Oracle running Our backup job is currently being scheduled by the cron daemon on AIX via the command ( issued as root ) su - userid -c 'sh /tsmscript/backup.sh' I was trying to have the same command defined on TSM scheduler. But i was getting a return code of 1 when the same command is issued by the TSM scheduler. Is there a way to let the TSM scheduler use another userid instead of root ? Any suggestions.
AIX backup command via TSM scheduler
Environment: Server TSM v5.1.5 on W2k Client TSM v5.1.5 on AIX with Oracle running Our backup job is currently being scheduled by the cron daemon on AIX via the command ( issued as root ) su - userid -c 'sh /tsmscript/backup.sh' I was trying to have the same command defined on TSM scheduler. But i was getting a return code of 1 when the same command is issued by the TSM scheduler. Is there a way to let the TSM scheduler use another userid instead of root ? Any suggestions.
Re: AIX backup command via TSM scheduler
Most likely the problem is that you need to enclose the ENTIRE command in quotes when putting it in an object parameter on the TSM server schedule. (That's in addition to the quotes that are already in it.) David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 06/05/03 08:44PM Environment: Server TSM v5.1.5 on W2k Client TSM v5.1.5 on AIX with Oracle running Our backup job is currently being scheduled by the cron daemon on AIX via the command ( issued as root ) su - userid -c 'sh /tsmscript/backup.sh' I was trying to have the same command defined on TSM scheduler. But i was getting a return code of 1 when the same command is issued by the TSM scheduler. Is there a way to let the TSM scheduler use another userid instead of root ? Any suggestions. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
