SQL Intelligent Policy backup of newly configured client fails with error status: 2: none of the requested files were backed up

Problem

SQL Intelligent Policy backup of newly configured client fails with error status: 2: none of the requested files were backed up

Error Message

Job Details:

May 15, 2020 1:17:35 AM - Info dbclient (pid=5432) INF - Created VDI object for SQL Server instance <Test>. Connection timeout is <300> seconds.
May 15, 2020 1:22:40 AM - Info dbclient (pid=5432) ERR - Error in GetConfiguration: 0x80770003.
May 15, 2020 1:22:41 AM - Info dbclient (pid=5432)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
May 15, 2020 1:22:46 AM - Info dbclient (pid=5432) INF - OPERATION #1 of batch __01_11_41_125_00.bch FAILED with STATUS x (0 is normal). Elapsed time = 313(313) seconds.
May 15, 2020 1:22:48 AM - Info dbclient (pid=5432) INF - Results of executing <__01_11_41_125_00.bch>: 
May 15, 2020 1:22:48 AM - Info dbclient (pid=5432) <0> operations succeeded. <1> operations failed.
May 15, 2020 1:22:48 AM - Info dbclient (pid=5432) INF - The following object(s) were not backed up successfully.
none of the requested files were backed up  (2)

dbclient logs:

<4> dbc_GetServerClientConfig: ServerName: <Master>, ClientName: <Veritas>
<8> dbc_GetServerClientConfig: WARNING - NBU's client name= <Veritas> differs from gethostname()= <Test_Veritas>

Cause

This issue can occur if a VM is deployed using a VMware Template and has Browser and Client Name Set of the Original Template, this can be confirmed from registry.

Solution

On the Client, Open registry editor

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Navigate to the below mentioned registry Hive,

HKLM\SOFTWARE\VERITAS\NETBACKUP\CURRENT VERSION\CONFIG

Compare the REG_SZ values -Browser and Client_Name.

Update these keys to Match the Hostname of the Client

Browser Key "Test_Veritas" , Client_Name "Test_Veritas",

Recycle the NBU client Services on the Client.