I have seen this before.
Can you push it from the client side?
I took me more than a month to figure a similar issue.
My problem was I was able to push it from the client.
But was not able to do a backup from the client.
After many sleep less hrs I found out that there was some software installed
which was blocking the remote calls.
I found out this the hard way. I even went and installed the server version
and tried to do a back up of itself to the disk that's when it failed.
Finally the Server owner said by the way they installed some port monitoring
software which they were testing. I never got the name of the software
package though.
Hope this helps.

-Venkat

On Thu, Jul 24, 2008 at 3:59 PM, Will Aymond <Wilbur.Aymond AT shell DOT com>
wrote:

> I've seen this once before with firewall settings blocking ports between
> the server and the client.
>
> Two questions:
>
> 1. Does a client initiated backup work correctly? (that doesn't necessarily
> mean that a server initiated backup will, but would be some more information
> for the group here)
> 2. Can you verify port connectivity between the Networker server and the
> client?
>
> Do something like this from the backup server:
>
> # telnet workingclient 7937
> Trying 111.111.111.111...
> Connected to workingclient.domain.com.
> Escape character is '^]'.
> ^]
> telnet> quit
> Connection closed.
>
> /
> # telnet nonworkingclient 7937
> Trying 222.222.222.222...
>
> ^C
> #
>
>
> You'll note that the workingclient responded immediately, and the
> nonworkingclient didn't respond immediately. -You'll have to control-C out
> of second portion. In the above case, this is due to exactly what I'm
> talking about.. firewall settings between the server and client. -Oddly
> enough, these ports are only blocked one way in my case. So client initiated
> backups still work, but not server.
>
> Good luck,
>  -Will
>
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On
> Behalf Of rwgill
> Sent: Thursday, July 24, 2008 1:39 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Backup stuck "Waiting to run"
>
>
> pattiac wrote:
> > ... it is waiting for a tape
> > from the "default" pool.  The log usually has a message to this effect.
>
>
> Thanks for the reply.  In this case the backup never attempts to load a
> tape nor does the log show anything other than the start of the savegrp.
>
> +----------------------------------------------------------------------
> |This was sent by bob_gill AT bose DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>



-- 
Venkat Tudi

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER