Re: TSM client scheduler issue

2014-05-20 Thread Arbogast, Warren K
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 
>  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

2014-05-20 Thread Swartz, Jerome
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  
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

2014-05-20 Thread Remco Post
tsm rc -53 means auth failure iirc, check your password settings.

Op 20 mei 2014, om 15:03 heeft Swartz, Jerome  
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

2014-05-20 Thread Vandeventer, Harold [BS]
Can you PING the IP of the TSM Server?
Or TELNET  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.
***


TSM client scheduler issue

2014-05-20 Thread Swartz, Jerome
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

2011-06-15 Thread Rainer Strunz
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.


Re: rc-scripts to start and stop multiple tsm client scheduler for linux red hat

2011-06-14 Thread Howard Coles
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 2>&1 &
/opt/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null 2>&1 &
;;
  '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 2>&1 &
/opt/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null 2>&1 &
;;
  *)
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.


Antwort: [ADSM-L] rc-scripts to start and stop multiple tsm client scheduler for linux red hat

2011-06-14 Thread Ullrich Mänz
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 
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" 



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.


rc-scripts to start and stop multiple tsm client scheduler for linux red hat

2011-06-14 Thread TSM
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: Tsm client scheduler 6.2 with centos linux

2010-05-18 Thread Remco Post
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: Tsm client scheduler 6.2 with centos linux

2010-05-18 Thread Richard Sims
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


Tsm client scheduler 6.2 with centos linux

2010-05-18 Thread Lee, Gary D.
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: Client hangs when TSM Client Acceptor starts TSM Client Scheduler.

2009-03-18 Thread Clark, Robert A
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.


Re: Client hangs when TSM Client Acceptor starts TSM Client Scheduler.

2009-03-10 Thread Andrew Raibeck
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"  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" 
>
> 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: Client hangs when TSM Client Acceptor starts TSM Client Scheduler.

2009-03-10 Thread Richard Sims

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


Client hangs when TSM Client Acceptor starts TSM Client Scheduler.

2009-03-10 Thread Clark, Robert A
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: 网易邮箱自动回复: [ADSM-L] TSM Client Scheduler v5.3.0 - Windows 2003 server

2005-09-12 Thread Scott Pichelman
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" 
09/12/2005 03:48 PM
Please respond to
"ADSM: Dist Stor Manager" 


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.


TSM Client Scheduler v5.3.0 - Windows 2003 server

2005-09-12 Thread Scott Pichelman
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

Re: TSM client scheduler

2003-08-06 Thread Prather, Wanda
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

2003-08-03 Thread Bill Boyer
Switch to the MANAGEDSERVICES SCHEDULE option. We've seen less "missed"
events since changing over.

Bill Boyer
DSS, Inc.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Andrew Raibeck
Sent: Sunday, August 03, 2003 9:08 AM
To: [EMAIL PROTECTED]
Subject: 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


Re: TSM client scheduler

2003-08-03 Thread Andrew Raibeck
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

2003-08-02 Thread Zosimo Noriega
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

2003-06-06 Thread Joshua Bassi
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


Re: Stop/Starting TSM client scheduler

2000-11-17 Thread Cook, Dwight E

ps -ef | grep sched
then look for the process number
kill dsmc_sched_process_number

I set up in inittab
root>lsitab -a | grep sched
adsm:2:respawn:/usr/tivoli/tsm/client/ba/bin/dsmc sched >/dev/null 2>&1

now to start it from the aix prompt
nohup /usr/tivoli/tsm/client/ba/bin/dsmc sched >/dev/null 2>&1  &

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]



Re: Stop/Starting TSM client scheduler

2000-11-17 Thread James Healy

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

2000-11-17 Thread Mauro Jr, Frank

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

2000-11-17 Thread Mark Brown

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

2000-11-17 Thread Lawrence Clark

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 2>&1 &

/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] 



Stop/Starting TSM client scheduler

2000-11-17 Thread Ken Sedlacek

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]