4. The Software-Defined Data Center
Transform storage
by aligning it with
app demands
4
Expand virtual
compute to all
applications
Virtualize the
network for speed
and efficiency
Management
tools give way
to automation
5. VMware Software-Defined Storage
5
vSphere
Storage Policy-Based Mgmt
Virtual SAN
Storage Policy-Based Mgmt
SAN / NAS
vSphere Virtual Volumes
Virtual Datastore
VMware Software-Defined Storage
Virtual Datastore
Bringing the Efficient Operational Model of Virtualization to Storage and Availability
6. VMware Virtual SAN : Hybrid
6
vSphere + Virtual SAN
…
• Software-defined storage built into vSphere
• Runs on any standard x86 server
• Pools flash-based devices into a shared
datastore
• Managed through per-VM storage policies
• Delivers High performance through flash
acceleration
• 2x more IOPS with VSAN Hybrid
• Up to 40K IOPS/host
• Highly resilient - zero data loss in the event of
hardware failures
• Deeply integrated with the VMware stack
Virtual SAN
Hard disksSSD
Hard disks
SSD
Hard disks
SSD
Virtual SAN Datastore
Radically Simple Hypervisor-Converged Storage Software
7. VMware Virtual SAN : All-Flash
7
vSphere + Virtual SAN
…
• Flash-based devices used for caching as
well as persistence
• Cost-effective all-flash 2-tier model:
o Cache is 100% write: using write-intensive,
higher grade flash-based devices
o Persistent storage: can leverage lower cost read-
intensive flash-based devices
• Very high IOPS: up to 90K(1) IOPS/Host
• Consistent performance with sub-
millisecond latencies
Virtual SAN All-Flash
Virtual SAN All-Flash Datastore
NEW in 6.0
SSDs SSDs SSDs
(1) All performance numbers are subject to final benchmarking results. Please refer to guidance published at GA
Extremely High Performance with Predictability
8. 8
Hosts per Cluster
VMs per Host
VMs per Cluster
IOPS per Host
(70/30 R/W)
Snapshot depth per VM
Virtual Disk size
Enterprise-Class Scale and Performance
Virtual SAN 5.5
32
100
3200
20K
2
2TB
Virtual SAN 6
Hybrid
64
200
6400
40K
32
62TB
Virtual SAN 6
All-Flash
64
200
6400
90K
32
62TB
2x4.5x
2x
2x
16x
31x
Enhancements
in 6.0
Note: All performance numbers are subject to final benchmarking results. Please refer to guidance published at GA
2x
9. Virtual SAN Simplifies and Automates Storage Management
Per VM Storage Service Levels From a Single Self-tuning Datastore
Storage Policy-Based Management
Virtual SAN
Shared Datastore
vSphere + Virtual SAN
SLAs
Software Automates
Control of Service Levels
No more LUNs/Volumes!
Policies Set Based
on Application Needs
Capacity
Performance
Availability
Per VM
Storage Policies
9
10. Virtual SAN is Resilient To Rack, Host, Network or Disk Failures
Rack A Rack B
• Automated and controlled through VM-level policy
• Zero data loss and zero downtime despite
hardware failures:
Disk
Host
Network
Rack
• Interoperable with vSphere HA and Maintenance
Mode
Virtual SAN Datastore
NEW
10
11. Scale UP
Add more Disks
IOPSCapacity
10 TB
100 TB
8.8 PB
Scale OUT
Add more
nodes
Elastic
Grow or shrink on demand
Granular
Add single nodes or disks
Non-disruptive
No app downtime
Virtual SAN Enables Elastic Scaling of Performance and Capacity
No More Complex Forecasting & Large Upfront Investments
“Virtual SAN lets us buy what we need
when we need it. With non-disruptive
scaling we can add capacity or increase
performance at any time without
interrupting our operations.”
— Chris Reynolds
Senior Systems Engineer
11
12. Virtual SAN
Virtual SAN Puts The App In Charge
12
VM-centric Service Levels for Simpler and Automated Storage Management Through App-centric Approach
1. Define storage
policy
2. Apply policy at
VM creation
✖ Hardware-centric, vendor-
specific management
✖ Slow provisioning, rigid
storage constructs (LUNs,
Volumes)
✖ Data services aligned to
storage container, not directly
with VM needs
✖ Frequent data migrations
Fast, VM-centric provisioning
No need to manage LUNs, Vols.
Resources and data service are
automatically provisioned and
maintained
Easy to change without data
migration
Today
Virtual SAN
Storage Policy
Capacity
Availability
Performance
Virtual SAN DatastoreLUN
LUN
14. VMware Virtual SAN Architecture
• Each ESX host contributes SSD and magnetic
disk capacity
• Virtual SAN aggregates these resources into one
global Datastore per vSphere cluster
• Each VM home directory and each virtual disk is
represented by a VSAN object
• Virtual machines run on the ESX hosts that belong
to the cluster
• HA/DRS ensures the VM is restarted if a host
crashes
• Virtual SAN objects can be split into multiple
components for performance and data protection.
This is governed by the storage policies.
VSAN Cluster
ESX ESX
VM
Virtual Disk
VSAN Object
Replica-1 Replica-2
Storage Policy
ESX
Witness
14
15. Virtual SAN Scalable Architecture
• Scale up and Scale out architecture – granular and linearly storage, performance and compute
scaling capabilities
– Per magnetic disks – for capacity
– Per flash based device – for performance
– Per disk group – for performance and capacity
– Per node – for compute capacity
disk group disk group disk group
VSAN network VSAN networkVSAN network
vsanDatastore
HDD
disk group
HDD HDD HDD
disk group
VSAN network
HDD
scaleup
scale out
15
16. Virtual SAN 6.0 Enables Both Hybrid or All-Flash Architectures
16
Hybrid All-Flash
40K IOPS/Host 90K IOPS/Host
predictable sub-millisecond latency
New!
Caching
SSD, PCIe, Ultra DIMM etc.
Read cache / Write buffer
SSD, PCIe, Ultra DIMM etc.
Write-only buffer
Magnetic Disks Flash Devices
Data
Persistence
18. Technical Characteristics
Virtual SAN is a cluster level feature similar to:
– vSphere DRS
– vSphere HA
– Virtual SAN
Deployed, configured and manage from vCenter through the vSphere Web Client (ONLY!).
– Radically simple
• Configure VMkernel interface for Virtual SAN
• Enable Virtual SAN by clicking Turn On
18
19. Virtual SAN Implementation Requirements
• Virtual SAN requires:
– Minimum of 3 hosts in a cluster configuration
– All 3 host MUST!!! contribute storage
• vSphere 5.5 U1 or later
– Maximum of 32 hosts (VSAN 5.5)
– Maximum of 64 hosts (VSAN 6.0)
– Locally attached disks
• Magnetic disks (HDD)
• Flash-based devices (SSD)
– Network connectivity
• 1GB Ethernet
• 10GB Ethernet (preferred)
esxi-01
local storage local storage local storage
vSphere 5.5 U1 Cluster
esxi-02 esxi-03
cluster
HDDHDD HDD
19
20. Storage Policy-based Management (SPBM)
• SPBM is a storage policy framework built into vSphere that enables virtual machine policy
driven provisioning
• Virtual SAN leverages this new framework in conjunction with VASA API’s to expose storage
characteristics to vCenter:
– Storage capabilities
• Underlying storage surfaces up to vCenter and what it is capable of offering
– Virtual machine storage requirements
• Requirements can only be used against available capabilities
– VM storage policies
• Construct that stores virtual machine’s storage provisioning requirements based on storage capabilities
20
21. Virtual SAN Disk Groups
• Virtual SAN uses the concept of disk groups to pool together flash devices and magnetic disks
as single management constructs.
• In VSAN 5.5, disk groups are composed of at least 1 flash device and 1 magnetic disk.
– Flash devices are use for performance (Read cache + Write buffer).
– Magnetic disks are used for storage capacity.
– Disk groups cannot be created without a flash device.
disk group disk group disk group disk group
Each host: 5 disk groups max. Each disk group: 1 SSD + 1 to 7 HDDs
disk group
HDD HDDHDDHDDHDD
21
22. Virtual SAN Objects
• Virtual SAN manages data in the form of flexible data containers called objects. virtual machine
files are referred to as objects.
• Virtual machines files are referred to as objects.
– There are four different types of virtual machine objects:
• VM Home
• VM swap
• VMDK
• Snapshots
• Virtual machine objects are split into multiple
components based on performance and availability
requirements defined in VM Storage
profile.
disk group disk group disk group disk group
Each host: 5 disk groups max. Each disk group: 1 SSD + 1 to 7 HDDs
disk group
VSAN network VSAN network VSAN network VSAN networkVSAN network
vsanDatastore
HDD HDD HDD HDD HDD
22
23. Virtual SAN Components
• Virtual SAN components are chunks of objects distributes across multiple hosts in a cluster in
order to tolerate simultaneous failures and meet performance requirements.
• Virtual SAN utilizes a Distributed RAID architecture to distribute data across the cluster.
• Components are distributed with the use of two
main techniques:
– Striping (RAID0)
– Mirroring (RAID1)
• Number of component replicas and copies created is
based on the object policy definition.
disk group disk group disk group disk group disk group
VSAN network VSAN network VSAN network VSAN networkVSAN network
vsanDatastore
replica-1 replica-2
RAID1
HDD HDD HDD HDD HDD
23
24. Virtual SAN Network
• New Virtual SAN traffic VMkernel interface.
– Dedicated for Virtual SAN intra-cluster communication and data replication.
• Supports both Standard and Distributes vSwitches
– Leverage NIOC for QoS in shared scenarios
• NIC teaming – used for availability and not for bandwidth aggregation.
• Layer 2 Multicast must be enabled on physical switches.
– Much easier to manage and implement than Layer 3 Multicast
Management Virtual Machines vMotion Virtual SAN
Distributed Switch
20 shares 30 shares 50 shares 100 shares
uplink1 uplink2
vmk1 vmk2vmk0
24
25. 25
Maximum Flexibility Maximum Ease of Use
…using VMware Virtual SAN
Compatibility Guide (VCG) (1)
Choose from over 100 HDDs,
150 SDDs, 80 Controllers …
Pick one of 40+ OEM validated
server configurations (2)
Software + Hardware
Component Based Virtual SAN Ready Node
(1) Components must be chosen from Virtual SAN HCL, using any other components is unsupported – see Virtual SAN VMware Compatibility Guide
(2) VMware continues to update/add list of the available Ready Nodes, please refer to Virtual SAN VMware Compatibility Guide or latest list
Ways to Build a Virtual SAN Node for Service Providers
Completely Hardware Independent
26. Use Cases & Interoperability
VMware Virtual SAN
26
27. Virtual SAN 6.0 Now Ready For Business-Critical Apps
27
VDI DR Test/Dev
Virtual Infrastructure
Best storage for VMs
Optimized for Virtual Infrastructure
Enterprise-class
Ready for business critical apps
Business
Critical Apps
28. Virtual SAN is Deeply Integrated with VMware Stack
28
Ideal for VMware Environments
vMotion
vSphere HA
DRS
Storage vMotion
vSphere
Snapshots
Linked Clones
VDP Advanced
vSphere Replication
Data Protection
VMware View
Virtual Desktop
vRealize Operations
vRealize Automation
IaaS
Cloud Ops and Automation
Site Recovery Manager
Disaster Recovery
Site A Site B
Storage Policy-Based Management
vCloud Director for Service Provider
29. Horizon View
• Virtual SAN and Horizon View:
– Handle peak performance such as boot, login, read/write storms
– Seamless granular scaling without huge upfront investments
– Support high VDI density
– Support high end virtual desktop GPU requirements
• Virtual SAN is compatible with the following Horizon View
versions:
– Horizon View 5.3 (SPBM manually implemented)
– Policies maintained across operations such as refresh/refresh – no need to re-associate
vSphere + Virtual SAN
Hard disksHard disks
SSD SSD Hard disks
SSD
…
Full Clone Policies
– FTT = 1 for persistent
– FTT = 0 for non-persistent
– Provisioning 100% reserved
Linked Clone Policies
– OS Disk: FTT = 1 for dedicated pools
– OS Disk: FTT = 0 for floating pool
– Replica Disk: FTT = 1
– Replica Disk: Read Cache Reservation 10%
– Provisioning: Thin
29
30. vSphere Replication and Site Recovery Manager
• Virtual SAN is compatible with:
– vSphere Replication 5.5 (vSphere Web Client)
– SPBM configured as part of replication
– vCenter Site Recovery Manager 5.5 (vSphere C#)
– SRM configuration based on VR replication
• vSphere Replication & vCenter Site Recovery
Manager
– Asynchronous replication – 15 minute RPO
– VM-Centric based protection
– Provide automated DR operation & orchestration
– Automated failover – execution of user defined plans
– Automated failback – reverser original recovery plan
– Planned migration – ensure zero data loss
– Point-in-Time Recovery – multiple recovery points
– Non-disruptive test – automate test on isolated network
vCenter
Server
VR/SRM
vSphere
VMFS
vCenter
Server
VR/SRM
production site recovery site
replication
Hard disks
SSD
vSphere + Virtual SAN
Hard
disks
SSD Hard
disks
SSD
30
31. vSphere Data Protection
• Virtual SAN and vSphere Data Protection
– Radically simple to deploy and manage
– Integrated User Interface – vSphere Web Client
– Highly available storage solution
– Increase operation efficiency
• vSphere Data Protection Advanced 5.5
– Source and target De-duplication capabilities
– Bidirectional replication capabilities
– Secure, easy, reliable, network-efficient replication
– Application-consistent backup and recovery capabilities
– Higher RTO and RPO – 24 hours RTO, minutes – hours RPO
– Incorporated technologies
• vStorage API for Data protection
• Change Block Tracking (CBT)
• Avamar variable-length segment algorithm
vCenter
Server
Hard disks
SSD
vSphere + Virtual SAN
Hard
disks
SSD Hard
disks
SSD
vSphere
VMFS
vCenter
Server
31
32. Disaster Recovery For The Software-Defined Data Center
Production Site
vSphere
Site Recovery Manager
Recovery Site
vSphere
Site Recovery Manager
• Centralized recovery plans enables DR
scale for thousands of VMs
• DR workflow automation reduces OpEx
on DR management
Site Recovery Manager
• Server side economics
lower storage costs
• Hyper-convergence on x86
platform reduces DR
footprint
Virtual SAN
• VM-centric, storage-independent replication
simplifies protection
• Flexible storage topologies (External to Virtual
SAN)
vSphere Replication
• Storage-efficient dedupe
reduces storage investments
• WAN-efficient backup data
replication enables basic DR
vSphere Data Protection
vSphere Replication
VDP backup replication
VDP
Backup
Datastore
Virtual SAN Virtual SANExternal Storage
Replication Backup
Datastore
(EMC Avamar)
32
33. vRealize Automation
• vRealize Automation Advanced
complements VMware Virtual
SAN simplified operating and
storage consumption models
by:
– Delivering a dynamic storage
service level allocation on top
of Virtual SAN.
– Leveraging Storage Policy
Based Management (SPBM)
and underlying Virtual SAN
storage technologies.
34. vRealize Operations
• Day to Day Operations
Management
– Enable Alerting & Notification for
troubleshooting VSAN related failures
and performance issues
– Provide a single pane of glass for
simplified and automated operations
management for VSAN by means of
exploratory dashboards, heat maps etc
• Analytics and Future Capacity
Planning
– Analyze Health, Risk and Efficiency of
Virtual SAN cluster around
performance, capacity and availability
– Enable use of advanced analytics,
reporting and planning capabilities for
physical infrastructure supporting
Virtual SAN
35. OpenStack
• Virtual SAN and OpenStack Framework
– Cloud Ready App to Hypervisor Converged solution
– Leverage the use of Flash Optimized storage in
OpenStack
– Resiliency for legacy and Cloud Ready applications
– vSphere Web Plug-in for OpenStack UI
• Virtual SAN interoperates with OpenStack Framework.
– vSphere Driver
– vSphere Datastore
Swift
object store
Glance
image store
Horizon
Dashboard
OpenStack Framework
KeyStone
identity service
NSX
driver
Neutron
networking
Nova
compute node
vsphere
datastore
driver
Cinder
volume service
vsphere
driver
vSphere + Virtual SAN
Hard disksHard disks
SSD SSD Hard disks
SSD
…
35
36. Broad Partner Ecosystem Support for Virtual SAN
Storage
Server / Systems
Solution
Data Protection
Solution
36
+ More….