Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
vSphere 6.5
1 Introduction...................................................................................................................................... 3
1.2 Prerequisites.............................................................................................................................. 3
2 Lab Environment............................................................................................................................. 4
3.2 Explore the VSC Performance Dashboard, Reporting Page, and Related Objects
Panels in vCenter............................................................................................................................17
4.2 Use Datastore Provisioning Wizard for NAS Backed VVOL Creation................................ 67
4.3 Use the Datastore Provisioning Wizard for SAN Backed VVOL Creation.......................... 77
6 References....................................................................................................................................113
1.2 Prerequisites
In order to use this lab successfully, the following are the recommended prerequisites:
• Familiarity with clustered Data ONTAP®.
• Basic understanding of VMware Virtualization.
Figure 2-1:
The following tables contain host information that is used for this lab:
W2k8R2SVR-
Windows 2008R2 template (windows cloning demo) n/a
template
RHEL60-
Red Hat Ent. Linux template (large linux cloning demo) n/a
template
DEBIAN-SM-
Debian Linux tempate (small linux cloning demo) n/a
TEMPLATE
2 Lab Preparation
Because of the complexity of the nested VMware components and timing related to provisioning, a post-
provisioning script is necessary to prepare the enviornment for intial use. This script reconnects the nested
hypervisors to vCenter to essentially wake them up from their dormant state in order for vCenter (and VSC) tasks
to work.
This lab uses a preparation script that automatically runs when you first log in to the lab. Please wait for the script
to complete and the window to close before you proceed.
Figure 3-1:
Figure 3-2:
Figure 3-3:
Figure 3-4:
6
Figure 3-5:
Figure 3-6:
8. Press x.
Figure 3-7:
Figure 3-9:
Figure 3-10:
6. Click Advanced.
Figure 3-11:
Figure 3-12:
Figure 3-13:
9. When presented with a black browser screen, click the cursor in the screen and press the backspace
keey.
10. Log in with maint and Netapp1!
10
Figure 3-14:
11. Press 4.
11
Figure 3-15:
12. Observe that you have option 3 to Enable remote diagnostic access.
13. Press x to exit.
13
Figure 3-16:
Figure 3-17:
Figure 3-18:
Figure 3-19:
Figure 3-20:
3.2 Explore the VSC Performance Dashboard, Reporting Page, and Related Objects
Panels in vCenter
This activity explores enhancements that the Virtual Storage Console 7.0 for VMware vSphere® adds to storage
reporting in various sections of vCenter.
1. Launch the shortcut for vCenter.
Figure 3-21:
Figure 3-22:
Figure 3-23:
Figure 3-24:
Figure 3-25:
6. Click OK.
Figure 3-26:
7. Click OK.
7
Figure 3-27:
Figure 3-28:
9. Ensure that the Storage Virtual Machines appear along side the Clusters.
10. Navigate to Storage by hovering over Home > Storage.
10
9
Figure 3-29:
11 13
12
Figure 3-30:
14. Scroll down to see the NFS Details and Storage Details tiles added information.
15. Return to the VSC.
15
14
Figure 3-31:
Figure 3-32:
17. At this point there should be some data in the Datastore Summary Report, review then click on Virtual
Machine Summary Report.
17
Figure 3-33:
18. While on the Virtual Machine Summary Report page, take note that there is a button to Export to CSV
file
19. Click Back to return to the Summary page of the VSC.
Figure 3-34:
20. Data should now be populated in the Summary, explore the tiles and storage related information.
Figure 3-35:
4
Figure 3-36:
Figure 3-37:
7. Select a cluster.
8. Click Next.
Figure 3-38:
9
10
11
Figure 3-39:
12
Figure 3-40:
14. Examine the Recent Tasks pane and see that the new datastore has been created and mounted.
15. Optionally, go to OCSM for cluster1 to see what was done in ONTAP.
14
Figure 3-42:
16. To cleanly remove the datastore from vCenter, ESX and ONTAP, return to the VSC > Storage
Systems.
Figure 3-43:
17
Figure 3-44:
Figure 3-45:
19
Figure 3-46:
21
22
Figure 3-47:
Figure 3-48:
3.4 Taking a Backup using the SnapCenter Plug-in for VMware vSphere
1. Go to Home > SnapCenter Plug-in for VMware vSphere.
2. Since this is your first time using the SnapCenter Plug-in for VMware vSphere, you are presented with
the “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 two
steps, which are to create a backup policy and a resource group. From this point forward you will be
presented with the “Status” page. Click Status now.
Figure 3-49:
3. The “Status” page shows you the SnapCenter Server and the SnapCenter Plug-in versions in the top
right. It also gives you quick access to the online help center, as well as plug-in logs. Below you can see
the Job Monitor area. This is empty now, but as jobs are run the status and detail can be seen from this
page.
4. On the left hand navigation bar of the Plug-in interface, click Storage Systems. Notice that an SVM has
already been added. SnapCenter uses the SVM storage object and not the cluster.
Figure 3-50:
Figure 3-51:
7. Go to Policies.
Figure 3-52:
Figure 3-53:
11
12
13
Figure 3-54:
14
Figure 3-55:
Figure 3-56:
16. Expand the virtual datacenter, then right-click on Svr2012-SQL1. Go to NetApp SnapCenter, and
select Create Resource Group.
16
Figure 3-57:
17
18
19
Figure 3-58:
20
Figure 3-59:
21
22
Figure 3-60:
23. In this step, you configure the schedule for the backup job to run. Since you selected a policy with an
On Demand schedule, the options here are greyed out and you do not need to make any changes. The
schedule listed is determined by the policy, so if you select a policy with a frequency of Hourly, then you
will have the option to select the frequency, and the starting date and time for that schedule. Click Next.
Figure 3-61:
24
Figure 3-62:
26. Go back to SnapCenter Plug-in for VMware vSphere, and navigate to Resource Group.
26
Figure 3-64:
27. Select the Database Servers RG resource group that you just created, then click Run Now.
Note: You created the Resource Group earlier directly from the VM menu, but you can also
create new Resource Groups from this menu.
27
Figure 3-65:
Figure 3-66:
29
30
31
Figure 3-67:
32. Return to VMs and Templates, right click on Svr2012-SQL1 vm, go to NetApp SnapCenter > Restore
option.
33. Explore the available backup list and associated information, and also note that there is a search
option. You will perform a restore in a separate activity. Press Cancel to close the window without
mounting the backup.
Figure 3-69:
34. Right-click Svr2012-SQL1 again, and go to NetApp SnapCenter > Attach Virtual Disk.
Figure 3-70:
35. Press Cancel after seeing the backup and the VMDK disk are accessible, and can be used to perform
a single file restore.
Figure 3-71:
3.4 Demonstrate restore of SQL database files from a backup of SQL VM running
on VMDK
This activity demonstrates how to perform a single file restore by mounting a backup and attaching virtual disk file
to copy out files from within the VMDK. This operation will mount a NetApp SnapShot backup to view files that
were backed up inside of a VMDK operating system file. This demonstrates that from the same backup that can
restore an entire VM to a point in time it is also possible to access a particular virtual disk allowing for quick and
flexible restore options.
1. Click on the Microsoft Remote Desktop Connection Manager shortcut.
Figure 3-72:
2. RDP to “Svr2012-SQL1”.
Figure 3-73:
Figure 3-74:
Figure 3-75:
5. Navigate to confirm the database files are on C:\LOD\. Browse the folders to see that they contain mdf
and ldf (sql database and log) files.
Figure 3-76:
6. Return to the Jumphost browser for VC1, click Home > VMs and Templates, right-click on the VM, go to
NetApp SnapCenter > Attach Virtual Disk.
Figure 3-77:
Figure 3-78:
9. Click OK.
9
Figure 3-79:
10. Go to the VM, Datastores tab, and observe the backup is mounted.
Figure 3-80:
Figure 3-81:
13
14
Figure 3-82:
16
Figure 3-83:
Figure 3-84:
18. Use Windows Explorer to navigate to the MDF/LDF files from the mounted backup. The files are now
available to be copied to the local drive (C:), or mounted as a second instance on the same database
server using Microsoft SQL Server Management Studio, or they can be configured for another server.
Figure 3-85:
19. Return to vCenter, right click on VM, go to NetApp SnapCenter > Detach Virtual Disk.
Figure 3-86:
22
21
Figure 3-87:
23
Figure 3-88:
24. Return to the RDP to the SQL, and navigate to Computer Management > Disk Management to see
that the mounted backup is gone.
Figure 3-89:
Figure 4-1:
Figure 4-2:
Figure 4-3:
9. Click OK.
9
Figure 4-4:
11
Figure 4-6:
13
Figure 4-7:
Figure 4-8:
15. Once the Objects pane loads you should see “Associated Storage Capability” Profiles.
16. Optionally, you can generate new SCPs for all datastores by pressing Global auto-generate profiles.
17. Return to the previous menu for the VASA Provider for ONTAP.
17 16
15
Figure 4-9:
Figure 4-10:
19. Observe the available SCPs, and the options to create or clone new ones.
20. Return to the previous menu for the VASA Provider for ONTAP.
20
19
Figure 4-11:
Figure 4-12:
22. Observe two optional thresholds that can be set for Volume and Aggregate alarms.
22
Figure 4-13:
2 1
Figure 4-14:
3. Click Advanced.
Figure 4-15:
Figure 4-16:
Figure 4-17:
6. Log in with User Name administrator, and Password Netapp1!, and click OK.
Figure 4-18:
Figure 4-19:
4.2 Use Datastore Provisioning Wizard for NAS Backed VVOL Creation
Virtual volumes in vSphere enable hypervisors to offload storage related operations to the underlying storage
layer. When combined with NetApp's ONTAP, the Virtual Storage Console allows management of storage related
functionality from the vSphere Client to offload cloning operations and storage creation eliminating overhead in
the vSphere layer. This lab activity demonstrates how to set up virtual volume storage on the NFS protocol.
1. In the Storage navigation pane, expand the datacenter, demo.netapp.com.
2. Right-click on the datacenter, and scroll down to VASA Provider for ONTAP > Provision VVOL
Datastore.
Figure 4-20:
Figure 4-21:
Figure 4-22:
9. Confirm that the Storage System selected is cluster1, and the SVM is svm1, then click Next.
Figure 4-23:
10. Since there is no FlexVol created, click Next to create them in the following step.
10
Figure 4-24:
Figure 4-25:
14
15
16
17
Figure 4-26:
18. Click Add again, and repeat the steps above to create “nfs_vvol_fv2”.
Figure 4-27:
Figure 4-28:
Figure 4-29:
21
22
Figure 4-30:
Figure 4-31:
24
Figure 4-32:
25
Figure 4-33:
26. Click on the Refresh icon while on the Storage section in the Navigation pane.
Figure 4-34:
28
29
27
Figure 4-35:
4.3 Use the Datastore Provisioning Wizard for SAN Backed VVOL Creation
Virtual volumes in vSphere enables hypervisors to offload storage related operations to the underlying storage
layer. When combined with NetApp ONTAP, the Virtual Storage Console allows management of storage related
functionality from the vSphere Client to offload cloning operations and storage creation, eliminating overhead in
the vSphere layer. This activity demonstrates how to set up virtual volume storage on the iSCSI protocol.
1. In the Storage navigation pane, expand the datacenter, demo.netapp.com.
2. Right-click on the datacenter and scroll down to VASA Provider for ONTAP > Provision VVOL
Datastore.
Figure 4-36:
Figure 4-37:
Figure 4-38:
9. Confirm that the Storage System selected is cluster1, and the SVM is svm1, then click Next.
Figure 4-39:
10. Since there is no FlexVol created, click Next to create one in the following step.
10
Figure 4-40:
Figure 4-41:
14
15
16
17
Figure 4-42:
Figure 4-43:
19. Repeat the steps above to create “iscsi_vvol_fv2”, then click OK.
Figure 4-44:
Figure 4-45:
21
22
Figure 4-46:
Figure 4-47:
24
Figure 4-48:
25
Figure 4-49:
26. Wait for the Recent Tasks to be done for the hbas to rescan.
27. Click on the Refresh icon while on the Storage section in the Navigation pane.
26
Figure 4-50:
29
30
28
Figure 4-51:
Figure 4-52:
2. Click on the icon with the small green plus + and a yellow scroll picture to create a new VM storage
policy.
Figure 4-53:
Figure 4-54:
6. Take note that the Common Rules option is for the hosts, while the Rule-set options are data services
provided by the datastores. Click Next.
Figure 4-55:
7. Leave unchecked the option for “Use common rule in the VM storage policy”.
8. Click Next.
Figure 4-56:
13
Figure 4-57:
14. Observe the “Compatible” line, and the VVOL created in the previous steps should be listed below.
15. Click Next.
14
15
Figure 4-58:
Figure 4-59:
4
1
5
2
6
Figure 4-60:
Figure 4-61:
9. Explore additional options available (i.e., Capability sets, Default profiles, Connectivity with Hosts,
Protocol Endpoints).
Figure 4-62:
Figure 4-63:
3. Explore the options available to see how the VVOL is mounted to the ESX hosts.
Figure 4-64:
5
6
7
4
Figure 4-65:
8. Observe the storage details supplied to vCenter from the NetApp VASA Provider APIs, then click Start in
the “Deduplication Details” window.
Figure 4-66:
10
Figure 4-67:
11
Figure 4-68:
Figure 4-69:
2. Click Advanced.
Figure 4-70:
Figure 4-71:
Figure 4-72:
Figure 4-73:
7. Navigate to SVMs.
8. Double-click on svm1.
Figure 4-74:
9. Click Volumes.
10. Optionally, filter the Name column for “vvol”, observe the Flexible Volumes that were created with the
Datastore Provisioning Wizard.
10
Figure 4-75:
Figure 4-76:
12
Figure 4-77:
13. Click on SVM Settings, and examine the Export Policies created for you under Assigned Objects.
Figure 4-78:
Figure 4-79:
Figure 4-80:
5. Highlight cluster1.
6. Click Next.
Figure 4-81:
7. From the VM Storage Policy drop down menu, select the previously created DEMO VM Storage
Policy.
Figure 4-82:
10
11
Figure 4-83:
12
Figure 4-84:
Figure 4-85:
Figure 4-86:
2
Figure 4-87:
5
Figure 4-88:
6. Open OnCommand System Manager, and find the FlexVolume that increased. Take note of the $ Used
and the Available Space.
7. Click on the Storage Efficiency tab, and take note of the “Deduplication Savings” figures. (If you do not
see a change you may have previously had this open, and will need to click Refresh.
Figure 4-89:
Figure 4-90:
12. (Optional) Repeat with snapshot 3+, and try taking some with the VM started and running, then
continue to see the same results.
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.
®
Go further, faster
© 2017NetApp, 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, Data ONTAP®,
ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registered
trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or
registered trademarks of their respective holders and should be treated as such.