NetWorker Module for Microsoft SQL VDI Restore May Fail with Error "nsrsqlrc: Error opening tape session for MSSQL$Inst_Name:/DB_Name"
Summary: NetWorker Module for Microsoft (NMM) SQL Virtual Device Interface (VDI) restore may fail with error "nsrsqlrc: Error opening tape session for MSSQL$Inst_Name:/DB_Name."
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.
Symptoms
Product:
NetWorker Module for Microsoft (NMM) version 19.4.0.1
Issue:
NMM SQL Virtual Device Interface (VDI) restore may fail with error:
NetWorker Module for Microsoft (NMM) version 19.4.0.1
Issue:
NMM SQL Virtual Device Interface (VDI) restore may fail with error:
nsrsqlrc: Error opening tape session for MSSQL$Inst_Name:/DB_NameThe following errors are found in debug 9 logs:
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
The nsrla database on the client is only configured for nsrauth: 0.0.0.0/0,nsrauth
Resolution
- On the SQL client, update the nsrla database with nsrauth/oldauth using the following steps:
nsradmin -p nsrexec . nsrla show auth methods p update auth methods: "0.0.0.0/0,nsrauth/oldauth" y p q
- Restart all NetWorker NMM services on the client.
- Run NMM SQL VDI restore again.
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.