Start a Conversation

Unsolved

This post is more than 5 years old

8178

October 27th, 2014 09:00

53363:recover: Recover of rsid **** failed: Unknown host

Hello,

from a Solaris 10 (with NW 8.1.1.3), I'm trying to recover a file with the follwing command :

recover -s server_name -a fic1

I get this stupid undocumented error.

I can save the file from the client and I can save the file from the server with a group.

Even with the interactive recover, I get this message.

Server and client can ping and I don't use DNS (only /etc/hosts files).

So, where am I wrong ?

Thanks for help.

Denis

68 Posts

October 29th, 2014 07:00

@Hrvoje Crvelin :

Made some tests and it works against a Networker Server in 7.6.3.2 without changing nothing, neither names nor NIC IP !

So I'm confused about a specific system call for resolving names.

I don't know things about NSRLA, so if you can enlighten me :-)

I post the result of NSRLA resource on the client :

                      type: NSRLA;

                        name: client_name;

              nsrmmd version: ;

            nsrsnmd version: ;

NW instance info operations:  Import    New Keys    Export ;

      NW instance info file: ;

          installed products: ;

                auth methods: "0.0.0.0/0,oldauth";

          max auth attempts: 8;

              administrator: "isroot,host=server_name_8-1", "isroot,host=server_name_8-1_s", "isroot,host=another_server_name",

                              "isroot,host=server_name_7-6", "user=root,host=client_name", "user=root,host=localhost";

                        arch: sparc;

                kernel arch: sun4v;

                    CPU type: sun4v;

                machine type: workstation;

                          OS: SunOS 5.10;

          NetWorker version: 8.1.1.3.Build.289;

              client OS type: Solaris;

                        CPUs: 128;

                    MB used: 1396932;

                  IP address: Common LAN, LAN S/R;

  environment variable names: ;

14.3K Posts

October 29th, 2014 08:00

Using 8.1 client against 7.6.x server is not smartest thing.  Which server did you use before (version wise)?  Those auth messages we seen before are because nsrauth is not enabled on client (and I suspect if you had server running on NW8 you might have it enabled on server side before).  As for why it would work with 7.6 based server, I have no idea, but this might be good case for support call.

14.3K Posts

October 29th, 2014 09:00

You will need nsrauth enabled if you plan to use NMC8 on server.  And then, best practice is to have enabled on client too. You can enable it yourself via nsradmin:

nsradmin -p 390113

show auth methods

print type: NSRLA

update auth methods: "0.0.0.0/0,nsrauth/oldauth"

Yes

q

68 Posts

October 29th, 2014 09:00

Actually, my production server is 7.6.3.2 with clients from 7.1.2 to 7.6.5.6

I'm currently testing the 8.1.1.3 to ensure that it has no effect on saves organization that we currently have.

So, I've installed the 8.1 server version (on my test server) and migrate a client from 7.6 to 8.1 just to see if it was working (by saving and restoring a file) but as you see, I missed (or not ).

My intention was no to have a 8.1 client running against a 7.6 server. I've just noticed that it works fine among my multilples tests to find a clue (tested solaris 8, solaris 10, local zone, global zone...).

I've never understood these nsrauth and other authentication mechanisms, so I'm going to open a call in order to see if supprt can solve the problem.

Thanks for the help. I'll be back to update this topic.

68 Posts

November 4th, 2014 04:00

Some news :

support told me to add the 'standard vlan' IP NIC address in the client hosts file and it works...

No reason why it works previously with a 7.6 server and does not work with a 8.1 server since modification is made only client-side.

Thanks

Denis

14.3K Posts

November 4th, 2014 07:00

NW8 uses tightened security model check and obviously they check those as well.

No Events found!

Top