Hi Timothy,
Well... I'm not sure what to do/try next. One more thing that I have
seen, but with Backup Exec. Was that some of the Backup Exec modules
were still loaded. So my recommendation, is to be sure that no Arcserve
modules are loaded. And that you have at least tree lines in the hosts
files (as you probably already know).
IP localhost(loopback or what ever)
IP machineA machineA.domain.name
IP machineB machineB.domain.name
Is a long shot, but you could always try to use a laptop, or else, as
a backup server. To see if you have problems backing the NetWare box to
another server too. I'm thinking that maybe there is something on the
server side? But don't think so.
You said: "We have startet the rcmd and networkr module with -s
option. Corrected the admin/password from nsradmin according to some old
bulletin. I hope someone can help us with additional info on how to do."
Why? Try to just let it start as generic as possible, then you may
choose which server to connect to. Regarding the remote user and
password. I recommend that you write it down on the NetWorker for
NetWare GUI. Remember to push F9 key, before writing down the user, and
the same for the password. Or if you do it from a Windows frontend.
Sorry that I haven't been able to help more, but I'm out of ideas.
Good luck once more!
/Joaquin Camp.
On Tue, 2003-04-01 at 16:47, Timothy Biles wrote:
> Yes, that has all been checked too. DNS works, but as a precaution, we
> also added the entries for each in the coresponding hosts files on each
> machine. Both machines are on the same subnet, and no firewalls are in place.
>
> We have also run the saveset manually from the server in verbose mode to
> capture more details. It doesn't show anything helpful that we didn't
> already know. Something is funny with the TSA communications, but what it
> is I just can't figure out. Fortunately, I can still use my other backup
> product (ArcserveIT 6.6). However, we've been trying for many months to
> move away from this, to a solution that supports TCPIP. Since we already
> own Solstice(Legato), we didn't want to upgrade to current versions of
> Arcserve (which I haven't heard glowing comments about either). We also
> wanted a single backup solution for our enterprise, which was another
> reason to stick with Legato. Unfortunately, Netware seems to be an
> afterthought in most vendor's minds, and the support is extremely lacking.
> This probably has a lot to do with the fact that our support is through
> Sun, because we actually license it from them as the Solstice product. The
> documentation isn't much better, in my opinion.
>
> I appreciate all the ideas. Thank you.
>
> Joaquin Camp wrote:
> > Hi Timothy,
> >
> > Sorry that your backups aren't up and running yet. But have you
> > checked that name resolution works? It sounds like it could be that.
> > If the manual backups works but not the server initiated, name
> > resolution could be the answer. And just to be sure, I hope you don't
> > have any firewalls involved.
> >
> > Good luck with Sun.
> > /Joaquin Camp.
> >
> >
> > On Mon, 2003-03-31 at 23:52, Timothy Biles wrote:
> >
> >>The SMDR NEW procedure did not work either. I have submitted a support
> >>request to Sun (we have the Solstice, which is repackaged Legato). I'm not
> >>looking forward to that, as there is usually a long run around going
> >>through things I've already tried from previous problems.
> >>
> >>It is strange, as I can run a manual backup and restore from the server
> >>console. Anything I try from the server side ends up with the TSA error.
> >>My server backs up fine with Arcserve (which uses the TSAs) so I have a
> >>hard time believing there is anything wrong with the TSAs. I also tried
> >>the TSATEST.NLM utility from Novell, and it appears that SMS communications
> >>is taking place just fine.
> >>
> >>--
> >>Note: To sign off this list, send a "signoff networker" command via email
> >>to listserv AT listmail.temple DOT edu or visit the list's Web site at
> >>http://listmail.temple.edu/archives/networker.html where you can
> >>also view and post messages to the list.
> >>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> >
> >
>
>
> --
> Timothy M. Biles voice:(218) 726-6959
> ITSS - Systems Administrator fax:(218) 726-7674
> University of MN-Duluth
> MWAH 176
> 1023 University Drive e-mail: tbiles @ d.umn.edu
> Duluth, MN 55812
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
