Unsolved

This post is more than 5 years old

1 Rookie

 • 

6 Posts

2850

October 19th, 2017 16:00

2 servers with same hostname

Hi all ,

i'm trying to configure 2 serves to join networker

the main problem that the 2 servers is the same hostname and there is no way to change any of them

the server hostname is like pc

i have added 2 client to networker  nmc using the follwoing names

pc1-bkp

pc2-bkp

but when the backup start to run it use actual hostname  "Pc "  and i didn't add it to any of configured clients as alias in save command as below :

138851:save: 'pc:C:\Windows\System32\drivers\etc\hosts' is being reset/promoted to level 'Full' as no backup is found.

98519:save: Unable to setup direct save with server server.test.local: Client 'pc' is not properly configured on the NetWorker Server..

90095:save: Cannot open save session with 'server.test.local': Client 'pc' is not properly configured on the NetWorker Server.

is there another way to send another hostname rather actual hostname configured on server

Any suggestions ?

Thanks in advance

2.4K Posts

October 20th, 2017 04:00

This seems to be a weird one.

Obviously you want to add 1 client twice to the NW admin GUI.

Yes - you can do have multiple instances of the same client.

No - you cannot change the hostname - it will always be true hostname, 'pc' in your case.

Here is how to do that:

  - Add the client the first time, as usual

  - Copy the client resource. Before you confirm make sure

      - to use the 'comment' line to add a text which describes the purpose of your resource.

      - that the 'save set' is different

      - that this client most likely should be added to another "group'

1 Rookie

 • 

6 Posts

October 20th, 2017 09:00

Thanks bingo for your reply

but if we use your solution  , i will have the same client with 2 different save sets  and at the end it will point to the same

server , in this case only one server of two , will be defined to networker .

2.4K Posts

October 23rd, 2017 05:00

This is correct ... that's how I understood your message.

This is the way NW works - if you backup another file system/volume, NW will/NW must create a new save set.

No matter how you generate it during the backup.

In other words:

  - In the save set field you can specify the alias 'All'.

       If you have 3 volumes, C:, D: & E: NW will generate backups with seperate save sets for C:, D: & E:

  - In the save set field you can list specific volumes for instance D:, E:

       If you have 3 volumes, C:, D: & E: NW will generate backups with seperate save sets for D: & E:

The file system is the separator.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

October 25th, 2017 08:00

Will that work bingo?  I mean, clientA will still say you need to add pc to alias list.  Fine, you add it... but then clientB will say the same and NW will detect same alias and won't let you do that.

Having different machines with same names doesn't make any sense and NW will always check for hostname of the machine which in return has to be on alias list (recommendation is actually always to use real name instead of canonical).

2.4K Posts

October 25th, 2017 12:00

I am talking about only 1 client.

It does not make sense to have both client resource in the same group but this is another story. #

For instance you could have ...

Group           1800_INT_2400_hours

  Client          abc

  Save Set     All

  Schedule    fri_full_incr_other days

Group           0000_INT_0200_hours

  Client          abc

  Save Set     D:\, E:\

  Schedule     incr_only

1 Message

March 9th, 2019 06:00

Hello, description of the process is clear but is not working because of error massage - Name conflict Client ID or Name conflict Alias name

6 Operator

 • 

1.3K Posts

March 12th, 2019 07:00

This might be usually because you have 2 client instances sharing the same clientID. CAn you please elaborate your scenario in more details?

0 events found

No Events found!

Top