클러스터 인스턴스의 NetWorker NMM SQL VDI 백업이 실패합니다. 공급자를 찾을 수 없습니다.

클라이언트가 클러스터 SQL Server 인스턴스인 경우 (NMM) NetWorker Module for Microsoft를 사용하면 Microsoft SQL Server 백업이 실패할 수 있습니다.  

일반적인 오류는 다음과 같습니다.
 

Cannot login to SQL Server --Provider cannot be found. It may not be properly installed.

예를 들어 다음과 같습니다. 

(pid=30180,2/25/2020 11:13:48 AM) D:/views/nw/19.2/nsr/db_apps/bsmsql/nsrsqlado.cpp(2261): Exiting GetProviderError().
(pid=30180,2/25/2020 11:13:48 AM) COM Error
(pid=30180,2/25/2020 11:13:48 AM) Code = 800a0e7a
(pid=30180,2/25/2020 11:13:48 AM) Code meaning = Unknown error 0x800A0E7A
(pid=30180,2/25/2020 11:13:48 AM) Source = ADODB.Connection

(pid=30180,2/25/2020 11:13:48 AM) Description = Provider cannot be found. It may not be properly installed.

(pid=30180,2/25/2020 11:13:48 AM) D:/views/nw/19.2/nsr/db_apps/bsmsql/nsrsqlado.cpp(1100): Exiting adoOpenConnection(), Exception.
66212 2/25/2020 11:13:48 AM  Cannot login to SQL Server VirtualSQLServerName\Instance01.

이 문제는 SQL Server를 설치하는 동안 Microsoft SQL Server 네이티브가 제대로 등록되지 않는 문제가 발생할 때 발생할 수 있습니다.

예를 들어,

프로그램 목록에는SQL Server 2012 및 2014용 Microsoft SQL Server Native Client 11.0이 표시됩니다

.

참고 자료: 

https://learn.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client?view=sql-server-ver15#support-lifecycle-exception참고 - 이는 SQL Server 2017까지의 SQL Server 버전에만 적용됩니다.  
SQL Server Native Client 권장 사항은 SQL Server 2019 이상에서 변경되었습니다.

STEP 1.  Check registry  

Open Powershell on SQL Server and run,

Get-Childitem  "hklm:\software\microsoft\microsoft sql server"

RESULT:  
If you do not see a Key called "SQLNCL11"  then there is an issue with SQL Native Client.


STEP 2.   Connect to SQL instance using OLE DB Driver 

Open Powershell on SQL Server and run, 
 
$conn = New-Object System.data.oledb.oledbconnection
$conn.ConnectionString = "Provider=SQLNCLI11.1;OLE DB Services = -2;Server=VirtualServer\Instancename ;Trusted_Connection=Yes;"

##  where you will please replace   -  VirtualServer\Instancename  --  with  Actual Cluster server name and Instance name   

$conn.open() 

RESULT:
When Open contains no errors  then continue to next step. 
When Open fails then this confirms that there is a problem with SQL Native Client. 

$conn
$conn.close() 

To resolve this issue,

Run Start, Control Panel, Programs and Features, Uninstall Programs, 
you will see a version of,

Microsoft SQL Server 2012 Native Client 

Action:   Right click and select Repair.