RE: [cobalt-developers] Legato Backup and RaQ3i

[Brian Krabach <briank@xxxxxxxxxxxxxxxx>]

That was the problem, what is the best method to ensure that portmapper
starts before networker client after every reboot?

I am still a little bit short of achieving a backup though.  I am now
receiving the following error:

* host1.wholesaleisp.net:/ save: SYSTEM error, Access violation - unknown
host: 208.30.159.61 (severity 5, number 13)
* host1.wholesaleisp.net:/ save: Cannot open save session with
wisp2.wholesaleisp.net

208.30.159.61 is the ip address of the client, while wisp2.wholesaleisp.net
is the name of the Networker server.  We have entered wisp2.wholesaleisp.net
(and we tried using it's ip address as well) into the /nsr/res/servers file.
We also entered both ip address and dns name via the cobalt admin menu.  On
the networker server, we have added both the ip address and dns name of the
cobalt server under the aliases for the client.


******************
Brian Krabach
Vice President
WholesaleISP, Inc.
****************** 

-----Original Message-----
From: Byron C. Servies [mailto:bservies@xxxxxxxxxx]
Sent: Thursday, May 11, 2000 11:28 AM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-developers] Legato Backup and RaQ3i


On 5/10/00 at 10:48 AM, briank@xxxxxxxxxxxxxxxx (Brian Krabach) wrote:

> I just purchased the Unix Client Pak for my Legato installation and
> experiencing difficulties getting the Cobalt RaQ3i to work with it.  The
> client has been set up and properly configured on the Networker server.  I
> have also specified the Networker server in the Cobalt configuration
panels.
> The error I receive from the Networker server is:
> 
> *host1.wholesaleisp.net:/ Networker: Unable to contact system to determine
> port ranges: host1.wholesaleisp.net.NetWorker: RPC error, Program not
> registered (severity 4, number 15)
> 
> If I run the portmap daemon in debug mode on the Cobalt, the only thing it
> returns when the Networker server attempts to talk to it is:
> 
> server: about do a switch
> 
> Ideas, suggests?

Did you start the portmapper on the cobalt before you start NetWorker on the
Cobalt?  The NetWorker client daemon, nsrexecd, needs to register with the
portmapper when it starts up. You can check to see if NetWorker on the
cobalt is
registered with the portmapper using:

        /usr/sbin/rpcinfo -p

look for program number 390113, the nsrexecd daemon that NetWorker on the
server
attempts to contact when running a backup.

Other notes of interest: backup and restore with the version of NetWorker
that
comes with the Cobalt products works fine, but it is an early linux port
that has
a few problems.  Since this is a developer list, I will describe them in
detail.

First, the linux 'select' call modifies the timeval parameter with the
amount of
time remaining when the call returns.  This has been documented forever in
the
select man page, but few platforms actually provide this service.  In the
version
of NetWorker that comes with Cobalt products right now, this means that some
select loops do not pause between itterations.  This will effect you if your
DNS
service occasionally has problems: if nsrexecd or save cannot contact the
NetWorker server, it will broadcast on the local subnet to find one: without
proper select handling this will cause a massive ping flood.  It will also
cause
nsrwatch on the cobalt to flood the NetWorker server, so I don't recommend
you use
it.

Second, the bane of all our existences, is NetWorker licensing.  nsrexecd on
cobalt MIPS products does not correctly determine the number of CPU's (1) to
the
NetWorker server.  It reports a special value that indicates the NetWorker
client
is part of a cluster and requires a cluster license; clearly a bug.  The
RaQ3i has
the 2.2 kernel and the IOCTL that NetWorker uses to determine this
information, so
you should not see this problem.

HTH,

Byron



_______________________________________________
cobalt-developers mailing list
cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers