NetWorker NMM: SQL Server Database Directed Restores Fail "NSR Client name could not be obtained"

SQL Server database directed restores fail with error:

NSR Client name could not be obtained

This error occurs in both user interfaces: 

• The Legacy UI: NetWorker User for SQL Server
• NetWorker Backup Plugin in SQL Server Management Studio

The error appears as follows:

NSR_CLIENT: NetWorker_SourceClientName ;
             NSR_DEBUG_LEVEL: 0;
                  NSR_SERVER: NetWorker_ServerName;
Recovering database 'SourceDatabaseName' into 'TargetDatabaseName ...

149342:(pid 7752): The NSR client name could not be obtained.

• NetWorker Client software on the source or the destination client has mismatching peer information (NSRLA) with NetWorker Server.
• The source or the destination Client resource has a missing fully qualified domain name (FQDN) in the Aliases field of the client.
• There are name resolution issues for the source or the destination client.

• You may have to add both the source and the target IP addresses to the host files on both the source and the target client. For example,

 IPAddress_source  hostname_source  FQDN_source
 IPAddress_target  hostname_target  FQDN_target

• You may have to generate a new NSRLA resource on the source or the destination client. For example, on the clients:

1. Stop the NetWorker Remote Exec service
2. Rename <NetWorker_Install_Path>\nsr\res\nsrladb to nsrladb.old 
3. Restart NetWorker Remote Exec service 
4. Run the following command in the Windows command prompt:

nsrnmsqlra -i

nsradmin -y -C -p nsrexecd  "type: nsr peer information; name:  source_client_name" 
        nsradmin -y -C -p nsrexecd  "type: nsr peer information; name:  target_client_name"

• Add any missing Aliases to the Aliases field of the client resources of either source or target client. For example, client named abc.domain, would typically contain in the Aliases field, both the hostname and the FQDN, abc and abc.domain.