There's a patch for this:

Solaris:  http://seer.support.veritas.com/docs/266197.htm

Windows:  http://seer.support.veritas.com/docs/266198.htm

--Steve





Goldfarb, Josh wrote:

>Kate from Aenta has provided information about this bug.  All credit goes to 
>her.  Thanks Kate.
>--
>see below
> 
>Not sure if people have seen this yet. Our S/E sent it out to us this 
>morning....
> 
>~Kate
>
> 
>It is possible for the volDB to be corrupted if the number of characters in a 
>pool name is a multiple of 4 bytes.  This problem only applies to a server 
>acting as a Media Manager Volume Database Host, running either VERITAS 
>NetBackup Enterprise Server (tm) 5.0, or VERITAS NetBackup Server (tm) 5.0. 
> 
>IMPORTANT NOTE:  for complete information see the TechNote at 
>http://seer.support.veritas.com/docs/265846.htm.  Please contact Technical 
>Support for all questions (do NOT reply to this e-mail).
> 
> 
>This alert is being sent to all NBU 3.4 and 4.5 customers.
> 
> 
>This problem can only occur on a server running VERITAS NetBackup (tm) 5.0 GA 
>(Server or Enterprise Server), which is also acting as a Media Manager Volume 
>Database Host (ie, it hosts the volDB).  This problem also affects the 
>operation of VERITAS Storage Migrator (tm) 5.0 for UNIX.  
>
>This issue does not affect NetBackup 3.4 or 4.5 customers.  However, if you 
>intend to upgrade to NetBackup 5.0, you need to be aware of this issue.
> 
> Symptom: 
>
> 
>It is possible for the volDB to be corrupted if the number of characters in a 
>pool name is a multiple of 4 bytes. This problem only applies to a server 
>acting as a Media Manager Volume Database Host, running either VERITAS 
>NetBackup Enterprise Server (tm) 5.0, or VERITAS NetBackup Server (tm) 5.0. 
>
>Exact Error Message: 
>
><16> select_media: unable to query Media Manager volume daemon on host vmhost, 
>unexpected data received
> 
>       -----Original Message----- 
>       From: veritas-bu-admin AT mailman.eng.auburn DOT edu on behalf of 
> Francisco.Miranda AT themills DOT com 
>       Sent: Wed 3/31/2004 8:13 PM 
>       To: veritas-bu AT mailman.eng.auburn DOT edu 
>       Cc: 
>       Subject: [Veritas-bu] unable to read volume database. NBU 5.0
>       
>       
>       I started having this problem a few days ago and only restarting the 
> server seems to fix it, but only temporally.  I can access my volume pools 
> when I restart the server but later on anytime that I try to access any of my 
> volume pools I get the following error:
>        
>       "unable to read the volume database: failed receiving from vmd(72)"
>        
>       I try restarting the services, but that doesn't fix it only restarting 
> the server seems to do it for a little while.
>        
>       I will appreciate if anyone has any ideas on how to fix this problem.  
> I have tried the support line and its been 2 hrs and still going.
>        
>       thanks
>        
>       Francisco Miranda
>       Francisco.Miranda AT millscorp DOT com
>        
>        
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>  
>


-- 
===================================

  Steven L. Sesar
  Senior Operating System Programmer/Analyst
  UNIX Application Services R101
  The MITRE Corporation
  202 Burlington Road - K101
  Bedford, MA 01730
  tel: (781) 271-7702
  fax: (781) 271-2600
  mobile: (617) 893-9635
  email: ssesar AT mitre DOT org
 
===================================