- PDF Free Download

Size: px

Start display at page:

Download ""

Daniel Owen
6 years ago
Views:

1 STO3305BES Replicating VMware VVols: A technical deep dive into VVol array based replication in vsphere 6.5 VMworld 2017 Claudio Calisto Storage Solutions Architect Nick Dyer Principal SE, Nimble Content: Not for publication #VMworld #STO3305BES

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

4 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

Over Half of Problems Happen Outside Storage Top

Related 2 Configuration Issues 3 Interoperability

performance 5 Host, compute, VM 46% 7% 28% 8% 11%

5 Over Half of Problems Happen Outside Storage Top problems contributing to the App-Data Gap 1 Storage Related 2 Configuration Issues 3 Interoperability Issues 4 Non-storage best practices impacting performance 5 Host, compute, VM 46% 7% 28% 8% 11% *Source: InfoSight analysis across more than 7,500 customers

vsphere to write VMs natively to storage arrays Common storage management tasks are automated Designed to be dynamic,

6 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

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

8 What changes between file and block protocols with VVols File Block Host adapter iscsi initiator (sw/hw) or HBA NFS Client I/O transport Network or fabric Host present Storage LUNs container File system vsphere vsphere managed native (VMFS) VM storage VMDK VVols files Array Storage vsphere Network Mount point managed VMDK VVols files container native (NFS) Storage visibility 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 hosts to VMs and their

& storage array Storage Container: Pool of raw storage capacity that becomes a logical grouping of VVols, seen as a virtual datastore by

of rules that define storage requirements for VMs based on capabilities provided by storage array (same as VSAN) Data Path hosts VM VM VM

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

10 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

11 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 VMworld Snapshots don t suck anymore 8. Easier for IT Generalists 9. One architecture to rule them all Available You Let Snapshots Easier Start Get One 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 in experience space vsphere the now suck Generalists to with rule of heavy anymore storage back them VVols editions lifting all Because You It s An No Don t and array longer more can get need wait architecture in it s use the over-provisioning left have until all a to darkness VVols out, purpose about be the to a get wait not last storage alongside the started built bind a hours VM, I/O or no of minute. manual 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 using wait keep 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 your possibly 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 Content: Not for publication

12 VVol Replication Deep Dive

13 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) Replication done at the VVol level (VM) not the datastore level like SRM (LUN) Replication Groups automatically created on array contain VVol objects VMworld 2017 Designed to be managed in vsphere, not on array side Nimble and 3PAR were both VMware design partners on VVols 2.0 Content: Not for publication

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

14 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

15 VVol Replication diagram VMworld 2017 vsphere Storage Policy (SPBM) VVols Storage Container Replication Group Content: Not for publication Local Array (Fault Domain) Remote Array (Fault Domain)

Preparing for VVol Replication vsphere 3PAR Nimble vsphere 6.

secondary sites Define Storage Policy with replication rules (Components) 3P

3.1 required Remote Copy license Connect arrays via FC or iscsi Define remote targets for Remote

16 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

17 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

18 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

VVol replication or Target array & Storage

drive tiers Remote Copy mode (Periodic only)

other VVol capabilities (i.e. deduplication)

19 Example Storage Policy [3PAR] Need only specify one replication constraint to enable VVol replication or Target array & Storage Container distribution 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

20 Example Storage Policy [Nimble] VMworld 2017 Content: Not for Protection schedule by minute, hour, daily or weekly Can set local and remote snapshot retention policies publication Choose replication partner and frequency Option to delete replicas from partner when source deleted

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

22 Changing a VM s Replication Policy or distribution Select VM Policies, Edit VM Storage Policies

23 Changing a VM s Replication Policy Selecting a Storage Policy with Replication Constraints or distribution

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

25 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 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 Output continued below

26 3PAR SSMC User Interface VMworld 2017 Content: Not for VVol replication info - Remote Copy Group - Remote Copy Role - Remote Copy Status publication

27 Nimble Replication Groups

28 Disaster Recovery with Vvols (With Demos!) 28

29 vsphere Replication Components Protocol Endpoint vcenter VASA Provider VMworld 2017 DR Orchestrator (PowerCLI) Remote Copy Protocol Endpoint vcenter VASA Provider Content: Not for publication Protected Site VVol Storage Container Recovery Site

30 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

31 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

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

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

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

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

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

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

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

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

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

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

42 Demo time! 42

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

44 Demo time! 44

45 Switch to Nimble Replication demo Play STO3305BUS_Dyer_NimbleDemo.mp4 (2:30) 45

46 Closing 46

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

48 Call To Action Find out more While at VMworld: Visit HPE Booth #D301 to talk to our experts Check out VMware Hands On Labs for some hands-on with Nimble VVols and replication VMworld 2017 Anytime: Stalk us @julian_cates Download DR scripts from github Bookmark Around The Storage Block blog Content: Not for publication 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

51 Backup slides 52

52 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. VMworld 2017 Content: Not for publication 53

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

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

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

56 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

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

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

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

Nimble Tech Preview Nimble tech preview released. VVol 2.0 GA with vsphere 6.5 3PAR & Nimble ready on Day 1 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