Table of Contents - VMware · Table of Contents Lab Overview - HOL-2005-02-HCI - Virtual Volumes ... with VMware Hands-on-Labs, ... With Virtual Volumes, there are two big changes

Table of ContentsLab Overview - HOL-2005-02-HCI - Virtual Volumes (VVOLs) and Storage Policy BasedManagement..................................................................................................................... 2

Lab Guidance .......................................................................................................... 3Module 1 - Overview and Requirements (30 minutes) ...................................................... 9

Introduction .......................................................................................................... 10Overview and Requirements ................................................................................. 11Benefits................................................................................................................. 20Requirements........................................................................................................ 23Conclusion............................................................................................................. 25

Module 2 - Virtual Volume Architecture (30 minutes) ..................................................... 26Introduction .......................................................................................................... 27Key Components .................................................................................................. 28Configuration Review ............................................................................................ 35Conclusion............................................................................................................. 47

Module 3 - Provisioning Virtual Volumes (45 minutes) .................................................... 48Introduction .......................................................................................................... 49Working with Nimble Virtual Volumes ................................................................... 50Conclusion ............................................................................................................ 66

Module 4 - Storage Policy Based Management and Virtual Volumes Replication(45minutes).......................................................................................................................... 67

Introduction........................................................................................................... 68Array Based Replication with Nimble Storage ....................................................... 69Conclusion........................................................................................................... 107

Module 5 - Virtual Volumes with SRM Integration (Demo - 15 minutes)........................108Introduction ........................................................................................................ 109SRM and VVols Demo .......................................................................................... 110Conclusion .......................................................................................................... 111

HOL-2005-02-HCI

Page 1HOL-2005-02-HCI

Lab Overview -HOL-2005-02-HCI - Virtual

Volumes (VVOLs) andStorage Policy Based

Management

HOL-2005-02-HCI


Lab GuidanceNote: It will take more than 90 minutes to complete this lab. You shouldexpect to only finish 2-3 of the modules during your time. If you are familiarwith VMware Hands-on-Labs, you may be familiar with the "Module Switcher".This lab does NOT be use the Module Switcher and all modules areindependent of each other. Additionally, this lab is part of a "shared vPod" andmay include VM's, vApps, and components you will not use throughout yourVVols learning. You may start at the beginning of any module and proceedfrom there. You can use the Table of Contents to access any module of yourchoosing.

The Table of Contents can be accessed in the upper right-hand corner of theLab Manual.

Virtual Volumes (VVols) is an integration and management framework that virtualizesSAN/NAS arrays, enabling a more efficient operational model that is optimized forvirtualized environments and centered on the application instead of the infrastructure.

VVols simplifies operations through policy-driven automation that enables more agilestorage consumption for virtual machines and dynamic adjustments in real time, whenthey are needed. It simplifies the delivery of storage service levels to individualapplications by providing finer control of hardware resources and native array-baseddata services that can be instantiated with virtual machine granularity.

With Virtual Volumes (VVols), VMware offers a new paradigm in which an individualvirtual machine and its disks, rather than a LUN, becomes a unit of storagemanagement for a storage system. Virtual volumes encapsulate virtual disks and othervirtual machine files, and natively store the files on the storage system.

This lab will guide you through the introduction, provisioning, and advance features ofVVols.

Lab Module List:

• Module 1 Overview and Requirements - (30 minutes) (Basic) High leveloverview of Virtual Volumes, add new Virtual Volume to vCenter.

• Module 2 - Virtual Volumes Architecture - (30 minutes) (Basic) DetailedVirtual Volumes Architecture including Key Components and their usage in Lab.

• Module 3 - Provisioning Virtual Volumes - (30 minutes) (Intermediate) HandsOn End-to-End (Storage Admin to VI Admin) Provisioning.

• Module 4 - Storage Policy Based Management with Virtual VolumeReplication - (45 minutes) (Advanced) Learn the true power of Virtual Volumesvia Storage Policy Management.

• Module 5 - Virtual Volumes with SRM Integration - (15 minutes) (Demo)Virtual Volumes Array-Based Replication and Fail Over with Nimble Storage.

HOL-2005-02-HCI


Lab Captains:

• Tim Koishor, Sr. Systems Engineer, US, TX - Dallas

Platform Partners:

• Nimble

This lab manual can be downloaded from the Hands-on Labs Document site found here:

http://docs.hol.vmware.com

This lab may be available in other languages. To set your language preference and havea localized manual deployed with your lab, you may utilize this document to help guideyou through the process:

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

Location of the Main Console

1. The area in the RED box contains the Main Console. The Lab Manual is on the tabto the Right of the Main Console.

2. A particular lab may have additional consoles found on separate tabs in the upperleft. You will be directed to open another specific console if needed.

3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All yourwork must be done during the lab session. But you can click the EXTEND toincrease your time. If you are at a VMware event, you can extend your lab time

HOL-2005-02-HCI


http://docs.hol.vmware.com

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

twice, for up to 30 minutes. Each click gives you an additional 15 minutes.Outside of VMware events, you can extend your lab time up to 9 hours and 30

minutes. Each click gives you an additional hour.

Alternate Methods of Keyboard Data Entry

During this module, you will input text into the Main Console. Besides directly typing itin, there are two very helpful methods of entering data which make it easier to entercomplex data.

Click and Drag Lab Manual Content Into Console ActiveWindow

You can also click and drag text and Command Line Interface (CLI) commands directlyfrom the Lab Manual into the active window in the Main Console.

Accessing the Online International Keyboard

You can also use the Online International Keyboard found in the Main Console.

1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar.

<div class="player-unavailable"><h1 class="message">An error occurred.</h1><div class="submessage"><ahref="http://www.youtube.com/watch?v=xS07n6GzGuo" target="_blank">Try watching this video on www.youtube.com</a>, or enableJavaScript if it is disabled in your browser.</div></div>

HOL-2005-02-HCI


Click once in active console window

In this example, you will use the Online Keyboard to enter the "@" sign used in emailaddresses. The "@" sign is Shift-2 on US keyboard layouts.

1. Click once in the active console window.2. Click on the Shift key.

Click on the @ key

1. Click on the "@ key".

Notice the @ sign entered in the active console window.

HOL-2005-02-HCI


Activation Prompt or Watermark

When you first start your lab, you may notice a watermark on the desktop indicatingthat Windows is not activated.

One of the major benefits of virtualization is that virtual machines can be moved andrun on any platform. The Hands-on Labs utilizes this benefit and we are able to run thelabs out of multiple datacenters. However, these datacenters may not have identicalprocessors, which triggers a Microsoft activation check through the Internet.

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoftlicensing requirements. The lab that you are using is a self-contained pod and does nothave full access to the Internet, which is required for Windows to verify the activation.Without full access to the Internet, this automated process fails and you see this

watermark.

This cosmetic issue has no effect on your lab.

Look at the lower right portion of the screen

HOL-2005-02-HCI


Please check to see that your lab is finished all the startup routines and is ready for youto start. If you see anything other than "Ready", please wait a few minutes. If after 5minutes your lab has not changed to "Ready", please ask for assistance.

HOL-2005-02-HCI


Module 1 - Overview andRequirements (30

minutes)

HOL-2005-02-HCI


IntroductionWelcome to the Virtual Volumes Lab!

In this Module, you will be given an overview of Virtual Volumes (VVols) and add yourfirst VVol to vCenter. You will also learn about the benefits that Virtual Volumes provideas well as the requirements necessary to utilize VMware Virtual Volumes.

HOL-2005-02-HCI


Overview and RequirementsvSphere Virtual Volumes or VVols, implements the core tenants of the VMware SoftwareDefined Storage vision to enable a fundamentally more efficient operational model forexternal storage in virtualized environments, centering it on the application instead ofthe physical infrastructure.

VVols enables application-specific requirements to drive storage provisioning decisionswhile leveraging the rich set of capabilities provided by existing storage arrays. Some ofthe primary benefits delivered by VVols are focused around operational efficiencies andflexible consumption models on a per-application (per-VM) basis at the hypervisor levelusing Storage Policy-Based Management (SPBM).

Virtual Volumes is an industry-wide initiative that allows customers to leverage theunique capabilities of their current storage investments and transition - withoutdisruption - to a simpler and more efficient operational model optimized for virtualenvironments that works across all storage types.

Did you know?

With Virtual Volumes, there are two big changes to how Virtual Machine Snapshots work:

1. Snapshots are no longer managed by vSphere. You still create them the sameway via the vSphere client; however, all of the snapshots are actually managedon the Storage Array.

2. With traditional VMFS based Virtual Machine snapshots, the base disk becomesread-only and all changes are written to delta files. Sounds familiar, right? Onceyou delete a snapshot, those delta files all have to be merged back into the basedisk which is both resource intensive and time consuming. With Virtual Volumes,the base disk remains read/write when a snapshot is taken (the delta snap fileshold the original data when a change is made). When you delete a snapshot yousimply discard the snap delta files since the base disk already contains all of thelatest data.

This results in an incredible benefit in performance and efficiency (with an additionalbenefit being that you no longer have to worry about keeping 'too many' snapshotsaround)!

HOL-2005-02-HCI


Storage Optimized for Virtualized Environments

Virtual Volumes enable Virtual Machine aware storage and policy based managementacross heterogeneous arrays.

Let's jump right in and create a Virtual Volume!

Open Chrome Browser from Windows Quick Launch TaskBar

1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

Launch vSphere using the HTML5 Client

For the purposes of this Hands On Lab, we will be using the HTML5-based vSphereclient.

1. Select RegionA

HOL-2005-02-HCI


2. Click RegionA vSphere Client (HTML)

vCenter Login

1. Select the checkbox for "Use Windows session authentication".2. Click Login

Alternatively, you can enter a User name of [email protected] and apassword of VMware1!

Host and Clusters

1. Hover over the "Menu"2. Select Storage.

HOL-2005-02-HCI


Add Storage

Expand vcsa-01a.corp.local if necessary

1. Right-click RegionA01 datacenter2. Select Storage3. Select New Datastore...

HOL-2005-02-HCI


Select Type

1. Select VVOL2. Click Next

HOL-2005-02-HCI


Name and container selection

In this case, we are creating a VVol that communicates to a Storage Array via an iSCSIbased protocol.

• A Storage Administrator has performed the necessary work in our lab to makethis particular Storage Container accessible. Notice that this disk is being madeavailable via a Nimble Virtual Storage Appliance (VSA).

1. Enter the Datastore Name: VVol-Default2. Choose the "NimOS-VVol-default" as the Backing Storage Container3. Click Next

HOL-2005-02-HCI


Select Hosts Accessibility

1. Select esx-01a and esx-02a host.2. Click Next

HOL-2005-02-HCI


Ready to complete

1. Review settings and click Finish

HOL-2005-02-HCI


Confirm VVol Creation

1. Select RegionA012. Select the Datastores Tab3. Notice that the newly created Virtual Volume (VVol-default) is showing Normal

(online) status.

The Virtual Volume is ready to be used by Virtual Machines!

Congratulations!

In just a few simple steps, you have added a Virtual Volume to your vSphere labenvironment.

If it feels like the exercise you just went through was nothing more than adding a NewDatastore to vCenter, don't worry. Working with Virtual Volumes is meant to provide afamiliar storage experience to Virtual Infrastructure Administrators; however, theyprovide powerful new capabilities that have not existed previously.

In later modules of this lab you will learn about each of the architectural componentsthat drive Virtual Volumes and see first-hand how Storage Administrators perform thenecessary steps to provision storage resources that are consumable via Virtual Volumes.

Virtual Volumes are enabled by features that are exposed via the back-end StorageArray (QoS, Disk Performance Tiers, Snapshotting, Replication, De-Duplication, etc.).Virtual Machines that use Virtual Volumes can leverage the features that you choose via

Software Based Policies, on the fly, without having to make any changes to the StorageArray or re-format LUNs via vSphere.

In the next Lesson you will learn about the benefits that Virtual Volumes provide. Youwill then complete the Module with a review of the Software and HardwareRequirements necessary for Virtual Volumes.

HOL-2005-02-HCI


BenefitsvSphere Virtual Volumes implements the core tenets of the VMware Software-DefinedStorage vision to enable a fundamentally more efficient Operational Model for externalstorage in virtualized environments, centering it on the Application instead of thephysical infrastructure.

Virtual Volumes enables Application-specific requirements to drive storage provisioningdecisions while leveraging the rich set of Capabilities provided by existing StorageArrays.

Read on to learn about some of the primary benefits delivered by Virtual Volumes.

Streamlined Storage Operations

Virtual Volumes simplifies storage operations by automating manual tasks andeliminating operational dependencies between the vSphere Admin and the StorageAdmin. Provisioning is faster, and change management is simpler as the newoperational model is built upon policy-driven automation.

Finer Controls

Virtual Volumes simplifies the delivery of storage service levels to applications byproviding administrators with finer control of storage resources and data services at theVM level that can be dynamically adjusted in real time.

Improved Resource Utilization

Virtual Volumes improves resource utilization by enabling more flexible consumption ofstorage resources, when needed and with greater granularity. The precise consumptionof storage resources eliminates over-provisioning. The Virtual Datastore defines capacityboundaries, access logic, and exposes a set of data services accessible to the virtualmachines provisioned in the pool.

Flexible Consumption Model

Virtual Datastores are purely logical constructs that can be configured on the fly, whenneeded, without disruption and don’t require formatting with a file system.

HOL-2005-02-HCI


Benefits Summary

Historically, vSphere storage management has been based on constructs defined by thestorage array: LUNs and filesystems. A storage administrator would configure arrayresources to present large, homogenous storage pools that would then be consumed byvSphere administrator.

Since a single, homogeneous storage pool would potentially contain many differentapplications and virtual machines; this approach resulted in needless complexity andinefficiency. vSphere administrators could not easily specify specific requirements on aper-VM basis.

Changing service levels for a given application usually meant relocating the applicationto a different storage pool. Storage administrators had to forecast well in advance whatstorage services might be needed in the future, usually resulting in the over-provisioning of resources.

With Virtual Volumes, this approach is fundamentally changed. vSphere administratorsuse policies to express application requirements to a storage array. The storage arrayresponds with an individual storage container that precisely maps to applicationrequirements and boundaries.

HOL-2005-02-HCI


Summary, cont.

Typically, the virtual datastore is the lowest granular level at which data managementoccurs from a storage perspective. However, a single virtual datastore contains multiplevirtual machines, which might have different requirements. With the traditionalapproach, differentiation on a per virtual machine level is difficult.

The Virtual Volumes functionalities allows for the differentiation of virtual machineservices on a per application level by offering a new approach to storage management.

Rather than arranging storage around features of a storage system, Virtual Volumesarranges storage around the needs of individual virtual machines, making storagevirtual machine centric.

Virtual Volumes map virtual disks and their respective components directly to objects,called virtual volumes, on a storage system. This mapping allows vSphere to offloadintensive storage operations such as snapshot, cloning, and replication to the storagesystem.

Now that you understand the Benefits, let's review the Requirements that are necessaryto use Virtual Volumes in our final Lesson of this Module.

HOL-2005-02-HCI


RequirementsVirtual Volumes requires the following Software, Hardware and Licensing Requirements.

Software

The use of Virtual Volumes requires the following software components:

• vCenter Server 6.0 or later Appliance (VCSA) or vCenter Server 6.0 or later forWindows

• ESXi 6.0 or later• vSphere Web Client

Hardware

There are over 150 array models certified for Virtual Volumes from multiple Partnerswith even more on the way.

The use of vSphere Virtual Volumes requires the following hardware components:

• Any Server that is certified for vSphere 6.0 or later that is listed on the VMwareCompatibility Guide

• A third party storage array system that supports vSphere Virtual Volumes and isable to integrate with vSphere through the VMware APIs for Storage Awareness(VASA)

• Depending on the vendor specific implementation, the storage array system mayor may not require a firmware upgrade in order to support vSphere Virtual

HOL-2005-02-HCI


Volumes. Check with your storage vendor for detailed information andconfiguration procedures.

The VMware Compatibility Guide for Virtual Volumes makes it easy to answerrequirement questions like:

• Which array models support VVols?• Which VASA Provider supports which VVols features?• Which array vendors support iSCSI VVols?• ...and many more!

License

The use of vSphere Virtual Volumes requires the following license:

• vSphere Standard• vSphere Enterprise Plus

HOL-2005-02-HCI


http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vvols

ConclusionIn this module you learned about the benefits that Virtual Volumes provides, therequirements necessary for Virtual Volumes and also added your first Virtual Volume tovSphere.

You've finished Module 1

Congratulations on completing Module 1!

If you are looking for additional information on a Virtual Volumes Overview:

• VMware Virtual Volumes Solutions Overview Whitepaper

The Virtual Volumes Compatibility Guide can be found here:

• VMware Compatibility Guide for Virtual Volumes

Proceed to any module below which interests you most.

• Module 2 - Virtual Volumes Architecture (30 minutes) (Basic) Detailed VirtualVolumes Architecture including Key Components and their usage in Lab.

• Module 3 - Provisioning Virtual Volumes (30 minutes) (Intermediate) HandsOn End-to-End (Storage Admin to VI Admin) Provisioning..

• Module 4 - Storage Policy Based Management with Virtual VolumesReplication (45 minutes) (Advanced) Learn the true power of Virtual Volumes viaStorage Policy Management.

• Module 5 - Virtual Volumes with SRM (Demo) (15 minutes) (Advanced)Virtual Volumes and VMware Site Recovery Manager

How to End Lab

To end your lab, click on the END button.

HOL-2005-02-HCI


https://www.vmware.com/files/pdf/products/virtualvolumes/VMware_Virtual_Volumes_SolutionsOverview.pdf

http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vvols

Module 2 - Virtual VolumeArchitecture (30 minutes)

HOL-2005-02-HCI


IntroductionIn this Module you will learn about all of the Key Components that enable VirtualVolumes.

You will then familiarize yourself with each of those working components within our LabEnvironment.

HOL-2005-02-HCI


Key ComponentsThe following module contains descriptions and definitions of the key components ofvSphere Virtual Volumes.

Virtual Volumes (VVols)

Virtual Volumes are considered a type of virtual machine object, which are created andstored natively on the storage array. VVols are stored in storage containers and mappedto virtual machine files/objects such as VM swap, VMDKs and their derivatives.

There are five different types of Virtual Volumes object types and each of them map to adifferent and specific virtual machine file.

• Config - VM Home, Configuration files, logs• Data - Equivalent to a Virtual Machine Disk File (VMDK)• Memory - Snapshots• SWAP - Virtual machine memory swap• Other - vSphere solution specific object

HOL-2005-02-HCI


Vendor Provider (VP)

The vendor provider, also known as the vSphere Storage APIs for Storage Awareness(VASA) provider, is a storage-side software component that acts as a storage awarenessservice for vSphere and mediates out-of-band communication between vCenter Serverand ESXi hosts on one side and a storage system on the other. Storage vendorsexclusively develop vendor providers.

ESXi hosts and vCenter Server connect to the Vendor Provider and obtain informationabout available storage topology, capabilities, and status.

Subsequently vCenter Server provides this information to vSphere clients, exposing thecapabilities around which the administrator might craft storage policies in SPBM.

Vendor Providers are typically setup and configured by the vSphere administrator in oneof two ways:

• Automatically via the array vendors plug-in• Manually through the vCenter Server

HOL-2005-02-HCI


Storage Container (SC)

Unlike traditional LUN and NFS based vSphere storage, the Virtual Volumes functionalitydoes not require preconfigured volumes on a storage side.

Instead, Virtual Volumes uses a storage container, which is a pool of raw storagecapacity and/or an aggregation of storage capabilities that a storage system canprovide to virtual volumes.

Depending on the storage array implementation, a single array may support multiplestorage containers. Storage Containers are typically setup and configured by storageadministrators.

Containers are used to define:

• Storage capacity allocations and restrictions • Storage policy settings based on data service capabilities on a per virtual

machine basis

HOL-2005-02-HCI


Virtual Datastore

A Virtual Datastore represents a storage container in a vCenter Server instance and thevSphere Web Client. A Virtual Datastore represents a one-to-one mapping to the storagesystem’s storage container.

The storage container (or Virtual Datastore) represents a logical pool where individualVirtual Volumes VMDKs are created.

Virtual Datastores are typically setup and configured by vSphere administrators.

HOL-2005-02-HCI


Virtual Datastore Mapping

A one to one mapping of VVols datastore to storage container on the array. If anotherVVols datastore is needed, a new storage container must be created.

HOL-2005-02-HCI


Protocol Endpoints (PE)

Although storage systems manage all aspects of virtual volumes, ESXi hosts have nodirect access to virtual volumes on the storage side. Instead, ESXi hosts use a logical I/Oproxy, called the protocol endpoint, to communicate with virtual volumes and virtualdisk files that virtual volumes encapsulate.

ESXi uses protocol endpoints to establish a data path on demand from virtual machinesto their respective virtual volumes.

Protocol Endpoints are compatible with all SAN/NAS industry standard protocols:

• iSCSI• NFS v3• Fiber Channel (FC)• Fiber Channel over Ethernet (FCoE)

Protocol Endpoints are setup and configured by Storage Administrators.

HOL-2005-02-HCI


Putting it all together

Here you can see the relationships between the Key Virtual Volumes Components,including views from a top-down (VI Admin) perspective and bottom-up (Storage Admin)perspective.

Published Capabilities will vary depending on Array types.

Once all of these components are in place, VI Admin's can easily create VM StoragePolicies to take advantage of Array capabilities as part of automating the SoftwareDefined Datacenter.

HOL-2005-02-HCI


Configuration ReviewNow that you know the different components that make up the Virtual VolumesArchitecture, let's examine how they are configured and utilized in our Lab Environment.

Our Lab is using nested Virtualized technology from HPE: Nimble VSA

Nimble

• The Nimble virtual array is a virtualized instance of NimbleOS developed for usein the VMware HOL. It provides block storage and VMware VVols support.



Launch vSphere using the HTML5 Client

Recall that for the purposes of this Hands On Lab, we will be using the traditional HTML-based vSphere client. (Not Flash)

1. Select RegionA2. Click RegionA vSphere Client

HOL-2005-02-HCI


vCenter Login



Examine Vendor (VASA) Providers

1. Hover over the Home Menu2. Select Storage

HOL-2005-02-HCI


Storage Providers

1. Make certain the focus is on the vCenter level: vcsa-01a.corp.local2. Click Configure3. Select Storage Providers

The Nimble VSA Storage Providers has already been added to the Lab and they are inOnline and Active status.

Virtual Volumes use vSphere Storage APIs (VASA) version 3.0.

As a reminder, these VASA providers are responsible for mediating out-of-bandcommunication between vSphere and Storage Systems. ESXi hosts and vCenterconnect to the Vendor Provider to obtain information about available storage topology,capabilities and status.

Note: The terms, "Storage Provider", "Vendor Provider" and "VASA Provider" can beused interchangeably.

Examine Nimble Storage Folders

1. Open a new Tab in your browser and select the Nimble-OS1 on the bookmarks bar

HOL-2005-02-HCI


Login

1. Login with the User: admin | Password: admin

Inspect Storage

HOL-2005-02-HCI


1. Select Manage2. Select Data Storage

1. In the left-hand navigation menu, Select the "NimOS1-VVol-DS" (This is theNimble Folder that we used to create VVol-default)

Storage Containers are pools of raw storage capacity that a storage system can provideto Virtual Volumes.

Review the usage statistics on the Nimble Storage Container for VVols and note theVolume Type and Protocol indicates VVols via iSCSI.

This Storage Container was created by a Storage Administrator and was used in aprevious module of this lab. As you've seen this Container is visible to a vSphereAdministrator when adding storage via vCenter (done via the 'New Datastore' Wizardwhen selecting 'VVol' as the Virtual Datastore type).

HOL-2005-02-HCI


Examine Nimble Protocol Endpoints

1. From the Manage menu choose Data Access

Notice that there are two Protocol Endpoints of the type iSCSI from this Nimble VSA tovSphere. These represent the in-band connections to both esx-01a and esx-02a.

Protocol Endpoints are used to establish the Data path between Virtual Machines andtheir respective Virtual Volumes. These Protocol Endpoints are using the iSCSI protocol;however, it is possible to use other SAN/NAS industry standard protocols like NFS, FiberChannel and Fiber Channel over Ethernet. In this case, iSCSI protocol endpoints canutilize any iSCSI interface or Fibre Channel connection for IO.

We'll now examine the Nimble configurations...

HOL-2005-02-HCI


Examine Nimble Storage Containers

The Nimble vSphere Plug-in has been installed on both vCenter Servers for you. You maynavigate back to your vSphere tab in chrome to view component. This Plug-in will bevaluable for later modules in this lab. To view the Plug-in follow the below:

1. Return to your vCenter Tab and Navigate to the Menu button2. Choose HPE Nimble Storage.

We'll now inspect the full web interface.

HOL-2005-02-HCI


(Note: Due to the nature of the Hands-on-Lab environment, it may be necessary toadjust the zoom settings on the Chrome browser window to view this plug-in properly -see below for an illustration on this setting. 80% zoom is recommended)

Examine Nimble Storage Containers

1. Select group-nimble-os1

HOL-2005-02-HCI


1. Select VVOL

Here you can see the VVols that are available to vSphere via the Nimble VSA. If youhave completed the previous steps of this Hands On Lab, your vCenter should have 2VVols available as shown.

You may inspect the VVols further before continuing to the next steps.

vSphere Web Client

The Nimble Protocol Endpoints are managed in vCenter.

1. Return to the RegionA vSphere Web Client by selecting the Chrome tab orminimized Windows Taskbar Item

If you need to re-authenticate:



HOL-2005-02-HCI


Managing Protocol Endpoints in vSphere

1. Hover over the Menu2. Select Hosts and Clusters

Manage Protocol Endpoints

1. Select esx-01a.corp.local2. Select the Configure Tab3. Under the Storage category, Click Protocol Endpoints

Notice that the Nimble VSA Protocol Endpoint is configured to use SCSI (leveragingiSCSI). As you learned earlier, Protocol Endpoints are used to establish the Data pathbetween Virtual Machines and their respective Virtual Volumes.

HOL-2005-02-HCI


Examine Virtual Datastores

1. Hover over the Menu2. Select Storage

Datastores

1. Select RegionA012. Click Datastores

Note that there are multiple Virtual Datastores present with type "VVol" that wereadded to vCenter by a VI Admin.

These Virtual Volumes are a one-to-one mapping to their Nimble Storage Containers andare ready for Virtual Machine usage.

Note: Based on the Modules you have completed in this Lab, you will see differentdatastores available. It is safe to continue to your next step if your datastores are notidentical to those listed in the screenshot.

HOL-2005-02-HCI


You have confirmed all of the key VVol Components within our Lab Environment. In alater Lab Module, you will create new Virtual Volumes all the way from End-to-End(Storage Array to vSphere).

HOL-2005-02-HCI


ConclusionIn this Module you learned about the Key Components that drive Virtual VolumesArchitecture and also examined them in action within our Lab Environment.



If you are looking for additional information on Virtual Volumes Architecture, try one ofthese:

• VMware vSphere Virtual Volumes: Getting Started Guide• Virtual Volumes Architecture (Official Virtual Volumes Documentation Guide)


• Module 1 - Overview and Requirements (30 minutes) (Basic) High leveloverview of Virtual Volumes, add new Virtual Volume to vCenter.

• Module 3 - Provisioning Virtual Volumes (30 minutes) (Basic) Hands On End-to-End (Storage Admin to VI Admin) Provisioning..


• Module 5 - Virtual Volumes with SRM (Demo) (15 minutes) (Advanced)Virtual Volumes with VMware Site Recovery Manager

How to End Lab

To end your lab, click on the END button.

HOL-2005-02-HCI


https://www.vmware.com/files/pdf/products/virtualvolumes/vmw-vsphere-virtual-volumes-getting-started-guide.pdf

http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-88742065-3650-42E3-B0C9-6C5496602DFB.html

Module 3 - ProvisioningVirtual Volumes (45

minutes)

HOL-2005-02-HCI


IntroductionIn this Module you will learn how Virtual Volumes are provisioned from end-to-end(Storage Array to vSphere) utilizing multiple Storage Vendor Appliances.

HOL-2005-02-HCI


Working with Nimble Virtual VolumesNimble - Storage Admin Steps

In this lesson you will see the end-to-end provisioning of a new Nimble Virtual Volumebeginning with the steps that a Storage Administrator must perform on the Array andfinishing with the steps that a VI Admin performs to add the VVol to vCenter.

1. Open a New Tab in your Browser2. Select the Nimble-OS1 shortcut on the bookmarks bar.

Login with the User: admin Password: admin

VASA Provider (VVols)

We will be provisioning a Block VVol Datastore on the Nimble Array that is accessible viavCenter using the iSCSI protocol. We will first verify the Nimble array can communicatewith vCenter through VASA (This was pre-configured for you)

1. Select Administration from the menu bar.

HOL-2005-02-HCI


2. Click VMWARE INTEGRATION

Test VASA on Nimble

Note that there is currently a registration for vcsa-01a and the Checkbox labeled VASAProvider (VVols) and Web Client are currently checked

1. Click TEST STATUS

This step was completed in the set up of this lab. This is a critical step to VVolsoperations. Recall that VASA (vStorage APIs for Storage Awareness) is a set of APIs thatenables vSphere vCenter to recognize the capabilities of storage arrays.

Nimble Folders

HOL-2005-02-HCI


Nimble utilizes folders, also referred to as storage containers, to house the virtualvolumes. To view the current folder configuration:

1. Select Manage from the menu bar2. Click Data Storage

View Nimble Folder and Properties

Here you can see the default Folders that were created labeled NimOS1-VVol andNimOS1-VVol-DS

Once vSphere starts using this container for virtual volumes you will see VMDK andother files stored natively within the folder.

Performance Policies

Our final step is to view the Performance Policies

HOL-2005-02-HCI


1. Select Manage from the menu bar2. Click Performance Policies

Performance Policies

There are 25 of pre-created Performance Policies as well as the capability to create ourown. These policies will be used in vSphere during the creation of the VM Storage Policy

HOL-2005-02-HCI


Create a New VVol on the Nimble Storage Array

We will now create a new VVol on the Nimble Array:

1. Select Manage on the menu bar2. Click Data Storage

View Folders

HOL-2005-02-HCI


You are presented with the above screen. VVols on the Nimble Array are created inFolders.

1. Click Folders .

Add Folder

We'll use the Nimble VVols wizard to create our volume

1. Click the "+"

HOL-2005-02-HCI


Create Folder

You are presented with the "Create Folder" dialog box. Follow the example screenshotand instructions below to complete the required fields.

1. Enter "NimOS1-VVol-2" in the Name field2. Choose "VMware virtual volumes" Management Type3. Choose "vcsa-01a" as the vCenter Server4. Enter 10 GiB Usage Limit5. Click Create

HOL-2005-02-HCI


View Created Folder

Upon creation, you are directed back to the Folder View. Notice NimOS1-VVol-2 is nowavailable.

VI Admin Steps

We will now return to the vSphere Web Client to provision our Nimble storage basedVirtual Volume.

1. Click vSphere Web Client on the Windows Task Bar

NOTE - If you need to re-authenticate to vSphere:



HOL-2005-02-HCI


vSphere Web Client

1. Click the vSphere Web Client Browser Tab2. Hover over the Menu and select Shortcuts

Navigate to Storage

1. Click on Storage

You are now presented with a wizard that will walk you through creating a newdatastore.

1. Verify RegoinA01 is set as the location.2. Click Next

HOL-2005-02-HCI


Create New Datastore

Here you will see a list of all existing datastores that have been provisioned.

1. Right-click on RegionA012. Select Storage3. Choose New Datastore

HOL-2005-02-HCI


Choose Type: VVol

In this dialog, we will choose what type of datastore you want to create.

1. Select the VVol radio button2. Click Next

HOL-2005-02-HCI


Name your Datastore

You will need to give your new datastore a name that will be displayed in vCenter. Fortracking purposes, name the datastore the same as you previously did in on the array.

1. Enter NimOS1-VVol-2 in the Datastore name field2. Scroll-down in Backing Storage Container pane and select NimOS1-VVol-23. Click Next

HOL-2005-02-HCI


Choose ESX hosts

We'll need to select the hosts that have access to this newly created Datastore.

1. Select the 2 checkboxes next to esx-01a.corp.local and esx-02a.corp.local.

2. Click Next

HOL-2005-02-HCI


Confirm and Finish

You are presented with a review screen. Review the contents to be sure they match thescreen above.

1. Click Finish

HOL-2005-02-HCI


View Newly Created Datastore

You will be returned to the vCenter view and your newly provisioned datastore will be inthe list.

Congratulations! You've just created a new VVol on the Nimble storage array andpresented it to 2 hosts in your vCenter!

Confirm datastore provisioning to hosts

Let's confirm that newly created datastore is presented to our hosts.

1. Click Menu

HOL-2005-02-HCI


2. Click Hosts and Clusters

View Datastore

1. Click the host esx-02a.corp.local2. Choose Datastores tab from the menu bar3. View NimOS1-VVol-2

At this point your newly created NimOS1-VVol-2 Datastore is ready for use in vSphere!

HOL-2005-02-HCI


ConclusionIn this Module you learned how to successfully provision Virtual Volumes from end-to-end on the Nimble Storage Array and the vSphere Platform.



If you are looking for additional information on Virtual Volumes, try this:

• VMware Virtual Volumes (Official Documentation)





• Module 5 - Virtual Volumes with SRM (Demo) (15 minutes) (Advanced)Virtual Volumes Replication with VMware Site Recovery Manager

How to End Lab

To end your lab click on the END button.

HOL-2005-02-HCI


https://pubs.vmware.com/vsphere-65/index.jsp#com.vmware.vsphere.storage.doc/GUID-0F225B19-7C2B-4F33-BADE-766DA1E3B565.html?resultof=%2522%2557%256f%2572%256b%2569%256e%2567%2522%2520%2522%2577%256f%2572%256b%2522%2520%2522%2576%2576%256f%256c%2573%2522%2520%2522%2576%2576%256f%256c%2522%2520

Module 4 - Storage PolicyBased Management and

Virtual VolumesReplication(45 minutes)

HOL-2005-02-HCI


IntroductionIn this Module you will see the power of the Software Defined Datacenter in action.

By creating and applying Storage Policies to a Virtual Volumes based Virtual Machineyou will learn how easy it is to change the storage characteristics of this VM, on-the-fly,all without requiring an outage.

Before we create Storage Policies, we'll need to create the Nimble Array Replication.

HOL-2005-02-HCI


Array Based Replication with NimbleStorageIntroduction

While VVol support for array based replication is supported by many vendors, in the labwe will be working with the Nimble storage array. Setting up replication with the Nimblearray and vCenter requires a few steps, all of which the lab will cover:

1. Establish replication partners between 2 VVol folders on the Nimble array.2. Create 2 new storage based policy for the Nimble array that controls the

replication schedule of the VM.3. Create a basic VM on Site B which we will assign the the storage based policy.4. Inspect Replication success and recovery options

Establish Replication Partners on the Nimble Array



Launch Nimble-OS1

1. Open a new Tab in your browser and select the Nimble-OS1 on the bookmarksbar.

HOL-2005-02-HCI


Nimble Login

Login with the User: admin | Password: admin

Data Protection

You are presented with the Nimble array dashboard.

1. Choose Manage from the menu bar2. Click Data Protection

HOL-2005-02-HCI


Replication Partner

On the Data Protection page

1. Click Replication Partners2. Select the "+"

Enter Replication Type Information

You will be presented with the "Select Replication Type" dialog.

1. Leave "On-Premises Replication Partner" Selected2. Click Next

HOL-2005-02-HCI


NOTE: Nimble supports Cloud-based VVol Replication via the HPE CloudVolumes - A demonstration video can be seen here: https://youtu.be/j42N0pfN2Cg?t=130

(Headphones are recommended to watch this ~4 minute video demonstration)

Enter Partner Information

You will be presented with the "Partner Creation" dialog in which we will enter allrequired information to connect to our second Nimble array.

1. Partner Name: group-nimble-os22. Hostname/IP: 192.168.210.201 (note: the 3rd octet is "210" as the

destination array is on the secondary side)3. Shared Secret: VMware1!4. Inbound Location: Select the arrow next to default and choose the folder labeled

NimOS1-VVol5. Click Next

HOL-2005-02-HCI


https://youtu.be/j42N0pfN2Cg?t=130

https://youtu.be/j42N0pfN2Cg?t=130

Create Replication Partner

In the QOS dialog, you have the option of creating a policy that sets bandwidth limits onthe replication. In production environments, this might be a requirement. In the lab, wewill not create a policy, thus using all available bandwidth for the replication.

1. Click Create

You will be returned to the "Replication Partners" screen. Initially your connection willhave a status of "unreachable" and connection tests will fail until we've configured thereplication from the secondary array.

Set Up Replication On The Second Nimble Array

Open a new tab in the Google Chrome browser and click the "Nimble-OS2" bookmark.

Login with the User: admin Password: admin

HOL-2005-02-HCI


Data Protection

We will repeat the exact same steps as we previously did on Nimble-OS1 to create thereplication partner. Upon login, you are presented with the Nimble Array dashboard.

1. Choose Manage from the menu bar2. Click Data Protection

Replication Partners

On the Data Protection page

1. Click Replication Partners2. Click the "+" to create a new connection

HOL-2005-02-HCI


Enter Replication Type Information

You will be presented with the "Select Replication Type" dialog.

1. Leave "On-Premises Replication Partner" Selected2. Click Next

HOL-2005-02-HCI


Enter Partner Information

You will be presented with the "Partner Creation" dialog in which we will enter allrequired information to connect to our first Nimble array.

1. Partner Name: group-nimble-os12. Hostname/IP: 192.168.110.201 (note the 3rd octet is "110")3. Shared Secret: VMware1!4. Inbound Location: Select Click the arrow next to default and choose the folder

"NimOS2-VVol".5. Click Next

HOL-2005-02-HCI


Create Replication Partner

1. Click Create

Test Connection

You are returned to the "Replication Partners" screen. Initially the status should belisted as "Unreachable" just as in the set up on the first array.

1. Check the box next to partner set up.2. Click Test

HOL-2005-02-HCI


Test Results on Nimble-OS2

You should be presented with an "Alive" status now. This is because we now haveconfigured both arrays as replication partners.

Test Results on Nimble-OS1

Return to the NimbleOS1 Array and test the status using the previous steps.

1. Select the check box next to the replication partner set up2. Click Test

Both source and destination should be showing "Alive"

Create Replication Storage Policy

1. Click the vSphere Web Client Browser Tab to return to vCenter

HOL-2005-02-HCI


More Storage Policies

In our final section, we will create Storage Policies.

1. Hover over the Menu2. Select Policies and Profiles

VM Storage Policies

HOL-2005-02-HCI


1. In the left navigation pane, click VM Storage Policies2. Click "Create VM Storage Policy"

Enter Policy Name

1. Enter Name: NimbleOS1-VVol-Replication2. Click Next

HOL-2005-02-HCI


View Policy Structure

1. Select "Enable rules for "NimbleStorage" storage" under Datastorespecific rules

2. Click Next

HOL-2005-02-HCI


Generate NimbleStorage Rules

(Note this screen will update as you make selections)

HOL-2005-02-HCI


1. Select Placement2. Select Select "ADD RULE"3. Choose Protection schedule (minutely)4. Choose Next


HOL-2005-02-HCI


1. Snapshot frequency: Every 5 minutes2. Replication partner: group-nimble-os23. Replication frequency: 14. Snapshots to retain on replica: 15. Delete replicas from partner: No


1. Select Replication2. Select Custom3. Choose Next

HOL-2005-02-HCI


Storage Compatibility

1. Confirm storage is available (NimOS1-VVol1)2. Choose Next

HOL-2005-02-HCI


Ready to Complete

Review the settings

1. Click Finish

Create A Replication Policy for Reverse Replication

We need to create a policy on the secondary side that matches the primary side (forreverse replication needs during a failover). As our vCenters are in Enhanced LinkedMode, this task will be done in the same interface and following the same steps from theprevious steps with 3 important differences in configuration:

1. The vCenter Server in focus will be VCSA-01B.CORP.LOCAL2. Name of the Replication: NimbleOS2-VVol-Replication3. Replication Partner: group-nimble-os1

Please proceed to create the policy via previous steps and reference the below image toconfirm the policy is created accurately.

Select Finish to continue

HOL-2005-02-HCI


Create a Replication Virtual Machine

To take full advantage of all Replication and DR options we will be creating our TestVMon the Secondary site:

1. Select Menu2. Select Hosts and Clusters

HOL-2005-02-HCI


New Virtual Machine

1. Right-click RegionB01-COMP012. Select New Virtual Machine...

HOL-2005-02-HCI


Select a Creation Type

1. Confirm that Create a new virtual machine is selected2. Click Next

HOL-2005-02-HCI


Enter VM name

1. Enter Name: Nimble-ReplicationVM2. Confirm that RegionB01 is selected3. Click Next

HOL-2005-02-HCI


Select Compute Resource

1. Select esx-01b.corp.local2. Click Next

HOL-2005-02-HCI


Select Storage Policy

1. In the VM Storage Policy list box, select NimbleOS2-VVol-Replication2. Click Next

HOL-2005-02-HCI


Select VVol

Notice how the available Datastores are automatically separated into Compatible orIncompatible datastores.

NimbleOS2-VVol-Replication is listed under Compatible because we configuredReplication and tagged these volumes properly in previous steps. Note: Depending onwhat modules you have completed in this lab, you may see different CompatibleVolumes.

1. Select NimOS2-VVol12. Verify Automatic is set for Replication Group3. Click Next

HOL-2005-02-HCI


Select Compatibility

1. Leave the default setting and click Next

HOL-2005-02-HCI


Select a Guest OS

1. Leave the default setting and click Next

HOL-2005-02-HCI


Customize Hardware

Since we are using a nested Virtualization environment/lab with limited resources, wewill be configuring a very small VM

1. Set CPU to 12. Set Memory to 128 MB3. Set New Hard Disk to 1 GB4. Click Next

HOL-2005-02-HCI


Review Settings

1. Review the Virtual Machine Summary and click Finish

Return to Nimble-OS2

1. Select the Nimble-OS2 shortcut on the bookmarks bar.

If your session has timed-out re-login with the User:admin Password:admin

HOL-2005-02-HCI


Open Data Storage

We will view the newly created Virtual Machine files on the Nimble Array in the FoldersView.


View VM files

Notice the Nimble-ReplicationVM files are now on Nimble-OS2 and in an Online state

HOL-2005-02-HCI


Return to Nimble-OS1

Return to Nimble-OS1 in the Google Chrome browser

Open Data Storage

We will view the Virtual Machine files that were replicated from Nimble-OS2 to Nimble-OS1 in the Folders View.


HOL-2005-02-HCI


View VM files

Here you can see the VM files that have been replicated.

HOL-2005-02-HCI


Explore the VVol Options via the Nimble Plug-in

1. Select Menu2. Select HPE Nimble Storage

HOL-2005-02-HCI


Select your Nimble Group

1. Select group-nimble-os1

Replicated VVol VMs

(Note: Due to the nature of the Hands-on-Lab environment, it may be necessary toadjust the zoom settings on the Chrome browser window to view this plug-in properly.)

1. Select VVol VM's2. Select Replicated

HOL-2005-02-HCI


(Note: Due to the nature of the Hands-on-Lab environment, it may be necessary toadjust the zoom settings on the Chrome browser window to view this plug-in properly -see below for an illustration on this setting. 80% zoom is recommended)

Select your Action

You may choose 3 actions to take on your VM once it is selected and available

HOL-2005-02-HCI


• Clone• Revert to earlier Point in time snapshot• Delete

1. Check the box next to your VM2. Select the Clone icon

Note that options 2 and 3 will be greyed out as you cannot take action on a VM that isactively being replicated from the upstream VM.

Clone the Replicated VM

The Clone VM dialog box will appear providing you options on on Days/Times you mayclone from.

1. Identify a time (There should only be one option in our lab - recall weconfigured this in our SPBM policy under the "Snapshots to retain on replica = 1"configuration )

2. Choose your location3. Click Clone

HOL-2005-02-HCI


Confirm the Clone Operation

1. Choose Yes

Confirm the Clone on Primary Array

1. Returning to NimbleOS1 Array you can now see our newly created cloneavailable and online

HOL-2005-02-HCI


Confirm the Clone on Primary vCenter

1. Returning to RegionA01 in vCenter you can now see our newly created cloneavailable as well.

At this point your VM is available for a variety of actions including:

1. SPBM assignment2. Power On and use3. Reverse Replication4. Additional Cloning, Snapshots, and Deletion5. etc.

Please feel free to explore these options before continuing to complete this module.

HOL-2005-02-HCI


ConclusionIn this Module you learned how to create and utilize Storage Policies for Virtual Volumesbased Virtual Machines.

The ability to leverage Policies for automation is a Key Tenet of VMware's SoftwareDefined Datacenter Vision.



If you are looking for additional information on Virtual Volumes Storage Policy-BasedManagement, try one of these:

• Virtual Volumes and Storage Policy-Based Management for Databases• Cormac Hogan Blog Series on Virtual Volumes





• Module 5 - Virtual Volumes with SRM (Demo) (15 minutes) (Advanced)Virtual Volumes with VMware Site Recovery Manager.

How to End Lab


HOL-2005-02-HCI


https://blogs.vmware.com/virtualblocks/2015/12/14/virtual-volumes-and-storage-policy-based-management-for-databases/

http://cormachogan.com/virtual-volume-vvols/

Module 5 - VirtualVolumes with SRM

Integration (Demo - 15minutes)

HOL-2005-02-HCI


IntroductionThis module will focus on a demonstration of the capabilities due to be released shortly:SRM support for VVols.

HOL-2005-02-HCI


SRM and VVols DemoClick here: https://youtu.be/duoLkATSLW8 to view the video demonstration of SRM withVVols

(Headphones are recommended)

HOL-2005-02-HCI


https://youtu.be/duoLkATSLW8

ConclusionIn this Module you learned how to configure Array Based Replication with SRM and VVolsIntegration

You've finished Module 5 and the Virtual Volumes (VVOLs)and Storage Policy Based Management Hands On Lab!

Congratulations on completing Module 5 and the HOL-2005-02-HCI - Virtual Volumes(VVOLs) and Storage Policy Based Management Hands On Lab!

If you are looking for additional information on Virtual Volumes Storage Policy-BasedManagement, try one of these:

• Virtual Volumes and Storage Policy-Based Management for Databases• Cormac Hogan Blog Series on Virtual Volumes

Review any module below which interests you most.





How to End Lab


HOL-2005-02-HCI


https://blogs.vmware.com/virtualblocks/2015/12/14/virtual-volumes-and-storage-policy-based-management-for-databases/

http://cormachogan.com/virtual-volume-vvols/

ConclusionThank you for participating in the VMware Hands-on Labs. Be sure to visithttp://hol.vmware.com/ to continue your lab experience online.

Lab SKU: HOL-2005-02-HCI

Version: 20191021-174602

HOL-2005-02-HCI


http://hol.vmware.com/

Documents

Table of Contents - VMware · Table of Contents Lab Overview - HOL-2005-02-HCI - Virtual Volumes ... with VMware Hands-on-Labs, ... With Virtual Volumes, there are two big changes