vmware srm backup and recovery with netapp sra ... srm backup and recovery with netapp sra including...

VMware SRM Backup and Recoverywith NetApp SRA includingSnapCenter

September 2017 | SL10325 Version 1.6.2

VMware SRM Backup and Recovery with NetApp SRA including SnapCenter2 © 2017 NetApp, Inc. All rights reserved. NetApp Proprietary

1 IntroductionThis lab introduces fundamentals concepts of how to use VMware vCenter Site Recovery Manager on clusteredData ONTAP. Using the two preconfigured sites, you will perform a Test Recovery, excute a Planned MigrationRecovery, then Re-protect back to the first site.

For your convienence, several steps for deploying and configuring this SRM lab environment have beenconfigured in advance.

Storage Replication Adapter is a storage vendor specific plug-in to VMware vCenter Site Recovery Manager thatenables interaction between Site Recovery Manager and the storage controller. The adapter interacts with thestorage controller on behalf of Site Recovery Manager to discover storage arrays, and their associated datastoresand RDM devices, that are connected to vSphere. The adapter manages failover and test-failover of the virtualmachines associated with these storage objects.

Site Recovery Manager uses Storage Replication Adapter to discover arrays and replicated and exporteddatastores, and to fail over or test failover of datastores. Site Recovery Manager employs virtualization to provideend-to-end disaster recovery management and automation across the entire data center. Additionally, SiteRecovery Manager uses a VMware infrastructure to build, automate, and test disaster recovery plans for the datacenter, and it integrates with vSphere to provide a seamless view of your environment that includes both virtualinfrastructure, and disaster recovery management.

Storage Replication Adapter provides array-specific support for Site Recovery Manager by following the inputspecifications from Site Recovery Manager.

The adapter enables Site Recovery Manager to execute the following work flows:

• Discovery of arrays and replicated devices• Test recovery• Recovery• Re-protect


Figure 1-1:

1 Lab ObjectivesThe following list identifies the objectives of this lab:

• Examine the SnapMirror replication.• Explore the setup of the protection groups.• Perform a Test Recovery Operation.• Perform a Planned Migration Recovery.• Perform a Re-protect Operation.• Create a Protection Group.


2 Lab EnvironmentAll 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 SRM and DataONTAP features that may interest you.

Figure 2-1:

2 Table of Systems

Host Name Operating System Role/Function IP Address

cluster1 ONTAP 9.1 cluster 1 at Site A 192.168.0.101

cluster1-01 ONTAP 9.1 cluster 1 node 1 192.168.0.111

cluster2 ONTAP 9.1 cluster 2 at Site B 192.168.0.102

cluster2-01 ONTAP 9.1 cluster 2 node 1 192.168.0.121

svm1 Storage Virtual Machinefor VMware datastore onNFS at Site A

SVM mgmt lif 192.168.0.130


Host Name Operating System Role/Function IP Address

svm2 Storage Virtual Machinefor VMware datastore onNFS at Site B

SVM mgmt lif 192.168.0.140

jumphost Windows Server 2012 R2 primary desktop entrypoint for lab

192.168.0.5

dc1 Windows Server 2012 R2 Active Directory / DNS 192.168.0.253

esx1 VMware vSphere ESX 6.5at Site A

VMware Hypervisor 192.168.0.51

esx2 VMware vSphere ESX 6.5at Site B

VMware Hypervisor 192.168.0.52

vc1 Windows Server 2012 R2at Site A

VMware vCenter Server 192.168.0.31

vc2 Windows Server 2012 R2at Site B

VMware vCenter Server 192.168.0.32

snapctr Windows Server 2012 R2 SnapCenter 3.0 Server 192.168.0.75

vsc7siteA Virtual Storage ConsoleUnified Appliance 7 for vc1

Nested Virtual Appliance 192.168.0.33

vsc7siteB Virtual Storage ConsoleUnified Appliance 7 for vc2

Nested Virtual Appliance 192.168.0.34

siteA-vm01 CentOS 6.5 x64 linux Nested VM running at SiteA

n/a

sql1-nested Windows Server 2012 R2 Nested VM running at SiteB (db on vmdk)

192.168.0.91

2 User IDs and Passwords

Host Name User ID Password Comments

jumphost DEMO\Administrator Netapp1! Domain Administrator

cluster... admin Netapp1! Same for individual clusternodes

svm... vsadmin Netapp1! svm administrator

vsc maint Netapp1! console admin

vsc administrator Netapp1! Administrator

esx... root Netapp1! Administrator

vc... [email protected]! Local Admin for vCenter


3 Lab Activities related to SRMThis lab contains the following activities and tasks:

• Tour the Environment on page 6• Test Recovery on page 17• Recovery using a Planned Migration on page 30• Running a Re-protect on page 37• Creating an SRM Protection Group on page 44

3.1 Tour the EnvironmentIn this activity you will log into the vCenter and System Manager web interfaces for both Site A and Site B.Additionally, you will examine the preconfigured SnapMirror relationship, and explore the Protection Groups andRecovery Plan that are also staged for this demonstration.

1. After connecting to the Jumphost, allow the PowerShell window to complete the lab prep script.

Figure 3-1:

2. Launch the link on the desktop for VC1.

Figure 3-2:

3. Login to VC1 with credentials: [email protected] and password: Netapp1! .

3

Figure 3-3:


4. Minimize the browser, then launch the link on the desktop for Cluster1, or navigate tohttps://192.168.0.101/.

Figure 3-4:

5. Click on Continue to this website ....

5

Figure 3-5:

6. Sign in to ONTAP with credentials: admin, and Netapp1!.

6

Figure 3-6:

7. Minimize the browser, then launch the link on the desktop for VC2.


Figure 3-7:

8. Login to VC2 with credentials: [email protected], and password: Netapp1!.

8

Figure 3-8:

9. Minimize the browser, then launch the link on the desktop for Cluster2, or navigate tohttps://192.168.0.102/.

Figure 3-9:

10. Click on Continue to this website....


10

Figure 3-10:

11. Sign in to ONTAP with credentials: admin, and Netapp1!.

11

Figure 3-11:

12. Return to the browser tab for VC1, click on Home, and select Site Recovery.


12

Figure 3-12:

13. Click Protection Groups.

13

Figure 3-13:

14. Click SiteA-NFS-PG.


14

Figure 3-14:

15. Login with User name: [email protected] and the password: Netapp1!.

Note: If you missed the prompt with the login to VC2 from VC1, you may get permission errors.If so, you should log out of VC1, log back in, and return to the steps above.

15

Figure 3-15:

16. Review the “Summary” tab to confirm the Protected Site is vc1, and the Recovery Site is vc2, then clickthe Related Objects tab.


16

Figure 3-16:

17. Click Virtual Machines, and review the settings.18. Click Recovery Plans.

1718

Figure 3-17:

19. Highlight SiteA-NFS-PG. Click Actions > Edit Plan....


19

Figure 3-18:

20. Review the Recovery Plan by clicking Next.

20

Figure 3-19:

21. Click Next.


21

Figure 3-20:

22. Click Next.


22

Figure 3-21:

23. Click Next.


23

Figure 3-22:

24. Click Finish.


24

Figure 3-23:

3.2 Test RecoveryA test recovery operation ensures that a real operation will work during a disaster, or a planned migration. A testrecovery operation does not affect an ongoing SnapMirror replication. During a test recovery operation, StorageReplication Adapter creates a FlexClone volume from the latest Snapshot copy of the SnapMirror destinationvolume, and displays the cloned export path to Site Recovery Manager.

This activity illustrates how to perform a Test Recovery.

1. First, examine the characteristics of the production VM at the Protected Site by going to the browser tabfor VC1. Navigate to Home > Hosts and Clusters.

2. Select siteA-vm01.3. In the “Summary” tab scroll down to the box labeled Related Objects.4. Observe that the VM in the Site A cluster, on host esx1, has a network assigned, and is on nfs1 storage

(in cluster1).


1

2

3

4

Figure 3-24:

5. Now observe the replicated seed copy of the VM at the Recovery site by going to the browser tab forVC2.

6. Navigate to Home > Hosts and Clusters.7. While still in VC2, select siteA-vm01, and in the “Summary” tab scroll down to the box labeled Related

Objects.8. Observe that the recovery copy is listed as being in the Site B cluster, is on host esx2, has no network

assigned, and is on esx2local.


6

5

7

8

Figure 3-25:

9. In ONTAP, go to the browser tab for Cluster1's System Manager UI, click on SVMs.10. Double-click on svm1.

9

10

Figure 3-26:

11. Drill down into Volumes.12. Notice that the volume nfs1 (which is the datastore for the virtual machine siteA-vm01) is in the

aggregate “aggr1_cluster1_1”, that is a set of disks in the Site A storage cluster.


11

12

Figure 3-27:

13. Now go to the browser tab for Cluster2’s System Manager UI, click on Protection > Relationships.

13Figure 3-28:

14. Examine the source SVM is “svm1” (on site A), and the source volume is “nfs1” with a destinationvolume of “nfs1_dr”.

14

Figure 3-29:

15. While still in Cluster2, drill down into SVMs > svm2.


15

Figure 3-30:

16. Click on Volumes.17. Examine the volume “nfs1_dr” (which is the target for the SnapMirror) is in the aggregate

“aggr1_cluster2_1”, that is a set of disks in the Site B storage cluster.

16

17

Figure 3-31:

18. Return to the browser tab for VC1, optionally power on the VM.19. Click on Home > Site Recovery.


1819

Figure 3-32:

20. Go to Recovery Plans.

20

Figure 3-33:

21. With SiteA-NFS-RP highlighted, click the Monitor tab.22. Click the green play icon to run a Test Recovery operation.


21

22

Figure 3-34:

23. Check the box for Replicate recent changes to recovery site.24. Click Next.


23

24

Figure 3-35:

25. Click Finish.


25

Figure 3-36:

26. Observe that the progress is updated in the “Status” column.

26

Figure 3-37:

27. After the Recovery Step 4 completes, go to the browser tab for Cluster2’s System Manager. UnderVolumes, click Refresh.

28. Note that a new volume has been created named “testfailover_nfs1_dr”.


27

28Figure 3-38:

29. Go to the browser tab for VC2, navigate to Hosts and Clusters, and click the Refresh icon.30. Highlight siteA-vm01, and in the “Summary” tab under “Related Objects”, note that the Cluster and

Host remain as they were, but a network is now assigned, and the storage is now “nfs1” (in Site B).

29

30

Figure 3-39:

31. Go back to the browser tab for VC1, navigate to the Hosts and Clusters, and click the Refresh icon.32. Note that the protected VM remained unaffected, and can be powered on to be fully operational while

the Test Recovery is being conducted.33. Go to Home > Site Recovery.


31

32

33

Figure 3-40:

34. Click on Recovery Plans.35. With SiteA-NFS-RP highlighted, click the yellow broom icon to begin the cleanup operation of the Test

Recovery.

34

35

Figure 3-41:

36. Click Next.


36

Figure 3-42:

37. Click Finish.


37

Figure 3-43:

38. Monitor progress under the “Status” tab.

38

Figure 3-44:

39. Return to the browser tab for Cluster2's System Manager, and under Volumes click Refresh.40. Note that the cleanup removed the created test volume .


39

40

Figure 3-45:

41. Return to the browser tab for VC2, click Refresh.42. Note that the “Related Objects” in the “Summary” tab for “siteA-vm01” now shows no network setting,

and the storage as “esx2local”.

41

42

Figure 3-46:

3.3 Recovery using a Planned MigrationWhen performing a recovery, Site Recovery Manager offers two options: one for planned migration of services,and one for unplanned disaster recovery.

During disaster recovery, Storage Replication Adapter cancels any ongoing transfers to the SnapMirrordestination, quiesces the destination, and breaks the SnapMirror relationship. When the SnapMirror relationship isbroken, the destination volume is ready for read/write operations.

During a planned migration, the recovery operation shuts down the virtual machines at the protected site.Storage Replication Adapter performs a SnapMirror update and synchronizes the storage systems, quiesces thedestination, and breaks the SnapMirror relationship. When the SnapMirror relationship is broken, the destinationvolume is ready for read/write operations.


This activity illustrates how to perform a Planned Migration Recovery operation.

1. In the browser tab for VC1, under Recovery Plans, confirm that “SiteA-NFS-RP” has a status of“Ready”.

1

Figure 3-47:

2. Optionally, power on the VM at the Protected Site, “siteA-vm01”. This is allowed because the plannedmigration will resolve the VM powered state.

2

Figure 3-48:

3. Click OK.


3

Figure 3-49:

4. Go to the browser tab for VC2, refresh and confirm that the replication copy on the Recovery Site in the“Summary” tab under “Related Objects” sits on “esx2local” storage, which is the Placeholder Datastorefor SRM.

4

Figure 3-50:

5. Return to the browser tab for VC1, under the “Recovery Plans, Objects” tab. With SiteA-NFS-RPhighlighted, click the red circle play icon to begin the operation: Run Recovery Plan.


5

Figure 3-51:

6. Click the “I understand...” checkbox.7. Select the Planned Migration “Recovery type”.8. Click Next.

6

7

8

Figure 3-52:

9. Click Finish.


9

Figure 3-53:

10. Select the plan, and go to the Monitor tab.11. Observe the progress as the “Status” column is updated.

10

11

Figure 3-54:

12. Click back to go to the “Array Based Replication”.


12

Figure 3-55:

13. Select one of the svms, go to the Manage tab, and observe the SVMs and the Replication.

13

Figure 3-56:

14. Click Related Objects, and observe that the status is listed as “Failover in progress”, then go to“Recovery complete”.


14

Figure 3-57:

15. Go to Home > Hosts and Clusters.16. Select siteA-vm01, scroll down in the “Summary” tab to the “Related Objects”, and note that the

network is not present, and the storage is listed as “esx1local”.

15

16

Figure 3-58:

17. Go to the browser tab for VC2, and click Refresh.18. Navigate to the Summary tab for “siteA-vm01”, and observe that the “Related Objects” section has

siteA-vm01 now running in the Recovery Site with the correct network assigned.


17

18

Figure 3-59:

3.4 Running a Re-protectAfter a recovery operation, you can run the re-protect operation to replicate the changes made at the recovery siteto the original protected site. During a re-protect operation, Storage Replication Adapter reverses the direction ofthe existing SnapMirror relationships, and starts replicating the changes made at the recovery site to the originalprotected site.

This activity demonstrates the steps to run a Reprotect.

1. (Optional) Right-click on siteA-vm01 on VC2, and select Power > Shut Down Guest OS, or press thered square icon.


1

Figure 3-60:

2. Click Yes.

2

Figure 3-61:

3. Go to the browser tab for VC2, in the “Summary” tab scroll down to the “Related Objects”, and observethat “siteA-vm01” has a network assigned, and is on nfs1 storage.


3

Figure 3-62:

4. Go to the browser tab for VC1, in the “Summary” tab scroll down to the “Related Objects” and observethat “siteA-vm01” has no network assigned, and is on “esx1local” storage.

4

Figure 3-63:

5. From VC1 (the Protected Site), go to Home > Site Recovery.6. Click on Recovery Plans.


5

6

Figure 3-64:

7. From the “Object” tab, select SiteA-NFS-RP.8. If prompted, login with the credentials for VC2 (the Recovery Site) of user name:

[email protected], and password Netapp1!.

7

Figure 3-65:

9. In the “Monitor” tab with the Recovery Steps button pressed, find and click on the gray shield with theyellow lightning bolt icon to begin the Reprotect Recovery Plan operation.


9

Figure 3-66:

10. Click the checkbox next to I understand ....11. Click Next.

10

11

Figure 3-67:

12. Click Finish.


12

Figure 3-68:

13. Monitor the progress as the status column is updated.

13

Figure 3-69:

14. After the final step the Plan status changes from “Reprotect in progress” to “Ready”.


14

Figure 3-70:

15. Click back in the “Navigator” panel.16. Select Array Based Replication.17. Select svm2.

17

Figure 3-71:

18. In the “Manage” tab with Array Pairs selected, observe that the status is “Ongoing Replication”. Thisdemonstrates that the Reprotect is now complete, and the VM is running from the Protected Site (SiteA), ready to be sent to the Recovery Site (Site B) once again, and the SnapMirror relationship is stillproviding the replication between sites.


18

Figure 3-72:

3.5 Creating an SRM Protection GroupAfter you configure a NetApp SnapMirror data protection relationship, the NetApp Site Replication Adapter forVMware's Site Recovery Manager makes SRM operations very simple. The tight integration between NetApp'sSRA with VMware's SRM allows for quick and easy setup of storage resources in SRM.

In this activity, a SnapMirror data protection relationship exists for the volume nfs2 on the storage virtual machinesvm2 on cluster 1, going to the volume nfs2_dr on storage virtual machine svm1 on cluster 1. Additionally, allSRM placeholders and mappings are pre-configured. This activity configures a Protection Group in SRM whileusing the NetApp SRA to demonstrate how tightly integrated the solution can be for an administrator.

1. From VC2, click on Home, then Site Recovery.


1

Figure 3-73:

2. Click on Array Based Replication.3. Click on svm2.

2

3

Figure 3-74:


4. If prompted, log into VC1 with user name [email protected] with password Netapp1!.

4

Figure 3-75:

5. Click on the Manage tab to confirm the Outgoing Replication exists.

5

Figure 3-76:

6. Return back to “Protection Groups” in the "Related Objects" tab.7. Click the blue shield with green plus icon to create a Protection Group.

67

Figure 3-77:

8. Enter SiteB-NFS-PG.9. Click Next.


8

9

Figure 3-78:

10. Accept the defaults, ensuring that array-based replication is selected, and click Next.


10

Figure 3-79:

11. Add a check next to the nfs2 datastore.12. Observe the registered VMs are displayed.13. Click Next.


11

12

13

Figure 3-80:

14. Click Finish.


14

Figure 3-81:

15. Go to the browser tab for Cluster1, click on Protection > Relationships.16. Note that there is now a second SnapMirror established going from the SVM on Site B to the SVM on

Site A.


15

16

Figure 3-82:

3.6 Accessing the NetApp VSC Unified AppliancesIn order to install the NetApp SRA 7.0 plug-in, known as the Storage Replication Adapter for ONTAP for VMwarevCenter Site Recovery Manager, a virtual appliance is deployed using VMware procedures. Following thedeployment, a small installer runs to link the vCenter/SRM server with the SRA appliance.

Following deployment, you can use a command line interface to the VSC unified appliance maintenance consolefor maintenance, diagnostics, or to start, stop, or enable ssh. In addition, the VSC Unified Appliance 7.0 providesyou with a web-based command-line interface to add, edit, or remove clusters or SVMs.

The following activities demonstrate two methods to interact with the VSC 7.0 unified appliances.

3.6 SSH CLI access to VSC Unified Appliances1. Open PuTTy.

Figure 3-83:

2. Double-click on vsc-siteA (or sra2).


2

Figure 3-84:

3. Log in with user name maint, and password Netapp1!.

3

Figure 3-85:

4. Examine the available options.5. Press x to exit.


4

5

Figure 3-86:

6. Optionally, open a console to the VM from vCenter, and compare the additional options available in theconsole access.

3.6 Web Based CLI access to Site Replication Adapter Appliances1. To navigate to the vsc-siteA web based CLI, open your browser, navigate tohttps://vsc-

sitea.demo.netapp.com:9083, or https://192.168.0.33:9083 (use .34 for vsc-siteB).

Figure 3-87:

2. Click Advanced.

2

Figure 3-88:

3. Click Add Exception.

https://vsc-sitea.demo.netapp.com:9083

https://vsc-sitea.demo.netapp.com:9083

https://192.168.0.33:9083


3

Figure 3-89:

4. Click Confirm Security Exception.

4

Figure 3-90:

5. Log in with user name administrator, and password Netapp1!.


5

Figure 3-91:

6. Examine and explore the available options.7. To exit, click Logout, or close the browser tab.

6

7

Figure 3-92:


4 Lab Activities related to Backup and RestoreThis lab contains the following activities and tasks:

• Managing Backups for SQL on VMDK using SnapCenter 3.0 on page 56• Managing Restores for SQL on VMDK using SnapCenter 3.0 on page 70

4.1 Managing Backups for SQL on VMDK using SnapCenter 3.0This activity demonstrates how to manage backups for a VMware guest VM running Microsoft SQL using theSnapCenter Plug-in for Microsoft SQL Server, and the SnapCenter Plug-in for VMware vSphere along withSnapCenter 3.0.

Note: This activity is executed from VC2. If you are accessing this section directly without completing thepreceding sections of this guide, be sure to launch the shortcut to vCenter's web UI for VC2, and login withuser name [email protected] and password Netapp1!.

1. In VC2, go to Home > SnapCenter Plug-in for VMware vSphere.

1

Figure 4-1:

2. Since this is your first time using the SnapCenter Plug-in for VMware vSphere, you are presented withthe “Getting Started” tab. In this lab environment the first two steps, “Configure SnapCenter Server” and“Add storage system”, have already been completed. During this task you will complete the other twosteps that are “Create backup policy” and “Create resource group”. From this point forward you will bepresented with the “Status” page. Click Status now.


2

Figure 4-2:

3. The “Status” page shows you the SnapCenter Server and the SnapCenter Plug-in versions in the topright. It also gives you a quick access to the online help center, as well as plug-in logs. Below you cansee the Job Monitor area. This is empty now, but as jobs are run the status and detail can be seen fromthis page.

4. On the left hand navigation bar of the “Plug-in” interface, click Storage Systems.

3

4

Figure 4-3:

5. Notice that an SVM has already been added. SnapCenter uses the SVM storage object and not thecluster.

6. Click Back.


56

Figure 4-4:

7. Go to Policies.8. Click New Policy.

7 8

Figure 4-5:

9. Enter a name of On Demand Only Policy.10. Enter a description of Demonstration of a Backup Policy.11. Set the “Retention to Days to keep” with the value of 1. This will keep one day’s worth of On Demand

backups, no matter how many backups you take.12. Change the “Frequency” to On demand only.

Note: You can click the Advanced button to see the advanced options, but do not make anychanges at this time.

13. Click Add.


910

11

12

13

Figure 4-6:

14. Click OK.

14

Figure 4-7:

15. Click Home to go to the “VMs and Templates”.


15

Figure 4-8:

16. In the “VMs and Template” view expand Site B, then expand db on vmdk demo. Right click on sql-nested vm, go to NetApp SnapCenter and select Create Resource Group.


16

Figure 4-9:

17. Enter name Database Servers RG.18. Enter description Demonstration of a Resource Group.19. Click Next.


1718

19

Figure 4-10:

20. Click Next.

20

Figure 4-11:

21. Select the Policy created earlier.22. Click Next.


21

22

Figure 4-12:

23. Click Next.

Note: The schedule is determined by the Policy.

23

Figure 4-13:

24. Click Finish.


24

Figure 4-14:

25. Click OK.

25Figure 4-15:

26. Go back to SnapCenter Plug-in for VMware vSphere.27. Go to Resource Groups.


26

27

Figure 4-16:

28. Click Run Now.

Note: You created the Resource Group earlier directly from the VM menu, but you can alsocreate new Resource Groups from this menu.

28

Figure 4-17:

29. Click OK.

29

Figure 4-18:

30. Click Back.


30

Figure 4-19:

31. Go to the “Dashboard Status Job Monitor”.32. Observe the status, as well as the “Recent Tasks”.

31

32

Figure 4-20:

33. Return to “VMs and Templates”, right click on sql-nested vm, go to NetApp SnapCenter, then to theRestore option.


33Figure 4-21:

34. Cancel after you see that the backup to confirm it is accessible, and that it can be used to do a full VMrestore.


34

Figure 4-22:

35. Right-click again, and go to Attach Virtual Disk.


35

Figure 4-23:

36. Cancel after you see that the backup and the VMDK disk are accessible, and can be used to perform asingle file restore.


36

Figure 4-24:

37. Optionally, check SnapCenter in VC1 to notice the Policy is visible but the Resource Group is not. Thisis because the defined policy can be defined in the same SnapCenter server visible to both vCenterservers, but the Resource Group includes VMs that are unique to the vCenter.

37

Figure 4-25:

4.2 Managing Restores for SQL on VMDK using SnapCenter 3.0This activity demonstrates how to perform a single file restore by mounting a backup and attaching virtual disk fileto copy out files from within the VMDK. This operation will mount a NetApp SnapShot backup to view files thatwere backed up inside of a VMDK operating system file. This demonstrates that from the same backup that canrestore an entire VM to a point in time it is also possible to access a particular virtual disk allowing for quick andflexible restore options.


1. RDP to nested SQL server by launching the Remote Desktop Connection Manager.

1

Figure 4-26:

2. Double-click on sql1.demo.netapp.com.3. If prompted, login with user name DEMO\Administrator and password Netapp1!, then click OK.

2

Figure 4-27:

4. Open Windows Explorer on the SQL server.

4

Figure 4-28:

5. Navigate to confirm the database files are on “C:\MSSQL\”. Browse the folders to see that they containmdf and ldf (sql database and log) files.


5

Figure 4-29:

6. Return to the Jumphost browser for VC2. Click Home > VMs and Templates, then expand Site B anddb on vmdk demo. Right click on the sql-nested VM.

7. Go to SnapCenter > Attach Virtual Disk.


7

Figure 4-30:

8. The virtual disk from the backup is selected by default.9. Click Attach.


8

9

Figure 4-31:

10. Click OK.

10

Figure 4-32:

11. Go to the VM, Datastore tab, observe the backup is mounted,


11

Figure 4-33:

12. Return to the RDP session on the SQL server.13. Right click on This PC, and go to Manage.

13

Figure 4-34:

14. From the “Windows Server Manager” Dashboard, click on Tools.15. Launch Computer Management.


14

15

Figure 4-35:

16. Go to Disk Management.17. Find Disk 1, and click on the box for Disk 1 to make it online.

16

17

Figure 4-36:

18. Windows will assign a drive letter.


18

Figure 4-37:

19. Use Windows Explorer to navigate to the Data and Log folders which contain the MDF (data) and LDF(log) database files from the mounted backup. The files are now available to be copied to the localdrive (C:), or mounted as a second instance on the same database server using Microsoft SQL ServerManagement Studio, or they can be configured for another server.


19

Figure 4-38:

20. Return to vCenter, right click on VM.21. Navigate to NetApp SnapCenter > Detach Virtual Disk.


21

Figure 4-39:

22. Ensure there is a check next ot the vmdk disk that is mounted.23. Confirm the action by adding a check next to Detach the selected disk(s).24. Click Detach.


22

2324

Figure 4-40:

25. Click OK.

25

Figure 4-41:

26. Return to the RDP to the SQL, and navigate to Computer Management > Disk Management to seethat the mounted backup is gone.


26

Figure 4-42:


5 Lab LimitationsThis lab has the following limitations:

• All of the servers and storage controllers presented in this lab are virtual devices. Consequently, anyoperations involving movement of large quantities of data will not exhibit performance representative ofreal systems.


6 ReferencesThe following references were used to create this lab guide.

• https://library.netapp.com/ecmdocs/ECMLP2770248/html/frameset.html• http://docs.netapp.com/mgmt/index.jsp?topic=%2Fcom.netapp.doc.ocsc-dpg-vm%2Fhome.html

https://library.netapp.com/ecmdocs/ECMLP2770248/html/frameset.html

http://docs.netapp.com/mgmt/index.jsp?topic=%2Fcom.netapp.doc.ocsc-dpg-vm%2Fhome.html


7 Version History

Version Date Document Version History

1.5.0 Apr 2016 Initial Release

1.6.0 July 2017 Updated for new VSC/SRA andvSphere/SRM versions

1.6.1 September 2017 Corrected screenshot

1.6.2 September 2017 Minor editing

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 the product components and versions that can be used to constructconfigurations that are supported by NetApp. Specific results depend on each customer's installation inaccordance with 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®

© 2017NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consentof NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP®,ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registeredtrademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks orregistered trademarks of their respective holders and should be treated as such.

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

vmware srm backup and recovery with netapp sra ... srm backup and recovery with netapp sra including...

Documents