Unsolved
1 Rookie
•
6 Posts
0
707
December 20th, 2022 04:00
SQL log and incremental networker backup failing due to DB mirroring
Dears,
Kindly note that i am facing and issue with my networker SQL backup for an SQL cluster. The backup is failing with the below
153887:nsrsqlsv: Microsoft SQL server documentation provides details about the following SQL Server Provider error:
38008:nsrsqlsv: Invalid authorization specification
153416:nsrsqlsv: (Error: 0)
Unable to determine the status of mirror partner backups for database
This backup of [] will be promoted to a full database backup.
Is there any solution for the above error, or there is something to do with the user we are running the backup with it should be given any specific privileges ?
.
No Events found!
barry_beckers
393 Posts
0
December 22nd, 2022 00:00
Was it ever working or is this a new setup? What NW and NMM version and MSSQL version is this?
Also you seem to be cherry picking the error you want us to see, instead of showing also other messages? As it states promoting the backup to a full, I'd expect it to state some other useful information also WHY it wants to do just that? for example a message stating " Last backup of database 'XXXXXX' was not created using NMSQL Module."...
Did you follow the NW NMM VDI backup guide, which states what permissions are required? You are using the approach to do this with SYSTEM?
Maybe that an older KB might apply? https://www.dell.com/support/kbdoc/en-uk/000079546?lang=en. However many KB articles do not have any follow-up stating if it is even addressed or fixed and in what release. Also missing any reference even to the NW or NMM module this is experienced with or what MSSQL version. The errors reported however show them to be from 2012 (!), hence one would assume things would have been addressed by now.
"Problem was resolved after user performed a manually started full backup (savegrp).
Resolution
Workaround Fix: After establishing mirror for SQL database and performing locall backup, it is required to perform a Full backup by NMSQL.
The best practice for SQL databases is after making any change to the database including even database recovery; the next backup performed by NMSQL should be manually scheduled as Full."
barry_beckers
393 Posts
0
December 22nd, 2022 01:00
for example see in https://dl.dell.com/content/docu94039_networker-module-for-microsoft-for-sql-vdi-19-1-user-guide.pdf?language=en_us the parts "Configuring permissions to perform NMM backup and recovery of Microsoft SQL Server" and "Assign SQL server roles for backup and recovery operations".
We ourselves do not use the NW client wizard to configure NMM backups, so we don't specify any user, thus depending on the SYSTEM part to be setup correctly on client end.
rayan-chazbek
1 Rookie
•
6 Posts
0
February 12th, 2023 23:00
Thank you for your information, I will contact the Database admins to try to run a manual full backup from their side and then check.
Regarding the permissions for the user, the user we are using is local administrator on both nodes and sysadmin from the SQL side as well.