Networker

Re: [Networker] linux client trying to use itself as server

2012-04-18 14:10:06
Subject: Re: [Networker] linux client trying to use itself as server
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 18 Apr 2012 13:05:41 -0500
In regard to: [Networker] linux client trying to use itself as server,...:

we have a problem with Postgres on linux doing backup with savepnpc.
OS is Redhat 5.7, networker version is 7.6.2.7.

Node is running a PostgresDB, backup goes with savepnpc. Pstclientsave
sends WAL-Logs from client to server. Sometimes (not very often) the
following messages appears in savepnpc.log:

3817:save: Using "clientname" as server
39076:save: RPC warning: RPC cannot make a procedure call: Create failed:
Program not registered

This could be any number of things.  The suggestion you've already
received to verify the contents of /nsr/res/servers is a good one,
especially if there are any hosts on your network that you don't trust,
as having an empty servers file has security implications.

Since it manifests as an intermittent network problem, it could
potentially be on the client, on the intervening network gear, or on
the server.

The Installation guide for the server software and the "Technical Guidance
for Upgrades to EMC NetWorker" documents on powerlink have a number of
tuning suggestions for each NetWorker server platform.  If you haven't
applied those suggestions, I highly recommend you investigate them.
Intermittent network issues could certainly happen if the server is
running short of some network-related resource.

After that it continues with
3817:save: Using "networker server" as server
and backup goes on.

One additional thing you could try is to modify the NetWorker client
properties so that the server passes "-s servername" to each save.  You
can do this via the GUI by filling in the *server's* name (we use FQDN,
but your environment may differ) in the "server network interface" on the
"Globals (1 of 2)" tab for the client properties.

This may just mask the underlying problem, though.

Savesets on the server are complete, so it seems the saveset is sent again
with the right servername and saved on tape as it should be.

Are "Client retries" set to some positive value in the properties for the
group containing that client?

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER