UNSOLVED
First Linux server: trouble backing it up
Hi guys (and ladies if there are any here!). I have set up my first linux server to backup. I can ping across my networks (Linux is on communications network and my backups is on my communications network) to/from each server so I know I have connectivity. I have all ports open (as far as I can tell; I don't set up firewall but our guys do and I told them to leave all ports open). When I go to my client information tab on the linux server however all my fields are blank: client OS type, Networker version, are all blank. I know I put client version 7.1.2 on it as that's what i've go on all of my other clients as I took it from the CD. Any help would be great. Thanks
340
0
Posted April 5th, 2006 11:00
We had a strange one like this with some Linux clients a while back. It appeared to us that the ports were locked down when we were testing it for the first time; it took a couple of hours to track down the guy who could open them, but there were no locked down ports; we then attempted to show him what the problem was we were observing and it backed up fine. Maybe this is something like that - have another try and see if something has sorted itself out!340
0
Posted April 5th, 2006 11:00
Just out of curiosity, what does the 390113 mean
(i've not read hardly any docs for this; will start
now!)? Thanks
NetWorker client-server model uses processes/daemons whcih do register with RPC on the box. Each process/daemon doing it gets allocated RPC port. These ports can by dynamic or fixed. Known nsr* processes/daemons have their ports fixed. nsrexecd will use network port 7937 and RPC port 390113. Since rpcinfo command tests RPC connection and RPC port/process/daemon availability you need to use 390113 to be able to communicate with nsrexecd on remote system.340
0
Posted April 5th, 2006 12:00
Well, can you communicate with the client via rpc: "rpcinfo -p client_box" and "rpcinfo -t client_box 390113 1
when I do each of these this is what I get (i've only got this far):
rpcinfo -p mediacenter I get this:
rpcinfo: can't contact lgtomapper: remote system error - connection refused
program vers proto port
100000 2 tcp 111
100000 2 udp 111
100024 1 udp 764
100024 1 tcp 767
when I do rpcinfo -t mediacenter 390113 1 I get:
rpcinfo: program not registered
program 390113 version is not available340
0
Posted April 5th, 2006 12:00
Then its easy - NetWorker is not runningTry to run it with /etc/init.d/networker start (under assumtion that NetWorker is installed - if not then you will need to install it first).
Use "rpm -qa | grep -i lgto" to verify if packages are installed (you need client and manual as optional one).340
0
Posted April 5th, 2006 12:00
Can you confirm that client is installed and running? When you go to Linux box how many nsrexecd process do you see (you should see 2 for 7.1.x and 7.2.x or 1 if running 7.3.x). What version of NW is that anyway and what version of Linux? Do you have software firewall enabled on the that box?
From above as it seems NW is either not running or has problems getting to local RPC to register. Check if on the box you have some software which also emulates portmapper (such conflicts can cause LGTO version of pormapper not to run - I have seen this on IRIX with CAD programs and one user on this forum already had a topic with that issue as well).340
0
Posted April 5th, 2006 12:00
Ok. I'll have to get my Linux guy to check this; I hate not knowing this stuff. I'll keep in touch340
0
Posted April 5th, 2006 12:00
When I checked for the processes I found none (I knew how to do that much!) running.340
0
Posted April 5th, 2006 13:00
Ok. Tried starting it and it worked!!! This is what I see now (even though it still gives same error):
/usr/sbin/nsrexecd
/usr/sbin/nsrexecd
rpm -qa |grep -i lgto
lgtoclnt-7.1.2-1215
0
Posted April 5th, 2006 13:00
Same error? Still? OK, what do you get when you start this from the Linux client:
save -D9 -s backup_server_name -bname_of_the_pool_you_use_for_backup /etc/hosts
Message was edited by: hcrvelin
ble1
6 Operator
•
14354 Posts
•
56186 Points
359
0
Posted April 5th, 2006 11:00
clients a while back. It appeared to us that the
ports were locked down when we were testing it for
the first time; it took a couple of hours to track
down the guy who could open them, but there were no
locked down ports; we then attempted to show him what
the problem was we were observing and it backed up
fine. Maybe this is something like that - have
another try and see if something has sorted itself
out!
What Linux admin could check is if iptables is running and if it is blocking down communication. That used to be an issue on RedHat. If that is the case then you Linux admin needs to open a ports for communication for backup to procced by changing /etc/sysconfig/iptables.