Microsoft SQL VDI Geri Yüklemesi için NetWorker Modülü"nsrsqlrc: Hatasıyla Başarısız Olabilir: MSSQL$Inst_Name:/DB_Name" için bant oturumu açılırken hata

Summary: Microsoft (NMM) SQL Virtual Device Interface (VDI) geri yüklemesi için NetWorker Modülü"nsrsqlrc: MSSQL$Inst_Name:/DB_Name için bant oturumu açılırken hata.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Ürün:
Microsoft (NMM) sürüm 19.4.0.1

için NetWorker ModülüSorunu:
NMM SQL Virtual Device Interface (VDI) geri yüklemesi şu hatayla başarısız olabilir: 
nsrsqlrc: Error opening tape session for MSSQL$Inst_Name:/DB_Name
Hata ayıklama 9 günlüklerinde aşağıdaki hatalar bulunur: 
nsrsqlrc: 10/25/23 16:41:09.172978 lgto_auth: redirected to Server_Name.FQDN.com prog 390103 vers 2
nsrsqlrc: 10/25/23 16:41:09.219849 lgto_auth for `nsrmmd' succeeded
nsrsqlrc: 10/25/23 16:41:09.266733 RPC Authentication: Client failed to obtain RPCSEC_GSS credentials: Authentication error; why = Server rejected credential
nsrsqlrc: 10/25/23 16:41:09.266733 Could not get a session key for GSS authentication.  Perhaps this authentication method is not allowed/supported by both the local and remote remote machines.
nsrsqlrc: 10/25/23 16:41:09.266733 Falling back to use the older protocol which does not support pipe impersonation. Perhaps were are talking to an older auth server.
nsrsqlrc: 10/25/23 16:41:09.297987 RPC Authentication: Client failed to obtain RPCSEC_GSS credentials: Authentication error; why = Server rejected credential
nsrsqlrc: 10/25/23 16:41:09.297987 Could not get a session key for GSS authentication.  Perhaps this authentication method is not allowed/supported by both the local and remote remote machines.
nsrsqlrc: 10/25/23 16:41:09.297987 Failed to create lgto_auth credential for RPCSEC_GSS: Could not get session key from FQDN_name.com for GSS authentication with FQDN_name.com: Authentication error; why = Server rejected credential
nsrsqlrc: 10/25/23 16:41:09.297987 direct recover mmd auth failed: Could not get session key from FQDN_name.com for GSS authentication with FQDN_name.com: Authentication error; why = Server rejected credential
(pid=12312,25-10-2023 16:41:09) [7768]D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlio.c(1268):Error failed to obtained tape session for null
(pid=12312,25-10-2023 16:41:09) [7768]D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlio.c(1269): Exiting openWorkItem(), BSAGetObject() failed.
(pid=12312,25-10-2023 16:41:09) [7768]D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlio.c(1420): Entering getWorkItemName().
(pid=12312,25-10-2023 16:41:09) [7768]D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlio.c(1445): Exiting getWorkItemName().
37840 25-10-2023 16:41:09  Error opening tape session for MSSQL$Inst_Name:/DB_Name.

xbsa.messages file
XBSA-1.0.1 19.4.0.1.Build.95 12312 Wed Oct 25 16:40:07 2023           _nwbsa_is_retryable_error: received a retryable network error (Severity 2 Number 7): Could not get session key from FQDN_name.com for GSS authentication with FQDN_name.com: Authentication error; why = Server rejected credential
XBSA-1.0.1 19.4.0.1.Build.95 12312 Wed Oct 25 16:41:09 2023           _nwbsa_is_retryable_error: received a network error (Severity 2 Number 7): Could not get session key from FQDN_name.com for GSS authentication with FQDN_name.com: Authentication error; why = Server rejected credential

Cause

İstemcideki nsrla veritabanı yalnızca nsrauth için yapılandırılmıştır: 0.0.0.0/0, nsrauth

Resolution

  1. SQL istemcide, aşağıdaki adımları kullanarak nsrla veritabanını nsrauth/oldauth ile güncelleştirin:
nsradmin -p nsrexec
. nsrla
show auth methods
p
update auth methods: "0.0.0.0/0,nsrauth/oldauth"
y
p
q
  1. İstemcideki tüm NetWorker NMM hizmetlerini yeniden başlatın.
  2. NMM SQL VDI geri yüklemeyi yeniden çalıştırın.
Article Properties
Article Number: 000219087
Article Type: Solution
Last Modified: 01 Nov 2023
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.