Veritas-bu

Re: [Veritas-bu] NB 6.5.1 issue, error 25, jobs fail

2008-03-17 14:01:11
Subject: Re: [Veritas-bu] NB 6.5.1 issue, error 25, jobs fail
From: Mike Kiles <mikekiles AT yahoo DOT com>
To: "S Conn." <sysadminlists AT gmail DOT com>, Veritas-bu AT mailman.eng.auburn DOT edu
Date: Mon, 17 Mar 2008 10:28:32 -0700 (PDT)
The fix may be in 6.5.2, not sure tho.
--- "S Conn." <sysadminlists AT gmail DOT com> wrote:

> Thursday, after reboot:
> bmrbd            1304    0.000%            0.078  
> 47M   3/12/08 12:06:44.375
> bmrd             1400    0.000%            0.203  
> 11M   3/12/08 12:06:46.843
> 
> Friday, having issue:
> bmrbd            1304    0.000%            0.093 
> 101M   3/12/08 12:06:44.375
> bmrd             1400    0.000%            0.218  
> 11M   3/12/08 12:06:46.843
> 
> Restarted the "Netbackup Bare Metal Restore Boot
> Server" process, but
> I was at a remote site and lost network connection
> to the server.
> Later I checked when I got back to the office and
> noticed I had no
> issue getting into the console and all my jobs had
> started on schedule
> and were running smoothly.  I'm going to disable the
> BMR stuff for a
> few days and see what happens.  I have the BMR stuff
> installed, but
> haven't gotten around to testing it yet.
> 
> Do you know of any fix for this, or do we have to
> wait for Symantec to
> get around to it?
> 
> Thanks for your help,
> 
> Seth
> 
> 
> 
> 
> On Thu, Mar 13, 2008 at 9:37 AM, Mike Kiles
> <mikekiles AT yahoo DOT com> wrote:
> > Check if your BMR processes are consuming too much
> >  memory by running "bpps" on the master server. If
> >  memory usage by these processes keeps on
> increasing,
> >  you may have the same bug that we encountered. As
> a
> >  workaround, we have disabled 4 BMR services.
> >
> >  Cheers
> >
> >
> > --- "S Conn." <sysadminlists AT gmail DOT com> wrote:
> >
> >  > I had Netbackup for a few years now, 4.5, 5.1,
> 6.0
> >  > MP4.  I finally got
> >  > a new backup server and decided to fresh
> install NB
> >  > 6.5.1 and start on
> >  > it from scratch.  I didn't import the catalogs
> or
> >  > anything over.  I'm
> >  > running Windows 2003 Enterprise R2 SP2.
> >  >
> >  > Well, after battling I got it working, except
> for
> >  > one major issue.  It
> >  > will back up for a day or two or sometimes
> three,
> >  > then it will have an
> >  > issue.  I'll come in the next morning to find
> that
> >  > half my jobs
> >  > failed.  I try to launch my Admin Console I get
> an
> >  > error message:
> >  >
> >  > Unable to connect to the selected NetBackup
> host
> >  > "bkpsrv01".
> >  > 1. Make sure the user has privileges on the
> host.
> >  > 2. Make sure the local host is listed in the
> server
> >  > list of the
> >  > destination host "bkpsrv01".
> >  > 3. Make sure there is a valid network
> connection.
> >  > 4. Check authentication.
> >  > 5. Make sure all the services are running on
> the
> >  > host.
> >  >
> >  > If I hit ok, it gives me a "Change Server"
> dialog,
> >  > asking me to choose
> >  > a different NB server.  I only have one. 
> Rebooting
> >  > the services
> >  > doesn't seem to fully help, rebooting the
> server
> >  > itself does.  And
> >  > then it will work fine for a few days.  When
> the
> >  > issue happens, all
> >  > services are running.  I restarted services one
> at a
> >  > time to
> >  > troubleshoot the issue.  Restarting the
> "Netbackup
> >  > Client Service"
> >  > worked but I was still getting some errors
> while
> >  > working in the
> >  > software.  A reboot clears everything up just
> fine..
> >  >
> >  > See here for the first error:
> >  >
> > 
>
http://i207.photobucket.com/albums/bb110/netmancer/SysAdminHell/1stNBerror.jpg
> >  > See here for the second error:
> >  >
> > 
>
http://i207.photobucket.com/albums/bb110/netmancer/SysAdminHell/2ndNBError.jpg
> >  >
> >  > Looking through my logs, I'm seeing everything
> >  > running fine, writing,
> >  > etc, but then I suddenly get an error
> "db_FLISTsend
> >  > failed: cannot
> >  > connect on socket (25)"  After that, nothing
> else
> >  > will write.
> >  > Anything already writing will quit, then all
> the new
> >  > jobs will queue
> >  > up and eventually time out without even
> attempting
> >  > to write.  There's
> >  > no other error that I can tell that caused it. 
> Even
> >  > the Windows event
> >  > logs don't show anything significant at that
> time.
> >  >
> >  > I've searched around without much luck.  Does
> anyone
> >  > have any ideas or
> >  > has anyone seen this problem before?
> >  >
> >  > Thanks,
> >  >
> >  > Seth
> >  > _______________________________________________
> >  > Veritas-bu maillist  -
> >  > Veritas-bu AT mailman.eng.auburn DOT edu
> >  >
> > 
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >  >
> >
> >
> >
> >
> >      
>
____________________________________________________________________________________
> >  Be a better friend, newshound, and
> >  know-it-all with Yahoo! Mobile.  Try it now. 
>
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> >
> _______________________________________________
> Veritas-bu maillist  - 
> Veritas-bu AT mailman.eng.auburn DOT edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 



      
____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu