Actually we have seen issues were if you do not have the portmapper service
running (and bound first) then you communications with local host will fail
as well as remote backups of clients.  I wish NetWorker did properly use its
own portmapper service like windows does but it does not.

Also we are backing up over 1300 Linux clients so that may help in
justifying this setup.

Regards,


Chad Smykay, RHCE, LCNA
Systems Storage Administrator
Rackspace Managed Hosting (TM)


-----Original Message-----
From: Byron Servies [mailto:bservies AT pacang DOT com]
Sent: Wednesday, May 12, 2004 4:57 PM
To: Legato NetWorker discussion; Chad Smykay
Subject: Re: [Networker] Linux client not backup'ing

On May 12, 2004, at 2:50 PM, Chad Smykay wrote:

> Darren is correct you will need to restart your NetWorker service
> after you bring up portmap.  Sorry for not specifying.
>
>>
>> Chad Smykay wrote:
>>> Do you have the "portmap" service installed and running?
>>
>> I did not, but do now.
>
> After you start 'portmap', you'll probably have to restart the
> services so they can register with it.  It wasn't clear if you did
> that or not.
>

Hi,

NetWorker will use portmap, but it does not need it on either the client or
the server.  There is a private port mapper included in nsrexecd, so if you
have that running, all should be well.  Note that since nsrexecd listens on
a different port than portmap, rpcinfo will not show available services.

HTH,

Byron

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=