NetBackup | MS SQL Server instances disappear from SQL Intelligent Policy

Problem

MS SQL Server instances disappear from SQL Intelligent Policy and previously discovered Availability Groups (AG) in NetBackup.

Cause

There is a mismatch in the following values:

- The output of the query SELECT @@SERVERNAME from SQL Management Studio.

- The Value in the Windows Registry under \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\X\Machines\OriginalMachineName 

Discovering AGs and instances involves both non-credential discovery and credential discovery. When NetBackup is not authenticated to connect to the SQL server, OriginalMachineName from the Windows Registry is collected by non-credential discovery as a source of the information for AGs or instances. Once connected, the information obtained from SQL Server will also be used. The conflict between these pieces of information will lead to a cycle of source information changing, which results in the issue of the AGs disappearing from NetBackup. 

This mismatch could be attributed to multiple factors. One to be considered is the cloning and deploying of VMs containing previously configured SQL Servers.

Solution

• Compare the following values in the client. 

           The output of the query SELECT @@SERVERNAME from SQL Management Studio.

           The Value from the Registry under \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\X\Machines\OriginalMachineName 

           If the values above do not match, then rename one of those to make them match based on the preferred naming convention used in your organization. 

• Restart NetBackup Services on the SQL client. 

• Register Instance Name using the same name selected for the Registry keys 

https://www.veritas.com/content/support/en_US/article.100067428