VMware® Virtual SAN™ is the industry’s first scale-out, hypervisor-converged storage solution based on the industry-leading VMware vSphere® solution. Virtual SAN is a software-defined storage solution that enables great flexibility and vendor choice in hardware platform.
This document provides guidance regarding hardware decisions—based on creating Virtual SAN solutions using VMware Compatibility Guide–certified hardware—when designing and deploying Virtual SAN. These decisions include the selection of server form factor, SSD, HDD, storage controller, and networking components.
This document does not supersede the official hardware compatibility information found in the VMware Compatibility Guide, which is the single source for up-to-date Virtual SAN hardware-compatibility information and must be used for a list of officially supported hardware.
When designing a Virtual SAN cluster from a sum of VMware Compatibility Guide–certified vendor components, this guide should be used in combination with the VMware® Virtual SAN™ Design and Sizing Guide. the Virtual SAN sizing tool, and other official Virtual SAN documentation from VMware Technical Marketing and VMware Technical Publications.
VMware Virtual SAN is a groundbreaking storage solution that enables unprecedented hardware configuration flexibility through building an individual solution based on preferred server vendor components. The guidance provided in this document enables users to make the best choice regarding their particular storage needs for their software-defined datacenter based on VMware vSphere. When selecting hardware components for a Virtual SAN solution, users should always utilize the VMware Compatibility Guide as the definitive resource tool.
Download out the full VMware® Virtual SAN™ Hardware Guidance technical white paper.
The purpose of this document is to provide sample server configurations as directional guidelines for use with VMware® Virtual SAN™. Use these guidelines as your first step toward determining the configuration for Virtual SAN.
How to use this document
1. Determine your workload profile requirement for your use case.
2. Refer to Ready Node profiles to determine the approximate configuration that meets your needs.
3. Use VSAN Hardware Compatibility Guide to pick a Ready Node aligned with the selected profile from the OEM server vendor of choice.
For more detail on Virtual SAN Design guidance, see
1. Virtual SAN Ready Node Configurator
2. Virtual SAN Hardware Guidance
3. VMware® Virtual SAN™ 6.0 Design and Sizing Guide.
4. Virtual SAN Sizing Calculator
5. VSAN Assessment Tool
Download out the full Virtual SAN Hardware Quick Reference Guide technical white paper.
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
In the 5.1 release of View, VMware introduced some complex configuration options for the usage and management of USB devices in a View virtual desktop session. This white paper gives a high-level overview of USB remoting, discusses the configuration options, and provides some practical worked examples to illustrate how these options can be used.
USB Redirection Overview
We are all familiar with using USB devices on laptop or desktop machines. If you are working in a virtual desktop infrastructure (VDI) environment such as View, you may want to use your USB devices in the virtual desktop, too. USB device redirection is a function in View that allows USB devices to be connected to the virtual desktop as if they had been physically plugged into it. Typically, the user selects a device from the VMware Horizon Client menu and selects it to be forwarded to the virtual desktop. After a few moments, the device appears in the guest virtual machine, ready for use.
Definitions of Terms
In this paper, various terms are used to describe the components involved in USB redirection. The following are some brief definitions of terms:
- USB redirection – Forwarding of the functions of a USB device from the physical endpoint to the View virtual machine.
- Client computer, or client, or client machine – Physical endpoint displaying the virtual desktop with which the user interfaces, and where the USB device is physically plugged in.
- Virtual desktop or guest virtual machine – The Windows desktop stored in the data center that is displayed remotely on the endpoint. This virtual desktop runs a Windows guest operating system, and has the View Agent installed on it.
- Soft client – Horizon Client in software format, such as a Horizon Client for Windows or Linux. The soft client is installed on a hardware endpoint, such as a laptop, and displays the virtual desktop on the endpoint.
- Zero client – A hardware-based client used to connect to a View desktop. Stateless device containing no operating system. Delivers the client login interface for View.
- Thin client – A hardware device similar to a zero client, but with an OS installed. The Horizon Client is installed onto the OS of the thin client. Both devices generally lack local user-accessible storage and simply connect to the virtual desktop in the data center.
- USB interface – A function within a USB device, such as mouse or keyboard or audio. Some USB devices have multiple functions and are called composite (USB) devices.
- Composite (USB) device – A USB device with multiple functions, or interfaces.
- HID – Human interface device. A device with which the user physically interacts, such as mice, keyboards, and joysticks.
- VID – The vendor identification, or code, for a USB device, which identifies the vendor that produced the device.
- PID – The product identification, or code, which, combined with the VID, uniquely identifies a USB device within a vendor’s family of USB products. The VID and PID are used within View USB configuration settings to identify the specific driver needed for the device.
- USB device filtering – Restricting some USB devices from being forwarded from the endpoint to the virtual desktop. You specify which devices will be prevented from being forwarded: individual VID-PID device models, device families, such as storage devices, or devices from specific vendors.
- USB device splitting – The ability to configure the USB device such that when connected to a View desktop leaves some of the USB interfaces local to the client endpoint, and other interfaces forwarded to the guest. This can result in an improved user experience of the device in a virtual environment.
- USB Boolean settings – Simple “on” or “off” settings. For example, whether a specific feature is enabled (true) or disabled (false).
Download out the full USB Device Redirection, Configuration, and Usage in View Virtual Desktops white paper.
This is a copy of Jeff’s presentation from the November 16th COVMUG meeting. Please be sure to thank Jeff when you see him. You can follow him on Twitter at @jhuntervmware.
VMware vCenter Site Recovery Manager 5 – Technical
Jeff Hunter, VCAP-DCD
Senior Systems Engineer – BC/DR Specialist
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
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.
An overview of the solution and the logical architecture as well as results of the tested physical implementation are provided. Consult with your VMware representative as to how to modify the architecture to suit your business needs.
This document will assist enterprise architects, solution architects, sales engineers, field consultants, advanced services specialists, and customers who are responsible for infrastructure services. This guide provides an example of a successful deployment of an SDDC.
Expectations for IT to deliver applications and services at speed and scale are greater than ever. The VMware SDDC enables companies to evolve beyond outdated, hardware-centric architectures and to create an automated, easily managed platform that embraces all applications, for fast deployment across data centers and clouds. With an SDDC, users see a predefined list of services available to them and can have these services created instantly upon request, while still enabling IT to control and secure these services. This reference architecture delivers a working configuration that provides users with the on-demand access they need while ensuring that IT maintains the control and security it requires.
The VMware Software-Defined Data Center Foundation Reference Architecture
This reference architecture describes the implementation of a software-defined data center (SDDC) that leverages the latest VMware components and capabilities. The reference architecture is built on the Foundation VMware Validated Design. The Foundation VMware Validated Design is the core of all higher-level VMware Validated Designs.
Foundation describes a scalable, resilient, best-practice configuration on which all additional functionality is layered. The Foundation configuration uses industry-standard servers, IP-based and VMware Virtual SAN™ storage, and software-defined networking to support a scalable and redundant architecture.
The VMware Validated Design process gathers data from customer support, VMware IT, and VMware and partner professional services to create a standardized configuration that meets the majority of customer requirements. Internally, VMware engineering teams test new product capabilities, installations, upgrades,
and more, against the standardized configuration. VMware and partner professional services teams build delivery kits based on this design, knowing that they are deploying with the best possible configuration.
Customers planning “do it yourself” deployments also benefit from following this architecture, confident that future product upgrades, patches, and so on, have already been tested against a configuration identical to theirs.
This document will assist those who are responsible for infrastructure services, including enterprise architects, solution architects, sales engineers, field consultants, advanced services specialists, and customers. This guide provides an example of a successful deployment of an SDDC.