Thanks to those who did reply.
I think what this came down to was having to install a couple of patches after
the standard install of the solaris 8 os.
Another long day almost done.
John
> -----Original Message-----
> From: John Rothlisberger
> Sent: Tuesday, July 08, 2003 9:09 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Please help... Lost st.conf data
>
>
> ok, I am getting tired of replying to my own emails.
>
> Right after I send this out I was able to get bpdbm and bprd to run
> and was able to run bp to do some restores.
>
> After I stated a restore, it failed with:
> 18:52:43 (39267.001) INF - TAR EXITING WITH STATUS = 40
>
> I suspect that the entry that I have put into the st.conf file is
> incorrect.
>
> I added:
> "SEAGATE ULTRIUM06242-XX","Seagate LTO","SEAGATE_LTO";
> SEAGATE_LTO = 1,0x36,0,0x1d639,4,0x00,0x00,0x00,0x00,1;
>
> Can anybody tell me if this is right or what is the correct entry?
>
> Thanks again,
> John
>
> > -----Original Message-----
> > From: John Rothlisberger
> > Sent: Tuesday, July 08, 2003 8:38 PM
> > To: veritas-bu AT mailman.eng.auburn DOT edu
> > Subject: RE: [Veritas-bu] Please help... Lost st.conf data
> >
> >
> > Well, got farther but am still having trouble.
> >
> > I have been able to get the drive and robot configured and can see
> > media etc. Looks good.
> >
> > When I try to do a restore using bp I get:
> > Cannot connect to server
> >
> > bprd is not running and won't stay running.
> > In /var/adm/messages I see:
> > Jul 8 18:24:02 chimisc1 bprd[223]: [ID 192819 daemon.error]
> > Cannot contact NetBackup bpdbm. Terminating.
> >
> >
> > Any ideas? Really, any?
> >
> > Thanks,
> > John
> >
> > > -----Original Message-----
> > > From: John Rothlisberger
> > > Sent: Tuesday, July 08, 2003 5:19 PM
> > > To: veritas-bu AT mailman.eng.auburn DOT edu
> > > Subject: [Veritas-bu] Please help... Lost st.conf data
> > >
> > >
> > > This morning we had a drive 0 failure and I have had to
> > > rebuild it. Part of what I need
> > > to get my robot working again are the entries that need to go
> > > into st.conf.
> > >
> > > We are using NetBackup 3.4.1_3 server on a Solaris 8 Sun 220R.
> > > The robot is a StorageTek L20 with a single seagate
> > > STU420001LW LTO drive.
> > >
> > > All of my Netbackup data was on a seperate drive and not
> > > lost, but I can no longer start
> > > up vmadm or bpadm.
> > >
> > > I cannot see the robot or drive anymore.
> > >
> > > Any help would be appreciated.
> > >
> > > Thanks,
> > > John
> > >
> > > > --
> > > > John Rothlisberger
> > > > Unix Systems Administrator
> > > > jrothlisberger AT indeliq DOT com
> > > >
> > > > Indeliq, An Accenture Company
> > > > 1 North Franklin, Suite 2200
> > > > Chicago, IL 60606
> > > > Phone: 312.442.6672
> > > > Fax: 312.442.6606
> > > > http://www.indeliq.com
> > > >
> > > >
> > >
> > > _______________________________________________
> > > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > >
> >
> > _______________________________________________
> > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|