snapmanager for microsoft sql server - netapp snapmanager for microsoft sql server ... sql1 windows...

$: SnapManager for Microsoft SQL Server - NetApp SnapManager for Microsoft SQL Server ... SQL1 Windows Server 2012 R2 192.168.0.91 DEMO\Administrator Netapp1! SQL2 Windows Server 2012$
SnapManager for Microsoft SQLServer

December 2016 | SL10311 Version 1.6.0

2 SnapManager for Microsoft SQL Server © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

TABLE OF CONTENTS

1 Introduction...................................................................................................................................... 3

1.1 Why SnapManager for SQL?....................................................................................................3

1.2 Prerequisites.............................................................................................................................. 3

2 Lab Environment............................................................................................................................. 4

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

3.1 Perform a backup with SMSQL................................................................................................6

3.2 Delete a Database and Restore it from a Backup Copy...................................................... 24

3.3 Delete a Table and Restore it from a Backup Copy.............................................................48

3.4 Configure Consistently Available Shares............................................................................. 89

3.5 Migrate a local database to a CIFS share with SMSQL Configuration Wizard...................96

3.6 Clone a database from Production to Dev with SMSQL....................................................122

3.7 Clone a Clone Database from Dev to Dev using SMSQL.................................................. 138

3.8 Clone a Cloned Database from Dev to QA using SMSQL................................................. 158

4 References....................................................................................................................................175

5 Version History............................................................................................................................ 176


1 IntroductionThis lab introduces the fundamentals of SnapManager for Microsoft SQL with clustered Data ONTAP. You willperform various backup and recovery operations and explore the Data Protection features with SnapMirror andSnapVault that aid in both business continuity and disaster recovery management. You will also explore runningSQL on both SAN (iSCSI), and NAS (CIFS or SMB3).

This lab demonstrates the benefits and how to use the newest release of SnapManager for Microsoft SQL Server7.2. This lab covers basic backup, restore, and clone database functionality. It also demonstrates and highlightsthe new database clone of clone capability through clone database from Production to QA, and from QA to Devenvironment.

1.1 Why SnapManager for SQL?Deploying SQL server on NetApp storage comes with the added enhancement of simplifying management byusing the SnapDrive and SnapManager products. SnapManager for SQL (SMSQL) simplifies data managementof backups, and helps the database administrator use the benefits of SnapShot technology without havingto engage the storage administrator. The solution allows for non-disruptive storage provisioning, and offersa multiprotocol environment. In addition, SMSQL offers the ability to quickly tap into many of the features inclustered Data ONTAP to include data protection features, and to provide the database administrator the requiredaccess to reduce duplicate data management efforts.

1.2 PrerequisitesThis lab introduces SnapManager (and SnapDrive) for Microsoft SQL on NetApp storage running clustered DataONTAP. A basic understanding of SQL, of SAN, and of NAS fundamentals will help you to execute the lab, butthey are not required. Suggested prerequisite labs include the Introductory labs for clustered Data ONTAP.

This lab includes steps for mapping shares and mounting LUNs on a Windows client. These steps assume thatyou have a basic understanding of Microsoft Windows.


2 Lab Environment

The following illustration provides a diagram of the environment for this lab.

Figure 2-1:

All of the servers and storage controllers presented in this lab are virtual devices, and the networks thatinterconnect them are exclusive to just your lab session. While we encourage you to follow the demonstrationsteps outlined in this lab guide, you are free to deviate from this guide and experiment with other Data ONTAPfeatures that may interest you. The virtual storage controllers (vsims) used in this lab offer nearly all the samefunctionality as do physical storage controllers (the main exception right now being that these vsims don’t offer HAsupport) but at a reduced performance profile.

Table 1: Lab Host Credentials

Hostname Description IP Address(es) Username Password

JUMPHOSTWindows Server 2012R2

192.168.0.5 DEMO\Administrator Netapp1!

SQL1Windows Server 2012R2


SQL2Windows Server 2012R2


SQL-QAWindows Server 2012R2


SQL-DEVWindows Server 2012R2


DC1Active DirectoryServer Win2k8R2


SVM1Storage VirtualMachine – primary

192.168.0.139 vsadmin Netapp1!

SVM2 Storage VirtualMachine –



Hostname Description IP Address(es) Username PasswordSM secondary(SnapMirror)

SVM3Storage VirtualMachine – SV archive(SnapVault)


The Storage Virtual Machines (a.k.a., vservers) in this lab are designed to provide SAN (iSCSI) and NAS(cifs/smb3) protocols environments for each of the SQL servers. All four SQL servers have SnapDrive andSnapManager installed, but only SQL1 is pre-configured. SVM1 has the source volumes for iSCSI and CIFS.SVM2 is the SnapMirror Destination for the iSCSI volumes on SVM1. SVM3 is the SnapVault Destination for theiSCSI volumes on SVM1.

Table 2: Lab Controller Credentials

Hostname Description IP Address(es) Username Password

cluster1 cluster1 mgmt LIF 192.168.0.101 admin Netapp1!

cluster1-018.3.1 clustered DataONTAP node 1

192.168.0.111 admin Netapp1!

cluster1-028.3.1 clustered DataONTAP node 2

192.168.0.112 admin Netapp1!


3 Lab ActivitiesThis lab contains the following activities and tasks:

• Backup up SQL on NetApp Storage

• Perform a backup with SMSQL on page 6• Alternate Restore options for SQL on NetApp Storage

• Delete a Database and Restore it from a Backup Copy on page 24• Delete a Table and Restore it from a Backup Copy on page 48

• SQL on NAS (CIFS / SMB3)

• Configure Consistently Available Shares on page 89• Migrate a local database to a CIFS share with SMSQL Configuration Wizard on page 96

• Using the Clone of Clones Features

• Clone a database from Production to Dev with SMSQL on page 122• Clone a Clone Database from Dev to Dev using SMSQL on page 138• Clone a Cloned Database from Dev to QA using SMSQL on page 158

3.1 Perform a backup with SMSQL1. Launch the Remote Desktop Connection Manager (RDCMan) link on the jumphost.

Figure 3-1:

2. Remote Desktop to sql1.demo.netapp.com using RDC Manager or the RDP Client.

2

Figure 3-2:

3. Click the SnapMananger for Microsoft SQL Server Management Console shortcut on the taskbar.


3

Figure 3-3:

4. Expand SnapManager for SQL Server in the left pane.5. Click SQL1 and wait for SMSQL to connect.6. Click Backup Wizard.

4

5

6

Figure 3-4:

7. Click Next.


7

Figure 3-5:

8. Select SQL1.9. Click Next.


8

9

Figure 3-6:

10. Click Next.


10

Figure 3-7:

11. Click Next.


11

Figure 3-8:

12. Click Next.


12

Figure 3-9:

13. Click Next.


13

Figure 3-10:

14. Click Next.


14

Figure 3-11:

15. Click Next.


15

Figure 3-12:

16. Click Next.


16

Figure 3-13:

17. Select Yes, or No (Yes will increase backup time).18. Click Next.


17

18

Figure 3-14:

19. Select Update SnapMirror after operation to update the Business Continuity DP backup.20. Select Archive backup to Secondary Storage to update DR archive backup.21. Click Next.


19

20

21Figure 3-15:

22. Click Next.


22

Figure 3-16:

23. Click Next.


23

Figure 3-17:

24. Click Finish.


24Figure 3-18:

25. Click Start Now and review tasks.26. Click the Backup Report tab.


25

26

Figure 3-19:

27. Review scrolling event log.28. Return to the Backup Task List.


27

28

Figure 3-20:

29. Click OK.30. Click Close.


29

30

Figure 3-21:

3.2 Delete a Database and Restore it from a Backup Copy1. From the Jumphost launch the Remote Desktop Manager.

Figure 3-22:

2. From the Remote Desktop Connection Manager (or standard RDP client), connect tosql1.demo.netapp.com.


2

Figure 3-23:

3. From the desktop of SQL1, launch Microsoft SQL Server 2014 Management Studio.

3

Figure 3-24:

4. Click Connect to log into SQL1.

4

Figure 3-25:

5. Right-click AdventureWorks2014.6. Navigate to Tasks > Select Detach ….


56

Figure 3-26:

7. Click OK.


7

Figure 3-27:

8. Observe that the AdventureWorks2014 database is no longer attached.


Figure 3-28:

9. Click the Windows Explorer icon.

9

Figure 3-29:

10. Click Local Disk (C:\).11. Navigate to C:\MSSQL\Data\12. Right-click the AdventureWorks2012_Data.mdf file.13. Select Delete.


10

11

12

13

Figure 3-30:

14. Navigate to C:\MSSQL\Log\15. Right-click the AdventureWorks2012_log.ldf file.16. Select Delete.


14

15

16

Figure 3-31:

17. From the desktop of SQL1, right-click the Recycle Bin.18. Select Empty Recycle Bin.

17 18

Figure 3-32:

19. Click Yes.


19

Figure 3-33:

20. Maximize, or re-launch SMSQL.21. Navigate to the Restore options for SQL1.22. Click Restore Wizard from the Actions Menu to the right.

2122

Figure 3-34:

23. Click Next.


23Figure 3-35:

24. Click Next.


24

Figure 3-36:

25. Double-click on one of the backups.26. Observe that the backup is listed.27. Click Next.


25

26

27Figure 3-37:

28. Press Next.


28

Figure 3-38:

29. Click Next.


29

Figure 3-39:

30. Click Next.


30

Figure 3-40:

31. Click Next.


31Figure 3-41:

32. Click Next.


32Figure 3-42:

33. Click Next.


33Figure 3-43:

34. Click Yes.

34

Figure 3-44:

35. Click Next.


35Figure 3-45:

36. Click Next.


36Figure 3-46:

37. Click Finish.


37

Figure 3-47:

38. Press Start Now.39. Click the Restore Report tab.


38

39

Figure 3-48:

40. Observe the restore progress.41. Click the Restore Task List tab.


40

41

Figure 3-49:



42

43

Figure 3-50:

44. In Microsoft SQL Server 2014 Management Studio, click Database.45. Click the Refresh icon.


44

45

Figure 3-51:

46. Expand and observe that the database has been restored and re-attached.

46

Figure 3-52:

47. OPTIONAL: By going to Windows Explorer, you will also see the files have been restored to theiroriginal location in C:\MSSQL\.


47

Figure 3-53:

3.3 Delete a Table and Restore it from a Backup Copy1. RDP to sql1.demo.netapp.com.

1

Figure 3-54:

2. Launch Microsoft SQL Server 2014 Management Studio.


2

Figure 3-55:

3. Enter SQL1 as the Server Name.4. Click Connect.

3

4

Figure 3-56:

5. Expand the Tables list under the AdventureWorks2012 database.6. Right-click the dbo.DatabaseLog table.7. Select Delete.


56

7

Figure 3-57:

8. Click OK.9. Confirm the dbo.DatabaseLog is gone.


8

Figure 3-58:

10. Under SMSQL, navigate to Restore.11. Click Clone Wizard in the Action menu (alternatively, you can double-click on the backup, and click

the Clone Option for that backup).


1011

Figure 3-59:

12. Click Next.


12Figure 3-60:

13. Select Clone Database from existing Backup Set.14. Click Next.


13

14

Figure 3-61:

15. Double-click on backup (completed at the beginning of this section).16. Confirm the backup name shows up in the field below the selection window.17. Click Next.


15

16

17

Figure 3-62:

18. Click Next.


18Figure 3-63:

19. Click Next.


19

Figure 3-64:

20. Append the name with _restoredemo, or something similar, as long as it is not the same as theattached database.

21. Click Next.


20

21

Figure 3-65:

22. Click Next.


22

Figure 3-66:

23. Click Next.


23

Figure 3-67:

24. Click Next.


24Figure 3-68:

25. Click Next.


25Figure 3-69:

26. Click Next.


26Figure 3-70:

27. Click Finish.


27

Figure 3-71:

28. Click Start Now.29. Click the Clone Report tab to review the event log progress.


28

29

Figure 3-72:

30. Review the active log window31. Click Clone Task List to return to the job task list.


30

31

Figure 3-73:



32

33

Figure 3-74:

34. Maximize, or Open SSMS.35. Click Refresh (assuming SSMS was not closed).


35

Figure 3-75:

36. Observe the database backup copy is connected.

36

Figure 3-76:

37. Navigate to the attached database backup copy.


38. Confirm the existence of the previously deleted table.

37

38

Figure 3-77:

39. Right-click on the database with table to import to the original.40. Go to Tasks.41. Select Import Data.


40

41

39

Figure 3-78:

42. Click Next.


42

Figure 3-79:

43. Select Data source as SQL Server Native Client 11.0.44. Select SQL1 as the Server name.45. Pick the source database as the attached copy from backup.46. Click Next.


4344

45

46

Figure 3-80:

47. Select SQL Server Native Client 11.0 as the Destination.48. Select SQL1 as the Server name.49. Pick the destination database as the original database.50. Click Next.


4748

49

50

Figure 3-81:

51. Click Next.


51

Figure 3-82:

52. Select dbo.DatabaseLog table.53. Click Next.


52

53

Figure 3-83:

54. Click Run immediately.55. Click Next.


54

55

Figure 3-84:

56. Click Finish.


56

Figure 3-85:

57. Review the Status of each item as they succeed.58. Click Close.


57

58

Figure 3-86:

59. Refresh and expand Tables under the original database.60. Find the restored dbo.DatabaseLog table imported from the backup copy.


59

60

Figure 3-87:

61. Return to SMSQL and click Restore under SQL1.62. Under the Action menu, Click Clone Wizard.


61 62

Figure 3-88:

63. Click Next.


63

Figure 3-89:

64. Select Delete Cloned Database.65. Click Next.


64

65Figure 3-90:

66. Select the attached cloned database backup from earlier.67. Click Next.


66

67Figure 3-91:

68. Click Finish.


68

Figure 3-92:

69. Click Start Now.70. Click Delete Clone Report tab to review log.


69

70

Figure 3-93:

71. Click Delete Clone Task List to return to the task list.


71

Figure 3-94:



72

73

Figure 3-95:

74. Refresh the Databases list attached to SQL1.


74

Figure 3-96:

75. Confirm the previously attached backup copy is now detached.

75

Figure 3-97:


3.4 Configure Consistently Available Shares1. From the Jumphost, launch the OnCommand System Manager shortcut.

Figure 3-98:

2. Click Advanced.

2

Figure 3-99:

3. Click Proceed to cluster1.demo.netapp.com.


3

Figure 3-100:

4. Enter Username as admin and Password as Netapp1!5. Click Sign In.


4

5

Figure 3-101:

6. Navigate to Storage Virtual Machines > svm1 > Storage > Shares.7. Highlight the sql2_data share.8. Click Edit.


6 7

8

Figure 3-102:

9. Click the checkbox next to Enable continuous availability for Hyper-V and SQL.10. Click Save and Close.


9

10

Figure 3-103:

11. Highlight the sql2_log share.12. Click Edit.


11

12

Figure 3-104:

13. Click the checkbox next to Enable continuous availability for Hyper-V and SQL.14. Click Save and Close.


13

14

Figure 3-105:

15. Observe the status of the CA Shares Properties for both shares.


15

Figure 3-106:

3.5 Migrate a local database to a CIFS share with SMSQL Configuration WizardSUMMARY OF ENVIRONMENT:

• SVM Management name / IP of LIF: svm1 / 192.168.0.139• CIFS Server name / IP of Data LIF: sql-share / 192.168.0.130• Both above are registered in DNS

Caution: if the OCSM Wizard is used to build the SVM (vserver) and/or the CIFS server makesure the data and management LIFs are separate for SQL on CIFS when the CIFS server isbuilt if the name for the CIFS server difffers from the SVM. Also make sure that DNS properlyresolves.

1. Using the RDCMan on the Jumphosht, connect to sql2.demo.netapp.com.


1

Figure 3-107:

2. Open Computer Management.

2

Figure 3-108:

3. Expand SnapDrive under Storage on SQL2.4. Select SQL2 (Local).5. Click Transport Protocol Settings in the Actions Menu, or right-click on SQL2.


34

5

Figure 3-109:

6. Confirm the Storage Virtual Machine is displayed.7. Click Cancel.


6

7

Figure 3-110:

8. On SQL2, launch Microsoft SQL Server 2014 Management Studio.9. Click Connect when prompted to connect to SQL2.

9

8

Figure 3-111:

10. Right-click the AdventureWorks2014 database.11. Select Properties.


10

11

Figure 3-112:

12. Select Files.13. Scroll window right.


12

13

Figure 3-113:

14. Observe the local file location of the database and log files.15. Click Cancel.


14

15

Figure 3-114:

16. Launch SnapManager for SQL.17. Click on SQL2.18. Click OK to start the Configuration Wizard.


17

18

Figure 3-115:

19. Click Next.


19

Figure 3-116:

20. Click Next.


20

Figure 3-117:

21. In the “Database Selection” Pane, select disk C under PRIMARY.22. In the Disk Select Pane, scroll to the right.23. Highlight the location: \\SQL-SHARE\sql2_data\24. Press the < = > button.


21

22

23

24

Figure 3-118:

25. Highlight the Log File in the Database Selection Pane.26. Highlight location: \\SQL-SHARE\sql2_log\27. Click < = > button.


25

26

27

Figure 3-119:

28. Click Next.


28Figure 3-120:

29. Click Next.


29Figure 3-121:

30. Scroll the “Disk Selection Pane” to the right.31. Highlight location: \\SQL-SHARE\sql2_si\.32. Click the < = > button.


30

3132

Figure 3-122:

33. Click Next.


33Figure 3-123:

34. Click Next.


34Figure 3-124:

35. Click Next.


35

Figure 3-125:

36. Click Next.


36Figure 3-126:

37. Click Next.


37Figure 3-127:

38. Click Finish.


38

Figure 3-128:

39. Click Start Now.40. Examine the Configuration Report.


39

40

Figure 3-129:

41. Observe the live status report, then click on Configuration Task List.


41

Figure 3-130:



42

43

Figure 3-131:

44. Return to SQL Management Studio.45. Right-click AdventureWorks2014.46. Select Properties.


45

46

Figure 3-132:

47. Select Files.48. Ensure that the path of the database and log files are now on the CIFS share. Then click Cancel.


47

48

Figure 3-133:

49. Open Windows File Explorer.50. Enter the path to the CIFS share: \\SQL-SHARE\sql2_data\MSSQL\Data\51. Observe that the .mdf file has been copied to the location.


50

51

Figure 3-134:

52. Review that the path of the database and log files are now on CIFS share.

52

Figure 3-135:

3.6 Clone a database from Production to Dev with SMSQL

Typical database application development life cycle starts with Development to Quality Assurance (QA), to UserAcceptance (UAT), then Production. After the code has been deployed to the production environment, developersnormally need the exact copy of the production database so that they can diagnose and improve the functionand performance of the application. This process can be complicated and time-consuming since it requiresstorage space and time. Using T-SQL, backup and restore might not be ideal for this task since during the backupprocess, the production environment will be impacted. SMSQL and SnapMirror provide snapshot backups thathave no impact, are fast, and use less space for these tasks. SMSQL empowers users to perform these clones ofthe Production database simply by using the SMSQL GUI.


1. From Jumphost, launch RDCMan.

Figure 3-136:

2. Connect to sql-dev.demo.netapp.com.

2

Figure 3-137:

3. Open SQL Server Management Studio.

3

Figure 3-138:

4. Connect to SQL1 and confirm that AdventureWorks2014.


4

Figure 3-139:

5. Click Connect.

5

Figure 3-140:

6. Select Database Engine ....


6

Figure 3-141:

7. Connect to the SQL-Dev server.

7

Figure 3-142:

8. Confirm that the only database is the local one named “AW2014DEV”.


8

Figure 3-143:

9. Still on SQL-DEV, open SnapManager for SQL Server.10. Go to Restore under SQL1.11. Find an existing backup under Local Backups.12. Double click on the backup, and Right-click and launch Clone.


10

11

12

Figure 3-144:

13. Click the elipses button ... next to Clone as Database.


13

Figure 3-145:

14. In the “Restore as Database” field enter: AdventureWorks2014_Dev01.15. Click OK.


14

15

Figure 3-146:

16. In the Clone to Server (instance), click the ... to change the instance to a new server.


16

Figure 3-147:

17. Enter SQL-Dev.18. Click OK.


17

18

Figure 3-148:

19. Click Clone....


19

Figure 3-149:

20. Click OK.


20

Figure 3-150:

21. Click Start Now.22. Click on the Clone Report tab to monitor the progress.


21

22

Figure 3-151:

23. Return to Clone Task List.


23

Figure 3-152:



24

25

Figure 3-153:

26. Once complete, return to SQL Server Management Studio and Refresh.


26

Figure 3-154:

27. Observe “AdventureWorks2014_Dev01” under SQL-DEV


27

Figure 3-155:

3.7 Clone a Clone Database from Dev to Dev using SMSQL

From time to time the software development life cycle has business requirements that require production copiesof a database used for development purposes, which are “cleaned” before using. For example, an applicationthat has user identifiable privacy type information, like social security numbers or customer sensitive data, mayneed to be removed from the copies of the prod used in Dev. This can become a time consuming and repetitivetask for a database administrator, especially when the adjustments need to be made each time the Productiondatabase is copied. Using the Clone of Clone feature, the database anonymization, or cleanup, can occur onthe first copy, and then subsequent copies of the cleaned clone can be repeated saving time and effort from thedatabase administration.

1. From the Jumphost, launch RDCMan.


Figure 3-156:

2. Connect to sql-dev.demo.netpp.com.

2

Figure 3-157:

3. Open SMSQL.

3

Figure 3-158:

4. Connect to SQL-Dev.5. Wait for the SQL server to load, and click on the Restore options.6. Click Clone Wizard.


56

Figure 3-159:

7. Click Next.


7

Figure 3-160:

8. Select Clone Active Production Databases (remember we are on the Dev copy).9. Add a check next to Run through Clone QuickStart Wizard.10. Click Next.


8

9

10

Figure 3-161:

11. Select the AdventureWorks2014_Dev01 database under the SQL-DEV instance.12. Click Next.


11

12

Figure 3-162:

13. The Clone Wizard walks you through the process, click Next.


13Figure 3-163:

14. Append the name of the “Restore as Database” with ..._Dev0215. Click Next.


14

15

Figure 3-164:

16. Click Next.


16

Figure 3-165:

17. Select No, I want to clone databases from an unverified backup.18. Click Next.


17

18Figure 3-166:

19. Click Yes.

19

Figure 3-167:

20. Click Next.


20Figure 3-168:

21. Click Next.


21

Figure 3-169:

22. Click Next.


22Figure 3-170:

23. Click Next.


23Figure 3-171:

24. Click Next.


24Figure 3-172:

25. Click Finish.


25Figure 3-173:

26. Click Start Now.27. Click on the Database Clone Report tab to monitor progress.


26

27

Figure 3-174:

28. Observe the progress, then Click Database Clone Task List tab.


28

Figure 3-175:



29

30

Figure 3-176:

31. Return to SQL Server Management Studio for the instance SQL-Dev.32. Click Refresh under Databases.


32

Figure 3-177:

33. Examine the Clone copy appears.


33

Figure 3-178:

Take note of the tables, and the changes made from AdventureWorks2014_Dev01 are not visible.This is a clean development copy from the clone of Production. AdventureWorks2014_Dev02 is nowavailable for another developer to use, or for parallel development testing without having to impactproduction.

3.8 Clone a Cloned Database from Dev to QA using SMSQL

The software development life cycle has specific business requirements that involve promoting builds of adatabase from one environment to another. For example, changes to a database in Development will need torun through a Quality Assurance testing-effort before the database can be approved for use in Production. In thisactivity, you will make a change to a cloned database copy in Dev, and clone it to a QA instance from the originalsnapshot to demonstrate that the clone occurs without impacting the working Dev copy.

1. Launch RDCMan.

Figure 3-179:

2. Connect to SQL-DEV.


2

Figure 3-180:

3. Launch SQL Server Management Studio.

3

Figure 3-181:

4. Expand tables under AdventureWorks2014_Dev01 under the SQL-Dev instance.5. Right click on the dbo.ErrorLog table, select Delete.


4

5

Figure 3-182:

6. Click OK.


6

Figure 3-183:

7. Note that the table is removed from AdventureWorks2014_Dev01.


7

Figure 3-184:

8. Open SMSQL.9. Click Restore under SQL-Dev10. Expand AdventureWorks2014_Dev01 under SQL-Dev.11. Right-click on the snapshot under local backup and select Clone.


9

10

11

Figure 3-185:

12. Click the ...button next to Clone as Database.


12

Figure 3-186:

13. Change the “Restore as Database” to: AdventureWorks2014_QA.14. Click OK.


13

14

Figure 3-187:

15. Change the Clone to Server ....


15

Figure 3-188:

16. Enter SQL-QA.17. Click OK.


16

17

Figure 3-189:

18. Click Clone.


18

Figure 3-190:

19. Click OK.


19

Figure 3-191:

20. Click Start Now.21. Click the Clone Report tab to monitor progress.


20

21

Figure 3-192:

22. Click on the Clone Task List tab.


22

Figure 3-193:



23

24

Figure 3-194:

25. From the SQL Management Studio Press Connect, select Database Engine . . ..

25

Figure 3-195:


26. Connect to SQL-QA.

26

Figure 3-196:

27. Expand Databases > AdventureWorks2014_QA.28. Expand Tables and find the dbo.ErrorLog table exists


27

28

Figure 3-197:


4 ReferencesThe following references were used to write this lab guide.

• SnapManager for Microsoft SQL Server 7.0 Documentation• TR-4003: MS SQL Server and SnapManager for SQL on Netapp Best Practices Guide• TR-4218: SnapDrive 7.0 for Windows SMB 3.0: Best Practices and Deployment Guide• TR-4228: SnapDrive 7.0 for Windows for clustered Data ONTAP 8.2• TR-4247: Deploying SQL Server 2012 over SMB3 CA Shares on Clustered Data ONTAP

http://support.netapp.com/documentation/docweb/index.html?productID=61697&language=en-US

http://www.netapp.com/us/media/tr-4218.pdf




5 Version History

Version Date Document Version History

Version 1.4.0 September 2015 Initial release

Version 1.5.0 June 2016 No changes to workflows

Version 1.6.0 Dec 2016 No changes to guide, match lab images

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

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

Go further, faster®

© 2016 NetApp, Inc. All rights reserved. No portions of this presentation may be reproduced without prior writtenconsent of NetApp, Inc. Specifications are subject to change without notice. NetApp and the NetApp logo areregistered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products aretrademarks or registered trademarks of their respective holders and should be treated as such.

http://support.netapp.com/matrix/mtx/login.do

snapmanager for microsoft sql server - netapp snapmanager for microsoft sql server ... sql1 windows...

Documents