12.5 Run now only Queues

[Pallentx]

Hello;

I have version 12.5 and when I right click a job and select RUN NOW, the job goes into a queue'd state and never does run????

Also, why do I have to select a 'time window' in the job setup.  I would prefer to actually SET the start time instead of hoping that it starts between X and Y.


Thank you.

[Colin_Weaver]

 The queued state implies it things the device you are sending to is busy - if you don't think it is busy try pausing the device and then unpausing it.

With regards the Window - the job will try and start at the start of the window - the between X and Y setting is so that if all the devices are genuinely busy then it will only let the job start during the window - if the device is released outside the Window the job won't start. Provides the ability not to immediately fail just because of scheduling too many jobs whilst giving you a finite end so you don't exceed your backup window for the environment.

[Pallentx]

Thank you for the quick reply.

I have a 4 tape changer (Overland NEO 4000) that has been idle when I select RUN NOW.  The job sat for 18 hours in a queue'd state.  I will test the pause and un-pause technique, but I feel that there is more going on here than meets the eye.

thank you again.

[CraigV]

Following on from Colin's suggestions, if the pause/unpause doesn't work, you can delete the autoloader and rescan for it. This should let it redetect.
Here are some articles frmo the Symantec site to read over:

http://seer.entsupport.symantec.com/docs/237047.htm

http://seer.entsupport.symantec.com/docs/191594.htm (Colin's suggestion)

http://seer.entsupport.symantec.com/docs/255501.htm

[Symboy]

 Hi 

   Also check if the job is set up correctly with respect to the media settings.  Is that happening with only this job and if so , what is the difference between other jobs and this one . Like Media set , device , overwrite settings etc.