NMM for SQL VDI , 3

Introduction to using NMM with Virtual Device Interface

You can use the EMC ® NetWorker® Module for Microsoft (NMM ) release 3.0 SP1 software to backup and recover SQL Server data. NMM utilizes Virtual Device Interface (VDI), an API provided by Microsoft SQL Server, to integrate with the SQL Server and enable the NetWorker software to back up and recover SQL Server data.

Microsoft SQL Server VDI environment:

◆ “Backup environments”

◆ “Recovery environments”

◆ “Cluster environments”

“Backup environments”

– Non-federated backup environment (traditional backup)

-Federated backup environment

· Non-federated backup environment (traditional backup)

The process interactions between the NetWorker client (NMM), the NetWorker server, and the SQL Server during a non-federated or traditional backup:

The following process occurs in a non-federated or traditional backup:

1. The nsrd program starts the backup on the NetWorker server.

2. The savegrp program executes the NMM backup command (nsrsqlsv) on the client instead of performing a standard NetWorker save.

3. 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 NetWorker server software performs all scheduling and storage management tasks.

· Federated backup environment:

Federated backups are only available for SQL Server 2012.

The process interactions between the NetWorker client (NMM), the NetWorker server, and the SQL Server during a federated backup.

During a federated backup, the save group command starts and creates the process in the active node of the Windows cluster. When the backup is started from the NetWorker server, a process called the master/co-ordination process calculates and detects the Backup Preference and priority from the Availability group, and starts the slave backup process in detected preferred node.

“Recovery environments”

The functional relationship between the NetWorker client (NMM), the NetWorker server, and the SQL Server during a traditional recovery operation.

1. The nsrsqlrc command starts the recovery.

2. The NetWorker XBSA API translates the object names requested by NMM into a format NetWorker understands, and forwards the translated object names to the NetWorker server nsrd service.

3. The media service, nsrmmd, starts the nsrmmdbd command to search the NetWorker server’s media database for the volumes that contain the objects requested.

4. After the media is mounted, the nsrmmd program sends the data through the NetWorker XBSA API to nsrsqlrc, which recovers the data to the SQL Server directories.

“Cluster environments”

NMM can back up or recover data exported by a SQL Server that is running as a virtual server in an WSFC cluster. NMM uses the virtual server name to perform the following tasks:

◆ Connect to the appropriate SQL Server instance.

◆ Initialize the SQL Server VDI to accept data from or deliver data to the appropriate SQL Server in the cluster.

◆ Create entries in the NetWorker client file index.

//WSFC cluster# A Windows Server Failover Clustering (WSFC) cluster is a group of independent servers that work together to increase the availability of applications and services.

How NMM detects SQL Server instances

NMM automatically detects all the SQL Servers in a WSFC cluster, including the virtu

servers but only on the active nodes, whenever:

◆ The NetWorker User for SQL Server program is started.

◆ The Select SQL Instance option is selected.

◆ A backup or recovery is started.

The following commands are used to perform backup and recovery:

nsrsqlsv backs up the specified SQL Server data objects.

nsrsqlrc recovers the specified SQL Server data objects.

nwmssql starts the GUI.

nsrsqlsv backs up the specified SQL Server data objects.

• Full backup of the database to a specified NetWorker server:

nsrsqlsv -s server -c client -b poolname -l full dbname

nsrsqlsv -s swraj -c SQL2012RC1Named -b Sub9VDI -l full 5

•Differential backup:

nsrsqlsv -s NetWorker_server_name -l diff my_database

• Incremental backup:

nsrsqlsv -s NetWorker_server_name -l incr my_database

nsrsqlrc recovers the specified SQL Server data objects.

The following example copies the database Sales from the SQL Server prod-sql, instance Venus, to the SQL Server test-sql, instance Mars:

nsrsqlrc -s nw_server.company.com -c prod-sql.company.com -d MSSQL$MARS: -$ MSSQL$VENUS: -d “MSSQL$MARS:Sales” -C” ‘Sales ‘=’D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataSales.mdf’, ‘Sales_log’=’D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataSales_log.ldf’" -t "Fri Dec 01 08:01:19 2006" "MSSQL$VENUS:Sales"

Note#If the -$ switch is used, and no instance is named, for example " -$ MSSQL:" , or the -$ switch is omitted, the default instance is used

nwmssql starts the GUI.

nwmssql [-t] -s NetWorker_server_name -b browse_time

Recovering SQL Server:

You must complete the required steps to recover the SQL Server.

1. Reinstall the operating system.

2. Reinstall the NetWorker software.

• If the computer that failed is the NetWorker server, reinstall the NetWorker server.

• If the computer that failed is a NetWorker client, reinstall the NetWorker client.

3. Recover or reinstall the SQL Server software. To determine if you need to reinstall the SQL Server,

4. Start the SQL Server.

5. When recovery is started, in the NetWorker User for SQL Server GUI, select the replace option to restore the SQL Server master database and the msdb database.

6. Recover the other SQL application databases.

NMM does not support snapshot backups or recoveries of the SQL Server master database. Recover from a traditional backup of the master system database during a disaster recovery.

◆ Database restore order—

When recovering a complete backup of all databases or when recovering certain system databases, the recovery must occur in a specific order. If system databases are present in the recovery list, NMM ensures that the recovery order follows SQL Server procedures as follows:

a. The master database is always recovered first and this ensures that metadata present in the master database is correct for all subsequent restored databases.

b. The msdb database is always recovered after the master database and before all other databases. This ensures that scheduling and other system data present in the msdb database are correct for all subsequent restored databases.

c. The model database is always recovered after the master and the msdb databases, and before all other databases. This ensures that the database configuration is correct for all subsequent databases.

Advertisements

About Ahmad Sabry ElGendi

https://www.linkedin.com/pub/ahmad-elgendi/94/223/559
This entry was posted in E20-597. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s