I have a similar question, I thought by stopping the scheduler service on the client that it would then poll. I think it is because I see the entry in the sched.log file. The problem is it's not immediate, the logs show that the job will start in 1 hour 20 minutes. So I restarted the client schedule again. The log now says the job will start in 45 minutes. So I restarted the client service again, it now says it will start in 52 minutes. At this point I though I should stop while I was ahead.
Does anyone know why the wait time had changed since I had changed the schedule to run NOW? Thanks, Mark Bertrand -----Original Message----- From: Joseph Seigh [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 3:57 AM To: [EMAIL PROTECTED] Subject: Re: schedmode polling and immediate client actions Quoting Karel Bos <[EMAIL PROTECTED]>: > Hi, > > We have changed our scheduling mode from prompted to polling. Scheduled > back-ups run fine. The immediate client schedule won't run. The status of > the immediate schedule turns to pending and will not function. > > It will run as soon as your client polls for schedules. If your client poll interval is 4 hours, then on average you will wait 2 hours for an immediate schedule to run. Joe Seigh
