Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Job stuck on qued

Status
Not open for further replies.

pct3ch

MIS
Feb 3, 2003
68
US
I recently tried duplicating a full backup. It looked like it worked but now wheneve the backup for the class starts it's always on qued. I've tried doing a manual backup and the same occurs. It never goes off qued status. Anyone know what the problem is?

 
The main problem with queued backups that never go active is that a new storage unit has been added and the master not rebooted if Windows or services recyled if Unix.
 
Thanks. I'll try that but now I can't get any jobs to start! Scheduled or manual. arrgg! help!
 
It's on unix but I've never rebooted it. Can you help me out with that?

I check the error report and this is what I'm getting:
No storage units available for use (213)

I greatly appreciate your help!
 
What version of NetBackup DataCentre? How many storage devices and where? Are they on the master or a separate media server?
 
Datacenter 3.4. 6 storage devices. All of it is on a Sun rack so I'm assuming it's all together.

Thanks!
 
If I recall correctly ... in openv/netbackup/bin/admincmd there are two files S77netbackup and K77netbackup - One to kill all services and another to start.

Two things that I am not 100% ccertain of as it has changed in 4.5 - The location and there may be another 7 but I do not think so.
 
Check that the duplication has finished.
The duplication can start whith only one drive available. If so your duplicatiion will never be finished.
Good luck.

Patrk
 
In NBU 4.5 you can use netbackup stop and netbackup start on the command line. I would also do a bbps -a to see if any processes are still active after the netbackup stop command. If there are, then I would us e the standard bp.kill_all.

 
Thanks guys! I killed all the processes and everythigns seems fine now. Pheew!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top