Nimble Tech Preview Nimble tech preview released. VVol 2.0 GA with vsphere 6.5 3PAR & Nimble ready on Day 1

Size: px

Start display at page:

Download "Nimble Tech Preview Nimble tech preview released. VVol 2.0 GA with vsphere 6.5 3PAR & Nimble ready on Day 1"

Brent Mason
6 years ago
Views:

2 A Brief History of 3PAR, Nimble & VMware VVols Design partnership between HPE and VMware Virtual Volumes VMworld VVol introduced with HPE as 1 of 5 original design partners VVol Beta 3PAR 1 of 3 partners ready on Beta Day 1 Nimble Tech Preview Nimble tech preview released VVol 2.0 GA with vsphere 6.5 3PAR & Nimble ready on Day 1 Aug 2011 Jul 2014 Jun 2015 Nov 2016 May 2012 Mar 2015 Mar 2016 Today 3PAR Reference Platform 3PAR selected as the FC reference platform VVol GA with vsphere 6.0 3PAR 1 of 4 partners ready Nimble GA Nimble releases VVol support Continued development 3PAR, Nimble and VMware continue working to develop and refine VVols

3 Why did VMware create a new storage architecture? Todays exercise: Challenges in external storage architectures LUN Centric storage preallocated into silos No Visibility cannot see inside VMFS volume Poor Efficiency typically overprovisioning LUNs Increased Administration must always go to storage admin Difficult Reclamation space reclamation is a manual process Hardware Centric must use vendor tools & plug-ins Long Provisioning time consuming manual requests Data Services array data services not aligned with VMs Key take-away: There are many hidden challenges with traditional external storage architectures in vsphere which decrease efficiency and increase management

4 What are VMware VVols? New vsphere storage architecture to replace VMFS/NFS Standard (VASA) for all storage vendors to adhere to Enables vsphere to write VMs natively to storage arrays Common storage management tasks are automated Designed to be dynamic, eliminates LUN provisioning Storage array features can be applied to individual VMs Key take-away: VVols provides automated and dynamic management of storage resources and enables storage arrays to interact directly with VMs

5 How VVols transforms storage in vsphere VMFS LUN-Centric Siloed storage pools, array services aligned to LUNs Static Pre-allocated storage, over- provisioned resources Complex Complicated management using vendor specific tools Time-consuming Longer provisioning, manual space reclamation VVols VM-Centric No siloed storage pools, array services aligned to VMs Dynamic Dynamically allocated storage, using only what is needed Simple Simplified management using vsphere interfaces Effortless Instant provisioning, automatic space reclamation

6 What changes between file and block protocols with VVols Host adapter I/O transport Host present File system VM storage Storage visibility File Block iscsi initiator (sw/hw) or HBA NFS Client Network or fabric Storage LUNs container vsphere vsphere managed native (VMFS) VMDK VVols files Array Storage vsphere Network Mount point managed VMDK VVols files container native (NFS) Data store VM level Level VM level

Overview of VVols Storage Architecture Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs

communication for VVols traffic between vcenter Server, ESXi hosts & storage array Data Path Control Path Storage Container: Pool of

7 Overview of VVols Storage Architecture Protocol Endpoint: Logical I/O proxy that serves as the data path between ESXi hosts to VMs and their respective VVols ESXi hosts VM VM VM VM VM vcenter Server SPBM VASA Provider: Software component that mediates out-ofband communication for VVols traffic between vcenter Server, ESXi hosts & storage array Data Path Control Path Storage Container: Pool of raw storage capacity that becomes a logical grouping of VVols, seen as a virtual datastore by ESXi hosts Virtual Volume (VVol): Container that encapsulates VM files, virtual disks and their derivatives Storage Profile: Set of rules that define storage requirements for VMs based on capabilities provided by storage array (same as VSAN) VVOLs Protocol Endpoint VASA Provider Storage Container Storage Array

8 Storage Policy-Based Management 1. Storage Array advertises capabilities via VASA Provider 2. Storage Policies created in vsphere and assigned array capabilities Policy 1 Policy 2 Policy 3 4. SPBM provisions VM on appropriate storage as defined by policy and maintains compliance 3. VMs assigned a Storage Policy based on requirements and SLAs

9 Top Reasons Customers will want to Start Using VVols Now 1. Don t have to go all in 2. Get early experience 3. Get your disk space back 4. Available in all vsphere editions 5. Let the array do the heavy lifting 6. Start using SPBM now 7. Snapshots don t suck anymore 8. Easier for IT Generalists 9. One architecture to rule them all Available You Easier Get One Start Let Snapshots The the your early VM don t architecture using for array is disk VVol to IT now don t SPBM all go a all unit Generalists in experience space vsphere the now suck to with rule of heavy anymore storage back them VVols editions lifting all Because You It s An No Don t and array more longer can wait get need architecture in it s use the over-provisioning left have until all a to darkness VVols purpose out, about be the to a get wait not last storage alongside the started built bind a hours VM, I/O or no manual of minute. feature, engine, using for admin, them more VMFS, I/O -the intensive NFS, LUNs fully How space array nothing same easy manage iscsi, long features reclamation, migration the SPBM to snapshot did license, VM Fiber storage you are that is now keep using wait will more VSAN deletions from Channel, a replace to first within your powerful Storage users switch class who array vsphere VMFS commit, have from cares? vmotion, and citizen thin been one ESX has plus VVols and day better take to your array possibly your ESXi visibility enjoying backups provides has time or from VM-level into automatically will a with unified storage complete vsphere it visibility storage Client faster to resources architecture Web Client? than across vsphere protocols has

10 VVol Replication Deep Dive

0 Nimble and 3PAR first to complete VVol replication implementations (before merger) Nimble and 3PAR were both VMware

11 Introduction Array replication support via SPBM introduced in vsphere 6.5 (VASA 3.0) Nimble supported replication in vsphere 6.0 Nimble and 3PAR first to complete VVol replication implementations (before merger) Nimble and 3PAR were both VMware design partners on VVols 2.0 Replication done at the VVol level (VM) not the datastore level like SRM (LUN) Replication Groups automatically created on array contain VVol objects Designed to be managed in vsphere, not on array side

Components of VVol Replication Fault Domains [new] Something that fails as a whole (3PAR = storage array, Nimble = Nimble group) Replication Groups [new] Replicate VVol-based VMs between fault

12 Components of VVol Replication Fault Domains [new] Something that fails as a whole (3PAR = storage array, Nimble = Nimble group) Replication Groups [new] Replicate VVol-based VMs between fault domains Groups maintain consistent point[s]-in-time 3PAR - Only maintains most recent point in time, which is no older than the most recent RPO Nimble Uses Volume Collections [most recent point for RGs] - plugin (workflows for replication) RPOs can be stretched when adding VMs or VVols to a replication group Groups are in a Source, Target, InTest or FailedOver state Terms Source/Primary/Protected are interchangeable Terms Target/Secondary/Recovery are interchangeable

13 VVol Replication diagram VVols Storage Container vsphere Storage Policy (SPBM) Replication Group Local Array (Fault Domain) Remote Array (Fault Domain)

Preparing for VVol Replication vsphere 3PAR Nimble vsphere 6.

datastores) at primary and secondary sites Define Storage Policy with

remote targets for Remote Copy Create Storage Containers on primary and

14 Preparing for VVol Replication vsphere 3PAR Nimble vsphere 6.5 required Register VASA Provider Mount Storage Containers (VVol datastores) at primary and secondary sites Define Storage Policy with replication rules (Components) 3PAR OS required Remote Copy license Connect arrays via FC or iscsi Define remote targets for Remote Copy Create Storage Containers on primary and secondary arrays vsphere 6.0 or 6.5 NimbleOS required for VASA 3.0 No licenses required Configure source and destination as replication partners Create Folders (storage containers) on source and destination

15 Creating Nimble Folder / Storage Container Nimble folders are used for general organization Setting VVol management type makes it a Storage Container Must set a capacity limit Can optionally set a folder-level performance limit

16 Replication Storage Policies Summary Granular (per VM/Virtual Disk) Empowers vsphere admin No need to coordinate with Storage admin No need to involve Storage admin during disaster recovery Storage admin may need to do some clean-up after a true disaster New Component feature for SPBM allows Components to be defined once and re-used Replication Components contain rules and constraints related to array replication Components are attached to policies which are attached to VMs SPBM maintains compliance to ensure VM resides on storage that can meet policy definition

Example Storage Policy [3PAR] Target array

17 Example Storage Policy [3PAR] Target array & Storage Container Need only specify one replication constraint to enable VVol replication Target & Snapshot CPG drive tiers Remote Copy mode (Periodic only) Desired RPO Minutes (5 min) Where possible, other VVol capabilities (i.e. deduplication) are mirrored at remote site if remote array/cpg allows for it

18 Example Storage Policy [Nimble] Protection schedule by minute, hour, daily or weekly Can set local and remote snapshot retention policies Choose replication partner and frequency Option to delete replicas from partner when source deleted

19 Creating a new VM with replication Choose an existing Replication Group or Automatic

20 Changing a VM s Replication Policy Select VM Policies, Edit VM Storage Policies

21 Changing a VM s Replication Policy Selecting a Storage Policy with Replication Constraints

22 Changing a VM s Replication Policy Selecting either a common or per storage object Replication Group

23 Replication Groups on the Array s932 cli% showvvolvm -sc SanJoseContainer -rcopy (MB) VM_Name GuestOS VM_State Num_vv Physical Logical VMSanJose other26xlinux64guest Unbound TinyVM2 other26xlinux64guest Unbound TinyVM1 other26xlinux64guest Unbound TinyVM3 other26xlinux64guest Unbound VMFremont other26xlinux64guest Unbound total Output continued below RcopyStatus RcopyGroup RcopyRole RcopyLastSyncTime Synced VMSanJosgrp_3c12e41 Primary :20:00 PDT Synced TinyVM2grp_80ed051 Primary :22:00 PDT None NA Synced TinyVM3grp_1a3d5ba.r99931 Secondary :20:10 PDT Synced VMFremongrp_ca4027f.r99931 Secondary :21:10 PDT

24 3PAR SSMC User Interface VVol replication info - Remote Copy Group - Remote Copy Role - Remote Copy Status

25 Nimble Replication Groups

26 Disaster Recovery with VVols 26

27 vsphere Replication Components vcenter DR Orchestrator (PowerCLI) vcenter ESXi ESXi ESXi ESXi Protocol Endpoint VASA Provider Protocol Endpoint VASA Provider Remote Copy Protected Site VVol Storage Container Recovery Site

28 Types of Disaster Recovery operations Planned Failover Unplanned Failover Test Failover Controlled Typically used for disaster avoidance, planned maintenance or relocating VMs Can be per VM or all VMs Primary and recovery site reverse roles Uncontrolled Typically loss of power or hardware failure Not usually a per VM event, all VMs recovered Primary and recovery site reverse roles Controlled Typically used to validate VM recoverability Non-impactful Replica VMs cloned and made visible to vsphere at recovery site

Recovery and Cloning Nimble vcenter Plugin Snapshot based recovery Choose from all available snapshots Local VM Recovery In-place restore of VM Cloned as a new VM Local Virtual Disk

29 Recovery and Cloning Nimble vcenter Plugin Snapshot based recovery Choose from all available snapshots Local VM Recovery In-place restore of VM Cloned as a new VM Local Virtual Disk Recovery In-place restore of virtual disk Cloned as a new disk to same VM Cloned as a new disk to different VM Remote VM Recovery Cloned as new VM at remote site No need to stop replication

30 Planned Failover Workflow with VVols Before Failover vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi Source VVol Replica VVol Array Storage Container Source Replication Group Sw 1 C 1 D 1 Sn 1 C 2 D 2 Sw 2 Storage Container Target Replication Group C 1 D 1 Sn 1 C 2 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

31 Planned Failover Workflow with VVols Discover VM-to-group relationship (Get-SpbmReplicationGroup/Pair) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array D 1 Sn 1 D 2 D 1 Sn 1 D 2 Array Sw 1 Sw 2 C 3 D 3 C 3 D 3 Local Site Remote Site

32 Planned Failover Workflow with VVols Power down source VMs (stop-vm) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array D 1 Sn 1 D 2 D 1 Sn 1 D 2 Array Sw 1 Sw 2 C 3 D 3 C 3 D 3 Local Site Remote Site

33 Planned Failover Workflow with VVols Perform final sync (Sync-SpbmReplicationGroup) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array D 1 Sn 1 D 2 D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

34 Planned Failover Workflow with VVols Issue a planned failover (Start-SpbmReplicationFailover) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Replication Group D 1 Sn 1 D 2 Failed-over Target Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

35 Planned Failover Workflow with VVols Register newly-failed-over VMs (New-VM) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Replication Group D 1 Sn 1 D 2 Failed-over Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

36 Planned Failover Workflow with VVols Apply an SPBM replication Policy to the VMs (Set-SpbmEntityConfiguration) vcenter vsphere API PowerCLI vsphere API Replication Policy vcenter ESXi VM1 VM2 VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Replication Group D 1 Sn 1 D 2 Failed-over Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

37 Planned Failover Workflow with VVols Unregister VMs at primary site (remove-vm) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Replication Group D 1 Sn 1 D 2 Failed-over Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

38 Planned Failover Workflow with VVols Power up VMs at Failed-Over site (start-vm) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Replication Group D 1 Sn 1 D 2 Failed-over Replication Group D 1 D 2 Sn 1 Sw 1 Sw 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

39 Planned Failover Workflow with VVols Power up VMs at Failed-Over site (Start-SpbmReplicationReverse) vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Target Replication Group D 1 Sn 1 D 2 Failed-over Source Replication Group D 1 D 2 Sn 1 Sw 1 Sw 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

40 Demo time! 40

41 Switch to 3PAR Replication unplanned failover demo Play STO3305BUS_Siebert_UnplannedFailover.mp4 (5:11) 41

42 Switch to Nimble Replication demo Play STO3305BUS_Siebert_NimbleDemo.mp4 (2:30) 42

43 Closing 43

44 The HPE 3PAR & Nimble advantage with VVOLs Solid and mature 6+ years of development VMware design partner Fibre Channel reference platform Simple and reliable Internal VASA Provider No external failure points Zero step installation Innovative and efficient Snapshots on different tiers Smallest capacity VM footprint Manage VVols folder by folder Rich and powerful App level optimized storage policies Architectures optimized for VVols VM Recovery directly from vcenter

45 Call To Action Find out more While at VMworld: Visit HPE Booth #600 to talk to our experts Check out HOL-1827 for some hands-on with Nimble VVols and replication Attend VVols Partner Panel session ID # Attend HPE in-booth VVol sessions Anytime: Stalk us Download DR scripts from github Bookmark Around The Storage Block blog 3PAR VVol Key docs: 3PAR VMware VVol Implementation Guide 3PAR VMware VVol Replication Guide Nimble VVol Key docs: VMware Integration Guide VMware vsphere 6 Deployment Considerations

46 Thank You

47 Backup slides 47

48 Two Primaries Window Summarize and simplify this During Planned and Unplanned failover a window exists when you have two source/primary replication groups During this time window, VMs changed as well as added/removed from replication groups, will require resolution when the groups are reversed. With traditional storage, any changes at the original source datastore are completely wiped out With VVols, it s possible to reverse some of the actions taken at the original source site. For example: A VM deleted at the primary is kept alive until the reverse-replication operation is performed. At which point, the VM is recovered, assuming it still exists at the new source site. Adding a new VM to the original source replication group will not be lost, but instead, auto-dismissed from the group when the reverse operation occurs. VM snapshots taken at the source replication group will be lost upon reversal. 48

49 Handling Conflicts with Two Primary Replication Groups Deleting a VM at the original source vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM1 VM2 VM3 ESXi C 1 C 2 C 1 C 2 Array Source Replication Group D 1 Sn 1 D 2 Failed-over Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

50 Handling Conflicts with Two Primary Replication Groups Adding a VM to the original source after fail-over vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM1 VM2 VM4 VM1 VM2 VM3 ESXi C 1 C 4 C 2 C 1 C 2 Array Source Replication Group D 1 D 4 Sn 1 D 2 Failedover Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

51 Planned Failover Workflow with VVols In-conflict VVols are automatically removed from the group, but not destroyed vcenter vsphere API PowerCLI vsphere API vcenter ESXi VM4 VM1 VM2 VM3 ESXi C 1 C 4 C 2 C 1 C 2 Array Source Target Replication Group D 1 D 4 Sn 1 D 2 C 4 D 4 Failed-over Source Replication Group D 1 Sn 1 D 2 Array C 3 D 3 C 3 D 3 Local Site Remote Site

52 Benefits of VVols on Nimble Storage Embedded VASA Provider No need to manage additional resources Highly available VASA Provider Management Automated registration of VP Automatic creation of PE and host access control management Folders Manage VVOLs folder by folder Folders can grow and shrink dynamically Backup and Recovery Replicate VM using array based replication Recover VM using Nimble vcenter Plugin

53 Nimble VVol Implementation Storage Policy Based Management New policy-based framework from VMware Foundation of VMware Software Defined Datacenter control pane Based on the VASA management protocol Nimble Policy Based Management Built-in application abstractions Pick from drop-down list - Exchange, SQL, VDI, Splunk, ESX etc. Auto-selects optimal storage settings Virtual Volumes Makes Nimble storage natively VM aware Enables virtual disk level offload of data services Snapshots, replication, encryption

54 Registering Nimble VASA Provider Done through Nimble Web UI Simply check the box 54

55 Additional SPBM Policy Options Application Policy Protection Schedule QoS / Performance Deduplication Data Encryption All-Flash

56 VVol Replication Objects VVol Storage Container Replication Group VVol Config, Data, RO/RW snapshots and k/v replicated. SWAP and storage policies not replicated Names of Storage Containers and CPGs shared shared between arrays Array A a.k.a Fault Domain Array B

57 Point-in-Time Snapshot for Failover Test [3PAR] VVol Replication Group Snapshot relationship C D C D C D VM1 RO VM1 RO VM1 RO Data & K/V C D C D C D VM2 RO VM2 RO VM2 RO VVol Datastore

58 3PAR VASA Replication Capabilities Built on top of HPE 3PAR Remote Copy rcopytargetcontainer Specifies the combined array sysname and Storage Container. Multiple values possible for each target sysname, one for each Storage Container at that target. Syntax: sysname:storagecontainername rcopymode Specifies requested remote copy mode. Periodic [only mode supported today for VVols] rcopyrpo Remote Copy itself supports synchronous, streaming and multi-target synchronous / periodic (SLD) Specifies periodic sync period. Range: (5min - 1 year) Requires rcopymode be set to Periodic

59 3PAR VASA Replication Capabilities Built on top of HPE 3PAR Remote Copy rcopyremotecpg Specifies the Provisioning Group (a.k.a CPG, a template for the volume physical characteristics, such RAID, and device type) to be used for remote copy at the target site for disk VVols. If not specified defaults to CPG capability, if specified. If not specified, VASA Provider selects a CPG. rcopyremotesnapcpg Specifies the CPG to be used for remote copy at the target site for base volumes One selectable from SPBM dropdown If not specified defaults to same as rcopyremotecpg capability Where possible, other VVol capabilities are mirrored at the remote site. For example, if deduplication is selected at the local site, a replica VVol on the remote array would be created with deduplication, if the remote array and remote CPG allow for it.

60 Disaster Recovery with VVol-based VMs Types of failover Planned Changes the responsibility for mastership of the VVol-based VMs from the Source/Primary site to the Target/Secondary site. Source and Target roles are reversed. Involves: Collecting replicated VM and group information at the Source and Target sites. Powering Down VMs at Source site Issuing a failover operation (Spbm-FailoverReplicationGroup in PowerCLI) Unregistering VMs at the source site Registering the VMs at the failover/target site. Applying a storage policy that allows replication back to the original Source site. Issuing a reverse operation (Spbm-ReverseReplicationGroup in PowerCLI) Optionally powering up the failed-over VMs 60

Disaster Recovery with VVol-based VMs Types of failover Unplanned Changes the responsibility for mastership of the VVol-based VMs from the Source/Primary site to the Target/Secondary site.

61 Disaster Recovery with VVol-based VMs Types of failover Unplanned Changes the responsibility for mastership of the VVol-based VMs from the Source/Primary site to the Target/Secondary site. Source and Target roles are reversed (eventually). When the disaster occurs: Collecting replicated group information at the Target/Recovery site Issuing a failover operation (Spbm-FailoverReplicationGroup in PowerCLI) Registering the VMs at the failover/target site. Applying a storage policy that allows replication back to the original Source site. Optionally powering up the failed-over VMs After the original Source site has recovered from it s disaster: Powering Down VMs at Source site (if needed) Unregistering VMs at the source site Issuing a reverse operation (Spbm-ReverseReplicationGroup in PowerCLI) There s no undo option. Once you issue a Planned or Unplanned failover, the only option is to continue forward. Issue a reverse, and optionally another failover and reverse to bring things back up at the original site. 61

62 Disaster Recovery with VVol-based VMs Types of failover Test Allows testing of replicated VVol-based VMs at the secondary site, by making copies of the replica VVols and exposing them to ESXi hosts for VM testing. Source and Target roles are NOT reversed. Involves: Collecting replicated VM and group information at the Source and Target sites. Issuing a test-failover operation (Start-SpbmReplicationTestFailover in PowerCLI) Registering the new test-vms at the target site. Applying a storage policy that allows replication back to the original Source site To help verify those replication policies are valid. Powering up, testing and powering down the in-test VMs Un-registering the test-vms Issuing a stop-test-failover operation (Stop-SpbmReplicationTestFailover in PowerCLI) Once the test is stopped, all VMs created by the test are destroyed permanently. 62

63 Storage Administrator s Responsibility after a Disaster [may remove this slide] Clean-up of automatically-created replication groups is automatic, unless a true disaster occurs. tbd 63

Your World is Hybrid:

Your World is Hybrid: vsphere Virtual Volumes: The Time is Now Nick Dyer Principal Systems Engineer, UK A Brief History of 3PAR, Nimble & VMware VVols Design partnership between HPE and VMware Virtual