Veritas-bu

[Veritas-bu] Error 219

2001-04-23 17:25:10
Subject: [Veritas-bu] Error 219
From: rob AT colltech DOT com (Rob Worman)
Date: Mon, 23 Apr 2001 16:25:10 -0500
IIRC, the command you are referring to is actually

   /usr/openv/netbackup/bin/admincmd/bpschedreq -read_stunits

(and it only works if it's run when there are no active backups...)

rob

At 11:18 PM 4/23/01 +0000, ysbrand bergman wrote:
>I remember that I've seen this error more than once in 3.4 as well. As far as
>I can remember that site got rid of the problem by issuing:
>
>/usr/openv/netbackup/bin/bpsched -reread
>
>What I understood is that Netbackup tries to keep track of what storage units
>are busy and how many instances. If that adds up to maximum number of
>concurrent sessions defined in the storage unit definition is gives the 219
>error. If a drive fails the scheduler might not become aware of the fact that
>is has been repaired. the -reread forces the scheduler to quiry all the
>mediaservers about their status.
>
>Please correct me if I'm wrong.
>
>Ysbrand
>
>
>
>David wrote:
>
>/usr/openv/netbackup/bin/admincmd/bpschedreq -read_stunits
>
>This is 'fixed' in 3.2 and following.
>
>David
>
><><><><><><><><><><><><><><><><><><><><>
>David A. Chapa
>Consulting Manager
>DataStaff, Inc.
>847 413 1144
>http://www.consulting.datastaff.com 
>---------------------------------------
>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
>olaf_behnke AT de.schindler DOT com
>Sent: Tuesday, April 17, 2001 11:07 AM
>To: veritas-bu AT eng.auburn DOT edu
>Subject: [Veritas-bu] Error 219
>
>
>Hi all,
>this morning one of our dlt drives went down. After solving the problem I
>put the drive into up state. The following jobs - scheduled an hour later -
>stopped with error 219 (required storage unit is unavailable). I know from
>the past, that I have to wait some hours until NB master will get the info
>that the drive is up again. If I don't want to wait I have to stop and
>restart all NB master processes. I decided to restart NB master today but
>have anyone a better solution?
>
>Environment: NBU 3.1 on HPUX 10.20, DLT Library HP 4845A (like StorageTek
>98..).
>
>Regards
>Olaf Behnke
>Schindler Deutschland Holding GmbH
>
>
>
>_______________________________________________
>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
>
>
>____________________________________________________________________
>Get free email and a permanent address at http://www.amexmail.com/?A=1
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


<Prev in Thread] Current Thread [Next in Thread>