[Veritas-bu] RE: Newbie Q: "219 - No storage units available"

what does bpsutlist -L show  you?

have you confirmed that you have the right media type selected for the
storage unit?

DLT and DLT2 are not the same media type...

David

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com

-----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 William
Enestvedt
Sent: Wednesday, September 19, 2001 11:39 AM
To: Veritas NBU list (E-mail)
Subject: [Veritas-bu] RE: Newbie Q: "219 - No storage units available"


More info: weirdly, the Master Server's bcshed log from this morning
includes plenty of lines like:
------------------------------------------------------------
00:19:18 [21045] <4> available_media: (BPTM) pvd-app-09-dlt3-robot-tld-0 --
num active = 0, num available = 8, num inuse = 0
------------------------------------------------------------
   Which is encouraging, because at least it sees the tapes in the robot.
   But I also see a line where the master Server, pvd-app-04, tried to kick
off client backup jobs on itself and pvd-app-09 (the Media Server), which
results in:
------------------------------------------------------------
00:29:05 [22786] <2> getsockconnected: Connect to pvd-app-09 on port 881
00:29:33 [22798] <4> bpsched: INITIATING...
00:29:33 [22798] <2> logparams: /usr/openv/netbackup/bin/bpsched
00:29:33 [22798] <4> bpsched_main: wait_on_que=0, timeout_in_que=36000,
reread_interval=300,queue_on_error=0, bptm_query_timeout=480
00:29:33 [22798] <2> LOCAL CLASS_ATT_DEFS: Product ID = 6
00:29:33 [22798] <4> bpsched_main: VSMInit () failed: 2d
00:29:33 [22798] <4> ?:   post process images:   yes
00:29:33 [22798] <4> ?:   keep tir:   yes
00:29:34 [22798] <2> getsockconnected: Connect to pvd-app-04 on port 875
00:29:34 [22803] <4> fork_unmount_all_tapes: forking unmount_all
00:29:34 [21045] <2> getsockconnected: Connect to pvd-app-04 on port 1000
00:29:34 [22798] <2> getsockconnected: Connect to pvd-app-09 on port 900
00:29:35 [21045] <4> available_media: (BPTM) pvd-app-04-dlt2-robot-tld-1 --
num active = 0, num available = 5, num inuse = 1
00:29:35 [21045] <2> getsockconnected: Connect to pvd-app-09 on port 887
00:29:35 [22798] <2> db_getCLIENTlist: from db_CLIENTreceive: no entity was
found 227
00:29:35 [22798] <4> get_db_info: Failed to get client list
------------------------------------------------------------
   The bit about "Available Media" which reads, "num available = 5, num
inuse = 1" is encouraging, but that's on the server that's been accepting
backups all along! What worries me -- perhaps needlessly -- is the part
about one of the servers (presumably the Master Server whose log this is)
returning, "get_db_info: Failed to get client list."
   And the errors this morning are now "213 - no storage units available for
use."
   It gets worse and worse -- I think I'm just going to call for help unless
someone sees something glaring in the above.
-wde
P.S. Thanks for the suggestions I've already recieved: very generous, and
fast.
--
Will Enestvedt
UNIX System Administrator
Johnson & Wales University -- Providence, RI
Will.Enestvedt AT jwu DOT edu    (401) 598-1584
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu