Hi, the box operated under the name 'box2' for quite a while. It was the
system that Netbackup was originally installed on. It was renamed 'box1' and
was tested successfully.
Everything works so far, but the "bpexpdate" function. I've since found
that by adding in 'box2's name to the bp.conf under "CLIENT_NAME" I can
expire tapes now, and remove the extraneous 'box2' entry in the /etc/hosts
file. Although I haven't found the configuration file that still thinks
'box2' is the real name of the system, things seem to be working.
Thanks,
Joe
> -----Original Message-----
> From: Larry Kingery [mailto:larry.kingery AT veritas DOT com]
> Sent: Friday, November 16, 2001 12:59 PM
> To: Sangemino, Joe
> Subject: RE: [Veritas-bu] Problem expiring tapes
>
>
> Was the box called box2 when the testing was done?
>
> Sangemino, Joe writes:
> > I'm not concerned with the old images as they don't have
> any. We just got
> > the system running again (after they'd done some creative
> 'customization' of
> > the settings)and it's just started doing backups there.
> The first set of
> > tapes in their 8 slot 8mm loader filled up and they
> reloaded with the tapes
> > that had been installed and used for testing that were in
> the unit when it
> > was sent to them. I sent them over 300 used tapes, all past
> retention date,
> > and they managed to install the only 8 tapes that were not
> expired ! 8-(
> > That's when I found out that the bpexpdate was not working.
> If you have any
> > ideas about that problem, I'd love to hear them.
> >
> > Thanks for replying.
> > Joe
> >
> > > -----Original Message-----
> > > From: lkingery AT veritas DOT com [mailto:lkingery AT veritas DOT com]
> > > Sent: Thursday, November 15, 2001 4:05 PM
> > > To: Sangemino, Joe
> > > Subject: Re: [Veritas-bu] Problem expiring tapes
> > >
> > >
> > > I suppose you can't restore from those images either.
> > >
> > > I'd scan through the image files and see if you can find
> FRAG lines
> > > which reference box2. If so, you'll need to use
> > >
> > > bpimage -oldserver box2 -newserver box1
> > >
> > >
> > > >
> > > > This message is in MIME format. Since your mail reader does
> > > not understand
> > > > this format, some or all of this message may not be legible.
> > > >
> > > > ------_=_NextPart_001_01C16DFE.BD205CA0
> > > > Content-Type: text/plain;
> > > > charset="iso-8859-1"
> > > >
> > > > Hello, I'm trying to solve a problem at our India
> > > location. Netbackup
> > > > 3.1 is running on a Solaris Unix box (box1) and all seems
> > > okay until we
> > > > try to expire a tape using the 'bpexpdate' command. I have
> > > no problem
> > > > using the command 'bpexpdate -d 0 -ev <mediaid>' on our
> > > local 3.2 box,
> > > > but when I attempt it on the remote system, I get an
> error "Client
> > > > Connection Refused" This happens after the bpexpdate
> > > command asks me to
> > > > verify that I want to delete the tape. When I view the
> > > reports using
> > > > bpadm, and select problems, I get a report that "bptm
> > > failed: 'box2'
> > > > client connection refused (57)
> > > >
> > > > 'box1' is the netbackup server.
> > > > 'box2' is the same server, but its previous name. The
> > > server's name was
> > > > originally 'box2' but was changed to 'box1'. Obviously,
> > > somewhere on the
> > > > system, it thinks it's still 'box2'. Any idea where I
> should look?
> > > > Adding 'box2' to the /etc/hosts file beside the 'box1
> localhost'
> > > > entry allows us to successfully run the bpexpdate
> command, but this
> > > > workaround could cause problems connecting to a new
> local box named
> > > > 'box2'
> > > >
> > > > Any suggestions for things to check? Have I been
> confusing enough?!
> > > > <grin>
> > > >
> > > > Thanks for any ideas you come up with.
> > > >
> > > > Regards,
> > > > Joe
> > > >
> > > > Joe Sangemino
> > > > NT/UNIX Systems Administrator
> > > > Eftia OSS Solutions Inc.
> > > > jsangemino AT eftia DOT com
> > > > Tel. (613)564-4407 x.2623
> > > >
> > > >
> > > >
>
|
