Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1872

August 18th, 2010 06:00

Hosts Suse 9 Linux will not backup with a server initiated backup

Hi Guys,

We have a SUSE Linux 9 box which I cannot backup with a server initiated backup.

Our NetWorker server is running 7.5.2 on Sun 10 and the client is also running 7.5.2 on SUSE Linux 9.

The client can backup data to the NW server as a client initiated backup with no problem, however when we run a server initiated backup we get the following error:

0 12/08/2010 09:57:24  2 0 0 2521585248 28157 0 prsas0 nsrexecd @(#) Product:      NetWorker
0 12/08/2010 09:57:24  2 0 0 2521585248 28157 0 prsas0 nsrexecd @(#) Release:      7.5.2.Build.452
0 12/08/2010 09:57:24  2 0 0 2521585248 28157 0 prsas0 nsrexecd @(#) Build number: 452
0 12/08/2010 09:57:24  2 0 0 2521585248 28157 0 prsas0 nsrexecd @(#) Build date:   
0 12/08/2010 09:57:24  2 0 0 2521585248 28157 0 prsas0 nsrexecd @(#) Build arch.:  linux86w
0 12/08/2010 09:57:24  2 0 0 2521585248 28157 0 prsas0 nsrexecd @(#) Build info:   DBG=0,OPT=-O2 -fno-strict-aliasing
61313 12/08/2010 10:19:55  5 1 13 1082128736 28157 0 prsas0 nsrexecd Couldn't look up the name of address: 10.215.121.231: Name or service not known
61313 12/08/2010 10:40:36  5 1 13 1082128736 28157 0 prsas0 nsrexecd Couldn't look up the name of address: 10.215.121.231: Name or service not known
61313 12/08/2010 12:46:42  5 1 13 1084225888 28157 0 prsas0 nsrexecd Couldn't look up the name of address: 10.215.121.231: Name or service not known
61313 12/08/2010 12:53:27  5 1 13 1084225888 28157 0 prsas0 nsrexecd Couldn't look up the name of address: 10.215.121.231: Name or service not known

Now the hostname resolution at the client side is done via /etc/hosts and here is what we have for the IP address which can't be resolved:

10.215.121.230 TOLNWKDZ3SVR001-FEA.emcmgmt.prv TOLNWKDZ3SVR001-FEA #
10.215.121.231 TOLNWKDZ3SVR001-FEB.emcmgmt.prv TOLNWKDZ3SVR001-FEB #
10.215.121.234 LCYNWKDZ3SND001-FEA.emcmgmt.prv LCYNWKDZ3SND001-FEA #
10.215.121.235 LCYNWKDZ3SND001-FEB.emcmgmt.prv LCYNWKDZ3SND001-FEB #
10.215.121.236 LCYNWKDZ3SND002-FEA.emcmgmt.prv LCYNWKDZ3SND002-FEA #

10.215.121.237 LCYNWKDZ3SND002-FEB.emcmgmt.prv LCYNWKDZ3SND002-FEB #

these are our entries in nswitch.conf:

passwd: files
shadow: files
group:  files

hosts:      files dns
networks:       files dns

services:       files
protocols:      files
rpc:        files
ethers:        files
netmasks:       files
netgroup:       files
publickey:    files

bootparams:     files nis
automount:      files nis
aliases:        files nis

Now as you can see we have all the correct entries for all of our NIcs on the NW server and SNs in the hosts table, however when starting a server initiated backup we get hostname resolution errors.

Below you can see that we have RPC connection to the client with the following command:

bash-3.00# echo print | nsradmin -p 390113 -i - -s prsas0.eud.schneider-electric.com
                        type: NSR remote agent;
                        name: Filesystem;
                 backup type: Filesystem;
             product version: ;
remote agent protocol version: 1;
                    features: Configuration, List Directory;
     remote agent executable: nsrfsra;

            backup type icon: ;

                        type: NSR log;
               administrator: root, "user=root,host=prsas0";
                       owner: NetWorker;
             maximum size MB: 2;
            maximum versions: 10;
        runtime rendered log: ;
                        name: daemon.raw;
                    log path: /nsr/logs/daemon.raw;

                        type: NSRLA;
                        name: prsas0;
NW instance info operations: ;
       NW instance info file: ;
          installed products: NetWorker 7.5.2.Build.452;
                     version: EMC NetWorker 7.5.2.Build.452 02/04/10;
                     servers: TOLNWKDZ3SVR001-FEA, TOLNWKDZ3SVR001-FEB;
                auth methods: "0.0.0.0/0,nsrauth/oldauth";
               administrator: "isroot,host=TOLNWKDZ3SVR001-FEA",
                              "isroot,host=TOLNWKDZ3SVR001-FEB", root,
                              "user=root,host=localhost",
                              "user=root,host=prsas0";
                 kernel arch: x86_64;
                    CPU type: x86_64;
                machine type: desktop;
                          OS: Linux 2.6.5-7.191-smp;
           NetWorker version: 7.5.2.Build.452;
              client OS type: Linux;
                        CPUs: 2;
                     MB used: 6188;
                  IP address: 10.215.4.66, 10.215.5.66, 10.215.6.72,
                              10.215.120.193, "fe80::214:5eff:fe36:648%253",
                              "fe80::214:5eff:fe36:649%253",
                              "fe80::214:5eff:fe36:648%253",
                              "fe80::214:5eff:fe36:648%253",
                              "fe80::214:5eff:fe36:648%253",
                              "fe80::214:5eff:fe36:648%253";

I have a call open with support but I think they are stumped too, does anyone have any ideas?

Thanks

August 19th, 2010 01:00

did you set the "Server network interface" attribut of your client object ?

5 Practitioner

 • 

274.2K Posts

August 18th, 2010 07:00

Thanks alan

334 Posts

August 18th, 2010 07:00

Hi Daniel,

This might get better responses over here in the support forum.

Thanks,

Allan

5 Practitioner

 • 

274.2K Posts

August 18th, 2010 08:00

They are the 2 NICs of the NetWorker server

August 18th, 2010 08:00

Are the following names different ipos of the same Server ?

TOLNWKDZ3SVR001-FEA #
TOLNWKDZ3SVR001-FEB #

If so check the aliases of your client.

5 Practitioner

 • 

274.2K Posts

August 19th, 2010 01:00

Sorry I clicked the "correct answer" by mistake.

Yes the Server NIC field is populated with:

TOLNWKDZ3SVR001-FEA

I have tried taking this value out and also placing just the IP address in there but the behaviour is still the same.

14.3K Posts

August 25th, 2010 05:00

2dam2 wrote:

Sorry I clicked the "correct answer" by mistake.

Yes the Server NIC field is populated with:

TOLNWKDZ3SVR001-FEA

I have tried taking this value out and also placing just the IP address in there but the behaviour is still the same.

Actually you should use TOLNWKDZ3SVR001-FEB as server initiated backup was complaining about that interface indicating it gets used during this server-client communication.  If you expected FEA to get used it might be an issue with routing.

Are you sure that both server and client have this entry in hosts table?  I would also disable nsrauth (just in case).  And last one, do you really need IPv6?  Hardly that it is an issue here, but I had experience where it broke indirectly few things.

No Events found!

Top