Gary,
There ought to be way to nail this one down. You seem to be
getting a behavior that cannot be explained by the facts, given our
collective experience with the product. So let's replay the details and
see if we are all overlooking the same thing. Tell me if any of my
facts are wrong:
1) Your client option is set to "schedmode prompted".
2) The client service has been restarted since "schedmode prompted" was
added?
3) Since the last time you restarted the client service, the scheduler
has run a regular client backup.
4) You are running a fairly recent version of the client and server? I
don't think you said what versions are involved.
5) You have checked the dsmsched.log and you know there is not already a
backup currently running or hung.
6) When you do a 'q event * * node=xxxxxx' you only see the client
action, and it is pending. You don't see any other events still
running? What if you add 'begint' and 'begind' to your 'q event' and go
back in time a ways?
6) You have checked the server actlog and you don't see any messages
from the server trying to connect to the client but being refused?
These messages may only contain the IP address of the client, not the
client name, so be sure you don't search through the activity log and
filter for the client name only.
7) There is not a firewall or other IP filter between client and server?
I have seen a firewall mess up a client action, even when the regular
client schedule was working. The fix was to restart the client service
one more time after the client action was scheduled.
Let me know if any of these ideas yield fruit.
(By the way, my nephew and his wife are both grad students at Ball
State. They say it is a great school.)
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: "Lee, Gary D." <g...@bsu.edu>
Date: Fri, June 19, 2009 1:46 pm
To: ADSM-L@VM.MARIST.EDU
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:ads...@vm.marist.edu] On Behalf Of
John Monahan
Sent: Friday, June 19, 2009 2:37 PM
To: ADSM-L@VM.MARIST.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.mona...@us.logicalis.com
http://www.us.logicalis.com
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
> Of Huebner,Andy,FORT WORTH,IT
> Sent: Friday, June 19, 2009 11:37 AM
> To: ADSM-L@VM.MARIST.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:ads...@vm.marist.edu] On Behalf
> Of Lee, Gary D.
> Sent: Friday, June 19, 2009 10:17 AM
> To: ADSM-L@VM.MARIST.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.
