netapp snapcenter software with microsoft sql … snapcenter software with microsoft sql server...

Technical Report

NetApp SnapCenter Software with Microsoft SQL Server Plug-in February 2017

2 <Insert Technical Report Title Here> <Insert Document Classification Label Here>

TABLE OF CONTENTS

1 Introduction .......................................................................................................................................... 4 1.1 SQL Server Plug-in .......................................................................................................................................... 4 1.2 Prerequisites .................................................................................................................................................... 4

2 LAB Environment ................................................................................................................................. 4

3 Lab Activities ........................................................................................................................................ 6

4 Connect to SnapCenter and Tour the Interface ................................................................................ 7 4.1 Dashboard and Reports ................................................................................................................................... 9

5 Perform a Backup .............................................................................................................................. 11

6 Perform a VMDK backup. ............................................................................................................... 13 6.1 Add the Nested SQL Server Host .................................................................................................................. 13 6.2 Discover and protect Database ...................................................................................................................... 16 6.3 Perform a Backup .......................................................................................................................................... 19

7 Backup Multiple Databases on a Single Volume. ......................................................................... 20 7.1 Create a Policy ............................................................................................................................................... 20 7.2 Create a Resource Group .............................................................................................................................. 23 7.3 Perform a Backup .......................................................................................................................................... 26

8 Clone from a Backup ......................................................................................................................... 29 8.1 Verify SQL Server Configuration .................................................................................................................... 29 8.2 Perform the cloning operation ........................................................................................................................ 29 8.3 Verify Existance of new database clone. ....................................................................................................... 33

9 Clone Lifecycle ................................................................................................................................... 35 9.1 Verify SQL Server Configuration .................................................................................................................... 35 9.2 Prepare new host ........................................................................................................................................... 36 9.3 Perform the cloning ........................................................................................................................................ 41 9.4 Verify Existance of new database clone. ....................................................................................................... 45 9.5 Clean up / Delete Clone (Optional Activity) .................................................................................................... 46

10 Restore a Deleted Database .............................................................................................................. 47 10.1 Delete a Database ......................................................................................................................................... 47 10.2 Restore Deleted Database ............................................................................................................................. 51 10.3 Verify Existance of restored database. .......................................................................................................... 52


Appendixes ............................................................................................................................................... 54

References ................................................................................................................................................ 54

Version History ......................................................................................................................................... 54


1 Introduction NetApp® SnapCenter software enables you to centralize data protection and clone management while offering RBAC and a single GUI across all of your application environments. NetApp SnapCenter software delivers a unifed, scalable platform and plug-in suite for application consistent data protection and clone management. Enterprises can empower application and database administrators to self-manage their own data protection and copies. This lab introduces the SnapCenter Plug-in for Microsoft SQL Server, and highlights the key features.

1.1 SQL Server Plug-in The Plug-in for SQL Server integrates with Microsoft SQL Server on the Windows host, and with NetApp Snapshot copy technology on the storage system. To work with the Plug-in for SQL Server, you use the SnapCenter interface.

The Plug-in for SQL Server includes these major features:

• Unified product user interface powered by SnapCenter — The SnapCenter interface provides you with standardization and consistency across plug-ins and environments. The SnapCenter interface enables you to complete consistent backup and restore processes across plug-ins, use centralized reporting, use at-a-glance Dashboard views, set up role-based access control (RBAC), and monitor jobs across all plug-ins. SnapCenter also offers centralized scheduling and policy management to support backup and clone operations.

• Automated central administration — You can schedule routine SQL Server database backups, configure policy-based backup retention, and set up point-in-time and up-to-the-minute restores. You can also proactively monitor your SQL Server environment with periodic email alerts.

• Nondisruptive NetApp Snapshot copy technology — The Plug-in for SQL Server uses NetApp Snapshot copy technology with the NetApp SnapCenter Plug-in for Microsoft Windows. This enables you to back up databases in seconds and restore them quickly without taking SQL offline. Snapshot copies consume minimal storage space.

• Integration with the Microsoft Volume Shadow Copy Service (VSS) — The integration with VSS ensures that write requests are frozen and write caches are flushed before you make backup copies.

1.2 Prerequisites This lab assumes minimal prior experience with NetApp products, and a basic understanding of Microsoft Windows and SQL Server products.

2 LAB Environment There are several Microsoft SQL Servers along with a SAN connection to the in-lab clustered Data ONTAP storage virtual machines. The servers will make use of the NetApp SnapCenter Plug-in Package for Windows to demonstrate the various options available for SQL Server database backup and clone management.

The use case scenario in this lab includes a mock company which has datacenters in LA and NYC. There is a NetApp FlexVol volume that serves as storage for databases in two large retail stores in LA and NYC. They are replicated to another location for archival and disaster recovery purposes. There is also a dedicated database server and FlexVol for a warehouse in LA.

Additionally, the scenario includes a FlexVol that hosts database instances for five other retail locations: Dallas, Idaho, RTP, Seattle, and SJC along with an additional SQL Server Instance residing locally on a virtual machine.


Table of Systems Host Name Operating System Role/Function IP Address

jumphost Windows Server 2012 R2 primary desktop entry point for lab 192.168.0.5

dc1 Windows Server 2008 R2 Active Directory / DNS 192.168.0.253

vc1 Windows Server 2012 R2 vCenter/VSC server 192.168.0.31

snapctr Windows Server 2012 R2 SnapCenter Enterprise Server 192.168.0.75

sql1 Windows Server 2012 R2 Microsoft SQL Server 1 192.168.0.91

sql2 Windows Server 2012 R2 Microsoft SQL Server 2 192.168.0.92

sql-dev Windows Server 2012 R2 Microsoft SQL Server Dev 192.168.0.94

sql-qa Windows Server 2012 R2 Microsoft SQL Server QA 192.168.0.93

sql-nested Windows Server 2012 R2 Microsoft SQL Server on VMDK 192.168.0.95

Storage Systems Host Name Operating System Role/Function IP Address

cluster2 clustered Data ONTAP 8.x cluster 192.168.0.102

cluster2-01 clustered Data ONTAP 8.x cluster 2 node 1 192.168.0.121

cluster2-02 clustered Data ONTAP 8.x cluster 2 node 2 192.168.0.122

svm-sql Storage Virtual Machine for Production SVM mgmt LIF 192.168.0.139

svm-sql SVM iSCSI LIF Cluster 2 Node 1 iSCSI LIF 192.168.0.131

svm-sql SVM iSCSI LIF Cluster 2 Node 1 iSCSI LIF 192.168.0.132

svm-sql-dr Storage Virtual Machine for Production SVM mgmt LIF 192.168.0.139


Host Name Operating System Role/Function IP Address

svm-sql2 Storage Virtual Machine for Dev and QA and SnapMirror target for Prod

SVM mgmt LIF 192.168.0.149

svm-sql-dr Storage Virtual Machine for Dev and QA and SnapMirror target for Prod

SVM mgmt LIF 192.168.0.159

svm-vmware SVM for running datastore for VMware SVM mgmt LIF 192.168.0.173

Database Information Host Name DB Version Instance(s) Database(s)

snapctr MySQL Server 5.7 N/A NSM

sql1 SQL Server 2016 MSSQLSERVER DallasRetail, IdahoRetail, LARetail, NYCRetail, RTPRetail, SeattleRetail, SJCRetail

sql2 SQL Server 2016 MSSQLSERVER LAWarehouse

sql-dev SQL Server 2016 MSSQLSERVER NONE

sql-qa SQL Server 2016 MSSQLSERVER NONE

sql-nested SQL Server 2014 MSSQLSERVER SQLN-AW

User IDs and Passwords User Purpose User Name Password

Cluster Administrator Account admin Netapp1!

SVM administrator vsadmin Netapp1!

SnapCenter Administrator demo\scadmin Netapp1!

SnapCenter User for SQL demo\sql_user Netapp1!

Root user for SnapCenter Database (MySQL) root Netapp1!

3 Lab Activities This lab contains the following activities and tasks: 1. Connect to SnapCenter GUI and Tour the Interface

2. Perform a Backup.

3. Perform a VMDK backup.

4. Backup Multiple Databases on a Single Volume.

5. Clone from Backup.

6. Clone Lifecycle.

7. Restore a Deleted Database.


4 Connect to SnapCenter and Tour the Interface NetApp SnapCenter Software is designed to allow enterprises to leverage a simple and scalable interface to coordinate and manage data protection across multiple applications and databases. This activity will serve as an introductory tour in navigating this very powerful yet simple user interface (UI). You will explore the layout of the UI and examine areas of adminstrative configuration options.

1. From the Jumphost, open the SnapCenter GUI (double click the desktop shortcut). 2. Enter the login credentials - username: demo\scadmin, password: Netapp1!.

Note: If a user is assigned multiple roles a selection box will be displayed on the login screen allowing the user a choice of which role to choose.

3. When initially logging into SnapCenter you will be presented with the Getting Started with SnapCenter screen. Displayed here are the typical workflows, and their “Getting Started” videos. You can return to this at any time by selecting Dashboard on the left hand navigation bar, then “Getting Started”.


4. After you have logged in, the banner at the top right shows the user you have logged in as (demo \scadmin) along with the selected role (SnapCenterAdmin). You can refer to this section to verify which user you are logged into SnapCenter as and which role that user has been assigned.

5. The following table describes the menu on the left of the graphical interface. Menu Item Description

or

This button displays or reveals the text next to the icons in the left hand navigation bar. If the text is hidden the other icons below will show the icon but not the text.

This page displays a single pane overview of the SnapCenter environment including host and job status along with protection status of data sources. It can also be customized to specific user needs. Direct access to reports is provided by clicking on one of the graphs. Access to the getting started workflows and videos is also provided in the Getting Started tab.

This page displays all of the resources (databases, availability groups, file systems, etc) that are managed in SnapCenter. From this page you can protect, clone, or restore resources or groups or resources.

This page contains the tools for monitoring jobs, viewing logs, viewing events, and viewing schedules.

This page provides Backup, Clone, Restore and Plug-in reports with the ability to specify period of time, host, dataset, or policy.

This page shows Servers, physical or virtual, that SnapCenter knows about for application/database protection. In this area you can also manage (create, delete, resize) LUNs attached to the hosts, create/delete shares, igroups, and/or iSCSI sessions.

This page enables you to add, modify, or delete storage systems connections, which enables SnapCenter to communicate with ONTAP SVMs.

This page covers SnapCenter’s global settings, policies, and Role-based Access Control including creation, modification and assignment of roles, and permissions to access specific resources. Plug-in updates can also be managed from this tab.

6. In the upper right center of the screen there are four icons. They are described below. Icon Description

This is the Show Notifications button. As SnapCenter runs operations it will display a pop up message in the bottom of the screen. Click this button to display the last message shown.


Icon Description

This is the Send Feedback button which lets you send feedback to the SnapCenter product team. This should be used for feedback about the product and NOT for support purposes.

This button will not work in the lab as no email tool is configured and SMTP ports are not open in the lab environment.

This is the About button, which tells you the version of SnapCenter in use

The ?, or the Help button, opens the contextual help

4.1 Dashboard and Reports Since the Dashboard provides an overview of the SnapCenter environment it can be customized to an individual user’s needs. The next few steps will walk you through how to modify the amount and type of information displayed in the Dashboard as well as how to use the graphs to get more details information and reports.

1. If you are not already there, on the left hand navigation bar click Dashboard. This defaults to the Status page.

2. If you wish to modify the graphs that you see, click the Modify button on the top right. Since you are logged on as a user with the SnapCenterAdmin role you can see all of the plug-ins available in SnapCenter. Don’t make any changes at this time and click OK to close.

3. Under the Status button there is a Plug-ins drop down box. From the Dropdown box select SnapCenter Plug-in for Microsoft SQL Server.

4. To see which data sources are protected, or more importantly are not protected, scroll the window down until the “Microsoft SQL Server Database Policy-Based Protection” graph is displayed. This chart is listing 2 backups as Unprotected, not Backed up, which means that these databases are protected by SnapCenter, but no backup of the database has occurred in selected interval (which by default is 7 days). There are also 5 databases that the graph reports as unprotected, not backups configured, which means that these databases are not protected, no policies are assigned, and the database is not backed up. You can click the “i” in the upper right of each graph to see a list of all of the possible status conditions.

5. To get more details about the information in the graph, click on the area in the chart above that is labeled Unprotected No Backups configured: 5


If you click most charts in the SnapCenter Dashboard, you are redirected to the “Reports” page in SnapCenter, where you can view more details about the selected graph.

Here is a listing of the unprotected databases that need to be configured for protection. In this case there are five. You will protect these databases as part of a lab exercise later in the guide.

Note: You can also go directly to the Reports page in SnapCenter, and view further information about Backups, Clones, Restores, and Plug-Ins.

6. You can export all reports in a variety of formats using the toolbar at the top of the page.

7. You can also filter reports using the right-hand toolbar to narrow results, then clicking Apply.


5 Perform a BackupThis SnapCenter lab has some hosts added with storage connections and policies already created. This is indicative of using a SnapCenter environment that is already setup and running. In this exercise you just need to select a resource and select Backup Now.

In the previous section you were logged into SnapCenter as demo\scadmin. The scadmin user is an administrative user with elevated permissions. To perform most of the steps in this lab you should use the sql_user account, which has a slightly more limited set of capabilities to better reflect what a DBA user would see.

1. If you are still logged into SnapCenter as demo\scadmin log out using the “Sign Out” button on the upper right.

2. Log into SnapCenter as demo\sql_user with password Netapp1! 3. From the left hand nav bar, click Resources. 4. The sql_user account has access to both the File Systems plug-in as well as the SQL Server Plug-in.

The File Systems view is shown in the initial resources view, so you will need to change the view to SQL Server. At the top of the page select Microsoft SQL Server from the drop-down menu.

5. This view defaults to the Database view, where you can see all of the databases that are known to SnapCenter. You can individually protect resources or you can protect resources as a group. This lab environment has a Resource Group already protected to backup the LARetail and NYCRetail databases. To see the existing Resource Groups, in the “View” field, click the dropdown arrow and select Resource Group.


6. In the list of Resource Groups select Large Market Retail. As mentioned the Large Market Retail Resource Group contains 2 databases – LARetail and NYCRetail. To backup both databases at once click BACKUP NOW.

7. In the “Backup” window, verify that the Resource Name value is Large Market Retail, and in the Policy field, verify that SQL Daily Full MirrorVault is selected.

8. Click Backup. 9. On the left hand navigation bar, go to the Monitor page and select the top job Backup of Resource

Group Large Market Retail with policy 'SQL Daily Full Mirror Vault’ and click Details.


Each of the steps can be expanded to reveal more detail of the backup job in progress.

10. When you are done reviewing the details, click Close.

6 Perform a VMDK backup. In order for SnapCenter to back up a SQL Server database on a VMDK, either the Virtual Storage console must be registered with SnapCenter or the SnapCenter Plug-in for vSphere (SCV) must be installed (not both). For purposes of this lab this we are using VSC and the registration has already been done.

6.1 Add the Nested SQL Server Host 1. If you are logged into SnapCenter as demo\scadmin, log out using the Sign Out button on the upper

right. 2. Log into SnapCenter as user demo\sql_user with password Netapp1! . 3. On the left hand navigation bar, go to the Hosts page. 4. Click Add .

5. In the “Add Host” window, enter the Host Name as sql-nested.demo.netapp.com . 6. Verify that Type field is set to Windows . 7. Verify that the Run as Name is set to Windows Admin . 8. Click NEXT .


9. On the “Discover Plug-ins” screen accept the defaults, and click NEXT . 10. On the “Select SnapCenter Plug-ins to Install” screen verify the following:

a. The Package drop-down box is set to SnapCenter Plug-ins Package 2.0 for Windows. b. The Microsoft Windows plug-in is checked. c. The Run As name is set to Windows Admin. d. The Microsoft SQL Server plug-in is checked. e. Click Next .

11. Verify the Summary information is correct, and click FINISH . 12. On the left hand navigation bar, go to the “Monitor” page, and verify the Add Host and Package

Installation jobs completed successfully for sql-nested.demo.netapp.com.

13. On the left hand navigation bar, go to the “Hosts” page and scroll down if necessary to view sqlnested-netapp.com.

14. With sql-nested.demo.netapp.com selected, click CONFIGURE PLUG-IN .


15. Click the Browse button, and click on the G:\ drive to select it. Click NEXT .

16. On the “Verification Server” screen, accept the defaults, and click NEXT . 17. On the “Summary” screen, verify the information, and click FINISH . 18. Verify the status of the host is “Running”. If you end up not getting the expected result, try also

pressing "Update ESX Info" to force the host status to update.


6.2 Discover and protect Database 1. On the left hand navigation bar, go to the Resources page and click on Microsoft SQL Server at the

top to select SQL Server objects. 2. Make sure View field is set to Database, and in the search bar type AW. 3. There should be a database named “SQLN-AW” in the listing, and a Overall status of Not Protected.

If you do not see this database, click Refresh Resources.

4. Select the SQLN-AW database. A protection wizard will begin. 5. On the Resource page of the protect wizard accept the defaults and click Next.

6. On the Policies page of the protect wizard you can select a policy or create a new one. Once a policy is selected you congifure the schedules to define when they run.


a. From the dropdown box notice that several policies already exist. You could choose an existing policy or multiple policies, but for this example you will select an existing policy.

b. From the dropdown box select the SQL Daily Full policy. c. The SQL Daily Full policy is now selected in the dropdown box. If desired you can select

additional policies or click the + button to create additional policies. For the lab purposes leave only the one policy selected.

7. Under the “Configure schedules for selected policies” heading the policy is listed with a button

under Configure Schedules. Click the button to specify when the schedule runs. 8. On the “Add schedules” page specify the start date and time. Optionally you can also set an

expiration date and time and set the interval for which the job will repeat. Accept the defaults and click OK.

9. Back in the Protection wizard, notice that there is now an applied schedule listed. Click NEXT.


10. This step allow the specification of whether verification of the backup will occur and when. For purposes of this exercise, just click NEXT.

11. On the “Notification” screen accept the defaults, and click NEXT.


12. Verify the information on the “Summary” screen, and click FINISH.

6.3 Perform a Backup If you have ben following along with the guide you have just added the SQL-Nested host and protected the SQLN-AW Database. This section picks up right where the last section left of.

1. As soon as the protection wizard completed you are taken to the topology view of the database. At this point you have setup the database to be protected, but no backups have yet been run..

2. Click Backup Now. 3. In the “Backup” window, verify that the “Resource Name” value is “SQLN-AW”, the “Policy” field is ,

SQL Daily Full.


4. Click Backup. You can monitor the Backup job status in the Job monitor. 5. On the left hand navigation bar, select the Monitor tab, and select the top detail, Backup of Resource

Group 'SQLN-AW' with policy 'SQL Daily Full' (click the name).

6. Click the Details button. 7. In the “Job Details” window, expand each available detail to view its status.

Note: In the lab environment the backup operations may take several minutes to complete. This is expected.

8. When you are done reviewing the details click Close.

7 Backup Multiple Databases on a Single Volume. SnapCenter communicates with both Storage Virtual Machine and the Microsoft SQL Servers to manage all NetApp backups, and to provide clone management. When multiple databases exist on a single volume, SnapCenter backs up all databases with one backup operation. In this lab activity you create a Resource Group, assign a policy, and run a backup for multiple databases that share a volume.

7.1 Create a Policy In the previous exercise you performed a backup of an existing Resource Group, which in turn had an existing policy attached. The next several exercises will take you through the steps of creating a policy and Resource Group then performing a backup.

A policy is a set of rules governing backup, clone, or verification jobs. Policy components include schedule, retention, and replication settings, and provide pre-script and post-script arguments and other settings. You must have one or more policies attached to a Resource Group before you can run backup, clone, or verification jobs. This activity shows you how to create a policy.


1. Verify that you are logged into SnapCenter as user demo\sql_user with password Netapp1!.

2. On the left hand navigation bar, select the Settings page. 3. Select Policies at the top and in the dropdown box below select Microsoft SQL Server.

4. Click New.

5. In the “New SQL Server Backup Policy” window, in the “Policy Name” field, enter SQL Daily Full Mirror 6. In the “Description” field, enter SQL Daily Full Backup Policy with Mirror Update .

7. Click Next . 8. Select Backup Type to be Full Backup.


9. Using the scroll bar on the right of the window, scroll down to the Schedule Frequency section and select Daily. Click Next.

10. In the Retention page perform the following steps: a. Leave the Log backup retention settings at their defaults. These are the retention settings used

for the SQL Log Backup Directory. The data stored in the Log Backup Directory is used for up to the minute restore operations, but the data contained within the Snapshot copy is incremental forever, so it is actually ideal to keep a low number of Snapshots even though you may think you need to set this higher.

b. Click On demand under the Full backup retention settings. These are the retention settings used when you perform an on demand backup

c. Click Daily under the Full backup retention settings. These are the retention settings for the daily schedule that will run at the scheduled time (which will be defined later). Change if desired.

d. Click Next. 11. In the secondary replication options page, check Update SnapMirror after creating a local Snapshot

copy. Click Next.


12. On the Script page you have the option of defining any type of script or command that can be run either before or after the backup job. Leave the defaults and click Next.

13. On the Verification page you can set options to perform SQL verification. Accept the defaults and click Next to continue.

14. Verify that the Summary is correct, and click Finish . 15. The new policy is now displayed.

7.2 Create a Resource Group 1. On the left hand navigation bar, select the Resources page. 2. Set the dropdown box at the top to Microsoft SQL Server.

3. Click New Resource Group at the right.

4. In the New Resource Group screen, enter MidMarket Retail in the Name field. Click Next.


5. Under Available Resources select Dallas Retail (SQL1) . This will select all other databases on the same volume. This is the default behavior as NetApp Snapshot copies are taken at the volume level, so automatically selecting databases that share a volume helps you be more efficient by minimizing the number of Snapshot copies taken on a volume.

6. Click the right >> button to add these databases to “Selected Resources”.


7. Click Next. 8. On the Policies screen, click the dropdown box and select SQL Daily Full Mirror

9. Under the “Configure schedules for selected policies” heading the policy is listed with a button

under Configure Schedules. Click the button to specify when the schedule runs. 10. On the “Add schedules” page specify the start date and time. Optionally you can also set an

expiration date and time and set the interval for which the job will repeat. Accept the defaults and click OK.


11. Note that there is now an applied schedule listed. Click Next. 12. Since no verification is done in this case click Next . 13. Since you are not using notification in this case click Next . 14. Verify if the Summary information is correct, and click Finish .

7.3 Perform a Backup 1. On the left hand navigation bar, select the Resources page

2. Set the dropdown box at the top to Microsoft SQL Server.

3. In the View dropdown, select Resource Group.

4. Select MIdMarket Retail.


5. Click Backup Now.

6. In the Backup window, verify the Resource Group is MidMarket Retail.

7. In the Policy field, select SQL Daily Full Mirror.

8. Click Backup.

9. On the left hand navigation bar, go to the Monitor page and select the top job, Backup of Resource Group MidMarket Retail with policy SQL Daily Full Mirror (click the name).

10. Click Details.

11. In the Job Details Window, expand each available detail to view its status.


12. Once the top level has a green check mark, click Close. (Mirror updates may continue in the background.)

13. On the left hand navigation bar, go to the Dashboard page.

14. Look at the tile titled Microsoft SQL Server Database Policy Based Protection, and notice the following:

While we started with seven unprotected SQL Server resources, we now have two protected resources as a result of the following actions: Section 5 – We backed up the Large Market Retail group which contained LARetail and NYCRetail databases. Section 6 – We backed up the MId Market Retail group which contained DallasRetail, IdahoRetail, RTPRetail, SeattleRetail, and SJCRetail databases.


8 Clone from a Backup NetApp FlexClone technology enables users to create space-efficient, point-in-time copies of a production database for testing or data extraction. Using NetApp SnapCenter Software, you can manage and deploy these backups to different managed MS SQL servers in the inventory. This lab activity demonstrates how to take a backup from production, and deploy it to a development server.Verify SQL Server Configuration

8.1 Verify SQL Server Configuration 1. On the jumphost, open SQL Server 2014 Management Studio. The icon is located in the start bar of

the jump host and looks like this:

2. Click Connect in the Object Explorer and select Database Engine.

3. In the Server name field, select SQL-Dev.

4. In the Authentication field, select Windows Authentication.

5. Click Connect.

6. Once the Server Instance connects, expand databases beneath this Instance.

Only two folders should display; System Databases and Database Snapshots. No databases should be visible. This shows that the SQL-Dev host currently does not have any databases present on the SQL Server. As part of the next task you will create a clone of a database and mount the clone on the SQL-Dev host.

8.2 Perform the cloning operation 1. Verify that you are logged into SnapCenter as user demo\sql_user with password Netapp1!.

2. On the left hand navigation bar, go to the Resources page.


3. At the top of the page make sure that Microsoft SQL Server is selected.

4. In the “View” field, click the dropdown arrow and select Database.

5. Click on the funnel at the right end of the search box.

6. In the SQL Server Host dropdown select SQL-Dev.

7. The only existing databases that should be displayed are the system databases. If no databases are visible, click the Refresh Resources button.

8. Now in the Host field, select All, and leave the Resource Type as Database.


9. In the list of Databases, select LARetail and select the the backup box under Vault Copies.

10. Select the backup listed and click the Clone button.

11. In the Clone Options window, Click the Clone server dropdown and select sql-dev.demo.netapp.com to clone from the vault backup.


12. In the Clone instance field select SQL-Dev.

13. In the Clone suffix field enter _Clone_Dev.

14. Select the Auto assign mount point radio button and Click Next.

15. On the Logs screen accept the defaults (none) and click Next.

16. On the Scripts screen accept the defaults and click Next.

17. On the Notifications screen accept the defaults and click Next.


18. Verify the Summary information is correct, and click Finish.

19. On the left hand navigation bar, go to the Monitor page, and verify the job Clone from backup ‘Large Market Retail_SQL1_...’ has a green checkmark indicating the clone process was successful.

Note: In the lab environment the clone operations may take several minutes to complete. This is expected.

8.3 Verify Existance of new database clone. 1. Open SQL Server 2014 Management Studio. If it is already open, from an earlier step skip to step #5.

2. In the Server name field, select SQL-Dev.


4. Click Connect.

5. Right-click SQL-Dev (SQL Server…) in the Object Explorer pane to the left, or right click the Databases folder and select Refresh.


6. Now the database LARetail_Clone_Dev should appear. The Clone from Backup successfully completed and the database is now ready for use.


9 Clone Lifecycle In the previous step you selected an existing, specific Snapshot copy and used it to create a clone of a database. The Clone lifecycle step is similar, but rather than pointing to an existing Snapshot copy the clone lifecycle will take a new Snapshot copy and clone that new Snapshot. As part of the lifecycle operation we can also delete any existing Snapshot copy of the database.

The advantage of a clone lifecycle operation is that you can schedule this to run, perhaps nightly, to refresh the database clone so that the newest data is available in the clone.

Summary of Tasks

• Verify the new host has SQL Server installed with no databases currently running/ • Prepare the new host by provisioning iSCSI storage and connecting it to the host. • Perform the cloning operation • Verify the existence of the clone database. • Optionally delete the clone

9.1 Verify SQL Server Configuration 1. Open SQL Server 2014 Management Studio. If it is already open, click Connect in the Object

Explorer and select Database Engine.

2. In the Server name field, select or type SQL-QA.


4. Click Connect.

5. Expand the Databases folder located inside the Instance “SQL-QA (SQL Server…)”. There should only be two folders under Databases.


9.2 Prepare new host The ability to clone a live database allows a user to take an instant copy of a database and mount it to another SQL server. In this activity you will add a new server to the SnapCenter inventory, and configure it from scratch. To start you must first install the plugin using the following steps.

This lab activity guides you through configuration of iSCSI for a SAN connection. For purposes of the cloning operation you will be setting up two iSCSI sessions, one to each node in the storage cluster.

1. Open Remote Desktop Connection Manager from the taskbar on the bottom. The icon is located on

the start bar and looks like this:

2. In the left pane under LOD > SQL Servers, double click sql-qa.demo.netapp.com.

3. In the remote desktop window, open a Powershell session. The icon for PowerShell is in the start bar

and looks like this:


4. At the PS c:\ prompt type get-service msiscsi

A message should be displayed indicating that the iSCSI service is running. 5. If the service is not running type start-service msiscsi.

6. Return to the jumphost by closing or minimizing the Remote Desktop Connection Manager 7. Return to your SnapCenter GUI and verify that you are logged into SnapCenter as demo\sql_user

with password Netapp1! 8. On the left hand navigation bar, go to the Hosts page.

9. Select the Host SQL-QA.demo.netapp.com. Make sure the “Host status” is “Up” and that the “Plug-in Status” says “Running” for the SnapCenter Plug-ins Package 2.0 for Windows.

10. While still on the Hosts page, click iSCSI Session at the top.


11. At the Storage Virtual Machine tab, choose svm-sql.demo.netapp.com.

12. At the Host field, select the host SQL1.demo.netapp.com.

13. Look at the “Target IP address” (one of the controller IP addresses). This is already configured for SQL1, but we need to configure iSCSI sessions for the SQL-QA host to these same Target IP Addresses.

14. Now in the host dropdown, select SQL-QA.demo.netapp.com.


15. Notice that no iSCSI sessions exist. To create, click the Establish Session button.

16. In the “Establish Session” window, in the Target portal address field, enter the previously seen Target IP address 192.168.0.131.

This will establish a session with node 1 of the storage cluster. The other fields can be left blank. 17. Click Connect.

18. Verify the storage virtual machine svm-sql.demo.netapp.com and the host SQL-QA.demo.netapp.com are still selected.

19. Click the Establish Session button once more.


20. Enter the other controller “Target IP address” 192.168.0.132 and click Connect.

This will establish a session with node 2 of the storage cluster. 21. After connection you should see the following:

22. While still in the Hosts page, at the top click Igroup.

23. In the Storage Virtual Machine menu, select svm-sql.demo.netapp.com and click the New button.


24. In the Create Igroup window, in the Storage system field, select svm-sql.demo.netapp.com.

25. In the Host field, enter SQL-QA.demo.netapp.com

26. In the IGroup name field, enter sql-qa.

27. Check the box for the Initiator (iqn.1991-05.com…)

28. In the Type field, select iscsi.

29. Click OK.

9.3 Perform the cloning 1. On the left hand navigation bar, go to the Resources page.


3. In the View field select Database

4. Click on the filter at the right end of the search box.


5. In the Hosts dropdown select SQL-QA.demo.netapp.com. 6. Set the SQL Server Instance field to be All.

Note that the only database currently on SQL-QA are the SQL Server system databases.

7. In the Hosts dropdown select SQL1.demo.netapp.com. 8. In the list of Databases, select LARetail and select the the backup box under Local Copies.

9. Select the backup listed and click the Clone Lifecycle button.


10. In the Resource Clone Lifecycle Management window, in the Clone Job name field, enter LARetail Live Clone to QA.

11. In the Clone server field, select SQL-QA.demo.netapp.com.

12. In the Clone instance field, select SQL-QA.

13. In the Clone suffix field, select _clone_qa.

14. Select the Auto assign mount point radio button and Click Next.

15. On the Location screen click to select Primary then click Next.


16. On the Scripts screen accept the defaults and click Next.

17. On the Schedule screen you have the option of scheduling the clone lifecycle operation or running it on demand. The Schedule option will enable you to schedule clone lifecycle operations to run on a schedule of your choosing. For lab purposes, accept the default (Run now) and click Next.

18. On the Notifications screen accept the defaults and click Next.

19. Verify that the Summary information is correct, and click Finish.

20. Go to the Monitor tab, and select the top job “Clone life cycle Resource Group ‘LARetail Live Clone to QA” (click the name). It may take a few seconds to load this detail.


21. Click Details

22. Once the top level has a green check mark, click Close.

9.4 Verify Existance of new database clone. 1. Open SQL Server Management Studio.

2. In the “Object Explorer” pane on the left, Right click on the SQL-QA (SQL Server…) Instance, or right click Databases.

3. Select Refresh.

4. Now the database LARetail_Live_Clone_QA should appear.

5. Open up SnapCenter and on the left hand navigation bar, go to the Resources page.


7. In the View field select Database 8. In the search bar type LA


LARetail_Live_Clone_QA should now appear indicating the Live Clone of Database from SQL1 to SQL-QA was successful.

9.5 Clean up / Delete Clone (Optional Activity) The following activity is optional, where you use SnapCenter to clean up the SQL Server.

1. In SnapCenter, on the left hand navigation bar click Resources.



4. In the search box type: LAR

5. Assuming that you have completed all tasks to this point, this should return to you the LARetail database as well as the two clones or LARetail that you have created.

While the database view shows you the clone as well as the source, the clones databases can only be deleted from the source of the clone.

6. Select the LARetail database.

This will show the visual topology map including clones that exist on both the Primary and the Secondary. Since LARetail uses a Mirror/Vault or unified replication relationship, the secondary clone is reported on both the mirror and the vault copy since this is actually one combined destination.


7. Select the one Clone that is on the local copy. This is the LARetail_clone_qa mounted to SQL-QA.

8. Select the LARetail_clone_qa copy, then click Delete.

9. When prompted to confirm delete for the clone, Click OK.

10. You can monitor the status in the job monitor. On the left hand navigation bar go to Monitor, and select the Deleting clone job.

11. Click Details.

12. Review the details as the cleanup is performed, then click Close when completed.

10 Restore a Deleted Database You can restore SQL Server database from one or more backups to your active file system, and then recover the database. This activity walks through a restore of a database.

10.1 Delete a Database 1. Open SQL Server Management Studio (SSMS).


2. SQL Server Management Studio may already be open from a previous task. If so, Click Connect, then Database Engine. .

3. In the Server Name field, select SQL1.

4. In the Authentication field, choose Windows Authentication.

5. Click Connect.

6. In the “Object Explorer” (left pane) make sure the top level, “SQL1 (SQL Server…)” has a green triangle icon over the database icon to verify that it has connected properly.

7. In the Object Explorer on the left expand Databases and several databases should appear, including LARetail.

8. Expand LARetail.


9. Expand Tables, and verify that there are several tables within this folder.

10. To simulate a condition in which database restore is required, you are going to delete the database..

11. Right click the LARetail database and select Delete.


12. In the “Delete Object” window, make sure Delete backup and restore history information for databases is checked.

13. Check the box next to Close existing connections.


14. Click OK.

15. In the “Object Explorer” (left pane), right click Databases.

16. Select Refresh.

LARetail should no longer appear under Databases.

10.2 Restore Deleted Database 1. Return to the SnapCenter GUI and verify that you are logged into SnapCenter as user

demo\sql_user with password Netapp1!.

2. On the left hand navigation bar, go to the Resources page.



5. Under Databases, select LARetail.


6. There are several backups available across multiple destinations. You can restore from primary or secondary, but for this exercise you will restore from the primary. Select the Large Market Retail backup and click the Restore button.

7. In the Restore window, on the Logs screen accept the default of None and click Next.

8. On the Restore As screen accept the defaults and click Next.

9. On the Script screen accept the defaults and click Next.

10. On the Options screen accept the defaults and click Next.

11. On Notifcations screen accept the defaults and click Next.

12. Verify the “Summary” information is correct and click Finish.

13. On the left hand navigation bar, go to Monitor.

14. Click the top job named Restore SQL1\LARetail (click the name) and click Details.

15. Review the restore steps. Once the top level has a green check mark, click Close.

10.3 Verify Existance of restored database. 1. Open SQL Server Management Studio. You should still be connected from your previous session.

2. Right click Databases under SQL1 (SQL Server…), and select Refresh.


3. Verify that the database LARetail shows up under Databases.

4. Expand LARetail.

5. Expand Tables, there should be several tables that show in this folder.

6. The restore operation is complete and your database is back to serving data to your end users.


Appendixes Table 1) NetApp Information Classification Policy document classifications and labels.

NetApp Confidential— Limited Use

NetApp Confidential—Internal Use Only

© [year] NetApp, Inc. All Rights Reserved. (NetApp Public)

Definition Sensitive business information that is intended for use within NetApp.

Information that does not clearly fit into the NetApp Confidential—Limited Use classification.

All information that is made freely available to the public.

Restrictions Anyone receiving this information must have a fully-executed nondisclosure agreement (NDA) with NetApp.

Anyone receiving this information must have a fully executed nondisclosure agreement with NetApp.

No restrictions.

Use Information should not be copied or removed from the organization’s operational control without specific management authorization. Encryption is strongly recommended.

Information should be managed on a need-to-know basis but does not require management approval for internal distribution.

Information has been explicitly approved by NetApp management for release to the public.

Examples • Salary and employee information

• Customer information • Future company

product and service information

• Company-wide memos • Project team minutes • Conference rooms and

phone numbers

• Current company products and services

• External contacts • Authorized press releases

References

Version History As an option, use the NetApp Table style to create a Version History table. Do not add a table number or caption.

Version Date Document Version History

Version 1.0 Month 20XX Use this version numbering for the initial release and subsequent major releases.

Version 1.0.1 Month 20XX Use this version numbering for minor releases.

NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.

© 2016 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, xxx, and xxx are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. <<Insert third-party trademark notices here.>> All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. TR-XXXX-MMYR

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications.

netapp snapcenter software with microsoft sql … snapcenter software with microsoft sql server...

Documents