Well 219 is storage unit unavailable and 58 is a timeout/unable to connect 
to the client, sounds like network connectivty issues to me.. at certain 
hours of the night?

On Tue, 13 Feb 2007, Steve Jenkins wrote:

> I installed right to mp5 about six months ago.  When it started
> happening, I applied mp6 to see if anything would change - it didn't.  I
> had logging on high, but backed down to see if that would help free up
> resources (it didn't).  I just opened a case with Veritas and am
> awaiting a call back.
>
>   Steve
>
>>>> Justin Piszcz <jpiszcz at lucidpixels.com> 2/13/2007 6:25:53 AM >>>
>
> Did that ever happen with 5.1MP4? Do you have logging on 5 (max)?  Did
> you
> open a case with veritas?
>
> On Tue, 13 Feb 2007, Steve Jenkins wrote:
>
>> Starting a couple of weeks ago, running netbackup 5.1 mp6, in the
> middle
>> of the night, a bunch of backups start crashing and burning with a
>> mixture of 202's, 205's, 219's and 58.  Running a single
> master/media
>> server on hpux.  The error codes don't make any sense, as I'm not
> seeing
>> any obvious errors system wise.  Once this starts happening, it
> seems
>> the only way to get out of it is to reboot the server, then
> everything
>> runs clean for a few days.  I suspect we're just trying to push too
> much
>> though the server, but looking for any input.....
>>
>> Anybody else seen anything similar?
>>
>>
>>
>>
>>
>> Steve Jenkins
>> Sparrow Health Systems
>> Database & System Integration Group
>> p - 517-364-6459
>> pager: 517-226-0497
>>
>
>