This demonstration showcases the extensible deployment and configuration flexibility of VMware Virtual SAN through the use of command line interface tools such as PowerCLI by automating the creation of all of the necessary artifacts required to successfully prepared and form an 8 node all-flash VMware Virtual cluster with a single PowerCLI script.
VMware Virtual SAN is a software defined storage solution introduced by VMware in 2012 that allows you
to create a clustered data store from the storage (SSDs and HDDs, or all-flash using SSDs and PCIeSSDs) that is present in the ESXi hosts. The Virtual SAN solution simplifies storage management through objectbased storage systems and fully supports vSphere enterprise features such as HA, DRS and vMotion. The Virtual SAN storage cluster must be made up of at least three ESXi servers. VMware Virtual SAN is built into the ESXi 6.0 hypervisor and can be used with ESXi hosts that are configured with PERC RAID controllers.
To be able to use Virtual SAN in a hybrid configuration, which is the context of this document, you will need at least one SSD and one HDD in each of the servers participating in the Virtual SAN cluster and it’s important to note that the SSD doesn’t contribute to the storage capacity. The SSDs are used for read cache and write buffering whereas the HDD’s are there to offer persistent storage. Virtual SAN is highly available as it’s based on the distributed object-based RAIN (redundant array of independent nodes) architecture. Virtual SAN is fully integrated with vSphere. It aims to simplify storage placement decisions for vSphere administrators and its goal is to provide both high availability as well as scale out storage functionality.
Download out the full VMware VSAN 6.2 for ESXi 6.0 with Horizon View Technical Whitepaper
Radically simple, enterprise-class native storage for vSphere
Q: What is VMware Virtual SAN?
Q: What are the use cases for Virtual SAN?
Q: What are the most significant new capabilities in
Virtual SAN 6.2?
Q: What are the software requirements for
Q: What are the hardware requirements for
Q: Why use Virtual SAN Ready Nodes?
Q: What configurations are not supported?
Q: Are all Virtual SAN nodes required to carry disks?
Q: Which types of virtual switches are supported?
Download out the full VMware vSAN 6.2 Frequently Asked Questions
Extensive user experience and operations testing, including use of Login VSI desktop performance testing of up-to 1,600 desktops, desktop provisioning operations of up-to 2,400 desktops, revealed world-class performance at an extremely low cost. VMware Virtual SAN technology allows easy scalability while maintaining superior performance at a competitive price point.
VMware reference architectures are built and validated by VMware and supporting partners. They are designed to address common use cases; examples include enterprise desktop replacement, remote access, business process outsourcing, and disaster recovery. A reference architecture describes the environment and workload used to simulate realistic usage, and draws conclusions based on that particular deployment.
This guide is intended to help customers—IT architects, consultants, and administrators—involved in the early phases of planning, design and deployment of Horizon View–based solutions. The purpose is to
provide a standard, repeatable, and highly scalable design that can be easily adapted to specific
environments and customer requirements.
The reference architecture “building block” approach uses common components to minimize support costs
and deployment risks during the planning of large-scale, Horizon View–based deployments. The building block approach is based on information and experiences from some of the largest VMware deployments in production today. While drawing on existing best practices and deployment guides pertinent to many of the individual specific components, the reference architectures are tested and validated in the field and described in detail.
Some key features that can help an organization get started quickly with a solution that integrates easily into existing IT processes and procedures include:
- Standardized, validated, readily available components
- Scalable designs that allow room for future growth
- Validated and tested designs that reduce implementation and operational risks
- Quick implementation, reduced costs, and minimized risk
Storage and Availability Business Unit
VMware, v 1.0.5/April 2015
VMware® Virtual SAN™ is a hypervisor-converged, software-defined storage platform that is fully integrated with VMware vSphere®. Virtual SAN aggregates locally attached disks of hosts that are members of a vSphere cluster, to create a distributed shared storage solution. Virtual SAN enables the rapid provisioning of storage within VMware vCenter™ as part of virtual machine creation and deployment operations.
Virtual SAN is the first policy-driven storage product designed for vSphere environments that simplifies and streamlines storage provisioning and management. Using VM-level storage policies, Virtual SAN automatically and dynamically matches requirements with underlying storage resources. With Virtual SAN, many manual storage tasks are automated – delivering a more efficient and cost-effective operational model.
Virtual SAN 6.0 provides two different configuration options, a hybrid configuration that leverages both flash-based devices and magnetic disks, and an all-flash configuration. The hybrid configuration uses server-based flash devices to provide a cache layer for optimal performance while using magnetic disks to provide capacity and persistent data storage. This delivers enterprise performance and a resilient storage platform.
The all-flash configuration uses flash for both the caching layer and capacity layer. There area wide range of options for selecting a host model, storage controller as well as flash devices and magnetic disks. It is herefore extremely important that the VMware Compatibility Guide (VCG) is followed rigorously when selecting hardware components for a Virtual SAN design.
This document focuses on the helping administrators to correctly design and size a Virtual SAN cluster, and answer some of the common questions around number of hosts, number of flash devices, number of magnetic disks, and detailed configuration questions to help to correctly and successfully deploy a Virtual SAN.
Download out the full VMware® Virtual SAN™ 6.0 Design and Sizing Guide.
Download also VMware® Virtual SAN™ 6.0 Administrators Guide.
Virtual SAN uses a hybrid disk architecture that leverages both flash-based devices for performance and magnetic disks for capacity and persistent data storage. This hybrid architecture delivers a scale-out storage platform with enterprise performance and resiliency at a compelling price point.
The distributed datastore of Virtual SAN is an object-store file system that leverages the vSphere Storage Policy–Based Management (SPBM) framework to deliver application-centric storage services and capabilities that are centrally managed through vSphere virtual machine storage policies.
This document focuses on the definitions, sizing guidelines, and characteristics of the Virtual SAN distributed datastore for Horizon™ View™ virtual desktop infrastructures.
VSAN uses the concept of policy driven storage. This video describing the steps to create a VM Storage Policy, and then deploy a virtual machine using that VM Storage Policy on VSAN. Sign up for the free beta at VSANbeta.com
In this session we will cover Horizon 6 integration points with Virtual SAN as well as the ease, streamline management and implementation capabilities for virtual desktop infrastructures.
Speaker: Rawlinson Rivera, Sr Technical Marketing Architect
Hardly a day goes by without somebody asking how to deploy App Volumes or take advantage of Virtual SAN on View virtual desktops in VMware Horizon 6. This new VMware Horizon 6 with App Volumes and Virtual SAN Reference Architecture provides the answers.
Based on the proven approach of modular pod and block design principles, this validated architecture offers a standard, repeatable, scalable design that IT architects, consultants, and administrators can adapt to their own requirements and environments.
The reference environment and hardware configuration were both subjected to rigorous performance benchmarking, workload simulation, and operations testing.
Wherever possible, this reference architecture offers alternate ways to answer customer needs. For instance, Horizon 6 provides end users with access to all their desktops and applications through a single, unified workspace, whether they connect to their View desktops directly or use RDSH to connect to a desktop session. Similarly, RDSH application remoting and App Volumes AppStacks and writable volumes provide different methods for delivering applications. These alternatives and many more are supported by Virtual SAN.
Test results support the following conclusions:
- App Volumes improved the desktop consolidation ratio and reduced CPU and memory usage while providing satisfactory or better end-user experience.
- Storage provisioning and management required little effort, and performance was excellent, with low latency from Virtual SAN, even under heavy load.
- Desktop maintenance, storage provisioning and management, and application delivery and patching required only minimal time and effort from one administrator for this large deployment.
The bottom line is that the VMware Horizon 6 with App Volumes and Virtual SAN Reference Architecture shows how a deployment for 960 users on 700 linked-clone View desktops and 260 RDSH sessions can provide performance equivalent to high-end physical computers.
The book can be found here VMware Horizon 6 with App Volumes and Virtual SAN Reference Architecture.
Learn about VMware Virtual SAN 6.1 in this Technical Overview.