Greetings,
In order for a Define Clientaction to work right away, you have to
either restart the scheduler service (or daemon) so it checks for the
next schedule, or run the client in 'schedmode prompted' mode.
I don't think you mentioned if you were in 'schedmode prompted' or not.
If not, add that to your options file and restart the service. It
should start within five minutes. We do 5-10 of these every day at
least.
Another problem that can happen is IP problems between the server and
client, like not being able to resolve the host name, or some such. But
if regular schedules have been running OK, it probably isn't that. The
activity log will show you if the TSM server is trying to start the
schedule, and if the client is ignoring the server, or rejecting the
connection, or whatever. You should check the activity log. It you are
in 'schedmode polling' instead of 'prompted', you won't get anything in
the activity log, because the TSM server is content to wait until the
client happens to check to see if a new schedule has been created for
it.
Best Regards,
John D. Schneider
The Computer Coaching Community, LLC
Office: (314) 635-5424
Toll Free: (866) 796-9226
Cell: (314) 750-8721
Best Regards,
John D. Schneider
The Computer Coaching Community, LLC
Office: (314) 635-5424
Toll Free: (866) 796-9226
Cell: (314) 750-8721
-------- Original Message --------
Subject: Re: [ADSM-L] Making sure clientactions start
From: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>
Date: Fri, June 19, 2009 2:25 pm
To: ADSM-L AT VM.MARIST DOT EDU
I agree, we run about 1,200 of these each night without a problem
related to the define clientaction command.
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
John Monahan
Sent: Friday, June 19, 2009 2:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Making sure clientactions start
I think something is still wrong or unique in your environment. I
deploy scripts that run immediate clientactions all the time at several
of my customers and they always start within a minute or two unless
there is a problem.
______________________________
John Monahan
Infrastructure Services Consultant
Logicalis, Inc.
5500 Wayzata Blvd Suite 315
Golden Valley, MN 55416
Office: 763-226-2088
Mobile: 952-221-6938
Fax: 763-226-2081
John.Monahan AT us.logicalis DOT com
http://www.us.logicalis.com
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Lee, Gary D.
> Sent: Friday, June 19, 2009 1:46 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Making sure clientactions start
>
> Status on server is pending.
> Communications is good, client backs up nightly as it is supposed to.
> We were testing an include option.
>
> I agree with Richard, there needs to be some way to specify when it
> should run.
>
> I checked the server log, and after two hours the scheduler had not
> attempted to contact the client.
> This is a recurring problem with clientactions, and needs to be
> addressed.
>
> Thank you all for your suggestions.
>
>
>
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of John Monahan
> Sent: Friday, June 19, 2009 2:37 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Making sure clientactions start
>
> Is the status from the server side pending or started (or something
> else)?
>
> The client can only run one scheduled task at a time. Another
> possibility is it is still running something else.
>
> ______________________________
>
> John Monahan
> Infrastructure Services Consultant
> Logicalis, Inc.
> 5500 Wayzata Blvd Suite 315
> Golden Valley, MN 55416
> Office: 763-226-2088
> Mobile: 952-221-6938
> Fax: 763-226-2081
> John.Monahan AT us.logicalis DOT com
> http://www.us.logicalis.com
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf
> > Of Huebner,Andy,FORT WORTH,IT
> > Sent: Friday, June 19, 2009 11:37 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Making sure clientactions start
> >
> > Is the client running is schedule mode? If so stop and start the
> > acceptor and wait 1 minute then check the log.
> > If you are looking for reason, then check the server log, a quick
> > search on the node name should help. Our most common problem is the
> > server cannot contact the node due to an IP resolution problem.
> When
> > the scheduler contacts the server IP resolution is not needed to
> start
> > the job.
> >
> > Andy Huebner
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf
> > Of Lee, Gary D.
> > Sent: Friday, June 19, 2009 10:17 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] Making sure clientactions start
> >
> > I have a clientaction defined for a node whose schedmode is set to
> > prompted.
> > However, I have now been waiting for 45 minutes for the action to
> take
> > place.
> >
> > Is there a way to get the server to kick itself and prompt the
> client
> > to perform the actions in a clientaction?
> >
> > Gary Lee
> > Senior System Programmer
> > Ball State University
> > phone: 765-285-1310
> >
> >
> >
> >
> > This e-mail (including any attachments) is confidential and may be
> > legally privileged. If you are not an intended recipient or an
> > authorized representative of an intended recipient, you are
> prohibited
> > from using, copying or distributing the information in this e-mail
> or
> > its attachments. If you have received this e-mail in error, please
> > notify the sender immediately by return e-mail and delete all copies
> > of this message and any attachments.
> > Thank you.
This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this e-mail or
its attachments. If you have received this e-mail in error, please
notify the sender immediately by return e-mail and delete all copies of
this message and any attachments.
Thank you.
|
