TSM client scheduler issue
Hi Fellow TSM'ers TSM server 5.5 Client 5.4 It seems my client has lost connection to the backup server. Errorlog: 5/20/2014 14:48:14 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. I have tried updating the scheduler but get the following error; Error 9 establishing TSM API session unknown TSM API error. Once a click ok its says scheduler service successfully updated but it's not as my still has no comms. 5/20/2014 14:46:57 Will attempt to get schedule from server again in 20 minutes. 05/20/2014 14:48:14 Querying server for next scheduled event. 05/20/2014 14:48:14 Node Name: CARME_DAILY 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com **
Re: TSM client scheduler issue
Can you PING the IP of the TSM Server? Or TELNET IP 1500? Those tests check for network connectivity and open firewalls. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Swartz, Jerome Sent: Tuesday, May 20, 2014 8:03 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM client scheduler issue Hi Fellow TSM'ers TSM server 5.5 Client 5.4 It seems my client has lost connection to the backup server. Errorlog: 5/20/2014 14:48:14 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. I have tried updating the scheduler but get the following error; Error 9 establishing TSM API session unknown TSM API error. Once a click ok its says scheduler service successfully updated but it's not as my still has no comms. 5/20/2014 14:46:57 Will attempt to get schedule from server again in 20 minutes. 05/20/2014 14:48:14 Querying server for next scheduled event. 05/20/2014 14:48:14 Node Name: CARME_DAILY 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: TSM client scheduler issue
tsm rc -53 means auth failure iirc, check your password settings. Op 20 mei 2014, om 15:03 heeft Swartz, Jerome jerome.swa...@computacenter.com het volgende geschreven: Hi Fellow TSM'ers TSM server 5.5 Client 5.4 It seems my client has lost connection to the backup server. Errorlog: 5/20/2014 14:48:14 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. I have tried updating the scheduler but get the following error; Error 9 establishing TSM API session unknown TSM API error. Once a click ok its says scheduler service successfully updated but it's not as my still has no comms. 5/20/2014 14:46:57 Will attempt to get schedule from server again in 20 minutes. 05/20/2014 14:48:14 Querying server for next scheduled event. 05/20/2014 14:48:14 Node Name: CARME_DAILY 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com **
Re: TSM client scheduler issue
Thanks, It was a DNS issue. Resolved now :) -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco Post Sent: 20 May 2014 03:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM client scheduler issue tsm rc -53 means auth failure iirc, check your password settings. Op 20 mei 2014, om 15:03 heeft Swartz, Jerome jerome.swa...@computacenter.com het volgende geschreven: Hi Fellow TSM'ers TSM server 5.5 Client 5.4 It seems my client has lost connection to the backup server. Errorlog: 5/20/2014 14:48:14 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. I have tried updating the scheduler but get the following error; Error 9 establishing TSM API session unknown TSM API error. Once a click ok its says scheduler service successfully updated but it's not as my still has no comms. 5/20/2014 14:46:57 Will attempt to get schedule from server again in 20 minutes. 05/20/2014 14:48:14 Querying server for next scheduled event. 05/20/2014 14:48:14 Node Name: CARME_DAILY 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com **
Re: TSM client scheduler issue
It may mean the TSM Scheduler is already running when the Acceptor or dsmcad tries to start it. That can happen when a backup session crashes and an orphan Scheduler process is left dangling. And, I may be confusing two recent weird problems we had. One of them was a RC -53. K. On May 20, 2014, at 9:41 AM, Remco Post wrote: tsm rc -53 means auth failure iirc, check your password settings. Op 20 mei 2014, om 15:03 heeft Swartz, Jerome jerome.swa...@computacenter.com het volgende geschreven: Hi Fellow TSM'ers TSM server 5.5 Client 5.4 It seems my client has lost connection to the backup server. Errorlog: 5/20/2014 14:48:14 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. I have tried updating the scheduler but get the following error; Error 9 establishing TSM API session unknown TSM API error. Once a click ok its says scheduler service successfully updated but it's not as my still has no comms. 5/20/2014 14:46:57 Will attempt to get schedule from server again in 20 minutes. 05/20/2014 14:48:14 Querying server for next scheduled event. 05/20/2014 14:48:14 Node Name: CARME_DAILY 05/20/2014 14:48:14 ANS1029E Communication with the TSM server is lost. ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com **
Re: rc-scripts to start and stop multiple tsm client scheduler for linux red hat
You do not have to create different scripts to accomplish this task. Simply bundle your settings using appropriate servername stanzas in dsm.sys and use a script (see http://www.dat.lrz.de/dat/dsm/scr/#mdsm, DSM multiple schedule daemons manager) to manage one or more schedule daemons by separating them using these different server stanza names. Unfortunately this script wasn't developed for RedHat, but has been built right now on a SuSE system. Nevertheless it should run on some other Unices, too. Rainer PS: Some real-world usage # /etc/init.d/mdsm status mdsm: status: scheduler for servername local is running (pid 18450) mdsm: status: scheduler for servername special is not running # /etc/init.d/mdsm start mdsm: start: scheduler for servername local is already running (pid 18450) mdsm: start: started scheduler for servername special (pid 21623) # /etc/init.d/mdsm stop local mdsm: stop: stopped scheduler for servername local (pid 18450) # /etc/init.d/mdsm status mdsm: status: scheduler for servername local is not running mdsm: status: scheduler for servername special is running (pid 21623) Without any configuration mdsm will manage your default servername.
rc-scripts to start and stop multiple tsm client scheduler for linux red hat
Hello, can anyone share rc-scripts to start and stop multiple tsm client scheduler for linux red hat. The idea is, to use different rc-scripts for separat tsm client-option-files with different tsm nodename. We would like to start and stop the tsm client-schedules separantly using the pid. Thanks in advance Andreas.
Antwort: [ADSM-L] rc-scripts to start and stop multiple tsm client scheduler for linux red hat
Hi, look at appendices on my private website http://www.mensam.dynaccess.de/TSMwiki/index.php?B%2FA-Client. You'll find a script dsmclient.rc that should work on RedHat directly. Versions of that script are available on request for other UX platforms, too. You'll need to create a link for each schedule in /opt/tivoli/tsm/baclient, i.e. ln -s dsmcad dsmcad1, create a copy of dsmclient.rc (like dsmmontlybackup.rc) and change entry prog=dsmcad to point to the link created above. Regards Ulli - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ullrich Mänz System-Integration FRITZ MACZIOL Software und Computervertrieb GmbH Ludwig Str. 180D, 63067 Offenbach, Germany Mobil: +49 170 7678434 Fax: +49 69 38013500 10 Web: http://www.fum.de Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936 Geschäftsführer: Heribert Fritz, Oliver Schallhorn, Frank Haines Inhaber: Imtech N.V., Gouda, Niederlande Referenzen finden Sie auf unserer Website, Rubrik 'News'. Von:TSM t...@profi-ag.de An: ADSM-L@VM.MARIST.EDU Datum: 14.06.2011 15:59 Betreff:[ADSM-L] rc-scripts to start and stop multiple tsm client scheduler for linux red hat Gesendet von: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Hello, can anyone share rc-scripts to start and stop multiple tsm client scheduler for linux red hat. The idea is, to use different rc-scripts for separat tsm client-option-files with different tsm nodename. We would like to start and stop the tsm client-schedules separantly using the pid. Thanks in advance Andreas.
Re: rc-scripts to start and stop multiple tsm client scheduler for linux red hat
Here's the one I use:
START:
#!/bin/bash
# Start Script for TSM Client on Linux and AIX
#
# Checkconfig lines below for Linux machines:
#
# chkconfig: 345 96 07
# description: tsmdsm
export DSM_DIR=/opt/tivoli/tsm/client/ba/bin
export DSM_LOG=/var/log/tsm
export DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt
case $1 in
'start')
ps -ef | grep dsmc | grep -v grep | awk -F '{print $2}' |while
read I
do
kill -9 $I
done
/opt/tivoli/tsm/client/ba/bin/dsmcad /dev/null 21
/opt/tivoli/tsm/client/ba/bin/dsmc sched /dev/null 21
;;
'stop')
ps -ef | grep dsmc | grep -v grep | awk -F '{print $2}' |while
read I
do
kill -9 $I
done
;;
'restart')
ps -ef | grep dsmc | grep -v grep | awk -F '{print $2}' |while
read I
do
kill -9 $I
done
/opt/tivoli/tsm/client/ba/bin/dsmcad /dev/null 21
/opt/tivoli/tsm/client/ba/bin/dsmc sched /dev/null 21
;;
*)
echo Usage: $0 {start|stop|restart}
esac
END:
Just add as many /opt/tivoli . . . lines as you need adding
-optfile=/location/of/dsm/opt for each node that doesn't use the
DSM_CONFIG variable at the top. You would obviously have different
stanzas in your dsm.sys for each dsm.opt file, along with different port
definitions to avoid conflicts.
This works on AIX and Linux across our enterprise with no need to write
out a pid file.
See Ya'
Howard Coles Jr., RHCE, CNE, CDE
John 3:16!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
TSM
Sent: Tuesday, June 14, 2011 8:55 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] rc-scripts to start and stop multiple tsm client
scheduler for linux red hat
Hello,
can anyone share rc-scripts to start and stop multiple tsm client
scheduler for linux red hat.
The idea is, to use different rc-scripts for separat tsm
client-option-files with different tsm nodename.
We would like to start and stop the tsm client-schedules separantly
using
the pid.
Thanks in advance
Andreas.
Tsm client scheduler 6.2 with centos linux
Client version 6.2 Best I can get for the linux version is as follows: Linux version 2.6.18-128.el5xen (mockbu...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Jan 21 11:12:42 EST 2009 When dsmc sched is run, about a minute later in the error log is the following: 05/17/2010 14:04:25 ANS2820E An interrupt has occurred. The current operation will end and the client will shut down. 05/17/2010 14:04:26 ANS0361I DIAG: Unknown thread, fatal error, signal 11 This is not my machine, and I have no privs. Any pointers will be helpful. Google turned up nothing, tsm help turned up nothing. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Tsm client scheduler 6.2 with centos linux
Gary - Signal 11 is a segfault, the result of a programming error. Best to contact TSM Support. You may be able to get around the segfault by tweaking various client options until the client no longer fails (e.g., Memoryefficient) as a temporary expedient. Also assure that the client is not virtual-storage constrained. Richard Sims
Re: Tsm client scheduler 6.2 with centos linux
Downgrade to 5.5 or some other TSM client level that is not at major 6 ;-) On 18 mei 2010, at 17:09, Lee, Gary D. wrote: Client version 6.2 Best I can get for the linux version is as follows: Linux version 2.6.18-128.el5xen (mockbu...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Jan 21 11:12:42 EST 2009 When dsmc sched is run, about a minute later in the error log is the following: 05/17/2010 14:04:25 ANS2820E An interrupt has occurred. The current operation will end and the client will shut down. 05/17/2010 14:04:26 ANS0361I DIAG: Unknown thread, fatal error, signal 11 This is not my machine, and I have no privs. Any pointers will be helpful. Google turned up nothing, tsm help turned up nothing. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: Why need password to create client scheduler?
In Windows this is so that the password can be stored in the registry, once stored you do not have to reenter it. when the client is installed and configured issue any generic command from the cli, such as dsmc q tsm, it will prompt you for the password, enter it and you are set. Additionally, when the password expires, as defined on the TSM server it will be updated on the client. ~Rick JAX FL -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Roger Deschner Sent: Thursday, April 01, 2010 5:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Why need password to create client scheduler? If PASSWORDACCESS GENERATE is in effect and has been initialized with the node password successfully encrypted and stored, and if you then go to create a scheduler, why do you need to give the node password again? This sometimes means, that if the user no longer knows their password, that we have to change their password for them just so they can create a scheduler. Is there a way around this? Perhaps some creative use of the dsmcutil program? Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Re: Why need password to create client scheduler?
That's how PASSWORDACCESS GENERATE works for sure, but I'm not quite sure that's what Roger is asking -the question is why, if you're already using PASSWORDACCESS GENERATE and your password is already presumably stored in the registry, you need to input it again when setting up the scheduler. /David McClelland London On 2 Apr 2010, at 14:03, Rick Adamson rickadam...@winn-dixie.com wrote: In Windows this is so that the password can be stored in the registry, once stored you do not have to reenter it. when the client is installed and configured issue any generic command from the cli, such as dsmc q tsm, it will prompt you for the password, enter it and you are set. Additionally, when the password expires, as defined on the TSM server it will be updated on the client. ~Rick JAX FL -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Roger Deschner Sent: Thursday, April 01, 2010 5:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Why need password to create client scheduler? If PASSWORDACCESS GENERATE is in effect and has been initialized with the node password successfully encrypted and stored, and if you then go to create a scheduler, why do you need to give the node password again? This sometimes means, that if the user no longer knows their password, that we have to change their password for them just so they can create a scheduler. Is there a way around this? Perhaps some creative use of the dsmcutil program? Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Re: Why need password to create client scheduler?
Doesn't work that way. The password must not have been stored (i.e. the GUI run for the first time). When defining or resetting the password for a Windoz box, I always tell the client: 1. Stop the scheduler/GUI 2. I reset the password on the TSM server 3. Start the GUI. You will be prompted for the password. Stop and start the GUI again. You should not be prompted for the password, the second time. 4. Start the scheduler service From: ADSM-L t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Date: 04/02/2010 09:51 AM Subject: Re: [ADSM-L] Why need password to create client scheduler? Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU That's how PASSWORDACCESS GENERATE works for sure, but I'm not quite sure that's what Roger is asking -the question is why, if you're already using PASSWORDACCESS GENERATE and your password is already presumably stored in the registry, you need to input it again when setting up the scheduler. /David McClelland London On 2 Apr 2010, at 14:03, Rick Adamson rickadam...@winn-dixie.com wrote: In Windows this is so that the password can be stored in the registry, once stored you do not have to reenter it. when the client is installed and configured issue any generic command from the cli, such as dsmc q tsm, it will prompt you for the password, enter it and you are set. Additionally, when the password expires, as defined on the TSM server it will be updated on the client. ~Rick JAX FL -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Roger Deschner Sent: Thursday, April 01, 2010 5:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Why need password to create client scheduler? If PASSWORDACCESS GENERATE is in effect and has been initialized with the node password successfully encrypted and stored, and if you then go to create a scheduler, why do you need to give the node password again? This sometimes means, that if the user no longer knows their password, that we have to change their password for them just so they can create a scheduler. Is there a way around this? Perhaps some creative use of the dsmcutil program? Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Why need password to create client scheduler?
If PASSWORDACCESS GENERATE is in effect and has been initialized with the node password successfully encrypted and stored, and if you then go to create a scheduler, why do you need to give the node password again? This sometimes means, that if the user no longer knows their password, that we have to change their password for them just so they can create a scheduler. Is there a way around this? Perhaps some creative use of the dsmcutil program? Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Re: Client hangs when TSM Client Acceptor starts TSM Client Scheduler.
I looked into everything I could, and didn't find anything useful. Dsmcad is no longer managing the scheduler, and that seems to make the problem go away. This one goes on my list of known issues that I hope to resolve and document in the future. Thanks, [RC] -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Tuesday, March 10, 2009 12:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Client hangs when TSM Client Acceptor starts TSM Client Scheduler. Things I would first check: That client and server are syncing to a time standard, for overall sanity. Check for any errors in dsmerror.log. On the server side, do 'Query SEssion F=D' and see what's going on with that node, and inspect the Activity Log for issues regarding the session. Backups are relatively low priority, so long waits for tape drives are possible. In Windows, look for any questionable Event Log entries, and see if the dsmc scheduler process is using any CPU, if the server indicates it healthy. Richard Sims DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
Client hangs when TSM Client Acceptor starts TSM Client Scheduler.
I have several Windows clients that hang at night if the TSM Client Acceptor service starts the TSM Client Scheduler to check the schedule while the backup is running. The admin who set the client up did so at approximately 14:20, and the backup starts at 02:00. Right around 02:20, I can see an event in the dsmwebcl.log file that shows the client checking in, and after that point there is no more progress shown on the backup in the dsmsched.log. When I look at the services, the TSM Client Scheduler is still running (and effectively hung) the next day. The client level is 5.5.1.0 on Windows 2003 R2 Standard Edition w/ SP2, and the TSM server is 5.4.2.0 running on AIX 5.3. So far, I've removed and re-added the TSM Client Scheduler, making sure dsmcad is managing the scheduler. I've searched the TSM site. Any pointers appreciated. DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
Re: Client hangs when TSM Client Acceptor starts TSM Client Scheduler.
Things I would first check: That client and server are syncing to a time standard, for overall sanity. Check for any errors in dsmerror.log. On the server side, do 'Query SEssion F=D' and see what's going on with that node, and inspect the Activity Log for issues regarding the session. Backups are relatively low priority, so long waits for tape drives are possible. In Windows, look for any questionable Event Log entries, and see if the dsmc scheduler process is using any CPU, if the server indicates it healthy. Richard Sims
Re: Client hangs when TSM Client Acceptor starts TSM Client Scheduler.
Go to the URL in my sig and do a search on the following: snp Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html 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 03/10/2009 03:21:07 PM: [image removed] Client hangs when TSM Client Acceptor starts TSM Client Scheduler. Clark, Robert A to: ADSM-L 03/10/2009 03:25 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager I have several Windows clients that hang at night if the TSM Client Acceptor service starts the TSM Client Scheduler to check the schedule while the backup is running. The admin who set the client up did so at approximately 14:20, and the backup starts at 02:00. Right around 02:20, I can see an event in the dsmwebcl.log file that shows the client checking in, and after that point there is no more progress shown on the backup in the dsmsched.log. When I look at the services, the TSM Client Scheduler is still running (and effectively hung) the next day. The client level is 5.5.1.0 on Windows 2003 R2 Standard Edition w/ SP2, and the TSM server is 5.4.2.0 running on AIX 5.3. So far, I've removed and re-added the TSM Client Scheduler, making sure dsmcad is managing the scheduler. I've searched the TSM site. Any pointers appreciated. DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
Re: CAD Control Client scheduler
From: Smith, I (Ian) [EMAIL PROTECTED] Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew It has been my experience that with cad controling the scheduler I have seen a increase in unexplainable misses. That being said your milage may vary depending on version of tsm and the os. On the flip side, if you make a change in the client option file, using CAD to run the scheduler doesn't require you to stop and restart the scheduler service to enact the change. -- Mark Stapleton ([EMAIL PROTECTED]) Senior TSM engineer
Re: CAD Control Client scheduler
- Original Message - From: Mark Stapleton [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 16, 2006 3:28 PM Subject: Re: CAD Control Client scheduler From: Smith, I (Ian) [EMAIL PROTECTED] Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew It has been my experience that with cad controling the scheduler I have seen a increase in unexplainable misses. That being said your milage may vary depending on version of tsm and the os. On the flip side, if you make a change in the client option file, using CAD to run the scheduler doesn't require you to stop and restart the scheduler service to enact the change. -- Mark Stapleton ([EMAIL PROTECTED]) Senior TSM engineer _-- really ? how ?
Re: CAD Control Client scheduler
CAD starts the scheduler each time backup will run. And TSM reads dsm.opt everytime the scheduler starts.. ... But dont we think enterprise and use cloptsets...? :-) //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: den 16 oktober 2006 15:37 To: ADSM-L@VM.MARIST.EDU Subject: Re: CAD Control Client scheduler - Original Message - From: Mark Stapleton [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 16, 2006 3:28 PM Subject: Re: CAD Control Client scheduler From: Smith, I (Ian) [EMAIL PROTECTED] Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew It has been my experience that with cad controling the scheduler I have seen a increase in unexplainable misses. That being said your milage may vary depending on version of tsm and the os. On the flip side, if you make a change in the client option file, using CAD to run the scheduler doesn't require you to stop and restart the scheduler service to enact the change. -- Mark Stapleton ([EMAIL PROTECTED]) Senior TSM engineer _-- really ? how ? --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
CAD Control Client scheduler
Hello Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? Is this best practice? _ Ian Smith SAN/TSM Specialist _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: CAD Control Client scheduler
Ian, Both options are best practices. According to IBM one should use the CAD to control the scheduler (on Netware I would advise it as well). Met vriendelijke groet, with kind regards, Richard van Denzel -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens Smith, I (Ian) Verzonden: vrijdag 13 oktober 2006 12:59 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] CAD Control Client scheduler Hello Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? Is this best practice? _ Ian Smith SAN/TSM Specialist _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
AW: [ADSM-L] CAD Control Client scheduler
My 2 cents. When using the CAD to control the scheduler you can make (almost all) changes to dsm.opt whithout (forgetting to) restart the scheduler. Thomas Rupp -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Smith, I (Ian) Gesendet: Freitag, 13. Oktober 2006 12:59 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] CAD Control Client scheduler Hello Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? Is this best practice? _ Ian Smith SAN/TSM Specialist _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: CAD Control Client scheduler
It has been my experience that with cad controling the scheduler I have seen a increase in unexplainable misses. That being said your milage may vary depending on version of tsm and the os. -Original Message- From: Smith, I (Ian) [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Sent: 10/13/06 6:31 AM Subject: CAD Control Client scheduler Hello Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? Is this best practice? _ Ian Smith SAN/TSM Specialist _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _ This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Re: CAD Control Client scheduler
This was my worry. I seem to have heard of lots of stability and function problems using this method. However with an oncoming 5.3 environment upgrade I am thinking of amending policy. _ Ian Smith -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew Sent: 13 October 2006 14:48 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] CAD Control Client scheduler It has been my experience that with cad controling the scheduler I have seen a increase in unexplainable misses. That being said your milage may vary depending on version of tsm and the os. -Original Message- From: Smith, I (Ian) [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Sent: 10/13/06 6:31 AM Subject: CAD Control Client scheduler Hello Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? Is this best practice? _ Ian Smith SAN/TSM Specialist _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _ This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Re: CAD Control Client scheduler
Smith, I (Ian) wrote: This was my worry. I seem to have heard of lots of stability and function problems using this method. However with an oncoming 5.3 environment upgrade I am thinking of amending policy. I've not seen much missed backups (and advise all my customers to use dsmcad). I do however know that 'dsmc sched' eats up lots of memory, or at least it used to. We backup about 800 clients. I do sometimes see some reports that indicate two schedulers run on one node, but that is only once in a while _ Ian Smith -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew Sent: 13 October 2006 14:48 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] CAD Control Client scheduler It has been my experience that with cad controling the scheduler I have seen a increase in unexplainable misses. That being said your milage may vary depending on version of tsm and the os. -Original Message- From: Smith, I (Ian) [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Sent: 10/13/06 6:31 AM Subject: CAD Control Client scheduler Hello Do people use the CAD to control the scheduler? Is this a good idea, what happens if the CAD fails? Is this best practice? -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16 B3F6 048A 02BF DC93 94EC 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
TSM Client Scheduler v5.3.0 - Windows 2003 server
Hi all, Been seeing these errors in my log. There is no update to the v5.3.0 client yet on IBM's FTP site? I haven't changed any entries in my inclexcl or dsm.opt files. Errors: 09/09/2005 08:50:10 psNpOpen(): Error opening named pipe '\\.\pipe\Server1', CreateFile: Win32 rc=2 . 09/09/2005 08:50:10 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -190. 09/09/2005 08:50:10 ANS1029E Communication with the TSM server is lost. 09/09/2005 08:55:02 ConsoleEventHandler(): Caught Logoff console event . 09/09/2005 08:55:02 ConsoleEventHandler(): Process Detached. 09/09/2005 08:55:03 ConsoleEventHandler(): Caught Logoff console event . 09/09/2005 08:55:03 ConsoleEventHandler(): Process Detached. 09/09/2005 08:55:06 ConsoleEventHandler(): Caught Shutdown console event . 09/09/2005 08:55:06 ConsoleEventHandler(): Cleaning up and terminating Process ... 09/09/2005 08:55:06 ANS2820E An interrupt has occurred. The current operation will end and the client will shut down. 09/09/2005 08:59:37 psNpOpen(): Error opening named pipe '\\.\pipe\Server1', CreateFile: Win32 rc=2 . 09/09/2005 08:59:37 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -190. 09/09/2005 08:59:37 ANS1029E Communication with the TSM server is lost. 09/09/2005 23:05:01 ANS1076E *** Directory path not found *** 09/09/2005 23:05:06 ANS1076E *** Directory path not found *** 09/09/2005 23:05:11 ANS1076E *** Directory path not found *** 09/10/2005 19:00:04 ANS1076E *** Directory path not found *** 09/10/2005 19:00:04 ANS1076E *** Directory path not found *** 09/10/2005 19:21:54 ANS1512E Scheduled event 'WILMSNTCH5_ARCH' failed. Return code = 12. A while back I just put all my inclexcl files in the dsm.opt fie, seemd to work until now... Dsm.opt: *=== * Note: This file was generated by a TSM client configuration utility. * * Generated on Fri Mar 11 16:57:10 2005 * *=== * commmethod Namedpipes tcpport 1500 tcpserveraddress localhost PASSWORDACCESS GENERATE SCHEDMODe Polling COMPRESSALWAYS No DOMAIN C: DOMAIN E: DOMAIN SYSTEMSERVICES DOMAIN SYSTEMSTATE DOMAIN.IMAGEC: TxnByteLimit25600 TCPNoDelay Yes TCPWindowsize 63 *TestFlag Instrument:Detail ResourceUtilization 5 LargeCommBuffersNo MemoryEfficientBackup No CHAngingretries 2 *INCLEXCL C:\Progra~1\Tivoli\TSM\baclient\tsm-inclexcl.txt EXCLUDE.DIR *:\Recycler EXCLUDE.DIR *:\Recycled EXCLUDE.DIR *:\...\Temporary Internet Files EXCLUDE.DIR *:\System Volume Information INCLUDE.ARCHIVE *:\...\system32\dns\backup\...\* EXCLUDE.ARCHIVE *:\...\system32\dns\...\* INCLUDE.ARCHIVE *:\...\system32\dhcp\backup\...\* EXCLUDE.ARCHIVE *:\...\system32\dhcp\...\* EXCLUDE.ARCHIVE *:\...\system32\Perflib*.dat EXCLUDE.ARCHIVE *:\...\system32\config\...\* EXCLUDE.ARCHIVE *:\IO.SYS EXCLUDE.ARCHIVE *:\IBMDOS.COM EXCLUDE.ARCHIVE *:\IBMBIO.COM EXCLUDE.ARCHIVE *:\...\EA DATA. SF EXCLUDE.ARCHIVE *:\microsoft uam volume\...\*.* EXCLUDE.ARCHIVE *:\microsoft uam volume\...\* INCLUDE.BACKUP *:\...\system32\dns\backup\...\* EXCLUDE.BACKUP *:\...\system32\dns\...\* INCLUDE.BACKUP *:\...\system32\dhcp\backup\...\* EXCLUDE.BACKUP *:\...\system32\dhcp\...\* EXCLUDE.BACKUP *:\...\system32\Perflib*.dat EXCLUDE.BACKUP *:\...\system32\config\...\* EXCLUDE.BACKUP *:\IO.SYS EXCLUDE.BACKUP *:\IBMDOS.COM EXCLUDE.BACKUP *:\IBMBIO.COM EXCLUDE.BACKUP *:\...\EA DATA. SF EXCLUDE.BACKUP *:\microsoft uam volume\...\*.* EXCLUDE.BACKUP *:\microsoft uam volume\...\* EXCLUDE.BACKUP *:\...\*.a EXCLUDE.BACKUP *:\...\*.aif EXCLUDE.BACKUP *:\...\*.aiff EXCLUDE.BACKUP *:\...\*.arj EXCLUDE.BACKUP *:\...\*.asf EXCLUDE.BACKUP *:\...\*.asx EXCLUDE.BACKUP *:\...\*.au EXCLUDE.BACKUP *:\...\*.avi EXCLUDE.BACKUP *:\...\*.dmp EXCLUDE.BACKUP *:\...\*.hlp EXCLUDE.BACKUP *:\...\*.m4p EXCLUDE.BACKUP *:\...\*.mid EXCLUDE.BACKUP *:\...\*.midi EXCLUDE.BACKUP *:\...\*.mov.mp3 EXCLUDE.BACKUP *:\...\*.mp4 EXCLUDE.BACKUP *:\...\*.mpeg EXCLUDE.BACKUP *:\...\*.mpg EXCLUDE.BACKUP *:\...\*.ram EXCLUDE.BACKUP *:\...\*.rmvb EXCLUDE.BACKUP *:\...\*.smi EXCLUDE.BACKUP *:\...\*.snd EXCLUDE.BACKUP *:\...\*.wav EXCLUDE.BACKUP *:\...\*.wma EXCLUDE.BACKUP *:\...\*.wmf.wmv EXCLUDE C:\Program Files\Tivoli\TSM\baclient\dsmsched.log EXCLUDE.DIR C:\Documents and Settings\All Users\Application Data\...\* EXCLUDE.DIR C:\Documents and Settings\Administrator.WILMSN\...\* EXCLUDE C:\pagefile.sys EXCLUDE C:\Documents and Settings\Administrator.WILMSN\NTUSER.DAT EXCLUDE C:\Documents and Settings\Administrator.WILMSN\ntuser.dat.LOG EXCLUDE C:\Documents and Settings\LocalService\ntuser.dat.LOG EXCLUDE C:\Documents and Settings\jensens\ntuser.dat.LOG EXCLUDE C:\Documents and Settings\infodba\ntuser.dat.LOG EXCLUDE C:\Documents and
Re: 网易邮箱自动回复: [ADSM-L] TSM Client Scheduler v5.3.0 - Windows 2003 server
I'm sorry, your email didn't come thru, see below... Do I need to convert to text or ? Please advise, thanks. Scott Regards, Scott Pichelman Systems Administrator Weir Slurry TM North America 2701 S Stoughton Rd Madison WI 53716 USA T: +001 608 226 5615 F: +001 608 221 5807 M: +001 608 346 2784 E: [EMAIL PROTECTED] W: http://weirslurry.com [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 09/12/2005 03:48 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To [EMAIL PROTECTED] cc Subject 网易邮箱自动回复: [ADSM-L] TSM Client Scheduler v5.3.0 - Windows 2003 server ÄúµÄÀ´ÐÅÒѾÊÕµ½£¬ÎÒ»áºÜ¿ìºÍÄãÁªÏµ£¡ The information contained in this email (including any attachments) is confidential, subject to copyright and for the use of the intended recipient only. If you are not the intended recipient please delete this message after notifying the sender. Unauthorised retention, alteration or distribution of this email is forbidden and may be actionable. Attachments are opened at your own risk and you are advised to scan incoming email for viruses before opening any attached files. We give no guarantee that any communication is virus-free and accept no responsibility for virus contamination or other system loss or damage of any kind.
ANS0101E on linux starting client scheduler
Not sure what changed between last week and today, but I can't seem to get the client scheduler started on a linux box. I was able to start it last week, but now when I try I get: ANS0101E Unable to open English message repository 'dsmclientV3.cat' I've searched the archives, and about all I've found on this error is to set LANG to en_US. I've done that. dsmclientV3.cat does exist in /opt/tivoli/tsm/client/ba/bin/en_US. What could be the problem? Thanks for your help, T. __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail
Re: ANS0101E on linux starting client scheduler
Not sure what changed between last week and today, but I can't seem to get the client scheduler started on a linux box. I was able to start it last week, but now when I try I get: ANS0101E Unable to open English message repository 'dsmclientV3.cat' I've searched the archives, and about all I've found on this error is to set LANG to en_US. I've done that. dsmclientV3.cat does exist in /opt/tivoli/tsm/client/ba/bin/en_US. What could be the problem? http://people.bu.edu/rbs/ADSM.QuickFacts has supplementary info... Have you checked that the directory and file permissions allow access by the invoker, and that DSM_* environment variables are not pointing somewhere else? I assume there's no further error indication in dsmerror.log. If all else fails, you might try using DSM_DIR in a site script which starts the client scheduler, identifying the directory where the client config files are. Richard Sims
Re: ANS0101E on linux starting client scheduler
As Homer says D'OH! Had my DSM_DIR variable set incorrectly. Thanks for the pointer. T. --- Richard Sims [EMAIL PROTECTED] wrote: Not sure what changed between last week and today, but I can't seem to get the client scheduler started on a linux box. I was able to start it last week, but now when I try I get: ANS0101E Unable to open English message repository 'dsmclientV3.cat' I've searched the archives, and about all I've found on this error is to set LANG to en_US. I've done that. dsmclientV3.cat does exist in /opt/tivoli/tsm/client/ba/bin/en_US. What could be the problem? http://people.bu.edu/rbs/ADSM.QuickFacts has supplementary info... Have you checked that the directory and file permissions allow access by the invoker, and that DSM_* environment variables are not pointing somewhere else? I assume there's no further error indication in dsmerror.log. If all else fails, you might try using DSM_DIR in a site script which starts the client scheduler, identifying the directory where the client config files are. Richard Sims __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Linux; Oracle TDP; Client Scheduler
Not a silly question at all. I do have the guide and have gone through it but am having issues and was looking to see if what I was doing was correct that was why I sent for more information from the list. After looking over the guide again this could be environment variable issues on my end which I am ashamed to admit. Ill do a bit more due diligence and I appreciate the email Neil because I am not looking at 3 different pdf's for information and narrow down my search to just this one. Data Protection for Oracle for UNIX Installation and User's Guide Version 5 Release 2 R. -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Re: Linux; Oracle TDP; Client Schedular I know this might sound like a silly question - but have you read the DP for Oracle User's Guide. There is a whole section on setting up the scheduler with DP for Oracle. It walks you through all the steps for dealing with root user vs. Oracle user. Regards, Neil Rasmussen Software Development Data Protection for Oracle CORP Rick Willmore [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02/19/2004 09:55 AM Please respond to ADSM: Dist Stor Manager To [EMAIL PROTECTED] cc Subject Re: Linux; Oracle TDP; Client Schedular How do you su - oracle -c script.sh if you use the client sched or do you? TSM support stated I couldnt do this. R. -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 5:26 AM To: [EMAIL PROTECTED] Subject: Re: Linux; Oracle TDP; Client Schedular We have never used crontab to perform the backups for Oracle, MS-SQL or Domino/Notes. We always use the scheduler to run the COMMAND on the client. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/18/2004 06:50:47 PM: Anyone using the Client schedular to backup oracle databases/logs via the tdp? I need/want to run the backup script from the user oracle and was curious if anyone is doing this or if everyone is just using the crontab. R.
Re: TSM client scheduler
A good temporary workaround for those intermittent stops is to have Win2K restart the service automatically. Open control panel - admin tools - SERVICES Right click on the TSM scheduler service, select PROPERTIES, then RECOVERY. Set first and second failure to RESTART THE SERVICE. Set RESET FAIL COUNT to 1. -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Saturday, August 02, 2003 11:39 PM To: [EMAIL PROTECTED] Subject: TSM client scheduler Hi to all, Why do we have to restart the TSM client scheduler services so often? It stops after a while. How do we fix this? My TSM client is 5.1.5.0. installed on Windows 2000 and NT4. Thanks. Zosi Noriega
Re: TSM client scheduler
Can you be more specific about what you mean by it stops after a while? What exactly do you mean by stop? If you mean crash, then perhaps this is APAR IC36474, which is fixed in 5.2; an interim fix at the 5.1.6 level is currently targeted for availability near the end of August of beginning of September. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Zosimo Noriega [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/02/2003 20:39 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TSM client scheduler Hi to all, Why do we have to restart the TSM client scheduler services so often? It stops after a while. How do we fix this? My TSM client is 5.1.5.0. installed on Windows 2000 and NT4. Thanks. Zosi Noriega InterScan_Disclaimer.txt has been removed from this note on August 03, 2003 by Andrew Raibeck
TSM client scheduler
Hi to all, Why do we have to restart the TSM client scheduler services so often? It stops after a while. How do we fix this? My TSM client is 5.1.5.0. installed on Windows 2000 and NT4. Thanks. Zosi Noriega This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
TSM Client Scheduler on Windows
All, Has anybody seen issues with the new TSM 5.1.6.0 client scheduler being started by the dsmcad process? I installed the scheduler service and the dsmcad service as always, but this time the dsmcad process isn't able to start the scheduler. In the error log it says that the schedule name is empty. I fixed the issue by removing and reinstalling the scheduler and when it asks for the client acceptor name giving it the name TSM Client Scheduler 2. If I used the default name it won't work at all. -- Joshua S. Bassi Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP IBM Certified - AIX 4/5L, SAN, Shark Cell (831) 595-3962
Mac client scheduler
Macintosh *SMers, Can any of you please share you experience and advice on the best and most reliable method for starting the TSM Scheduler on Mac OS 9 and OS X? The installer is sets up an alias to the daemon in startup folder. Have any of you done differently, for example, to use the scheduler application in start up? Thanks. John
Re: Mac client scheduler
The most reliable method is to not use the Daemon at all, but to instead place an alias of the actual scheduler in the startup folder. The Daemon has issues under Mac OS 9 and 10. The drwaback to this is that if the user quits out of the scheduler, it will not restart like the Daemon does so you must warn your users not to quit out. Also, the scheduler will pop up when the system is turned on or the user logs back in. To get this pop up to go away, the user must click anywhere in the background or on another app to get it to move to the background. Jim Neal TSM Administrator NASA/AMES Research Center -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of John Bremer Sent: Monday, February 10, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: Mac client scheduler Macintosh *SMers, Can any of you please share you experience and advice on the best and most reliable method for starting the TSM Scheduler on Mac OS 9 and OS X? The installer is sets up an alias to the daemon in startup folder. Have any of you done differently, for example, to use the scheduler application in start up? Thanks. John
Re: Client Scheduler stopping/ TSM 5.1.5.1
my feeling is that Resource Timeout will not change the situation.it should help in giving insight in the lock status. I am seeing this elsewhere but we have not yet found out the culprit. at least in EMEA. one workaround with the NT scheduler is to use AT commands to stop/start it remotely if you can do that. some people on the forum will smile now because it will remind them of things alredy seen... ;-) Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] The people of Krikkit,are, well, you know, they're just a bunch of real sweet guys, you know, who just happen to want to kill everybody. Hell, I feel the same way some mornings... Gill, Geoffrey L. GEOFFREY.L.GILTo [EMAIL PROTECTED][EMAIL PROTECTED] Sent by: ADSM:cc Dist Stor Manager bcc [EMAIL PROTECTED] ST.EDU Subject Client Scheduler stopping/ TSM 5.1.5.1 06/11/2002 00.23 Please respond to ADSM: Dist Stor Manager A short update to everyone watching the TSM 5.1.5.1 posts. I've been asked twice to change Resource Timeout value, which is now 100. Most of the missed backups I was having are gone but support still wants me to monitor for the lock I was seeing and then run a bunch of commands to gather info if I can. Unfortunately backups are so late I've just had it. It's not that I don't want to help, it's just so late I'm tired. As for the missed backups I am seeing now, I can tell it's because the schedule service is stopped. Since I don't have access to these computers I can't start it, don't know if it stopped on its own, or if someone purposefully stopped it. Are there any issues related to the Scheduler service stopping with certain levels of TSM client on WIN2K or NT? I'm also seeing a failed report on what looks like a completed backup. The data is there, the session tries to connect to the server and none are available and an entry in the client log as failed. ANS1512E Scheduled event BLAH-BLAH failed. Return code=12. After the 15 minute window it retries and sends the data to the server because this time it got a connection and it returns the next scheduled backup. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:gillg;saic.com [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Client Scheduler stopping/ TSM 5.1.5.1
re: missed backups because schedule service is stopped I have this problem. The most cases occur because the service fails to start after a reboot. There are other cases where it stops for no apparent reason. I've modified the recovery property for the scheduler service to restart the service. This has reduced the number of occurances but they still occur. On Tue, 5 Nov 2002, Gill, Geoffrey L. wrote: A short update to everyone watching the TSM 5.1.5.1 posts. I've been asked twice to change Resource Timeout value, which is now 100. Most of the missed backups I was having are gone but support still wants me to monitor for the lock I was seeing and then run a bunch of commands to gather info if I can. Unfortunately backups are so late I've just had it. It's not that I don't want to help, it's just so late I'm tired. As for the missed backups I am seeing now, I can tell it's because the schedule service is stopped. Since I don't have access to these computers I can't start it, don't know if it stopped on its own, or if someone purposefully stopped it. Are there any issues related to the Scheduler service stopping with certain levels of TSM client on WIN2K or NT? I'm also seeing a failed report on what looks like a completed backup. The data is there, the session tries to connect to the server and none are available and an entry in the client log as failed. ANS1512E Scheduled event BLAH-BLAH failed. Return code=12. After the 15 minute window it retries and sends the data to the server because this time it got a connection and it returns the next scheduled backup. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:gillg;saic.com [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Client Scheduler stopping/ TSM 5.1.5.1
A short update to everyone watching the TSM 5.1.5.1 posts. I've been asked twice to change Resource Timeout value, which is now 100. Most of the missed backups I was having are gone but support still wants me to monitor for the lock I was seeing and then run a bunch of commands to gather info if I can. Unfortunately backups are so late I've just had it. It's not that I don't want to help, it's just so late I'm tired. As for the missed backups I am seeing now, I can tell it's because the schedule service is stopped. Since I don't have access to these computers I can't start it, don't know if it stopped on its own, or if someone purposefully stopped it. Are there any issues related to the Scheduler service stopping with certain levels of TSM client on WIN2K or NT? I'm also seeing a failed report on what looks like a completed backup. The data is there, the session tries to connect to the server and none are available and an entry in the client log as failed. ANS1512E Scheduled event BLAH-BLAH failed. Return code=12. After the 15 minute window it retries and sends the data to the server because this time it got a connection and it returns the next scheduled backup. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:gillg;saic.com [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
urgent - 4.2.1 client scheduler frequently stops during backup
Hello all I have the 4.2.1.32 client running on a W2K server over a T1 WAN link. The backup of this client is generally less than 500M 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: 7/16/2002 Time: 8:04:38 PM User: N/A Computer: FILESERVER Description: The TSM Scheduler service terminated unexpectedly. It has done this 31 time(s). The following corrective action will be taken in 0 milliseconds: No action. This client uses the CAD to manage the scheduler and web client access. When the scheduler terminates, the CAD restarts it 10 minutes later, until the startup window for the backup expires. There are no errors in the dsmsched.log or dsmerror.log. The dsmwebcl.log file shows the restart after 10 minutes. The server activity log merely shows ANR0480W - the connection was severed. Because this is a WAN client, I've looked at COMMTimeout (600 seconds), IDLETimeout (30 minutes), client compression (ON), TCPBuffSize (128), TCPWindowSize (default=32), TCPNoDelay (NO). I can't tell what is causing the scheduler service to terminate. Any ideas? Would running the scheduler service full time, rather than using the CAD to manage it, remedy this problem? Thanks... Ken
Re: Sun Solaris 8 client scheduler dumps ...
Hi Edgar, I tried changing the SchedulerMode to prompted and polling without luck. At the moment I have got the dsmc incr command simply running on the cron which does the trick however obviously isn't the ideal solution. Other way that you can try, is configure the daemon Web Client manages both services: Web Client and Scheduler. How do you go about doing this ? Has anyone else found a way to get the scheduler working in this situation - perhaps via a patch or something? Thanks, Charles Hi. I have already had this problem, which was resolved configuring the TSM Client Scheduler in prompted mode. Other way that you can try, is configure the daemon Web Client manages both services: Web Client and Scheduler. I hope this is useful for you. Best Regards. -- Ing. Edgar Flores R. Soluciones en Sistemas e Informatica, S.A. de C.V. www.GrupoSSI.com.mx Tel. 55353949 e-mail: [EMAIL PROTECTED] Sun Solaris 8 TSM 5.1.0.0 client scheduler dumps core upon starting to execute a schedule Forum: ADSM.ORG - ADSM / TSM Mailing List Archive Date: Jul 03, 09:27 From: Charles Pizzato [EMAIL PROTECTED] I'm having a problem with the Sun TSM client (version 5.1.0.0) in that the scheduler dumps core on commencement of executing a scheduled command (be it Incremental or Command or whatever). I have traced the problem to the dsmagent binary which dumps core immediately when run. Has anyone got this problem/know of a solution? Other AIX/HP-UX clients work fine (it is just the Sun client). Also I can manually start the backup from the web interface without trouble. Thanks in advance, Charles The dsmerror.log file contains this error message: main thread, fatal error, signal 11 Sample output from dsmc sched: bash-2.03# dsmc sched Tivoli Storage Manager Command Line Backup/Archive Client Interface - Version 5, Release 1, Level 0.0 (C) Copyright IBM Corporation 1990, 2002 All Rights Reserved. Querying server for next scheduled event. Node Name: SUN02 Session established with server TSMSERV: AIX-RS/6000 Server Version 5, Release 1, Level 0.0 Server date/time: 07/03/02 17:40:49 Last access: 07/03/02 17:29:59 Next operation scheduled: Schedule Name: AUST-TEST Action:Incremental Objects: Options: Server Window Start: 17:40:06 on 07/03/02 Executing scheduled command now. Abort (core dumped) bash-2.03#
Sun Solaris 8 TSM 5.1.0.0 client scheduler dumps core upon starting to execute a schedule
I'm having a problem with the Sun TSM client (version 5.1.0.0) in that the scheduler dumps core on commencement of executing a scheduled command (be it Incremental or Command or whatever). I have traced the problem to the dsmagent binary which dumps core immediately when run. Has anyone got this problem/know of a solution? Other AIX/HP-UX clients work fine (it is just the Sun client). Also I can manually start the backup from the web interface without trouble. Thanks in advance, Charles The dsmerror.log file contains this error message: main thread, fatal error, signal 11 Sample output from dsmc sched: bash-2.03# dsmc sched Tivoli Storage Manager Command Line Backup/Archive Client Interface - Version 5, Release 1, Level 0.0 (C) Copyright IBM Corporation 1990, 2002 All Rights Reserved. Querying server for next scheduled event. Node Name: SUN02 Session established with server TSMSERV: AIX-RS/6000 Server Version 5, Release 1, Level 0.0 Server date/time: 07/03/02 17:40:49 Last access: 07/03/02 17:29:59 Next operation scheduled: Schedule Name: AUST-TEST Action:Incremental Objects: Options: Server Window Start: 17:40:06 on 07/03/02 Executing scheduled command now. Abort (core dumped) bash-2.03# Copyright 2002 ADC Telecommunications, Inc. This communication is the property of ADC and may contain information confidential and/or privileged. This communication has been transmitted for the exclusive use of the intended recipient. If you are not the intended recipient, please send a copy of it with the title Received in error to [EMAIL PROTECTED] and then delete the email and destroy any copies of it. You may not otherwise distribute, copy, or use this communication or the information in it in any manner. Please contact ADC at 780 431-6565 if you need assistance. Thank you for your cooperation.
Re: Client scheduler
TSM server had MST and I changed to EST, CUT -5, but the result was wrong one. So, I went to SMIT on AIX and changed time only without rebooting again. It looked fine and TSM was getting the right time. You're probably right on that, but I don't know how to calculate the difference in time. Do baclients need to be restarted after TSM server having been rebooted ? If not, as you said, I'll wait tonight to see if client schedules work. I just want to make sure that I don' need to do anything else. Thanks for your help. Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] 05/15/02 05:07PM Did the resulting change in time on the TSM server mean that the schedules were now past their startup window? Eg. 01:00 change time to 04:00 Client schedule is set to start at 02:00 - has 1 hour startup window In this case, the schedules would be misssed because TSM server was down (sort of) between 01:00 and 04:00 -Original Message- From: Jin Bae Chi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 3:35 PM To: [EMAIL PROTECTED] Subject: Client scheduler Hi, all, Last night I had to reboot the AIX on which TSM was running because I changed time zone on AIX. I made sure of no session and no process running and disabled sessions and 'halted' TSM. and shutdown and reboot AIX box. TSM came up automatically. I enabled sessions and accepted date. Well, everything looked normal. When I checked this morning, all client scheduler had been MISSED. What did I do wrong? Do I need to start admin scheduler from server manually? how? Any comment will be appreciated. Thanks Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED]
Re: Client scheduler
I would recommend doing basic troubleshooting.. check the TSM server activity log around the time the backup window occurred (e.g. - q act startt=01:00). What was the TSM server doing if not backing anyone up? Was it trying to contact the clients and failing to (there would be repeated contacting client blahblah msgs if it was). Is there nothing there except a client XX missed backup window at the end of the window? Ditto check the dsmsched.log on some of the clients. What were they doing around the supposed backup time? It should say clearly when they got their last schedule and what it was. Are your clients in prompted or polling mode? The reason for the missed backups could vary depending on what mode you use. If polling, what was the interval the clients poll at (default is 12 hours)? By looking at the logs you should be easily able to determine if it was a connectivity problem or if the clients simply missed their schedules due to an error in timing. You should also be able to see if the clients are receiving the schedules and what time they individually think they're supposed to being their backups. Some basic troubleshooting goes a long way.. Regards, Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -Original Message- From: Jin Bae Chi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 2:29 PM To: [EMAIL PROTECTED] Subject: Re: Client scheduler TSM server had MST and I changed to EST, CUT -5, but the result was wrong one. So, I went to SMIT on AIX and changed time only without rebooting again. It looked fine and TSM was getting the right time. You're probably right on that, but I don't know how to calculate the difference in time. Do baclients need to be restarted after TSM server having been rebooted ? If not, as you said, I'll wait tonight to see if client schedules work. I just want to make sure that I don' need to do anything else. Thanks for your help. Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] 05/15/02 05:07PM Did the resulting change in time on the TSM server mean that the schedules were now past their startup window? Eg. 01:00 change time to 04:00 Client schedule is set to start at 02:00 - has 1 hour startup window In this case, the schedules would be misssed because TSM server was down (sort of) between 01:00 and 04:00 -Original Message- From: Jin Bae Chi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 3:35 PM To: [EMAIL PROTECTED] Subject: Client scheduler Hi, all, Last night I had to reboot the AIX on which TSM was running because I changed time zone on AIX. I made sure of no session and no process running and disabled sessions and 'halted' TSM. and shutdown and reboot AIX box. TSM came up automatically. I enabled sessions and accepted date. Well, everything looked normal. When I checked this morning, all client scheduler had been MISSED. What did I do wrong? Do I need to start admin scheduler from server manually? how? Any comment will be appreciated. Thanks Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED]
Re: Client scheduler
Thanks for giving me a good insight. I'm attaching the actlog from 00:00.(I'm sorry if it's too long). We have client polling every 12 hours. It looks like the client started and couldn't connect with the server and ended inmmediately. Today I did a test on one of client node. I rebooted the client node and ran its schedule and it went OK. I suspect all other nodes need to be restarted or rebooted to able to connect to the server with new time. If that's the case, there are too many nodes that need to be rebooted. Please correct me if I'm wrong. Thanks again. 05/15/02 00:00:12 ANR0403I Session 414 ended for node COMPAQ2 (Win95). 05/15/02 00:00:15 ANR0407I Session 422 started for administrator JBAECHI (WebBrowser) (HTTP 10.2.11.119(1251)). 05/15/02 00:00:15 ANR2017I Administrator JBAECHI issued command: QUERY ACTLOG 05/15/02 00:00:15 ANR0405I Session 422 ended for administrator JBAECHI (WebBrowser). 05/15/02 00:01:22 ANR0406I Session 434 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1263)). 05/15/02 00:01:24 ANR0406I Session 435 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1264)). 05/15/02 00:01:30 ANR2562I Automatic event record deletion started. 05/15/02 00:01:30 ANR2565I 0 schedules for immediate client actions have been deleted. 05/15/02 00:01:30 ANR2563I Removing event records dated prior to 05/08/02 00:00:00. 05/15/02 00:01:30 ANR2564I Automatic event record deletion ended - 40 records deleted. 05/15/02 00:02:32 ANR0403I Session 434 ended for node COMPAQ2 (Win95). 05/15/02 00:02:33 ANR0403I Session 435 ended for node COMPAQ2 (Win95). 05/15/02 00:02:47 ANR0406I Session 436 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1265)). 05/15/02 00:02:51 ANR0403I Session 436 ended for node COMPAQ2 (Win95). 05/15/02 00:05:33 ANR0406I Session 437 started for node DUBLIN (NetWare) (Tcp/Ip 10.15.1.5(3003)). 05/15/02 00:05:33 ANR0403I Session 437 ended for node DUBLIN (NetWare). 05/15/02 00:05:33 ANR0406I Session 438 started for node DUBLIN (NetWare) (Tcp/Ip 10.15.1.5(3004)). 05/15/02 00:05:33 ANR0403I Session 438 ended for node DUBLIN (NetWare). 05/15/02 00:06:38 ANR0406I Session 439 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1266)). 05/15/02 00:06:40 ANR0403I Session 439 ended for node COMPAQ2 (Win95). 05/15/02 00:10:59 ANR0406I Session 440 started for node BOLTON (NetWare) (Tcp/Ip 10.13.1.5(1842)). 05/15/02 00:11:00 ANR0403I Session 440 ended for node BOLTON (NetWare). 05/15/02 00:11:00 ANR0406I Session 441 started for node BOLTON (NetWare) (Tcp/Ip 10.13.1.5(1843)). 05/15/02 00:11:00 ANR0403I Session 441 ended for node BOLTON (NetWare). 05/15/02 00:17:45 ANR0406I Session 442 started for node GLOBAL (WinNT) (Tcp/Ip 10.51.1.5(1619)). 05/15/02 00:17:45 ANR0403I Session 442 ended for node GLOBAL (WinNT). 05/15/02 00:17:45 ANR0406I Session 443 started for node GLOBAL (WinNT) (Tcp/Ip 10.51.1.5(1620)). 05/15/02 00:17:45 ANR0403I Session 443 ended for node GLOBAL (WinNT). [EMAIL PROTECTED] 05/15/02 07:02PM I would recommend doing basic troubleshooting.. check the TSM server activity log around the time the backup window occurred (e.g. - q act startt=01:00). What was the TSM server doing if not backing anyone up? Was it trying to contact the clients and failing to (there would be repeated contacting client blahblah msgs if it was). Is there nothing there except a client XX missed backup window at the end of the window? Ditto check the dsmsched.log on some of the clients. What were they doing around the supposed backup time? It should say clearly when they got their last schedule and what it was. Are your clients in prompted or polling mode? The reason for the missed backups could vary depending on what mode you use. If polling, what was the interval the clients poll at (default is 12 hours)? By looking at the logs you should be easily able to determine if it was a connectivity problem or if the clients simply missed their schedules due to an error in timing. You should also be able to see if the clients are receiving the schedules and what time they individually think they're supposed to being their backups. Some basic troubleshooting goes a long way.. Regards, Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -Original Message- From: Jin Bae Chi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 2:29 PM To: [EMAIL PROTECTED] Subject: Re: Client scheduler TSM server had MST and I changed to EST, CUT -5, but the result was wrong one. So, I went
Re: Client scheduler
There isn't any reason to reboot the clients.. At worst all you need to do is stop/start the dsmc schedule process. How you go about that is dependent on the operating system. On NT/2000 it's a service you just click stop and start. On Unix you kill the dsmc sched process and restart it. Regardless it's highly unlikely that needs to be done for something like a time change. The output sent is relatively useless. It shows clients connecting to the server successfully and doing something. What are they doing? Who knows.. Maybe they're polling the server for a schedule. Maybe they're actually performing a backup. I don't know because I only see a 17 minute timeframe of your activity log. You need to look at the entire activity log for your backup window. Since I don't know how big your scheduled backup window is I don't know how much that would be either. Bottom line is it'd be inappropriate to post it on this list anyways so don't do it. In order to really know whats going on between a given client and the TSM server you also need to look at the client's dsmsched.log file. Comparing that with the same window of time on the TSM server's activity log should paint a real clear picture of what the two were doing and why the schedule was missed. Do not post any more logs here. You need to look at them yourself and troubleshoot. It's highly likely the backups will run fine tonight and it was simple a discrepancy in time as was mentioned previously. There are a number of ways this can occur but the fact that you are in polling mode with the interval set to 12 hours makes it even more likely. If this is not something you feel comfortable solving yourself then pick up the phone and call Tivoli support. That's what they're there for and they'll figure it out quicker then doing so here. Regards, Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -Original Message- From: Jin Bae Chi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 5:03 PM To: [EMAIL PROTECTED] Subject: Re: Client scheduler Thanks for giving me a good insight. I'm attaching the actlog from 00:00.(I'm sorry if it's too long). We have client polling every 12 hours. It looks like the client started and couldn't connect with the server and ended inmmediately. Today I did a test on one of client node. I rebooted the client node and ran its schedule and it went OK. I suspect all other nodes need to be restarted or rebooted to able to connect to the server with new time. If that's the case, there are too many nodes that need to be rebooted. Please correct me if I'm wrong. Thanks again. 05/15/02 00:00:12 ANR0403I Session 414 ended for node COMPAQ2 (Win95). 05/15/02 00:00:15 ANR0407I Session 422 started for administrator JBAECHI (WebBrowser) (HTTP 10.2.11.119(1251)). 05/15/02 00:00:15 ANR2017I Administrator JBAECHI issued command: QUERY ACTLOG 05/15/02 00:00:15 ANR0405I Session 422 ended for administrator JBAECHI (WebBrowser). 05/15/02 00:01:22 ANR0406I Session 434 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1263)). 05/15/02 00:01:24 ANR0406I Session 435 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1264)). 05/15/02 00:01:30 ANR2562I Automatic event record deletion started. 05/15/02 00:01:30 ANR2565I 0 schedules for immediate client actions have been deleted. 05/15/02 00:01:30 ANR2563I Removing event records dated prior to 05/08/02 00:00:00. 05/15/02 00:01:30 ANR2564I Automatic event record deletion ended - 40 records deleted. 05/15/02 00:02:32 ANR0403I Session 434 ended for node COMPAQ2 (Win95). 05/15/02 00:02:33 ANR0403I Session 435 ended for node COMPAQ2 (Win95). 05/15/02 00:02:47 ANR0406I Session 436 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1265)). 05/15/02 00:02:51 ANR0403I Session 436 ended for node COMPAQ2 (Win95). 05/15/02 00:05:33 ANR0406I Session 437 started for node DUBLIN (NetWare) (Tcp/Ip 10.15.1.5(3003)). 05/15/02 00:05:33 ANR0403I Session 437 ended for node DUBLIN (NetWare). 05/15/02 00:05:33 ANR0406I Session 438 started for node DUBLIN (NetWare) (Tcp/Ip 10.15.1.5(3004)). 05/15/02 00:05:33 ANR0403I Session 438 ended for node DUBLIN (NetWare). 05/15/02 00:06:38 ANR0406I Session 439 started for node COMPAQ2 (Win95) (Tcp/Ip 10.2.11.119(1266)). 05/15/02 00:06:40 ANR0403I Session 439 ended for node COMPAQ2 (Win95). 05/15/02 00:10:59 ANR0406I Session 440 started for node BOLTON (NetWare) (Tcp/Ip 10.13.1.5(1842)). 05/15/02 00:11:00 ANR0403I Session 440 ended for node BOLTON (NetWare). 05/15/02 00:11:00 ANR0406I Session 441 started for node BOLTON (NetWare
TSM 4.2.1 client scheduler problems
We have just upgrade our AIX TSM server to 4.2.1.13. Some of our users have upgraded the clients (AIX and Solaris) to 4.2.1.X (whatever is LATEST). A strange thing is happening, for clients using the scheduler, that have a pre and post schedule command defined. When the scheduler fires off, it does not send any files, it just runs the pre/post schedule (rc=0) and ends. If we remove the pre/post schedule, the scheduler backs up files normally. Presently, the pre/post schedule commands don't run anything on the clients we have tested, they just exit (they are actually just templates of things to be defined later). The clients did not have this problem at 4.1.3. Anyone seen this problem? For now, we have removed the pre/post from the problem clients, but this will be a glitch in the future. thanks, Bob
Re: when to recycle client scheduler service?
This information might help you, even though your post indicates that you are using schedmode polled rather than our practice, which is schedmode prompted. We noticed that, over time, our IRIX 6.5.x clients' allocation of memory (especially swap space) grew out of proportion, eventually requiring either (1) recycling the client, or (2) rebooting the system. Most of our administrators had been using kill -9 dsmc-pid, but that did not return allocated resources to the system. The alternative we found to work was kill -HUP dsmc-pid, which did allow cleanup. However, all this monitoring and recycling turned out to be a bit much of a chore for a couple hundred clients, so we looked into other options, and found the Client Acceptor Daemon/Service (dsmcad). This great little program handles the problem nicely for us, since it is small (SZ/RSS~=180/150, and never grows), and it handles the cycling of the dsmc sched program properly, so that system resources are returned at the end of every backup. I suggest that you check the on-line documentation and try the Client Acceptor Daemon or Service (Daemon for UNIX, Service for the Monster from Microsoft), and see if it helps. You will have to ensure the line: managedservices schedule is in your dsm.opt file. Dennis Glover Systems Analyst/Backup Administrator Integrated System Test Capability Advanced Research Center Colsa Corporation Huntsville, Alabama USA!
Re: when to recycle client scheduler service?
Have you turned in a problem on this to Tivoli? Second, we need more information. What type of server and client and what levels of code? -Original Message- From: Glass, Peter [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 21, 2002 4:40 PM To: [EMAIL PROTECTED] Subject: when to recycle client scheduler service? Hello, Folks! We happened to have the TSM Server down during a time when a certain client would have been polled for a backup that was to take place 12 hours later. Our polling intervals are 4 hours apart. TSM last polled this clients 4 hours previously, and did not resume any polling of this client until the next day, when the client scheduler service was recycles. In the meantime, they missed their backup. Did polling for this client stop because the TSM Server happened to be down during the time this client would have been polled? Does missing even 1 poll suffice to require recycling of the scheduler service for the client? It seems that we are always needing to have clients recycle their scheduler services, for reasons often unclear. We often don't know until the client has missed their backup -- we really need to know beforehand, so we can better prevent missed schedules. If somebody can produce or point us to a summary of which conditions require recycling of client scheduler services, we would be most grateful. We would also welcome any other tips on how to deal with this situation -- especially if there is a way to automate this into a non-issue. Thanks, in advance. Peter Glass Distributed Storage Management (DSM) Wells Fargo Services Company * [EMAIL PROTECTED]
when to recycle client scheduler service?
Hello, Folks! We happened to have the TSM Server down during a time when a certain client would have been polled for a backup that was to take place 12 hours later. Our polling intervals are 4 hours apart. TSM last polled this clients 4 hours previously, and did not resume any polling of this client until the next day, when the client scheduler service was recycles. In the meantime, they missed their backup. Did polling for this client stop because the TSM Server happened to be down during the time this client would have been polled? Does missing even 1 poll suffice to require recycling of the scheduler service for the client? It seems that we are always needing to have clients recycle their scheduler services, for reasons often unclear. We often don't know until the client has missed their backup -- we really need to know beforehand, so we can better prevent missed schedules. If somebody can produce or point us to a summary of which conditions require recycling of client scheduler services, we would be most grateful. We would also welcome any other tips on how to deal with this situation -- especially if there is a way to automate this into a non-issue. Thanks, in advance. Peter Glass Distributed Storage Management (DSM) Wells Fargo Services Company * [EMAIL PROTECTED]
pc client scheduler looks at 1 server, gui looks at another serve r
Hello, I have TSM 4.1.4 on one z/OS 1.1 lpar and I am trying to test TSM 4.1.5 on a different z/OS 1.1 lpar. The client that I am testing is a Win2000 4.1.12 client. I changed the IP address in the DSM.OPT file, stopped the scheduler, client acceptor, and remote client. The client is defined to bothe the 4.1.4 (production) system and the 4.1.5 (test system). I started the schedule and it started communicating with the production system even though the IP address of the test system is in the DSM.OPT. I started the GUI client and it started a session with the test system. How can this be? I bounced the PC, same situation. I shutdown all 3 and left them down for an hour to let any network cache clear out, same effect. I changed the ip address again so it would use a different shared adapter and restarted everything. Same situation. What is going on? Matt
Re: TSM Win2K 4.2.0 client scheduler problems
This sounds like a bad design. How about a Correction of the Design process? Jeff Bach -Original Message- From: Eliza Lau [SMTP:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 3:49 PM To: [EMAIL PROTECTED] Subject:Re: TSM Win2K 4.2.0 client scheduler problems I just got off the phone with TSM level 2 support. This is a known problem with the Windows 2000 4.2.0 client. It is a timing issue. The client can't get the password from the server and tries 3 times. A second later it gets it. The developers have no fixes for this, no APAR either. They may just document it as working as designed. Beside getting these erroneous errors in dsmerror.log and the event log, scheduled backup works just fine. Eliza I have the excact same experience - and have found no other solution than to go back to TSM v4.1 lev. 2.19. Then the problem was gone. Server: TSM v4.1 lev 1.0 on OS/390 Client: Windows NT 4.0, SP6 Henrik Bach Gravesen Jyske Bank A/S, Denmark [EMAIL PROTECTED] A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399 ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **
Re: TSM Win2K 4.2.0 client scheduler problems
Check the adsm-l archives at www.adsm.org for my response back on August 9 with regard to this issue. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Jeff Bach [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/14/2001 06:00 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: TSM Win2K 4.2.0 client scheduler problems This sounds like a bad design. How about a Correction of the Design process? Jeff Bach -Original Message- From: Eliza Lau [SMTP:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 3:49 PM To: [EMAIL PROTECTED] Subject:Re: TSM Win2K 4.2.0 client scheduler problems I just got off the phone with TSM level 2 support. This is a known problem with the Windows 2000 4.2.0 client. It is a timing issue. The client can't get the password from the server and tries 3 times. A second later it gets it. The developers have no fixes for this, no APAR either. They may just document it as working as designed. Beside getting these erroneous errors in dsmerror.log and the event log, scheduled backup works just fine. Eliza I have the excact same experience - and have found no other solution than to go back to TSM v4.1 lev. 2.19. Then the problem was gone. Server: TSM v4.1 lev 1.0 on OS/390 Client: Windows NT 4.0, SP6 Henrik Bach Gravesen Jyske Bank A/S, Denmark [EMAIL PROTECTED] A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399 ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **
Re: TSM Win2K 4.2.0 client scheduler problems
I just got off the phone with TSM level 2 support. This is a known problem with the Windows 2000 4.2.0 client. It is a timing issue. The client can't get the password from the server and tries 3 times. A second later it gets it. The developers have no fixes for this, no APAR either. They may just document it as working as designed. Beside getting these erroneous errors in dsmerror.log and the event log, scheduled backup works just fine. Eliza I have the excact same experience - and have found no other solution than to go back to TSM v4.1 lev. 2.19. Then the problem was gone. Server: TSM v4.1 lev 1.0 on OS/390 Client: Windows NT 4.0, SP6 Henrik Bach Gravesen Jyske Bank A/S, Denmark [EMAIL PROTECTED] A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399
Re: TSM Win2K 4.2.0 client scheduler problems
I don't know the technical details surrounding this problem or why it (supposedly) can't be fixed (I don't like the word can't), but I can assure you that there *will* be an APAR. If/when it will be fixed is another matter, but it needs to be formally documented. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Eliza Lau [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2001 13:49 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: TSM Win2K 4.2.0 client scheduler problems I just got off the phone with TSM level 2 support. This is a known problem with the Windows 2000 4.2.0 client. It is a timing issue. The client can't get the password from the server and tries 3 times. A second later it gets it. The developers have no fixes for this, no APAR either. They may just document it as working as designed. Beside getting these erroneous errors in dsmerror.log and the event log, scheduled backup works just fine. Eliza I have the excact same experience - and have found no other solution than to go back to TSM v4.1 lev. 2.19. Then the problem was gone. Server: TSM v4.1 lev 1.0 on OS/390 Client: Windows NT 4.0, SP6 Henrik Bach Gravesen Jyske Bank A/S, Denmark [EMAIL PROTECTED] A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399
SV: TSM Win2K 4.2.0 client scheduler problems
I have the excact same experience - and have found no other solution than to go back to TSM v4.1 lev. 2.19. Then the problem was gone. Server: TSM v4.1 lev 1.0 on OS/390 Client: Windows NT 4.0, SP6 Henrik Bach Gravesen Jyske Bank A/S, Denmark [EMAIL PROTECTED] A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399
TSM Win2K 4.2.0 client scheduler problems
A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399
Re: Stop/Starting TSM client scheduler
Hi: I just do a ps -ef | grep dsm, then kill the process. root 11392 1 0 Nov 09 - 6:07 /usr/tivoli/tsm/client/ba/bin/dsm c sched To restart I place the command in a file and run the file: file /home/root/runtsmclient: /usr/tivoli/tsm/client/ba/bin/dsmc sched /dev/null 21 /home/root/tsmclient [EMAIL PROTECTED] 11/17/00 03:26PM Can anyone tell me the client command to stop the client scheduler, then to start it up again?? We are using an AIX 4.3, TSM 3.7 client. Thanks in advance Ken Sedlacek ITI-Kyrus Corp. Direct: 864-322-4260 Mobile: 864-444-8375 Page: 864-444-7243, follow prompts [EMAIL PROTECTED]
Re: Stop/Starting TSM client scheduler
Hello, I don't use aix but on solaris I do ps -eaf | grep dsm and then I kill -9 the process number for 'dsmc schedule' Mark Brown Ken Sedlacek wrote: Can anyone tell me the client command to stop the client scheduler, then to start it up again?? We are using an AIX 4.3, TSM 3.7 client. Thanks in advance Ken Sedlacek ITI-Kyrus Corp. Direct: 864-322-4260 Mobile: 864-444-8375 Page: 864-444-7243, follow prompts [EMAIL PROTECTED] -- Mark Brown Operations Supervisor = Tel --- 514-398-2321 Fax --- 514-398-6876 E-mail --- [EMAIL PROTECTED]
Re: Stop/Starting TSM client scheduler
ps -ef | grep dsm get the processor number - kill Frank Mauro Liberty Mutual Backup and Recovery Services [EMAIL PROTECTED] 603.245.3207 -Original Message- From: Ken Sedlacek [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 17, 2000 3:26 PM To: [EMAIL PROTECTED] Subject: Stop/Starting TSM client scheduler Can anyone tell me the client command to stop the client scheduler, then to start it up again?? We are using an AIX 4.3, TSM 3.7 client. Thanks in advance Ken Sedlacek ITI-Kyrus Corp. Direct: 864-322-4260 Mobile: 864-444-8375 Page: 864-444-7243, follow prompts [EMAIL PROTECTED]
Re: Stop/Starting TSM client scheduler
net stop "process name" (replace process name with actual process) net start "process name" - Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays!
Re: Stop/Starting TSM client scheduler
ps -ef | grep sched then look for the process number kill dsmc_sched_process_number I set up in inittab rootlsitab -a | grep sched adsm:2:respawn:/usr/tivoli/tsm/client/ba/bin/dsmc sched /dev/null 21 now to start it from the aix prompt nohup /usr/tivoli/tsm/client/ba/bin/dsmc sched /dev/null 21 later, Dwight -Original Message- From: Ken Sedlacek [mailto:[EMAIL PROTECTED]] Sent: Friday, November 17, 2000 2:26 PM To: [EMAIL PROTECTED] Subject: Stop/Starting TSM client scheduler Can anyone tell me the client command to stop the client scheduler, then to start it up again?? We are using an AIX 4.3, TSM 3.7 client. Thanks in advance Ken Sedlacek ITI-Kyrus Corp. Direct: 864-322-4260 Mobile: 864-444-8375 Page: 864-444-7243, follow prompts [EMAIL PROTECTED]
Windows NT Client scheduler
Hi there ! I have a problem with my ADSM Scheduler for Windows NT. When i try to start it, it tells me that it can't start the service: Could not start the ADSM Scheduler service on \\xx Error 0193: %1 is not a valid Windows NT application. This only happens on one Windows NT server ver. 4.0 SP 4. I'am running ADSM ver. 3.1.2.58 under AIX. I hope that anyone out there can help me, i have tryied to reboot the server, uninstall and install the ADSM client again, but nothing works. Kind regards. Peter
Re: Windows NT Client scheduler
Thank you vary much, it did the trick I can only say, thanks for this way off communicating, i have had this problem for 2 months and no one has been able to help me. Best regards Peter "Ilja G. Coolen" [EMAIL PROTECTED] - 12-09-2000 11:50:24 Besvar venligst til "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Til: [EMAIL PROTECTED] cc: (bcc: Peter Svendsen/ABR/ALMBRAND) Vedrørende:Re: Windows NT Client scheduler Peter, At the client, open the registry-editor and find the ADSM keys. In those keys there's a path to the dsmsrvc.exe. This would look like c:\program files\ibm\adsm\baclient\dsmsrvc.exe. The path will not be found because of the space in program file. This is a setting somewhere else in the registry, regarding long filename support. Just change "program files" to "progra~1" and all should work fine. Good Luck -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Peter Svendsen Verzonden: dinsdag 12 september 2000 11:09 Aan: [EMAIL PROTECTED] Onderwerp: Windows NT Client scheduler Hi there ! I have a problem with my ADSM Scheduler for Windows NT. When i try to start it, it tells me that it can't start the service: Could not start the ADSM Scheduler service on \\xx Error 0193: %1 is not a valid Windows NT application. This only happens on one Windows NT server ver. 4.0 SP 4. I'am running ADSM ver. 3.1.2.58 under AIX. I hope that anyone out there can help me, i have tryied to reboot the server, uninstall and install the ADSM client again, but nothing works. Kind regards. Peter
Re: Windows NT Client scheduler
use the /clientdir: option on installing the scheduler cant remember the apar # but is a known problem. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Svendsen Sent: Tuesday, September 12, 2000 5:09 AM To: [EMAIL PROTECTED] Subject: Windows NT Client scheduler Hi there ! I have a problem with my ADSM Scheduler for Windows NT. When i try to start it, it tells me that it can't start the service: Could not start the ADSM Scheduler service on \\xx Error 0193: %1 is not a valid Windows NT application. This only happens on one Windows NT server ver. 4.0 SP 4. I'am running ADSM ver. 3.1.2.58 under AIX. I hope that anyone out there can help me, i have tryied to reboot the server, uninstall and install the ADSM client again, but nothing works. Kind regards. Peter
