NMM - Introduction to SQL VDI based backups and Restore

NetWorker Commands App:
Google Play Store - qrgo.page.link...
Apple App store - apps.apple.com...
=========================================================================
My Lab Set up:
AMD Ryzen 7 3700x processor - amzn.to/32SHIXX
GIGABYTE X570 AORUS ELITE Wifi - amzn.to/31VDJuE
RIPJAW 16GB - amzn.to/34Y5UuJ
Radeon RX 580 - amzn.to/32P3j3w
cooler master 550 watt power supply - amzn.to/3lMSUy8
=========================================================================
Contact Information:
Twitter - / crazyrovs
Website - crazyrov.com/
Email - [e-mail]
DELL EMC Community Page - www.dell.com/c...
=========================================================================
This is a multipart video, I have broken down the topic into different parts because I understand that not everyone wants to understand the topic in depth and just want to know how to understand how to configure the backups. NetWorker uses the NMM or NetWorker module for Microsoft applications to support the backup and restore of microsoft SQL databases. In this video we will look at how the NetWorker module for microsoft interacts with the SQL server to do backup or restore. For how to configure videos check for the links in the description or check the SQL backups playlist.
First lets look at how the backups work in a traditional environment.
During a traditional backup, the backup starts from the nsrsqlsv program, which is started by using one of the following:
● Command prompt
● NMM plug-in for the Microsoft SQL Server Management Studio
The following process occurs in a traditional backup:
1. The nsrd program starts the backup nsrworkflow on the NetWorker server.
2. The nsrworkflow starts the savegrp program.
3. The savegrp program runs the NMM backup command (nsrsqlsv) on the client instead of performing a standard NetWorker save.
4. The nsrsqlsv program passes the backup data from SQL Server to the NetWorker server through an X-Open Backup Services application programming interface (XBSA). The XBSA in simple terms is the programming interface that allows the database to connect to the media management layer which in our case is the NetWorker application.
The next slide is about how the backup interacts with the node incase of a Alwayson Availability group.
During a federated backup, processes interact between the NetWorker client (that is, NMM), the NetWorker server, and the SQL Server.
The backup starts from the nsrsqlsv program, which is started by using one of the following:
● Command prompt
● NMM plug-in for the Microsoft SQL Server Management Studio
The following process occurs during a federated backup:
1. The NetWorker server starts the nsrsqlsv program in the active node of the Windows cluster (called the coordinator process).
2. The coordinator process queries the SQL Server and detects the Backup Preference and priority from the Availability group, and starts the worker process on the detected preferred node.
3. The backup is configured with and stored under the Windows cluster name on the Availability Group.
During a traditional recovery operation that uses a storage node without the Client Direct feature, process interactions occur between the NetWorker client (that is, NMM), the NetWorker server, and the SQL Server.
The following process occurs in a traditional recovery operation:
1. The nsrsqlrc program starts the recovery.
2. The NetWorker XBSA API translates the object names that NMM requests into a format that NetWorker understands and forwards the translated object names to the NetWorker server nsrd service.
3. The nsrmmd media service contacts the nsrmmdbd service to search the NetWorker server’s media database for the volumes that contain the requested objects.
4. After the media is mounted, the nsrmmd program sends the data through the NetWorker XBSA API to nsrsqlrc, which then sends data to the SQL Server.

[@damodarreddy8806]

Thanks for the video ....expecting videos on all modules of networker

[@crazyrov]

Gradually :)

[@Ofcourseitsbeared]

Thanks for Sharing again.. Correct no one want's to go depth knowledge .. everybody want's how to configure and clear interview..

[@crazyrov]

Thanks for you comment ! There are techies who come with varied expectations so just trying to make sure everyone gets the best from our videos.

[@TZAK4u]

Thanks again for sharing such great content

[@crazyrov]

Thanks for watching!

[@hendbensaad9331]

Thank you for the great content 😊 we expect videos for the case of postgres DB and what are the involved modules

[@crazyrov]

As soon as possible!

[@govindkonari5741]

Hai sir, tq u for shareing your knowledge ,can you please upload the file level recovery through NMC

[@crazyrov]

Hi Govind ! From FS backups or VM image level backups?

[@GovindaKonari-v3u]

FS backups@@crazyrov

[@GovindaKonari-v3u]

Hai sir, can you please upload the FS level recovery

[@aashortclips2427]

Hi
Can you pls let me know how can we identify the DB recovery model before we configure them for networker backups .. is there a way we can able to trace that information form networker server side or need to gather it form SQL DBAs

[@crazyrov]

Hi Bhargav ! Thanks for your comment. There is no option to check this from the NetWorker end, all this configuration is on the SQL and you will need SQL Management Studio(SMS) to change these configurations.