NetWorker: How to Enter FQDN Hostname of NetWorker Client in the nsrla Database

The NetWorker client was added to NetWorker using its Fully Qualified Domain Name (FQDN):

[root@nsr ~]# nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> print type: nsr client; name: rhel-client01.amer.lan
                        type: NSR client;
                        name: rhel-client01.amer.lan;
                client state: active;
                     comment: ;
                   directive: ;
  cross mount points enabled: No;
       protection group list: ;
                    save set: All;
          Checkpoint enabled: Disabled;
Parallel save streams per save set: Disabled;
       Disk Space Monitoring: Disabled;
               remote access: ;
                 remote user: ;
                    password: ;
         NAS management user: ;
     NAS management password: ;
        NAS file access user: ;
    NAS file access password: ;
        index backup content: No;
              backup command: ;
                 Pre command: ;
                Post command: ;
     application information: NSR_PS_DEBUG_LEVEL=0;
     ndmp vendor information: ;
                        ndmp: No;
  ndmp multi-streams enabled: No;
                Disable IPv6: No;
                  NAS device: No;
             NDMP array name: ;
  NAS device management name: ;
storage replication policy name: ;
         Probe resource name: ;
          Block based backup: No;
             executable path: ;
                     aliases: rhel-client01, rhel-client01.amer.lan;
                 parallelism: 4;
                 backup type: Filesystem;
                          OS: ;
                 module type: ;
              module version: ;
             client timezone: ;
                         tag: ;
              index hostname: ;
        restricted data zone: ;
nsradmin>

The nsrladb on the client is being generated with the shortname. 

[root@rhel-client01 ~]# nsradmin -p nsrexecd
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> show name
nsradmin> p type: nsrla
                        name: rhel-client01;
nsradmin>

NetWorker creates the /nsr/res/nsrladb with whatever hostname (short or FQDN) that it receives from the Operating System during the time it creates the database.

1. Open an Administrator command-prompt or root shell on the NetWorker client.
2. Stop the NetWorker client services:

Linux: nsr_shutdown
Windows: net stop nsrexecd /y

3. Open the operating system hosts file:

Linux: /etc/hosts
Windows: C:\Windows\System32\drivers\etc\hosts

4. Check for any conflicting entries in the hosts file for the client's name. For example, in this instance, the host file entry appears as:

192.168.9.121   rhel-client01   rhel-client01.amer.lan

The shortname appears before the FQDN so when the NetWorker client service started, it created the nsrladb resource using the shortname.

Correct the hosts file so that the NetWorker client name is the first name aliased to the IP address, for example:

192.168.9.121   rhel-client01.amer.lan  rhel-client01

5. Rename the nsrladb file:

Linux: /nsr/res/nsrladb
Windows: C:\Program Files\EMC NetWorker\nsr\res\nsrladb

6. Start the NetWorker client services:

Linux: systemctl start networker
Windows: net start nsrexecd

7. Use nsradmin to confirm that the client has the correct name in its nsrladb:

nsradmin -p nsrexecd
show name
print type: nsrla

[root@rhel-client01 ~]# nsradmin -p nsrexecd
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> show name
nsradmin> print type: nsrla
                        name: rhel-client01.amer.lan;
nsradmin>

8. On the NetWorker server, open an Administrator command prompt or root shell. 
9. Check for any peer conflicts regarding the client: nsradmin -C -y -p nsrexecd "nsr peer information"

[root@nsr ~]# nsradmin -C -y -p nsrexecd "nsr peer information"

Validate "nsr peer information" resources

Synopsis: For each NSR peer information resource in nsr.amer.lan's NSRLA database, verify the 'NW instance ID' and 'certificate' attributes match those found in the peer's NSRLA resource.

...
...

 Hostname: rhel-client01
 Instance ID: ca782745-00000004-c0984de0-68532545-00015000-a61cbe56

 * The "NSR peer information" resource for rhel-client01 in nsr.amer.lan's NSRLA database is out of date. The "NW instance ID" attribute does not match the one stored in rhel-client01's NSRLA resource. To correct the problem, delete the NSR peer information resource for rhel-client01 in nsr.amer.lan's NSRLA database.

 * Deleted "NSR peer information" resource for rhel-client01 from nsr.amer.lan's NSRLA database

 Matching certificates: Corrected

Summary:

NSR peer information resources checked:       1
        RAP connect errors:                   0
        RAP query errors:                     0
        Resource mismatches:                  1
        Resources corrected:                  1

Peers with mismatched certificates/instance IDs: rhel-client01

Corrections were made to the NSRLA databases of the following hosts: nsr.amer.lan

Total errors:                                 1