Many warnings

Hi,

Can you check if the client entry created for that storage node is created with the exact same name (short name or FQDN)as the storage node itself?

In some cases the client is created like "sn_client", and the storage node is created as "sn_client.domain.com"

Is the storage node enabled? Go to Media, and click on storage nodes, on the right side of NMC you will see the status of the storage node, also ensure that nsrsnmd and nsrmmd's processes are started on that SN

Thank you,

Carlos

Sorry, what does this mean: "client entry for that storage node". I have SN on my NW server.

Yes, SN enabled.

How can I check nsrsnmd and nsrmmd processes?

Thnx.

Here is what you need to check.

On the NMC go to -> Devices -> Storage Nodes, check the name of the storage node in question (you have to note if it is just he hostname or with the FQDN). Then go backup to the NMC -> Configuration -> Clients. search for that storage node in here and see what name it is configured with. The name should be same as the one under the storage node that you earlier noted.

I find name of the SN is the same as a name of one of clients. But this clients-are for savesets from backup server. In properties of this client there is parameter StorageNode. It is nsrserverhost (Globals 2 of 2). Should I create client for storage node if it is the same as the server name?

I can explain as example:

I have NW server "srvbackup.mydomain.com"

I have SN "srvbackup.mydomain.com"

I have client on NW server "srvbackup.mydomain.com", it was created to make a backup of disk C:\ on this server.

As i can see in you environment the NW server, SN and Client is the same host. in this case u can create a client wid  srvbackup.mydomain.com and make the storage node as srvbackup.mydomain.com or nsrserverhost. here nsrserverhost is ur NW server which is same as srvbackup.mydomain.com.

In case u have created ur SN as srvbackup only instead of srvbackup.mydomain.com u can also add the alias name srvbackup.mydomain.com in client properties--> Global (1 of 2)-->aliases. It will be affected to all the client instances

I thought that it will help me with warnings...

From the error it looks like NetWorker thinks your backup servers hostname is changed. Did you edit the hosts file on the backup server? If the shortname mentioned just after the IP, like follows :

1.1.1.1     backupserver    backupserver.xxx.com

either ways get the following output

# nsradmin -d "path_to_nsr\res\nsrdb"

nsradmin> . type: nsr client; name: backup_server_hostname

nsradmin> option hidden

nsradmin> show name; aliases

nsradmin> print

nsradmin> . type: nsr client; name: backup_server_hostname.fqdn.com

nsradmin> option hidden

nsradmin> show name; aliases

nsradmin> print

I restarted "Backup and recover server" service and now it doesn't start...no errors in logs

How can I put it back to aliases from command line?

84419 1410270061 5 5 0 3600 2656 0 nsrd NSR critical 228 NetWorker is

unable to continue its startup sequence due to a server hostname change to "%s".

Please verify that the server's hostname and its aliases are properly represent

ed in the local host database (eg. /etc/hosts) and DNS. 1 12 9

I checked host file both of short and FQDN names represented.

I deleted   from aliases. And put FQDN. After that I have error

Hi,

Did you make any changes in either DNS or hosts file? If so please revert those changes back.

As for the change of the alias, well, that is not really good practice, but to solve it please follow these steps:

On NW server run the following command:

nsradmin -d /nsr/res/nsrdb   <- This has to be the correct path to the nsrdb folder

nsradmin>. type: nsr client; name:server_name

nsradmin>update aliases: server_name, server_name.domain.com

update?y

(Type y every time you are asked for, as that will update every single client entry for the server)

nsradmin>quit

Thank you,

Carlos

Maximus,

       -d allows you to connect to the nsrdb when the nsrd is down. Ensure all the services are down both nsrd and nsrexecd then run the following command:

nsradmin -d "C:\Program Files\Legato\nsr\res\nsrdb"

Then follow what Carlos has mentioned in his post.

===================================================

nsradmin>. type: nsr client; name:server_name

nsradmin>update aliases: server_name, server_name.domain.com

update?y

(Type y every time you are asked for, as that will update every single client entry for the server)

nsradmin>quit

===================================================

for short name:no resources found for query

for FQDN several aliases like this:

aliases: FQDN_name

name: FQDN _name