I also recommend using another switch /clientdir:{path name to baclient
directory}. Make sure you use quotes if the path has a space in it. I've had
problems in the past without using that option and I needed to remove the
service and reinstall to fix the problem.
Geoff Gill
NT Systems Support Engineer
SAIC
Computer Systems Group
E-Mail: [EMAIL PROTECTED]
Phone: (858) 826-4062
Pager: (888) 997-9614
>-----Original Message-----
>From: Lawrence Clark [mailto:[EMAIL PROTECTED]]
>Sent: Monday, October 02, 2000 11:19 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Nt client processes
>
>
>Hi Jim:
>Thanks. Our MS-SQL agents services were installed using the
>dsmcutil command, but I do not recall having done that for the
>backup client under 3.1
>
>>>> [EMAIL PROTECTED] 10/02/00 01:57PM >>>
>You are missing a service. With TSM 3.7 you need to run a
>utility from the
>BAClient Directory like:
>
>dsmcutil install sched /name:"TSM Scheduler Service" /node:{nodename}
>/password:{node_password} /autostart:yes /validate:yes
>
>This will create the service for backups. The TSM Remote Client Agent
>should be on manual it is used by the TSM Client Acceptor when
>you attach to
>the client using the web.
>
>
>Jim Murray
>Senior Systems Engineer
>Liberty Bank
>[EMAIL PROTECTED]
>(860)638-2919
>On a clear disk you can
>seek forever!
>
>
>-----Original Message-----
>From: Lawrence Clark [mailto:[EMAIL PROTECTED]]
>Sent: Monday, October 02, 2000 1:38 PM
>To: [EMAIL PROTECTED]
>Subject: Nt client processes
>
>
>Hi:
>I just upgraded one NT server from the ADSM 3.1 client to TSM 3.7.
>I noticed it wasn't backing up and checked the NT services.
>Instead of the
>single service that existed previously under ADSM, I noticed
>there are now
>two services:
>TSM Client Acceptor
>TSM Remote Client Agent
>
>The Remote Client Agent was not started and so I'm assuming
>that was the
>cause of the missed backup. But what distinguishes these two services ?
>
>Larry Clark
>NYS Thruway Authority
>
>
