[Veritas-bu] Status code 24 on scheduled vault policy

Rob Worman (home) rob at worman.org
Wed Mar 16 18:49:32 CST 2005

sounds like you might have a bad "bpbrmvlt" binary (that's one of the 
big differences between the execution of a scheduled vault policy and 
the manual execution of the vault profile.

what happens if you run "/usr/openv/netbackup/bin/bpbprmvlt -help" ?  
If you get a library error, that's your problem.  This typically 
happens if you upgrade from a previous NBU version and immediatgely 
patch (e.g. upgraded from 4.5 to 5.0, then applied the 5.0MP4 vault 
patch) without installing the vault option from the newer Options 

If this is the case for you, I suggest you re-install vault from the 
newer Options CD-ROM, then reapply any VLT patch you may have already 


On Mar 16, 2005, at 11:02 AM, WebsterR at mont.disa.mil wrote:

> Has anyone seen this error Status: "(24) socket write failed" when the
> scheduled vault policy kicks off?  The master is a Sun Solaris 8 box.  
> I can
> manually run the vault profile and the duplication runs fine but 
> whenever it
> is time for the scheduler to run the vault policy for this vault 
> profile, I
> keep getting this error.
> I have checked the tcp_rexmit_interval_initital, ..._min, and ...._max
> values and they are set to 3000, 400, and 60000 respectively.  The
> tcp_ip_abort_interval is set to 480000.
> Thanks,

More information about the Veritas-bu mailing list