The restore log itself isn't telling you anything?  

Typically I see things like:

Restore started 03/04/2006 07:11:38

07:11:43 (109902.xxx) Restore job id 109902 will require 3 images.
07:11:43 (109902.xxx) Media id SU0188 is needed for the restore.
07:11:43 (109902.xxx) Media id SU1532 is needed for the restore.
07:11:43 (109902.xxx) Media id SU0146 is needed for the restore.
07:11:43 (109902.xxx) Media id SU0213 is needed for the restore.
07:11:43 (109902.xxx) Media id SU0909 is needed for the restore.
07:11:43 (109902.xxx) Media id SU1109 is needed for the restore.
07:11:43 (109902.xxx) Media id SU1828 is needed for the restore.
07:11:43 (109902.xxx) Media id SU1141 is needed for the restore.

07:12:18 (109902.001) Restoring from image created Thu Mar  2 05:36:29
2006
07:12:19 (109902.002) Restoring from image created Thu Mar  2 05:36:30
2006
07:12:21 (109902.001) INF - Waiting for mount of media id SU0188 on
server atudvd01 for reading.
07:12:22 (109902.002) INF - Waiting for mount of media id SU0146 on
server atudvd01 for reading.
07:12:58 (109902.001) INF - Waiting for positioning of media id SU0188
on server atudvd01 for reading.
07:13:13 (109902.001) INF - Beginning restore from server atudvd01 to
client atudvd.

The above by the way is for a backup that had 3 streams on backup.  The
"001" would be the first stream, "002" would be the second and "003"
would be the third.

Notice there is no "003" in the above (at the beginning).   This
occurred because due to issues during the backup the third stream
actually used a tape that the second stream had finished with.   Due to
this it waits until the second stream restore before it even requests a
mount for the third stream.

I'm wondering if you're not having some similar issue to that.   How far
along in the restore log do you get according to its log file?

Also I recall that at a prior job where we sent most backups off site
the restore job would actually wait until we had recalled the media from
offsite and re-injected into the robot.   If your log shows the media
have you verified they are actually in the robot?

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ambrose,
Monte
Sent: Monday, March 06, 2006 12:07 PM
To: netbackup AT whelan-consulting.co DOT uk; veritas-bu AT mailman.eng.auburn 
DOT edu
Subject: RE: [Veritas-bu] Third times the charm (I hope)

Patrick

Did you try creating a tar log on the client?  How about grepping for
the client in the master/media servers logs?  Did you do this from the
GUI?  It should indicate what it is waiting for in the restore log.

Monte

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
netbackup AT whelan-consulting.co DOT uk
Sent: Monday, March 06, 2006 6:00 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Third times the charm (I hope)

I have asked this question twice before with no answers so I thought I'd
try again.

How can I tell why a restore job is queued? I submit restore jobs and
they sit in the queue forever. There are plenty of tape drives, the
necessary tape is in the library. There are no pending mount requests. A
restore to the same client earlier today worked with no problem. I am at
my wits end trying to figure this out. Any feedback would be welcome,
even if it is just to let me know someone actually read this.

Regards,

Patrick Whelan
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu