Il Thu, Jan 02, 2003 at 01:32:58PM +0100, François-Xavier Peretmere ha scritto:
> > From: Giuseppe Sacco [mailto:eppesuigoccas AT iol DOT it]
> > Sent: Tuesday, December 24, 2002 11:36 AM
> 
> > I recently got an error 219. The NetBackup is a 3.4 and it was working
> > like a charm until some days ago.
> 
>  If it use to work and is not anymore, then my first question
> is "what has change between ?"  ;-)
> 
> ...
> ...
> > I then tried to use the command bplabel as suggested in the
> > list archive but this command seems to run forever. Is it normal?
> > I kept it running for at leat 3 hours, then I stopped it.
> 
>  Not. bplabel should run for a couple of minutes maximum. Seem
> like there's a problem in the data path between your host and the
> tape drive.
>  It the tape reachable with basic commands (mt, tar, cpio...) ?
> 
> > Actually the system is a SUN E4500 with an L9 tape library. The
> > netbackup is used for both file system backup and oracle RMAN backup.
> >
> > When I found the problem I tought that ths was because of a
> > communication problem between the SUN and the L9, but if I change the
> > tapes in the library the NetBackup is aware of this change. So they
> > communicate.
> 
>  Robotic path seems ok. robtest should work. But is the data path
> from the host to the robot the same than the one to the tape drives ?
> 
> > The only problem is that when a backup start (at its scheduled time)
> > then it switch to state 'done' with error 219.
> 
>  Are the drive UP (vmoprcmd) ? if yes, are the drives defined with
> the correct density ?

[sorry for the long quote]
After two more weeks of trouble, we found that it was an hardware
problem. After replacing the L9 unit, the backups are now working
correclty.

Thanks you again for your support.

Giuseppe Sacco