Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

mgossett1

261 Posts

2131

April 5th, 2006 09:00

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

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 5th, 2006 09:00

Do you have clientpak for Linux (license) installed? Those field do not get populated until backup is done. If your backup is failing what is the error message?

DavidHampson

2 Intern

 • 

1.1K Posts

April 5th, 2006 10:00

I think you'll find those fields get populated when you run the first backup.

mgossett1

261 Posts

April 5th, 2006 10:00

I was told this: i had some old servers I didn't need backed up so I deleted them. The person who sold me the licenses (maybe the wrong one to ask?!) said that all I needed to do was delete the old ones, create a new one and once the software was installed it would 'pick up' the free license(s).

DavidHampson

2 Intern

 • 

1.1K Posts

April 5th, 2006 10:00

I've found support has slipped quite a bit lately. Sometimes I wonder if there is anyone there at all!

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 5th, 2006 10:00

I'm lost now - is it Windows or Linux and is it fixed or not? :D

However, connection refused as you said is easy to trace down...

mgossett1

261 Posts

April 5th, 2006 10:00

I will definetly try this stuff out and let you know. Just out of curiosity, what does the 390113 mean (i've not read hardly any docs for this; will start now!)? Thanks

mgossett1

261 Posts

April 5th, 2006 10:00

They were actually windows clients. Sorry about not posting message: not sure what's wrong with the 'ole brain today. Here's the message which, by the way, I have gotten in the past for my windows machines (a few of them) and it wasn't hard to fix:

Unsuccessful saveset
*mediacenter: All 1 retry attempted
*mediacenter: All connection refuesed

That plus, of course, the missing information mentioned earlier. By the way, thanks for the responses. Best i've ever had in a support forum ever!

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 5th, 2006 10:00

Well, that makes sense if you delete them from NW as client resource (if they were also Linux clients). However, you still didn't say what is the error while doing the backup... Can you show us that?

mgossett1

261 Posts

April 5th, 2006 10:00

Ok. It is linux and it's not fixed: still broken. I can't remember how to track down the all connection refused dialog.

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 5th, 2006 10:00

Yes, lately they are a busy as it seems :D

- Well, can you communicate with the client via rpc: "rpcinfo -p client_box" and "rpcinfo -t client_box 390113 1"
- Can you get a response from client "echo print | nsradmin -p 390113 -i - -s client_box"
- Does the client initiated backup work
- If you check daemon.log do you see any extra information like server/client being unable to resolve each other or one of them?
- Is servers file listing correctly server (if listing it at all)

That would be enough for start :)

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

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!


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.

DavidHampson

2 Intern

 • 

1.1K Posts

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!

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

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.

mgossett1

261 Posts

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 available

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 5th, 2006 12:00

Then its easy - NetWorker is not running :D Try 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).

Was this post helpful?

View All

No Events found!

Top