EMC Solutions for NetWorker Procedure Generator

Topic
SQL Client Configuration

Selections Made
SQL Server: Stand Alone SQL Server Choose Databases to Backup: All Databases Instance: Default Configure Filesystem Backups?: Yes Backup Data to Advanced File Type Device?: No Backup Data to Dedicated Storage Node?: No Configure Cloning?: Yes Backup Data to Storage Node?: No

Procedure Generated on: 1/28/2012 8:29:47 PM

REPORTING PROBLEMS:

If you find any errors in this procedure or have comments regarding this application, please send email to PG-Feedback@emc.com.

Table of Contents

Security Requirements for SQL Server Module Backups .............................................................................. 3 Licensing Requirements for a Non-clustered SQL Server ............................................................................. 3 Client Connection licenses ........................................................................................................................ 3 NetWorker Module for SQL Licenses ........................................................................................................ 4 Configure a Backup Pool ............................................................................................................................... 4 Configure the Clone Pool .............................................................................................................................. 5 Configure a Schedule .................................................................................................................................... 5 Create a Schedule for Filesystem Backups.................................................................................................... 6 Configure a Group for filesystem Backup with Cloning ................................................................................ 6 Configure a Group for SQL Data Backup with Cloning .................................................................................. 7 Configure a Directive to Exclude Microsoft SQL Databases ......................................................................... 7 Configure the Client Resource for SQL Backups ........................................................................................... 8 Configure SQL Clients for Filesystem Backups .............................................................................................. 9

Security Requirements for SQL Server Module Backups

This module requires that the proper privileges are granted to the module processes. Microsoft SQL Server imposes the following requirements on third-party backup products: The logon account that the third-party backup process uses to connect to SQL Server must be granted the SQL Server system administrator (sysadmin) role. The Windows logon account under which the third-party backup process is running must be granted the SQL Server sysadmin role in order to open a shared memory handle when initializing the Microsoft Virtual Device Interface (VDI). This module imposes the following requirements: When using the nsrsqlsv and nsrsqlrc commands, the Windows logon account must be granted the SQL Server sysadmin role. NetWorker User for SQL Server must be a member of the local Backup Operators group. NetWorker User for SQL Server must be a member of the local Administrators group.

Licensing Requirements for a Non-clustered SQL Server

Client Connection licenses

One Client Connection license is required for each physical SQL server. To determine if additional licenses are required to backup a new SQL client: 1. At the NetWorker server prompt, type: nsrlic v 2. At the beginning of the output, make note of the number of remaining licenses underlined below: connecting to cdcsdunndl1c.corp.emc.com ... 12116:nsrlic: License Summary: 66441:nsrlic: 64047:nsrlic: 66442:nsrlic: nsrlic: nsrlic: Available: sv=12, virt=0, ndmp=0 Borrowed: sv_borrowed=0 Remaining: sv=11, virt=0, ndmp=0

Connected Clients: (1) cdcsdunndl1c.corp.emc.com

STANDARD CLIENT LICENSES

Available: 12 Used: 1 Loaned to Virtual: 0 Remaining: 11 3. If required, contact EMC Licensing to obtain additional Client Connection licenses. 4. If you are unable to obtain a required license, at the NetWorker server prompt, type the following temp enabler for an additional 5 client connection license: nsrcap c 888a0a-4e74cd-e7fbd2
Note: If you add a temporary Client Connection license to the NetWorker server, contact EMC

Licensing within 30 days to obtain a permanent authorized enabler code.

NetWorker Module for SQL Licenses

One NetWorker Module for SQL license is required for each physical SQL Server. To determine if additional licenses are required to backup a new SQL client: 1. At the NetWorker server prompt, type: nsrlic v 2. In Application Licenses of the nsrlic output, make note of the number of remaining licenses in NetWorker Module for SQL underlined below: APPLICATION LICENSES NetWorker Module for Microsoft SQL Server Available: 1 Used: 0 Remaining: 1 Connected Clients
Note: If NetWorker Module for SQL licenses are not added to the NetWorker server, there will not be

a reference to it in the Application Licenses section. 3. If you are unable to obtain a required license, at the NetWorker server prompt, type the following temp enabler: nsrcap c 74f1f6-3e80b7-4d7d3e
Note: If you add a temporary NetWorker Module for SQL license to the NetWorker server, contact

EMC Licensing within 30 days to obtain a permanent authorized enabler code

Configure a Backup Pool

To configure a backup pool: 1. Click Media, and select Media Pools.

2. Right-click the pool defined for client backups and select Properties. Right-click the Media Pool window, and select New if the pool is not yet created. 3. In the Name field, type the name of the pool, and define a Label Template in Configuration if required. 4. Verify that Enabled is selected in Configuration, and that Pool Type is defined as Backup. 5. In the Data Source section, select the group that is going to backup your SQL Server. 6. Click OK.

Configure the Clone Pool

To configure the clone pool: 1. If the clone pool is already configured, skip to Configure the Group, Client and Backup Pool section. 2. Click Media, and select Media Pools. 3. Right-click in the Media Pool window, and select New. In the Name field, type the name of the pool, and define a Label Template in Configuration if required. 4. Ensure that Enabled is selected in Configuration, and the Pool Type is defined as Backup Clone. 5. Click the Configuration tab. 6. In Configuration, click to de-select Store Index Entries. 7. Click OK.

Configure a Schedule

To configure a schedule for database backups: 1. Click the Configuration tab. 2. Click Schedules. 3. Right-click in the Schedules window, and select New. 4. In the Name field, type a name for this schedule. 5. In the Period field, select a Week or Month: Select Week to create a weekly backup schedule. For example, if a full backup for a Friday is selected, every Friday a full backup is taken. Select Month to create a monthly schedule. For example, if a full backup for the first of the month is selected, every month a full backup is taken on the first of the month.

6. Select a backup level for each day in the weekly or monthly period. 7. Select a day.

8. Right-click and select a backup level from the Set Level menu. 9. If required, select an override backup level for any day. An override occurs once only for the selected day: a. Select a day. b. Right-click to select a backup level from the Override Level menu. 10. Click OK.

Create a Schedule for Filesystem Backups

To configure a schedule for filesystem backups of the SQL Server: 1. Click the Configuration tab. 2. Click Schedules. 3. Right-click in the Schedules window, and select New. 4. In the Name field, type a name for this schedule. 5. In the Period field, select a Week or Month: Select Week to create a weekly backup schedule. For example, if a full backup for a Friday is selected, every Friday a full backup is taken. Select Month to create a monthly schedule. For example, if a full backup for the first of the month is selected, every month a full backup is taken on the first of the month.

6. Select a backup level for each day in the weekly or monthly period. 7. Select a day. 8. Right-click to select a backup level from the Set Level menu. 9. If required, select an override backup level for any day. An override occurs once only for the selected day. a. Select a day. b. Right-click to select a backup level from the Override Level menu. 10. Click OK.

Configure a Group for filesystem Backup with Cloning

To configure a group for filesystem backup with cloning: 1. Click Configuration.

2. Expand Groups. 3. Right-click the group with the SQL Server physical node clients, and select Properties. Right-click Groups, and select New if the group is not yet created. 4. In the Name field, type the name of the group. 5. In Setup, define the time the group will start in the Start Time field.
Note: The Start Time field is based on a 24 hour clock.

6. Select Enabled in the Autostart field. 7. Ensure that Clones is enabled and that the correct Clone Pool is defined for this group. 8. Click the Advanced tab, make adjustments to resources as required, and set the Schedule field to the schedule to be used for the SQL Server filesystem backup. 9. Click OK.

Configure a Group for SQL Data Backup with Cloning

To configure a group for SQL data backup with cloning: 10. Right-click the group with the SQL virtual node clients, and select Properties. Right-click Groups, and select New if the group is not yet created. 11. In the Name field, type the name of the group. 12. In Setup, define the time the group will start in the Start Time field.
Note: The Start Time is based on a 24 hour clock and the time should be set to avoid overlap with

the group defined for filesystem backups to avoid disk contention. 13. Select Enabled from the Autostart field. 14. Ensure that Clones is enabled, and that the correct Clone Pool is defined for this group. 15. Click the Advanced tab. 16. In the Schedule field, select the schedule to be used for the SQL data backup. 17. Set Client Retries to 0. 18. Click OK.

Configure a Directive to Exclude Microsoft SQL Databases

A directive is configured to exclude the Microsoft SQL databases, and the database/log file directories during a filesystem backup.

To configure a directive: 1. In the Configuration window, click Directives. 2. Right-click in the Directives window, and select New. 3. In the Name field, type SQL Directive. 4. In the Directive field, type the following: << "C:" >> skip: *.* <<"C:\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL\DATA">> skip: *.*
Note: If the path for the SQL server is different than C:\Program Files\Microsoft SQL

Server\MSSQL\Data, change the path name in the directive. 5. Click OK.

Configure the Client Resource for SQL Backups

To configure the Client resource for non-clustered SQL Server backups: 1. Right-click the client defined for the SQL Server backups and select Properties. If the client is not yet created, right-click in the Client window, and select New. 2. In the Name field, type the short name of the client. 3 In the Save Set field, type: MSSQL: 3. Ensure that the correct group has been selected in the Groups section. 4. Click the Apps and Modules tab. 5. In the Remote User field, leave this blank as this is not required for non-clustered SQL Server backups 6. In the Password field, leave this blank. 7. In the Backup Command field, type: nsrsqlsv 8. Click the Globals (1 of 2) tab. 9. Verify that the Alias field has the short name of the client and the fqdn of the client listed on separate lines. 10. Click the Globals (2 of 2) tab. 11. In the Storage Nodes field, type the name of the Storage Node host.
Note: The Storage Nodes field defines the host to which the backup data will be written.

The following lists examples of the mandatory Storage Node attribute entries for the SQL Client resource. If the backup saves to a device on the: NetWorker server, always use nsrserverhost (reserved word).

Remote storage node, use the hostname of the remote storage node. For example, stornode01. SQL Client resource, use the hostname of the SQL client. For example, sqlclient01.

12. In the Clone Storage Nodes field, type the name of the host.
Note: The Clone Storage Nodes field defines the host which clone data will be written.

13. In the Recover Storage Nodes field, type the name of the host.
Note: The Recover Storage Nodes field defines the host from which backup data will be read during

the clone operation or during recover operation. 14. Click OK.

Configure SQL Clients for Filesystem Backups

To configure SQL clients for filesystem backups: 1. Right-click the client defined for the filesystem backups of the SQL server and select Properties. Right-click in the Client window, and select New if the client is not yet defined. 2. In the Name field, type the short name of the client. 3. Verify that the correct group is selected in Groups. 4. In the Directive field, select SQL Directive. 5. In the Save Set field specify ALL. This backs up the local drives for the physical node as well as the VSS savesets. 6. Click the Globals (1 of 2) tab. 7. Verify that the Alias field has the short name of the client, and the fqdn of the client listed on separate lines. 8. Click the Globals (2 of 2) tab. 9. In the Storage Nodes field, type the name of the storage node host.
Note: The Storage Nodes field defines the host to which the backup data will be written.

The following lists examples of the mandatory Storage Node attribute entries for the SQL Client resource. If the backup saves to a device on the: NetWorker server, always use nsrserverhost (reserved word). Remote storage node, use the hostname of the remote storage node. For example, stornode01. SQL Client resource, use the hostname of the SQL client. For example, sqlclient01.

10. In the Clone Storage Nodes field, type the name of the host.
Note: The Clone Storage Nodes field defines the host to which clone data will be written.

11. In the Recover Storage Nodes field, type the name of the host.

Note: The Recover Storage Nodes field defines the host from which backup data will be read during

the clone operation or during recover operation. 12. Click OK.