In regard to: Re: [Networker] Problem backing up a server with multiple IP...:

On Mar 28, 2008, at 12:32 PM, Howard Martin wrote:

But is it a static host or static net route, if your flavour of linux
allows it then setting a static route using the IP you want to just the
backup server (as a host) should force it to use just that IP to talk to
the backup server.

But there's no evidence at this point that it is a routing problem.
Typically it's NetWorker being dense about resolution, not an underlying
routing problem.

The client in question is Red Hat Linux. I am not at all a Linux guy.
How do I determine what kind of route is in use on that client and force
it to use the backup server's IP address?

Nearly the same way you would on Solaris.  netstat -rn to show routes,
"route add" with some additional bits to add them.  To make the route
change survive reboots, you'll need to add the arguments to the "route
add" command to a file in /etc/sysconfig/network-scripts -- probably
something like "/etc/sysconfig-network-scripts/route-backupserver".

I doubt it's a routing issue, though.

Stan, can you post what error messages or symptoms you're actually seeing?

Tim
--
Tim Mooney                                        Tim.Mooney AT ndsu DOT edu
Information Technology Services                   (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