To perform federated backups using NMM, you must create a client resource for the Windows cluster name from which backup is performed, and dummy client resources for the other participating nodes in the cluster.
To create a client resource, you can use either of the following methods from the NMC:
l The Client Backup Configuration wizard
l The Client Properties dialog box
Complete the following tasks before creating client resources:
1. Create a protection group - The type of group that you create depends on the actions that you plan to perform for the group.
2. Create a policy - When you create a policy, you specify the name and notification settings for the policy.
3. Within the policy, create a workflow - When you create a workflow, you specify the name of the workflow, the schedule for running the workflow, notification settings for the workflow, and the protection group to which the workflow applies.
4. Create one or more actions for the workflow.
The NetWorker Administration Guide provides information about data protection policies.
By using the Client Backup Configuration wizard
The Client Backup Configuration wizard simplifies the configuration of client resources for scheduled backup for SQL Server 2012 or later backups in a Windows cluster
environment. The Client Backup Configuration wizard creates dummy client resources for participating cluster nodes.
The NetWorker Administration Guide and the NetWorker Module for Microsoft Administration Guide provide details about data protection policy. Review the information in these guides before creating the client resources.
To use the Client Backup Configuration wizard in a federated environment, ensure that the active node of the Windows cluster contains a SQL Server 2012 or later instance.
Follow the steps provided in the Scheduled Backups chapter to run the Client Backup Configuration wizard.
Manually creating a client resource by using the Client Properties dialog box
When creating client resources manually, ensure that a client resource is created for Windows cluster name, and dummy client resources are created for the other
Federated Backup
Performing federated backups 73
participating nodes in the cluster. Do not assign a group for the dummy clients. Not creating dummy clients causes the backup to fail.
In the procedure provided in this section for creating a client resource, the AG name is AG1. AG1 is created out of the default instance using Windows Cluster named
MSCSALWAYSON.nmmdev.com. The cluster nodes for AG1 are named MW2K8X64SQL1 and MW2K8X64SQL2.
Click the question mark icon at the bottom left of each page for details about each field in the page.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. From the File menu, select New.
4. Click the General tab.
5. In the Name field, the Windows Server cluster name appears.
6. In the Comment field, type a description.
If you are creating multiple client resources for the same NetWorker client host computer, use this field to differentiate the purpose of each resource.
7. In the Browse Policy field, select a browse policy from the list.
The browse policy determines the time period during which the rolled-over data is available for quick access.
8. In the Retention Policy field, select a retention policy from the list.
The retention policy determines the time period during which the rolled-over data is available, although not necessarily quickly.
9. Select the Scheduled Backups field.
10.In the Save Set field, specify the components to be backed up.
Table 20 Save Sets
Save set Description
MSSQL#AG1 AlwaysOn Group referring SQL default instance
MSSQL#AG1:Database1 AlwaysOn Group referring SQL default instance MSSQL$NamedInstance#AG2 AlwaysOn Group referring SQL named instance MSSQL$NamedInstance#AG2:Database2 AlwaysOn Group referring SQL named instance
11.Select the appropriate option in the Protection group list field.
If client resources for the same NMM host are added to different backup groups, ensure that the Start Time field for each backup group is spaced such that the backups for the host’s client resources do not overlap.
12.For the Schedule field, select a backup schedule.
13.Click the Apps & Modules tab.
Federated Backup
14.Type the remote user name and password in the Remote user and Password fields respectively.
15.In the Backup command field, type the following command:
nsrsqlsv.exe
where server name is the Windows cluster name and for which Netbios name or FQDN must be used.
16.In the Application Information field, type the required value.
The simple database is skipped when the NSR_SKIP_SIMPLE_DB environmental variable is set to TRUE on the client to skip the backup for simple databases.
Otherwise, the incremental backup request is promoted to full.
17.Under Deduplication, select Data Domain backup, for data deduplication by using a Data Domain device.
18.Click the Globals (1 of 2) tab.
19.In the Remote Access field, enter the user IDs or hostnames of other clients for the Remote Access field. This grants copy restore type permission to the hosts, which enables the named hosts to access the NetWorker server and receive directed recover data. If this field is left empty, only administrators and users logged on to the SQL Server host have access.
20.In the Aliases field, type all known aliases for the SQL Server host in the Aliases field on the Preference tab, as in the following example:
marsmars.emc.com
Include both the DNS short name and long name for the SQL Server host.
21.Click OK.
22.Run the backup from the save group.
Federated Backup
Manually creating a client resource by using the Client Properties dialog box 75
Federated Backup
CHAPTER 6 Data Recovery
This chapter includes the following sections:
l Overview... 78
l Prerequisites...78
l Performing SQL Server 2012 or later recovery... 79
l From the Microsoft SQL Server Management Studio GUI... 80
l From the NetWorker User for SQL Server GUI...84
l Performing recovery of federated backups...111
Data Recovery 77
Overview
You can recover SQL Server data by using:
l NetWorker User for SQL Server GUI
l NetWorker SQL Adhoc Plugin
l nsrsqlrc command Note
You cannot:
l Recover SQL Server data by using the NetWorker Management Console.
l Recover data that was backed up by third-party vendors
l Select SQL Server AlwaysOn Availability Group (AAG) databases in the NetWorker User for SQL Server GUI or the Recover tab in the SSMS plugin for recovery. All AAG databases are unavailable.
To rebuild system databases for SQL Servers by using the Command Prompt, refer to the information provided at the following link: http://msdn.microsoft.com/en-us/library/
ms144259(v=sql.100).aspx
Prerequisites
Review the prerequisites in this section before performing a recovery.
l Read the SQL Server product documentation to understand the limitations associated with recover types on the various SQL Server versions.
l Ensure that the NetWorker server software is running on the appropriate host and the NetWorker Remote Exec Service is started on the SQL Server host.
l Restoring the SQL master database requires a restart of the SQL instance in single user mode followed by logging on to that instance. Single user mode only allows one administrator to log on. Ensure that no other applications or services are waiting for or attempting to log on to the SQL instance.
l If a backup of a database is in progress, wait for it to finish. SQL Server will not restore a database while another database backup is in progress.
l If a SQL Server startup is in progress, wait for it to finish before starting a restore operation.
l Review the ERRORLOG file to determine if a database is currently being recovered or search the ERRORLOG file for the “Recovery complete” string.
If the nsrsqlrc program is started while the SQL Server is recovering databases, the following error message appears:
Could not find database ID. Database may not be activated yet or may be in transition.
l Ensure that all database users are logged off the database. A restore fails if other users try to use the database during the restore operation.
Data Recovery
Note
For the supported SQL Server versions, if the primary filegroup is not under restore, then the online (piecemeal) restore functionality allows user access to a database while backup or restore is in progress.
l Recovering filestream data of SQL Server 2008 or later, requires that the SQL Server filestream feature be enabled on the recovery instance.
l For piecemeal restore, SQL Server Enterprise Edition databases consisting of multiple filegroups can be restored in stages with piecemeal restore.
With piecemeal restore, the primary filegroup must be part of each piecemeal restore.
The database remains offline during the restore process. Piecemeal restore is a multistage process that restores a database to itself or to another location. The initial stage must include the primary filegroup and optionally other filegroups. Once the primary filegroup is restored, you can bring the database online and continue restoring the remaining filegroups in subsequent stages.