1 Rookie
•
35 Posts
0
631
BMR for MS SQL - No backups were found for client client.domain.com using browse time
NetWorker 19.3
I am testing BMR for Windows 2019 with MS SQL.
I am able to backup both the filesystem and the SQL Server from the NetWorker Console.
Once the backups are completed, from the client server, I am able to browse and restore the "TEST" database using NetWorker Plugin for SQL Server Management Studio.
However, after a successful BMR recovery, I am trying to recover the MS SQL database.
I open NetWorker User for Microsoft, and from the Recover > SharePoint and SQL Server Recover Session, no save sets are displayed, from the Monitor I get No backups were found for client client.domain.com using browse time.
There's a section called "Performing BMR of a standalone SQL Server" in the NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide which says to use the NMM as I was trying, however no save sets are showing for me.
I can confirm that Save Sets with type (MSSQL:msdb, model, master, TEST) appear in the NetWorker disk volume.
I deleted the nsr peer information for the client server with the nsradmin -p nsrexec command successfully, but it didn't help.
Using NetWorker Plugin for SQL Server Management Studio is not an option as it requires the SQL Agent to be in a started state.
What am I missing?
VictorGh
1 Rookie
1 Rookie
•
35 Posts
0
June 24th, 2023 15:00
The solution is as follow:
1. https://learn.microsoft.com/en-us/sql/relational-databases/databases/rebuild-system-databases?view=sql-server-ver16
2. Use NetWorker Plugin for SQL Server Management Studio
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
June 20th, 2023 04:00
Hi @VictorGh , You have launched the NMM User on the SQL server. Are you able to see NetWorker user for SQL under the NetWorker in All programs ?
VictorGh
1 Rookie
1 Rookie
•
35 Posts
0
June 20th, 2023 06:00
Hi @crazyrov
I open the NetWorker User for Microsoft from the SQL server that was just recovered via BMR.
From the app, the Update Server List works, I can see my backup server.
Then, I make sure the SharePoint and SQL Server Plug-in is Active, and I played with the Change Time to the dates around my backups, I always get No save sets for selected client and browse time
If it help, before I wipe the server and do a BMR, I tried the same procedure and I still get the same message, it doesn't find the save sets
Check out the save sets from the backup server below.
barry_beckers
393 Posts
0
June 20th, 2023 11:00
Did you setup the backup for MSSQL as VSS (*) backup or as VDI backup? We only use VDI backup as that offers also transaction log and incremental backups, unlike VSS backup that only allows full backups. So is the backup command using nsrmmsv (VSS based) or nsrsqlsv (VDI based)?
So VDI backups need to be restored via "networker user for sql" GUI while VSS based SQL backups need to be restored via "networker user for microsoft" GUI.
Are you possibly using the wrong GUI? The VSS backup configuration would have a save set like "APPLICATIONS:\SqlServerWriter" while the MSSQL: save sets seem to point you using VDI backup approach. Hence you should use the other SQL recover gui...
(*) VSS SQL backup limitations:
NMM does not support the following types of SQL VSS backups:
• SQL transaction log backups
• SQL database differential backups
• SQL backup of individual filegroups, files, or logs
VictorGh
1 Rookie
1 Rookie
•
35 Posts
0
June 20th, 2023 17:00
HI @barry_beckers
Thanks for the reply! I checked the SQL client resources which I created using the the New Client Wizard, it's using nsrsqlsv.exe (VDI based).
When I run command nwmssql, I get the message Networker User for SQL GUI has been Deprecated
I have NMM 19.3 installed on the SQL server.
barry_beckers
393 Posts
0
June 26th, 2023 00:00
Which is pretty much what is actually stated in the NW19.3 "Dell EMC NetWorker Module for Microsoft for SQL VDI User Guide" in Bare Metal Recovery chapter "Performing BMR of a stand-alone SQL Server"?
So you might wanna use the official documentation as reference. Or at least as a starting point...