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 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).

mgossett1

261 Posts

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 touch

mgossett1

261 Posts

April 5th, 2006 12:00

When I checked for the processes I found none (I knew how to do that much!) running.

mgossett1

261 Posts

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-1

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

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

mcprazak

19 Posts

April 7th, 2006 14:00

After reading this, I'm not sure where you are on getting the Linux server backed up. You shouldn't need to delete old server definitions to get the client licenses back. I was told all you have to do is stop backing them up.

The question was asked earlier if you had the "Clientpak for Linux" installed on your Legato Server? You mentioned this was your first Linux server. If so you will need to purchase "Clientpak for Linux" to enable Linux backups.


Message was edited by: mprazak


Message was edited by: mprazak

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 7th, 2006 15:00

To free up the license you must delete the client from resource database (so all instances of the client). I would assume he would see the error in the daemon.log if clientpak was missing (or from the debug output). However, from what we have been told so far he is not able to contact nsrexecd on local host of the client - so problem seems to be somewhere else.

mgossett1

261 Posts

April 10th, 2006 09:00

Here is the daemon.log file for your perusal just to check it out. if anyone has ideas awesome but i'm sending it to support just the same:

starting Linux Systems (with 1 client(s))
04/10/06 10:38:15 savegrp: command 'savefs -s backupserver -c mediacenter. -g Linux Systems -p -l full -R -v ' for client mediacenter. exited with return code 9.
04/10/06 10:38:15 savegrp: mediacenter.:probe will retry 1 more time(s)
04/10/06 10:39:36 savegrp: command 'savefs -s backupserver -c mediacenter. -g Linux Systems -p -l full -R -v ' for client mediacenter. exited with return code 9.
04/10/06 10:39:36 savegrp: mediacenter.:probe will retry 0 more time(s)

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 10th, 2006 13:00

Well, you will need clientpak. You will also need to make sure that address can be resolved for IPs hosted on that client. For some reason 172.16.3.214 is used - perhaps for management talk. DHCP clients are supported from 7.3 (but you will need server on 7.3 too). If your management and backup NIC have fixed IPs then this is more related to routing on the box.

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 10th, 2006 13:00

That is from the server - what about client and daemon .log there.

As it seems things fail at savefs level - this usually indicates troubles at very first step of server/client communication which usually is related to name resolution or availability of nsrexecd on the client side.

What happens if on the client you run: savefs -s backupserver -vpn

mgossett1

261 Posts

April 10th, 2006 13:00

When I tried to run the save on the linux client I got:

savefs: diagnostic: reverse DNS lookup failed for address 172.16.3.214. My backupserver has a static IP of 172.16.0.x so i don't even know what it's looking at. A 172.16.3.x on our network is for worstation DHCP. I also don't have clientpak for linux yet.

mgossett1

261 Posts

April 10th, 2006 13:00

Ok. i am getting clientpak shortly (hopefully next couple of days). By the way, what does the clinetpak do that the license isn't enough??? Also, all of my servers are static IP's which is why the 172.16.3.x DHCP stood out. Thanks!

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 10th, 2006 13:00

In LGTO/EMC world of licenses this how the things are: you have backup server which runs let's say on Solaris. Now, to backup some Solaris client you obviously need client connection license. To backup Windows client you need on top of that also so called clientpak for Windows to enable the backups on platform which is different from backup server OS. In release 6.x somewhere came up with idea that Linux is not UNIX so clientpak for Linux was introduced (to enable backups of Linux platform). In 7.x it become clear that to backup HPUX you need also clientpak for UNIX as Solaris and HPUX (or any other supported UNIX OS is not the same). Last one was not enforced in license check, but I believe that changed in some 7.x version since.

Clientpak is not required per client number - meaning one client for Linux will just unlock the feature to backup unlimited number of Linux client. That number will however be limited by the number of client connections available.

DavidHampson

2 Intern

 • 

1.1K Posts

April 10th, 2006 14:00

If you run the nsrlic command from the command line it may help to explain this - it will show you what you are backing up and allowed to back up with the current licenses.

You do not need to wait for a license; if you have a media pack there will be an evaluation enabler in that which you can put in now, then when you get the full license you can enter that. (I do not have a media pack here so cannot give you the code!)

mgossett1

261 Posts

April 14th, 2006 05:00

Well I did some checking. It appears the clientpak for linux I already have installed on my backup server!! I finally found it. I'm still getting the attempt 1 try and then failed. I do have two instances of nsrexecd running on the linux box. Both can ping back and forth so I know they're talking. we are on networker 7.1.2 (I don't know if that has anything to do with it but I wouldn't think so). ANy ideas would be great. I'm in the process of renewing my maintenance but let's just say I shouldn't have waited so long!! THanks

Was this post helpful?

View All

No Events found!

Top