NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes

Transcription

1 3 Technical Report NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes A Technical Preview Chris Gebhardt and Bhavik Desai, NetApp August 2015 TR-4428 Abstract In this reference architecture, NetApp tested VMware Horizon 6, version 6.1.1, user and administrative workloads to demonstrate how the NetApp AFF solution eliminates the most common barriers to virtual desktop adoption. Using VMware vsphere Virtual Volumes (VVOLs) for this reference architecture with NFS allowed us to test once for both persistent (full clones) and nonpersistent (linked clones) user types. The testing covered common administrative tasks such as provisioning virtual machines and booting them, persistent tasks such as patching and virus scanning, and nonpersistent tasks such as performing refresh and recompose maintenance activities. With all of these tasks, it was possible to understand time to complete each task, the storage response, and the storage utilization regardless of desktop type. We also included end-user workloads and reviewed how different types of logins affected login time and the end-user experience. Disclaimer: In its current state, this reference architecture is labeled as a Technical Preview because NetApp Data ONTAP software is not certified with VMware VVOLs. However, Data ONTAP is certified with traditional datastores, and its performance and in-line efficiency benefits still apply.

2 TABLE OF CONTENTS 1 Executive Summary Reference Architecture Objectives Solution Overview Introduction Document Overview NetApp All Flash FAS Overview VMware Horizon Login VSI vsphere Virtual Volumes VM Storage Policies VVOL Datastores Protocol Endpoints VVOL Considerations for VMware Horizon Solution Infrastructure Hardware Infrastructure Software Components VMware vsphere NetApp Virtual Storage Console NetApp VASA Provider 6.0 for Clustered Data ONTAP Virtual Desktops Login VSI Server Login VSI Launcher VM Windows Infrastructure VM Storage Design Storage Design Overview Aggregate Layout Volume Layout Always-On Deduplication Requirements for Always-On Deduplication Inline Deduplication of Zeros in Data ONTAP NetApp Virtual Storage Console for VMware vsphere NetApp VASA Provider Virtual Appliance Horizon 6 Design NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

3 6.1 Overview User Assignment Automated Desktop Pools Linked-Clone Desktops Creating VMware Horizon 6 Desktop Pools Login VSI Workload Login VSI Components Testing and Validation Overview Test Results Overview Storage Efficiency Provisioning 2,000 VMware Horizon 6 Desktops Boot Storm Test Boot Storm During Storage Failover Test Steady-State Login VSI Test Refresh Test Recompose Test Throttled Patching of 2,000 Desktops Throttled Virus Scan of 1,000 Desktops on One Node Conclusion Key Findings References Version History Acknowledgements LIST OF TABLES Table 1) Test results Table 2) AFF8000 storage system technical specifications Table 3) View Connection Server VM configuration Table 4) View Composer VM configuration Table 5) NetApp storage capabilities supported by VVOLs Table 6) VVOL types and implementation Table 7) Horizon View disk use Table 8) Disk type and use for VVOLs and Horizon View Table 9) Hardware components of server categories NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

4 Table 10) Solution software components Table 11) VMware vcenter Server VM configuration Table 12) Microsoft SQL Server database VM configuration Table 13) NetApp VSC VM configuration Table 14) NetApp VASA Provider VM configuration Table 15) Virtual desktop configuration Table 16) Login VSI server configuration Table 17) Login VSI launcher VM configuration Table 18) Windows infrastructure VM configuration Table 19) Disk types and protocols Table 20) VMware Horizon 6 configuration options Table 21) Test results overview Table 22) Efficiency results Table 23) Results for desktop provisioning Table 24) Results for a boot storm of 2,000 desktops Table 25) Power-on method, storage latency, and boot time Table 26) Results for a 2,000-desktop boot storm during storage failover Table 27) Results for a 2,000-desktop Monday morning login and workload Table 28) Results for a 2,000-desktop linked-clone Tuesday morning login and workload Table 29) Results for a 2,000-desktop linked-clone Tuesday morning login and workload during storage failover Table 30) Results for a 2,000-desktop refresh operation Table 31) Results for a 2,000-desktop recompose operation Table 32) Results for throttled patching of 2,000 desktops Table 33) Results for the throttled virus scan operation on one node LIST OF FIGURES Figure 1) Typical days in the life of a virtual desktop....9 Figure 2) Clustered Data ONTAP Figure 3) Improved read performance with Data ONTAP flash optimizations Figure 4) Horizon 6 deployment (graphic supplied by VMware) Figure 5) View Composer concurrent operation limits Figure 6) Binding relationship between a PE LUN and a VVOL Figure 7) LUN PEs Figure 8) NFS PEs Figure 9) One FlexVol volume per VVOL container Figure 10) Solution infrastructure Figure 11) Setting uuid.action in the.vmx file with Windows PowerShell Figure 12) VMware OS Optimization Tool Figure 13) Login VSI launcher configuration NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

5 Figure 14) Multipath HA to DS2246 shelves of SSD Figure 15) Advanced drive partitioning disk layout Figure 16) VVOL layout Figure 17) PowerShell script to configure always-on deduplication Figure 18) Configuring the efficiency policy for always-on deduplication Figure 19) VMware Horizon 6 pool and desktop-to-datastore relationship Figure 20) Windows PowerShell script to create 8 pools of 250 desktops each Figure 21) Login VSI components Figure 22) Desktop-to-launcher relationship Figure 23) Capacity and storage savings by volume Figure 24) Creating 250 VMs in one pool named vdi01n Figure 25) Throughput and IOPS for the creation of 2,000 desktops Figure 26) Storage controller CPU utilization for the creation of 2,000 desktops Figure 27) Throughput and IOPS for a 2,000-desktop boot storm Figure 28) Storage controller CPU utilization for a 2,000-desktop boot storm Figure 29) Read/write IOPS for a 2,000-desktop boot storm Figure 30) Read/write ratio for a 2,000-desktop boot storm Figure 31) Throughput and IOPS for a 2,000-desktop boot storm during storage failover Figure 32) Storage controller CPU utilization for a 2,000-desktop boot storm during storage failover Figure 33) Read/write IOPS for a desktop boot storm during storage failover Figure 34) Read/write ratio for a 2,000-desktop boot storm during storage failover Figure 35) VSImax results for a 2,000-desktop Monday morning login and workload Figure 36) Scatter plot of 2,000-desktop Monday morning login times Figure 37) Throughput, latency, and IOPS for a 2,000-desktop Monday morning login and workload Figure 38) Storage controller CPU utilization for a 2,000-desktop Monday morning login and workload Figure 39) Read/write IOPS for a 2,000-desktop Monday morning login and workload Figure 40) Read/write ratio for a 2,000-desktop Monday morning login and workload Figure 41) VSImax results for a 2,000-desktop Tuesday morning login and workload Figure 42) Scatter plot of 2,000-desktop Tuesday morning login times Figure 43) Throughput, latency, and IOPS for a 2,000-desktop Tuesday morning login and workload Figure 44) Storage controller CPU utilization for a 2,000-desktop Tuesday morning login and workload Figure 45) Read/write IOPS for a 2,000-desktop Tuesday morning login and workload Figure 46) Read/write ratio for a 2,000-desktop Tuesday morning login and workload Figure 47) VSImax results for a 2,000-desktopTuesday morning login and workload during storage failover Figure 48) Scatter plot of 2,000-desktop Tuesday morning login times during storage failover Figure 49) Throughput, latency, and IOPS for a 2,000-desktop Tuesday morning login and workload during storage failover Figure 50) Storage controller CPU utilization for a 2,000-desktop Tuesday morning login and workload during storage failover Figure 51) Read/write IOPS for a 2,000-desktop Tuesday morning login and workload during storage failover NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

6 Figure 52) Read/write ratio for a 2,000-desktop Tuesday morning login and workload during storage failover Figure 53) Windows PowerShell commands to refresh all eight pools of desktops Figure 54) Throughput and IOPS for a 2,000-desktop refresh operation Figure 55) Storage controller CPU utilization for a 2,000-desktop refresh operation Figure 56) Read/write IOPS for a 2,000-desktop refresh operation Figure 57) Read/write ratio for a 2,000-desktop refresh operation Figure 58) Windows PowerShell commands to recompose all eight pools of desktops Figure 59) Throughput and IOPS for a 2,000-desktop recompose operation Figure 60) Storage controller CPU utilization for a 2,000-desktop recompose operation Figure 61) Read/write IOPS for a 2,000-desktop recompose operation Figure 62) Read/write ratio for a 2,000-desktop recompose operation Figure 63) Throughput, latency, and IOPS for throttled patching of 2,000 desktops Figure 64) Storage controller CPU utilization for throttled patching of 2,000 desktops Figure 65) Read/write IOPS for throttled patching of 2,000 desktops Figure 66) Read/write ratio for throttled patching of 2,000 desktops Figure 67) Always-on deduplication storage efficiency over time Figure 68) Throttled virus scan script sample Figure 69) Throughput and IOPS for throttled virus scan operation on one node Figure 70) Storage controller CPU utilization for throttled virus scan operation on one node Figure 71) Read/write IOPS for throttled virus scan operation on one node Figure 72) Read/write ratio for throttled virus scan operation on one node NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

7 1 Executive Summary The decision to virtualize desktops affects multiple aspects of an IT organization, including infrastructure and storage requirements, application delivery, end-user devices, and technical support. In addition, correctly architecting, deploying, and managing a virtual desktop infrastructure (VDI) can be challenging because of the large number of solution components in the architecture. Therefore, it is critical to build the solution on an industry-proven platform such as NetApp storage along with industry-proven software solutions from VMware. VMware and NetApp provide leading desktop virtualization and storage solutions, respectively, for customers to successfully meet these challenges and gain the numerous benefits available from a VDI solution. Such benefits include workspace mobility, centralized management, consolidated and secure delivery of data, and device independence. New products are constantly being introduced that promise to solve all VDI challenges of performance, cost, or complexity. Each new product introduces more choices, complexities, and risks to your business in an already complicated solution. NetApp, founded in 1992, has been delivering enterprise-class storage solutions for virtual desktops since 2006, and it offers real answers to these problems. The criteria for determining the success of a VDI implementation include the end-user experience. The end-user experience must be as good as or better than any previous experience on a physical PC or virtual desktop. The VMware Horizon 6 desktop virtualization solution delivers excellent end-user experience and performance over LAN, WAN, and extreme WAN through the Horizon 6 PCoIP display protocol adaptive technology. In addition, VMware has repeatedly enhanced the protocol to deliver 3D applications, to improve real-time audio-video experiences, and to improve HTML5 and mobility features for small form-factor devices. Storage is often the leading cause of end-user performance problems. The NetApp All Flash FAS (AFF) solution with the AFF8000 platform solves the performance problems commonly found in VDI deployments. Another determinant of project success is solution cost. The original promise that virtual desktops could save companies endless amounts of money proved incorrect. Storage has often been the most expensive part of the VDI solution, especially when storage efficiency and flash acceleration technologies were lacking. It was also common practice to forgo an assessment. Because information is the key to making sound architectural decisions that result in wise IT spending, skipping this critical step meant that companies often overbought or undersized the storage infrastructure. NetApp has many technologies that help customers reduce the storage cost of a VDI solution. NetApp AFF is a solid-state drive (SSD) only controller platform with an optimized version of the NetApp Data ONTAP operating system (OS). The AFF platform is limited to using SSDs only, but it can participate in Data ONTAP clusters. Technologies such as always-on deduplication, thin provisioning, advanced drive partitioning, and inline compression help reduce the total amount of storage required for VDI. The NetApp Virtual Storage Tier (VST), extended with NetApp Flash Cache and Flash Pool technology, helps accelerate the end-user experience while reducing spinning media for nondesktop data such as user and profile data. Storage platforms that scale up and scale out with clustered Data ONTAP help deliver the right architecture to meet the customer s price and performance requirements. NetApp can help achieve the customer s cost and performance goals while providing rich data management features. NetApp customers might pay as little as US$39 per desktop for storage when deploying at scale. This figure includes the cost of hardware, software, and three years of 24/7 premium support with 4-hour parts replacement. With VMware and NetApp, companies can accelerate the VDI end-user experience by using NetApp AFF storage for Horizon 6. NetApp AFF storage, powered by the AFF8000 platform, is optimal for using highperforming SSDs without adding risk to desktop virtualization initiatives. When a storage failure prevents users from working, that inactivity translates into lost revenue and reduced productivity. For that reason, what used to be considered a tier 3 and 4 application is now tier 0 7 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

8 and is absolutely critical to business operations. Having a storage system with a robust set of data management and availability features is key to keeping the users working, and it lessens the risk to the business. NetApp clustered Data ONTAP has multiple built-in features to help improve availability, such as active-active high availability (HA) and nondisruptive operations to seamlessly move data in the storage cluster without user impact. NetApp also provides the ability to easily increase storage system capacity by simply adding disks or shelves. There is no need to purchase additional controllers to add users when additional capacity is required. When the platform requires expansion, additional nodes can be added in a scale-out fashion and managed within the same management framework and interface. Workloads can then be nondisruptively migrated or balanced to the new nodes in the cluster without the users ever noticing. 1.1 Reference Architecture Objectives In this reference architecture, NetApp tested VMware Horizon 6, version 6.1.1, user and administrative workloads to demonstrate how the NetApp AFF solution eliminates the most common barriers to virtual desktop adoption. User workloads consisted of everyday tasks, such as working within Microsoft Office, surfing the Internet, zipping files, and watching videos. Administrative workloads consisted of patching the virtual desktops, performing a virus scan, and other common VM maintenance activities. VMware vsphere Virtual Volumes (VVOLs) are a new method for defining, presenting, and consuming shared storage. Using VVOLs for this reference architecture with NFS allowed us to test once for both persistent (full clones) and nonpersistent (linked clones) user types. We could test both at once because the VVOLs feature does not use hypervisor-based snapshot cloning for linked clones. Both full clones and linked clones use Virtual Machine Disks (VMDKs) for NFS disks and use LUNs for block-based disks. The term linked clone is used regardless of whether the underlying clone method is based on VVOLs, on View Composer API for Array Integration (VCAI), or on hypervisor snapshots. Note: For the remainder of this document, the term linked clone refers to the workflow of creating nonpersistent desktops that do not rely on hypervisor snapshots. The VVOLs feature uses NetApp cloning, which is fast and storage efficient. The testing covered common administrative tasks on 2,000 desktops, or on 4,000 desktops when tests were performed in a failed-over state. It included common tasks such as provisioning virtual machines (VMs) and booting them, persistent tasks such as patching and virus scanning, and nonpersistent tasks such as performing refresh and recompose maintenance activities. With all of these tasks, it was possible to understand time to complete each task, the storage response, and the storage utilization regardless of desktop type. We also included end-user workloads and reviewed how different types of logins (Monday and Tuesday, representing cold and warm cache, respectively) affected login time and the end-user experience. A Monday login takes place after the VMs have been rebooted. None of the application binaries, libraries, profile data, or application data is resident in the VM s memory. A Tuesday login and workload take place after a user has used the desktop and no reboot of that desktop has occurred. Most of these login and workload scenarios took place not only during normal operations but also during storage failover. We refer to this sort of testing as a day in the life. It offers readers a better understanding of when these sorts of events occur and when they might expect to see similar workloads. Figure 1 shows a calendar noting typical events that might occur on any given day. 8 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

9 Figure 1) Typical days in the life of a virtual desktop. 1.2 Solution Overview The reference architecture is based on VMware vsphere 6.0; VMware Horizon 6, version 6.1.1; and VMware View Composer 6.1. These products were used to host, provision, and run 2,000 Windows 7 (32-bit) virtual desktops. The 2,000 desktops were hosted by a NetApp AFF8060 storage system running the NetApp Data ONTAP Release Candidate 1 (RC1) OS configured with forty-eight 400GB SSDs. Eight NFS-based VVOLs were presented from the NetApp system to the VMware ESXi hosts for use by the desktops. Host-to-host communication took place over a 10GbE network through the VMware virtual network adapters. VMs were used for core infrastructure components such as Active Directory, database servers, and other services. In all tests, end-user login time, guest response time, and maintenance activities performance were excellent. The NetApp AFF system performed well, reaching a combined peak input/output operations per second (IOPS) of 156,686 while averaging 50% CPU utilization during most operations. All test categories demonstrated that, based on the 2,000-user workload and maintenance operations, the AFF8060 system should be capable of doubling the workload to 4,000 users and still be able to fail over if necessary. At a density of 4,000 VMs on an AFF8060 system with the same I/O profile, storage for VDI might be as low as US$39 per desktop. This figure includes the cost of hardware, software, and three years of 24/7 premium support with 4-hour parts replacement. 9 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

10 Table 1 lists the results obtained during testing. Table 1) Test results. Test Time to Complete Peak IOPS Peak Throughput Average Storage Latency Provisioning 2,000 desktops 92 min 89, MBps 1.04ms Boot storm test 6 min, 17 sec 156, MBps 1.15ms Boot storm during storage failover 8 min, 45 sec 91, MBps 2.42ms Login VSI Monday morning login and workload 8.7 sec 37, MBps 0.92ms Login VSI Tuesday morning login and workload 8.2 sec 31, MBps 0.91ms Login VSI Tuesday morning login and workload during storage failover 8.6 sec 29, MBps 1.29ms Refresh operation 71 min 66, MBps 0.74ms Recompose operation 92 min 89, MBps 0.97ms Throttled patching of 2,000 desktops 189 min 124, MBps 1.36ms Throttled virus scan of 1,000 desktops 80 min 55, MBps 0.41ms 2 Introduction This section explains the purpose of this document, provides an overview of the NetApp All Flash FAS (AFF) solution for VMware Horizon 6, and introduces Login VSI, ( the industry standard load testing solution for centralized virtualized desktop environments. 2.1 Document Overview This document describes the solution components used in a 2,000-seat VMware Horizon 6 deployment on a NetApp AFF reference architecture. It covers the hardware and software used in the validation, the configuration of the hardware and software, use cases that were tested, and performance results of the completed tests. During these performance tests, many different scenarios were tested to validate the performance of the storage during the lifecycle of a virtual desktop deployment. The testing included the following criteria: Provisioning of 2,000 VMware Horizon 6 desktops Boot storm testing of 2,000 desktops Monday morning login and steady-state workload with Login VSI Tuesday morning login and steady-state workload with Login VSI (with and without storage node failover) Refresh and recompose of Horizon 6 maintenance activities Throttled patching of 2,000 desktops on one node Throttled virus scan of 1,000 desktops on one node Storage performance and end-user acceptance were the main focus of the testing. If a bottleneck occurred in any component of the infrastructure, it was identified and remediated if possible. There were multiple exceptions to this rule. The execution of certain tests (such as provisioning, refresh, and 10 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

11 recompose) was limited by the software and not by the storage. This fact was evident because no component in the infrastructure became the bottleneck. In addition, other reference architectures in the industry achieved identical results with no bottleneck in the storage systems or other components. 2.2 NetApp All Flash FAS Overview Built on more than 20 years of innovation, Data ONTAP has evolved to meet the changing needs of customers and help drive their success. Clustered Data ONTAP provides a rich set of data management features and clustering for scale-out, operational efficiency, and nondisruptive operations to offer customers one of the most compelling value propositions in the industry. The IT landscape is undergoing a fundamental shift to IT as a service, a model that requires a pool of compute, network, and storage resources to serve a wide range of applications and deliver a wide range of services. Innovations such as clustered Data ONTAP are fueling this revolution. Outstanding Performance The NetApp AFF solution shares the same Unified Storage Architecture, Data ONTAP OS, management interface, rich data services, and advanced feature set as the rest of the fabric-attached storage (FAS) product families. One difference is that it does not allow spinning media. The AFF system can, however, be a part of a Data ONTAP cluster that contains nodes with spinning media. Data ONTAP has been changed for the AFF platform in ways that help reduce latency and significantly improve performance. This innovative combination of all-flash media with Data ONTAP delivers the consistent low latency and high IOPS of all-flash storage with the industry-leading clustered Data ONTAP OS. In addition, it offers these key values: Proven enterprise availability Reliability Scalability Storage efficiency proven in thousands of VDI deployments Unified storage with multiprotocol access Advanced data services Operational agility achieved through tight application integrations AFF8000 Technical Specifications Table 2 provides the technical specifications for the four AFF8000 storage systems: AFF8080 EX, AFF8060, AFF8040, and AFF8020. Note: All of the data in Table 2 applies to active-active, dual-controller configurations. 11 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

12 Table 2) AFF8000 storage system technical specifications. Features AFF8080 EX AFF8060 AFF8040 AFF8020 Maximum raw capacity with SSDs Maximum number of SSDs 384TB 384TB 384TB 384TB Controller form factor Dual-enclosure HA; 2 controllers and 2 IOXM in two 6U chassis; total of 12U or single enclosure HA; 2 controllers in single 6U chassis Dual-enclosure HA; 2 controllers and 2 IOXM in two 6U chassis; total of 12U or single enclosure HA; 2 controllers in single 6U chassis Single-enclosure HA; 2 controllers in single 6U chassis Single-enclosure HA; 2 controllers in single 3U chassis Memory 256GB 128GB 64GB 48GB NVRAM 32GB 16GB 16GB 8GB PCIe expansion slots Onboard I/O: UTA2 (10GbE/FCoE, 16Gb FC) Onboard I/O: 10GbE Onboard I/O: 1GbE Onboard I/O: 6Gb SAS Optical SAS support Yes Yes Yes Yes Support for storage networking OS version FC, FCoE, iscsi, NFS, pnfs, CIFS/SMB Data ONTAP or later Scale-Out Data centers require agility. In a data center, each storage controller has CPU, memory, and disk shelf limits. Scale-out means that, as the storage environment grows, more controllers can be added seamlessly to the resource pool residing on a shared storage infrastructure. Host and client connections, as well as datastores, can be moved seamlessly and nondisruptively anywhere within the resource pool. The benefits of scale-out include the following: Nondisruptive operations Ability to keep adding thousands of users to the virtual desktop environment without downtime Operational simplicity and flexibility As Figure 2 shows, clustered Data ONTAP offers a way to meet the scalability requirements in a storage environment. A clustered Data ONTAP system can scale up to 24 nodes, depending on the platform and protocol, and it can contain different disk types and controller models in the same storage cluster. An AFF system cannot contain spinning media, but it can participate in a cluster that contains spinning media. 12 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

13 Figure 2) Clustered Data ONTAP. Nondisruptive Operations The move to shared infrastructure has made it nearly impossible to schedule downtime to accomplish routine maintenance. NetApp clustered Data ONTAP is designed to eliminate the planned downtime needed for maintenance and lifecycle operations, as well as the unplanned downtime caused by hardware and software failures. Three standard tools make it possible to eliminate downtime: NetApp DataMotion for Volumes (vol move) allows you to move data volumes from one aggregate to another on the same or a different cluster node. Logical interface (LIF) migrate allows you to virtualize the physical Ethernet interfaces in clustered Data ONTAP. LIF migrate lets you move LIFs from one network port to another on the same or a different cluster node. Aggregate relocation (ARL) allows you to transfer complete aggregates from one controller in an HA pair to the other without data movement. Used individually and in combination, these tools offer the ability to nondisruptively complete a full range of operations. These operations range from moving a volume from different media types to meet the application s capacity and performance requirements to performing a complete controller and storage technology refresh. As storage nodes are added to the system, all physical resources CPUs, cache memory, network I/O bandwidth, and disk I/O bandwidth can be easily kept in balance. Clustered Data ONTAP systems enable users to adjust as needed. Users can perform the following tasks: Add or remove storage shelves (over 3TB in an 8-node AFF cluster and up to 9.2PB in a 24-node AFF cluster) Move data between AFF and FAS system controllers and tiers of storage without disrupting users and applications Dynamically assign, promote, and retire storage while providing continuous access to data as administrators upgrade or replace storage These capabilities allow administrators to increase capacity while balancing workloads. These capabilities can also reduce or eliminate storage I/O hot spots without the need to remount shares, modify client settings, or stop running applications. 13 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

14 Availability A shared-storage infrastructure can provide services to thousands of virtual desktops. In such environments, downtime is not an option. The NetApp AFF solution eliminates sources of downtime and protects critical data against disaster through two key features: High availability (HA). A NetApp HA pair provides seamless failover to its partner in case of any hardware failure. Each of the two identical storage controllers in the HA pair configuration serves data independently during normal operation. During an individual storage controller failure, the data service process is transferred from the failed storage controller to the surviving partner. NetApp RAID DP technology. During any virtualized desktop deployment, data protection is critical because any RAID failure might disconnect hundreds to thousands of end users from their desktops, resulting in lost productivity. RAID DP provides performance comparable to that of RAID 10, yet it requires fewer disks to achieve equivalent protection. RAID DP provides protection against double disk failure, in contrast to RAID 5, which can protect against only one disk failure per RAID group. In effect, RAID DP provides RAID 10 performance and protection at a RAID 5 price point. Optimized Writes The NetApp WAFL (Write Anywhere File Layout) file system enables NetApp to process writes efficiently. When the Data ONTAP OS receives an I/O, it holds the I/O in memory and protects it with a log copy in battery-backed NVRAM; then it sends back an acknowledgment (or ACK), notifying the sender that the write is committed. Acknowledging the write before writing to storage allows Data ONTAP to perform many functions to optimize the data layout for optimal write/write coalescing. Before being written to storage, I/Os are coalesced into larger blocks because larger sequential blocks require less CPU for each operation. Read Improvements Flash optimizations in Data ONTAP deliver significantly better performance than Data ONTAP As shown in Figure 3, they can remove over a millisecond of latency from the read path, quadrupling the 8KB read IOPS at 1ms latency even when adaptive inline compression is enabled. Figure 3) Improved read performance with Data ONTAP flash optimizations. Enhancing Flash Data ONTAP and FAS systems have leveraged flash technologies since 2009 and have supported SSDs since This relatively long experience with flash storage has allowed NetApp to tune Data ONTAP 14 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

15 features to optimize SSD performance and enhance flash media endurance. When Data ONTAP is used with a NetApp AFF system, it has additional optimizations to improve flash performance over Data ONTAP with spinning media. As described in the previous sections, because Data ONTAP acknowledges writes after they are in DRAM and logged to NVRAM, SSDs are not in the critical write path. Therefore, write latencies are very low. By coalescing writes into a single sequential stripe across all SSDs at once, Data ONTAP also enables efficient use of SSDs when destaging write memory buffers. Data ONTAP writes to free space whenever possible, minimizing overwrites for every dataset, not only for deduplicated or compressed data. This wear-leveling feature of Data ONTAP is native to the architecture, and it also leverages the wearleveling and garbage-collection algorithms built into the SSDs to extend the life of the devices. NetApp provides up to 7 years of support at point-of-sale pricing. This support includes 3 years of standard and years of extended support, regardless of the number of drive writes per day. The parallelism built into Data ONTAP, combined with the multicore CPUs and large system memories in the AFF8000 storage controllers, takes full advantage of SSD performance and has powered the test results described in this document. Advanced Data Management Capabilities This section describes the storage efficiencies, multiprotocol support, VMware integrations, and replication capabilities of the NetApp AFF solution. Storage Efficiencies Most desktop virtualization implementations deploy thousands of desktops from a small number of golden VM images, resulting in large amounts of duplicate data. This is especially the case with the VM operating system. The NetApp AFF solution includes built-in thin provisioning, data deduplication, compression, and zerocost cloning with NetApp FlexClone technology. Customers get multilevel storage efficiency across virtual desktop data, installed applications, and user data. The comprehensive storage efficiency can significantly reduce the storage footprint for virtualized desktop implementations. Capacity can realistically be reduced by up to 10:1, or 90% (based on existing customer deployments and NetApp solutions lab validation). Seven features make this storage efficiency possible: Thin provisioning allows multiple applications to share a single pool of on-demand storage. This capability eliminates the need to provision more storage for one application when another application still has plenty of allocated but unused storage. Although thin provisioning is not really a storage efficiency technology because thin-provisioned VMs do not necessarily remain thin over time, it can help increase utilization. Always-on deduplication saves space on primary storage by removing redundant copies of blocks in a volume that hosts hundreds of virtual desktops. This process is transparent to the application and the user, and it can be enabled and disabled dynamically. To eliminate any potential concerns about deduplication causing additional wear on the SSDs, NetApp provides up to 7 years of support at point-of-sale pricing. This support includes 3 years of standard and years of extended support, regardless of the number of drive writes per day. With AFF, deduplication can be run in an always-on configuration to maintain storage efficiency over time. FlexClone technology offers hardware-assisted rapid creation of space-efficient, writable, point-intime images of individual VM files, LUNs, or flexible volumes. It is fully integrated with VMware vsphere vstorage APIs for Array Integration (VAAI) and Microsoft offloaded data transfer (ODX). The use of FlexClone technology in VDI deployments provides high levels of scalability and significant savings on cost, space, and time. Both file-level and volume-level cloning are tightly integrated with the VMware vcenter Server through the NetApp Virtual Storage Console (VSC) Provisioning and Cloning vcenter plug-in and native VM cloning offload with VMware VAAI and Microsoft ODX. The 15 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

16 VSC provides the flexibility to rapidly provision and redeploy thousands of VMs with hundreds of VMs in each datastore. Inline pattern matching occurs while data is being written to the storage system. Incoming data is received and hashed against existing data on the system; if the data is found to be similar, it is marked for bit-for-bit comparison. Any zeros written to the system are removed through inline deduplication. Inline deduplication saves space and improves performance by not writing zeroes. This feature is available in Data ONTAP 8.3 and later. By not writing zeroes, it increases performance. It improves storage efficiency by eliminating the need to deduplicate the zeroes. It improves cloning time for eager zeroed thick disk files and eliminates the zeroing of VMDKs that require zeroing before data write, thus increasing SSD life expectancy. Inline compression saves space by compressing data as it enters the storage controller. Inline compression can be beneficial for many of the different data types that make up a virtual desktop environment. Each of these different data types has different capacity and performance requirements, so some data types might be more suited for inline compression than others. Using inline compression and deduplication together can significantly increase storage efficiency over using each alone. Advanced drive partitioning distributes the root file system across multiple disks in an HA pair. It allows higher overall capacity utilization by removing the need for dedicated root and spare disks. This feature is available in Data ONTAP 8.3 and later. Multiprotocol Support By supporting all common NAS and SAN protocols on a single platform, NetApp unified storage enables the following benefits: Direct access to storage by each client Network file sharing across different platforms without the need for protocol-emulation products such as Samba, NFS Maestro, or PC-NFS Simple and fast data storage and data access for all client systems Fewer storage systems Greater efficiency from each system deployed Clustered Data ONTAP can support several protocols concurrently in the same storage system. Unified storage is important to VMware Horizon 6 solutions, such as CIFS/SMB for user data, NFS or SAN for the VM datastores, and guest-connect iscsi LUNs for Windows applications. The following protocols are supported: NFS v3, v4, and v4.1, including pnfs iscsi FC Fibre Channel over Ethernet (FCoE) CIFS/SMB VMware Integrations The complexity of deploying and managing thousands of virtual desktops can be daunting without the right tools. The NetApp Virtual Storage Console (VSC) for VMware vsphere is tightly integrated with VMware vcenter for rapidly provisioning, managing, configuring, and backing up a VMware Horizon 6 implementation. The NetApp VSC significantly increases operational efficiency and agility by simplifying the deployment and management process for thousands of virtual desktops. 16 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

17 The following plug-ins and software features simplify deployment and administration of virtual desktop environments: vsphere Virtual Volumes and the NetApp VASA Provider aggregate and abstract storage, allowing simpler management and visibility for the VMware administrator. The NetApp VSC Provisioning and Cloning plug-in enables customers to rapidly provision, manage, import, and reclaim space of thinly provisioned VMs and to redeploy thousands of VMs. The NetApp VSC Backup and Recovery plug-in integrates VMware snapshot functionality with NetApp Snapshot functionality to protect VMware Horizon 6 environments. Replication The NetApp Backup and Recovery plug-in for VSC is an innovative, scalable, integrated data protection solution for persistent desktop VMware Horizon 6 environments. The backup and recovery plug-in allows customers to leverage VMware snapshot functionality with NetApp array-based block-level Snapshot copies to provide consistent backups for the virtual desktops. The backup and recovery plug-in is integrated with NetApp SnapMirror replication technology, which preserves the deduplicated storage savings from the source to the destination storage array. Deduplication then does not have to be rerun on the destination storage array. When a VMware Horizon 6 environment is replicated with SnapMirror, the replicated data can be quickly brought online to provide production access during a site or data center outage. In addition, SnapMirror is fully integrated with VMware vcenter Site Recovery Manager (SRM) and NetApp FlexClone technology. Customers can instantly create zero-cost writable copies of the replicated virtual desktops at the remote site and use these copies for disaster recovery testing or for testing and development work. 2.3 VMware Horizon 6 VMware Horizon 6 is an enterprise-class desktop virtualization solution that delivers virtualized or remote desktops and applications to end users through a single platform. Horizon 6 allows IT professionals to manage desktops, applications, and data centrally while increasing flexibility and customization at the endpoint for the user. It enables levels of availability and agility of desktop services that are superior to traditional PCs at about half the total cost of ownership per desktop. Horizon 6 is a tightly integrated end-to-end solution built on the industry-leading virtualization platform, VMware vsphere. Figure 4 provides an architectural overview of a Horizon 6 deployment that includes seven main components: View Connection Server streamlines the management, provisioning, and deployment of virtual desktops by acting as a broker for client connections, authenticating and directing incoming user desktop requests. Administrators can centrally manage thousands of virtual desktops from a single console, and end users connect through View Connection Server to securely and easily access their personalized virtual desktops. View Security Server is an instance of View Connection Server that adds another layer of security between the Internet and the internal network. View Composer is an optional feature that allows you to manage pools of linked-cloned desktops by creating master images that share a common virtual disk. View Agent service communicates between VMs and Horizon Client. The View Agent is installed on all VMs managed by vcenter Server so that View Connection Server can communicate with them. Agent also provides features such as connection monitoring, virtual printing, persona management, and access to locally connected USB devices. View Agent is installed in the guest OS. Horizon Clients can be installed on each endpoint device to enable end users to access their virtual desktops from devices such as zero clients, thin clients, Windows PCs, Mac computers, and ios- 17 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

18 based and Android-based mobile devices. Horizon Clients are available for Windows, Mac, Ubuntu, Linux, ios, and Android to provide the connection to remote desktops from the device of choice. Persona management is an optional feature that provides persistent dynamic user profiles across user sessions on different desktops. This capability allows you to deploy pools of stateless floating desktops and enables users to maintain their designated settings between sessions. User profile data is downloaded as needed to speed up login and logout time. New user settings are automatically sent to the user profile repository during desktop use. ThinApp is an optional software component included with Horizon that creates virtualized applications. Figure 4) Horizon 6 deployment (graphic supplied by VMware). The following sections describe the Horizon 6 components used in this reference architecture: Horizon 6 View Connection Server and Horizon 6 View Composer. View Connection Server VMware View Connection Server is responsible for provisioning and managing virtual desktops and for brokering the connections between clients and the virtual desktop machines. A single View Connection Server instance can support up to 2,000 simultaneous connections. In addition, five View Connection Server instances can work together to support up to 10,000 virtual desktops. For increased availability, View supports using two additional Connection Server instances as standby servers. The Connection Server can optionally log events to a centralized database that is running either Oracle Database or Microsoft SQL Server. Table 3 lists the components of the View Connection Server VM configuration. Note: Only one View Connection Server was used in this reference architecture. This decision created a single point of failure but provided better control during testing. Production deployments should use multiple View Connection Servers to provide broker availability. 18 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

19 Table 3) View Connection Server VM configuration. View Connection Server VM Configuration VM quantity 1 OS Windows Server 2008 R2 (64-bit) VM hardware version 10 vcpu Memory Network adapter type 4 vcpus 10GB VMXNET3 Network adapters 2 Hard disk size Hard disk type 60GB Thin View Composer VMware Horizon 6 View Composer is a critical component of solutions with nonpersistent VMs. This server is responsible for the creation and maintenance operations of VMware Horizon 6 linked clones and nonpersistent VVOL VMs. It works with the View Connection Server to rapidly provision storage-efficient virtual desktops for use in the VMware Horizon 6 desktop environment. These linked-clone desktops created by View Composer can be either dedicated or floating virtual desktops in an automated pool. (For this reference architecture, dedicated desktops in an automated pool were created on VVOL datastores.) View Composer is also involved during maintenance operations such as refresh, recompose, and rebalance. These operations improve the storage efficiency, performance, security, and compliance of the virtual desktop environment. View Composer can be installed on a VMware vcenter Server or as a standalone server, excluding any servers participating in the VMware Horizon 6 environment, such as the Connection Server, the Transfer Server, or the Security Server. (For this reference architecture, the Composer server was installed on a separate VM.) Table 4 lists the components of the View Composer VM configuration. Table 4) View Composer VM configuration. View Composer VM Configuration VM quantity 1 OS Windows Server 2008 R2 (64-bit) VM hardware version 10 vcpu Memory Network adapter type 4 vcpus 8GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 60GB Thin 19 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

20 As Figure 5 shows, for these tests, we increased the maximum number of concurrent View Composer maintenance operations and the maximum number of provisioning operations to 30. Figure 5) View Composer concurrent operation limits. 2.4 Login VSI Login VSI provides performance insights for virtualized desktop and server environments. Enterprise IT departments use Login VSI products in all phases of their virtual desktop deployment from planning to deployment to change management for more predictable performance, higher availability, and a more consistent end-user experience. The world s leading virtualization vendors use the flagship product, Login VSI, to benchmark performance. With minimal configuration, Login VSI products work with VMware Horizon View, Citrix XenDesktop and XenApp, Microsoft Remote Desktop Services (Terminal Services), and any other Windows-based virtual desktop solution. For more information, download a trial at Login VSI bears no responsibility for this publication in any way and cannot be held liable for any damages following from or related to any information in this publication or any conclusions that may be drawn from it. 3 vsphere Virtual Volumes VMware vsphere Virtual Volumes (VVOLs) and related components are the building blocks for VM granular management. The fundamental goal of the technology is to separate the management of storage from the management of VMs so that the required knowledge and understanding for the two technology areas can be better focalized. Before VVOLs were added to VMware vsphere, administrators who understood storage had to explain to VI administrators who were not storage specialists how to identify the datastores to use for specific classes of VMs or for component virtual disks and other storage-consuming objects. They tried to achieve that objective through some combination of documentation and conventions for datastore naming. However, consistency, compliance, and verification were difficult to maintain and enforce. 20 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

21 3.1 VM Storage Policies VM storage policies constitute one of the key elements of the VVOL solution. These policies existed in versions of vsphere earlier than vsphere 6.0, but they lacked the sophistication to query the storage for the capabilities to include in rule sets. Consequently, capabilities could be advertised only as a single string. VMware vsphere APIs for Storage Awareness (VASA) 2.0 provides the technology to query storage and return a set of storage capabilities to vcenter. VASA vendor providers supply the translation between the storage system APIs and constructs and the VMware APIs that are understood by vcenter. In the NetApp implementation, the VASA vendor provider is NetApp VASA Provider 6.0 for clustered Data ONTAP, an appliance VM that is deployed to vcenter from an OVA file. VASA Provider is managed through pages and context-sensitive menus in the NetApp VSC plug-in. VASA Provider presents the set of capabilities of the storage array or of an object in the array to vcenter. The capabilities include features such as availability, performance, capacity, space efficiency, replication, and protocol. Support for a capability might require specific hardware, licenses, or configuration. A set of capabilities for a volume or a set of volumes is called a storage capability profile (SCP). Storage administrators use the VSC to create and manage SCPs. Storage for VMs that use VVOLs is provisioned through VM storage policies. The VI administrator creates VM storage policies to define the storage requirements for the VMs and then maps NetApp storage capabilities to one or more VM storage policies. Capabilities can be mapped to VM storage policies as an SCP, as individual capabilities, or as both. If both mapping methods are used, the individual capability selected in the VM storage policy overrides the capability selected in the SCP. For example, if a VM storage policy includes both an SCP that requires deduplication and a separate deduplication capability with the setting No, the resulting VM storage policy requires a NetApp FlexVol volume without deduplication. The Create VM Storage Policy wizard lists the storage objects that are compatible and incompatible with the VM storage policy after the VI administrator selects capabilities or a profile to add to the policy. Table 5 summarizes the NetApp storage capabilities that are supported by VVOLs. Table 5) NetApp storage capabilities supported by VVOLs. Capabilities VM Storage Policy Values Storage Capability Profile Values Requirements and Notes Profile name Selection from a list N/A Used in VM storage policies to map a NetApp SCP; allows the VI administrator to select a predefined set of capabilities Autogrow Yes, no Yes, no, any Volume set to allow autogrow Compression Yes, no Yes, no, any Compression enabled on volume Deduplication Yes, no Yes, no, any Deduplication enabled on volume Disk types Multiselection: SATA, FCAL, SAS, SSD SATA, FCAL, SAS, SSD, any Aggregate consisting of disks of the specified type Flash accelerated Yes, no Yes, no, any One of the following: NetApp Flash Cache cards installed in the node that hosts the containing aggregate NetApp Flash Pool aggregates containing SSDs 21 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

22 Capabilities VM Storage Policy Values Storage Capability Profile Values Requirements and Notes and another disk type, and the aggregate setting -hybrid=true High availability Yes, no HA pair, no HA, any Nodes configured as HA pairs MaxThroughput_IOPS Numeric value Enter number, then select IOPS or MBPS MaxThroughput_MBPS Numeric value Enter number, then select IOPS or MBPS Quality of service (QoS) on the FlexVol volume with an IOPS limit QoS on the FlexVol volume with a throughput limit Protocol Multiselection: NFS, iscsi, FCP NFS, iscsi, FCP, any Matching protocol licensed and properly configured in the storage virtual machine (SVM), including necessary data LIFs Replication Yes, no Async, sync, none, any NetApp SnapMirror relationship replicating the FlexVol volume to another FlexVol volume Replication relationships are created and managed outside of vcenter, VSC, and VASA Provider; for example, they can be created by using NetApp OnCommand System Manager. 3.2 VVOL Datastores Traditional datastores are either Virtual Machine File Systems (VMFSs) created on LUNs or storage controller file systems presented as NFS mounts. Within these datastores, each VM has a directory that contains a set of files. The set includes virtual disks, which are large files containing a disk image, and other files such as VM swap files, configuration files, and logs. In the NetApp implementation of VVOLs, a VVOL datastore consists of one or more FlexVol volumes within a storage container (displayed as backing storage ). A storage container is simply a set of FlexVol volumes used for VVOL datastores. All FlexVol volumes in a storage container must be accessed through the same protocol (NFS, iscsi, or FC) and must be owned by the same SVM. They can be hosted on different aggregates and different nodes of the NetApp cluster, however. Warning The VASA Provider virtual appliance must not reside on a VVOL datastore. The VASA Provider is a required component for power management operations of VVOL objects. If the VASA Provider is unavailable (for example, if it has been powered off), then VMs in the VVOL datastore cannot be managed. If a VASA Provider that is located in a VVOL datastore is powered off, it cannot be powered back on. FlexVol volumes can be created outside of the VSC workflows or through the new VVOL datastore wizard. However, all LUNs and other VVOL-related objects are created and managed by VASA Provider. A VVOL is either a LUN used with block protocols or a file or directory used with NFS. A VVOL LUN is not 22 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

23 mapped (masked, in common SAN terminology) to storage in the sense that traditional LUNs are. Table 6 lists the different types of VVOLs and describes how they are implemented. Table 6) VVOL types and implementation. VVOL Type Block Implementation NFS Implementation Notes or Examples Configuration LUN, 4GB Directory containing configuration files and pointers to other VVOLs Contains.vmx file, NVRAM, logs, VMDK descriptors, and VMware snapshot descriptors; one per VM; contains small VMFS Data LUN, size of virtual disk File, size of virtual disk N/A Swap LUN, size of virtual memory* File, size of virtual memory* Created when the VM is powered on; deleted when the VM is powered off Memory LUN, size of virtual memory File, size of virtual memory Created only if a memory VMware snapshot is selected when running a VM snapshot Other Depends on use case Depends on use case VMware HA datastore heartbeat information (4GB LUN or NFS directory) * Technically, the swap VVOL is the size of the VM memory minus any VM memory reservation. 3.3 Protocol Endpoints The I/O path to a VVOL travels through a new storage object called a protocol endpoint (PE). VVOL LUNs are bound to a specific PE through a binding call that is managed by VASA Provider. VASA Provider determines which PE is on the same node as the FlexVol volume that contains the VVOL and binds the VVOL to that PE. VVOLs are bound to a PE when they are accessed by a VMware ESXi server. The most common form of access is powering on the VM. The blue lines in the command block in Figure 6 show the binding relationship between a VVOL and the PE LUN through which the ESXi server accesses that VVOL. Figure 6) Binding relationship between a PE LUN and a VVOL. Vserver Name: WestPac_a_iSCSI PE MSID: PE Vdisk ID: d f1b9a VVol MSID: VVol Vdisk ID: d e193fe3b7 Vserver UUID: 4fe2e2b0-7cd8-11e4-b968-00a0983d22b6 Protocol Endpoint: /vol/netapp_iscsi_vvol_flexvol/vvolpe PE UUID: 047d0366-ee7b-4bcf-9cdc-99cecc PE Node: alpha-01 VVol: /vol/netapp_iscsi_vvol_flexvol/naa.600a d24464f vmdk VVol Node: alpha-01 VVol UUID: 534dc4ff-116c-47bb d27f97370cb Secondary LUN: d2249d Optimal binding: true Reference Count: 1 Best Practice To remove the need to create PEs manually, perform the VVOL workflows through the VSC. 23 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

24 For block protocols, a PE is a small (4MB) LUN. VASA Provider creates one PE in each FlexVol volume that is part of a VVOL datastore, as shown in Figure 7. PEs are mapped to initiator groups that are created and managed by VASA Provider. Best Practice LUN PEs are mapped by using LUN IDs of 300 and higher. Make sure that the advanced option Disk.MaxLUN allows a LUN ID number that is higher than 300 (the default is 1,024). Figure 7) LUN PEs. For NFS, a PE is a mount point to the root of the SVM. VASA Provider creates a PE for each data LIF of the SVM by using the LIF s IP address, as shown in Figure 8. VASA Provider creates PEs when the first VVOL datastore is created on the SVM by using a specific protocol. VASA Provider also creates export policy rules automatically. 24 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

25 Figure 8) NFS PEs. 3.4 VVOL Considerations for VMware Horizon 6 Relationship of VVOL to FlexVol When VVOLs are created for use with VMware Horizon 6, version 6.1.1, VVOL design is very important. A VVOL datastore can contain one or more FlexVol volumes, each with differing characteristics. However, to maximize VM provisioning speed and storage efficiency, NetApp recommends using only one FlexVol volume per VVOL container, as shown in Figure 9. For nonpersistent linked clones, each VVOL datastore receives its own replica, and then View Composer clones from it. Figure 9) One FlexVol volume per VVOL container. 25 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

26 Best Practice When VVOL datastores are provisioned for use with VMware Horizon 6, only one FlexVol volume should be provisioned per VVOL datastore. VVOL Types for VMware Horizon 6 When virtual desktops are created with VVOLs, multiple disks (VMDKs or LUNs) might be required for VMware Horizon 6 depending on the different technologies used. Table 7 and Table 8 list the different disks, their type, and their use. Table 7) Horizon View disk use. Horizon View Disk VVOL Type Desktop Type Use N/A Metadata All desktops (LUN for block protocols, directory for NFS) Stores VM configuration information (.vmx file, logs) OS disk Data All desktops C:\ drive and changed data (without disposable-data disk and View Composer persistent disk) (required) OS disk snapshot Data fast clone of data VVOL All linked clones Used for VM refresh operations to revert state View Composer persistent disks Data Dedicated linked clones Stores user data and profile (optional) Disposable-data disk Data Linked clones Stores temp and swap files (optional) Disposable-data disk snapshot Data clone of disposable file disk Linked clones FlexClone volume of disposable-data disk (automatically created) QuickPrep configurationdata disk Data All desktops Stores VM configuration information (required).vswp Swap All desktops VM swap file (required) Table 8) Disk type and use for VVOLs and Horizon View. Desktop Type and Disk Use Metadata Data Data Disk Snapshot Disposable Disk User Data Disk Internal Disk vswap Max. Disks per VM Nonpersistent desktops (data) 1 (snapshots) Persistent desktops N/A 1 N/A N/A N/A Note: When performing the VMware Horizon 6 validation for VVOLs, we had to enable all features, resulting in 8 VMDKs for NFS per VM or 8 LUNS per VM. 26 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

27 VVOLs and Storage Efficiency When Data ONTAP is used on an All Flash FAS system, inline-only is the default storage efficiency policy. The version of the VSC used in this reference architecture does not properly create volumes with this default policy, so we had to take additional steps to enable the appropriate storage efficiency technologies. To enable always-on deduplication, we first executed the script that appears in section 5.4, Always-On Deduplication. After we created and applied the new always-on deduplication policy to the volume, we used the following command line to enable inline compression on all of the volumes: vol efficiency modify -volume vdi* -inline-compression true 4 Solution Infrastructure This section describes the software and hardware components of the solution. Figure 10 shows the solution infrastructure. Figure 10) Solution infrastructure. 27 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

28 4.1 Hardware Infrastructure During solution testing, 24 servers were used to host the infrastructure and the desktop VMs. The desktops and infrastructure servers were hosted on discrete resources so that the workload to the NetApp All Flash FAS system could be precisely measured. It is both a NetApp and an industry best practice to separate the desktop VMs from the infrastructure VMs because noisy neighbors or bully virtual desktops can affect the infrastructure. This effect can have a negative impact on all users, applications, and performance results. A separate NetApp FAS system was used to host the infrastructure and launcher VMs. This configuration would be typical for a customer environment. Table 9 lists the hardware specifications of each server category. Table 9) Hardware components of server categories. Hardware Components Configuration Infrastructure Servers and Launcher Servers Server quantity 4 CPU model Intel Xeon CPU 2.6GHz (6-core) Total number of cores 12 Memory per server Storage 256GB Two 4GB embedded USB disks Desktop Servers Server quantity 20 CPU model Intel Xeon CPU 2.6GHz (6-core) Total number of cores 12 Memory per server Storage 256GB Two 4GB embedded USB disks Storage NetApp system Disk shelf Disk drives AFF8060 HA pair 2 DS2246 shelves Forty-eight 400GB SSDs 4.2 Software Components This section describes the purpose of each software product used to test the NetApp All Flash FAS system and provides configuration details. Table 10 lists the software components and identifies the version of each component. 28 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

29 Table 10) Solution software components. Software Version NetApp FAS Clustered Data ONTAP RC1 NetApp PowerShell Toolkit NetApp OnCommand System Manager NetApp VSC NetApp VASA Provider Storage protocol RC1 6.0 X1 6.0 X3 NFS VMware Software VMware ESXi 6.0.0, VMware vcenter Server build VMware Horizon 6 View Administrator build VMware Horizon 6 View Composer VMware Horizon 6 Client VMware Horizon 6 View Agent VMware vsphere PowerCLI Workload Generation Utility Login VSI Professional Database Server Microsoft SQL Server Microsoft SQL Server native client 2008 R2 (64-bit) 11.0 (64-bit) 4.3 VMware vsphere 6.0 This section describes the VMware vsphere components of the solution. VMware ESXi 6.0 The tested reference architecture used VMware ESXi 6.0 across all desktop servers. For hardware configuration information, refer to Table 9. VMware vsphere 6.0 Configuration The tested reference architecture used a VMware vcenter Server 6.0 virtual appliance. This vcenter Server was configured to host the infrastructure cluster, the Login VSI launcher cluster, and the desktop clusters. For the vcenter Server database, a Windows Server 2008 R2 VM was configured with Microsoft SQL Server 2008 R2. Table 11 lists the components of the VMware vcenter Server VM configuration, and Table 12 lists the components of the Microsoft SQL Server database VM configuration. 29 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

30 Table 11) VMware vcenter Server VM configuration. VMware vcenter Server VM Configuration VM quantity 1 OS SUSE Linux Enterprise (64-bit) (vcenter Server Appliance) VM hardware version 8 vcpu Memory Network adapter type 16 vcpus 32GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 11 VMDKs totaling 458GB Mixed Table 12) Microsoft SQL Server database VM configuration. Microsoft SQL Server VM Configuration VM quantity 1 OS Windows Server 2008 R2 (64-bit) VM hardware version 8 vcpu Memory Network adapter type 4 vcpus 8GB VMXNET3 Network adapters 2 Hard disk size Hard disk type 60GB Thin 4.4 NetApp Virtual Storage Console The NetApp VSC is a management plug-in for VMware vcenter Server that simplifies management and orchestration of common NetApp administrative tasks. The tested reference architecture used the VSC for the following tasks: Setting NetApp best practices for ESXi hosts: Timeout values Host bus adapter (HBA) Multipath input/output (MPIO) NFS settings Cloning infrastructure VMs and Login VSI launcher machines 30 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

31 The VSC can be coinstalled on the VMware vcenter Server instance if the Windows version of vcenter is used. For this reference architecture, a separate server was used to host the VSC. Table 13 lists the components of the tested NetApp VSC VM configuration. Table 13) NetApp VSC VM configuration. NetApp VSC Configuration VM quantity 1 OS Windows Server 2008 R2 (64-bit) VM hardware version 10 vcpu Memory Network adapter type 2 vcpus 4GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 60GB Thin 4.5 NetApp VASA Provider 6.0 for Clustered Data ONTAP NetApp VASA Provider is a virtual appliance that works in conjunction with the NetApp VSC. To improve storage feature visibility, VASA Provider supplies information about the NetApp storage systems back to the vcenter Server. The virtualization administrator can then make more informed decisions about storage and VM provisioning. VASA Provider also enables VVOL support and storage capability profiles as well as enhanced monitoring of storage systems. Table 14 lists the components of the tested NetApp VASA Provider VM configuration. Table 14) NetApp VASA Provider VM configuration. NetApp VASA Provider Configuration VM quantity 1 OS Other 2.6.x Linux (64-bit) VM hardware version 7 vcpu Memory Network adapter type 4 vcpus 8GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 4 VMDKs totaling 54GB Thin 31 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

32 4.6 Virtual Desktops The desktop VM template was created with the virtual hardware and software listed in Table 15. The VM hardware and software were installed and configured according to the Login VSI documentation. Table 15) Virtual desktop configuration. Desktop Configuration Desktop VM VM quantity 2,000 VM hardware version 11 vcpu Memory Network adapter type 1 vcpu 2GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 24GB Thin Desktop Software Guest OS Windows 7 (32-bit) VM hardware version ESXi 6.0 and later (VM version 11) VMware tools version Microsoft Office 2010 version Microsoft.NET Framework 3.5 Adobe Acrobat Reader Adobe Flash Player Java Doro Writer PDF 1.82 VMware Horizon 6 View Agent Login VSI target software After the desktops were provisioned, Windows PowerShell was used to set the uuid.action in the.vmx file on each VM in the desktop s datastore. We took this step so that during testing, no questions would be asked about the movements of VMs. Figure 11 shows the complete command. Figure 11) Setting uuid.action in the.vmx file with Windows PowerShell. Get-Cluster Desktops Get-VM Get-AdvancedSetting -Name uuid.action Set-AdvancedSetting -Value "keep" -Confirm:$false 32 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

33 Guest Optimization In keeping with VMware Horizon 6 best practices, guest OS optimizations were applied to the template VMs used in this reference architecture. Figure 12 shows the VMware OS Optimization Tool that was used to perform the guest optimizations. Figure 12) VMware OS Optimization Tool. Although it might be possible to run desktops without guest optimizations, the impact of not optimizing must first be understood. Many recommended optimizations address services and features (such as hibernation, Windows update, or system restore) that do not provide value in a virtual desktop environment. To run services and features that do not add value would decrease the overall density of the solution and increase cost because they would consume CPU, memory, and storage resources in relation to both capacity and I/O. To achieve superior scalability, performance, and cost-effectiveness in a virtual desktop deployment, NetApp recommends that each customer evaluate the optimization scripts for Horizon 6 and apply them as needed. The VMware Horizon View Optimization Guide for Windows 7 and Windows 8 describes the guest OS optimization process, from how to install Windows 7 to how to prepare the VM for deployment. 4.7 Login VSI Server The Login VSI server is where the Login VSI binaries are run as well as the Windows share that hosts the user data, binaries, and workload results. The tested machine was configured with the virtual hardware listed in Table NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

34 Table 16) Login VSI server configuration. Login VSI Server Configuration VM quantity 1 OS Windows Server 2008 R2 (64-bit) VM hardware version 10 vcpu Memory Network adapter type 2 vcpus 8GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 60GB Thin Figure 13 shows the Login VSI launcher configuration. Figure 13) Login VSI launcher configuration. 34 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

35 4.8 Login VSI Launcher VM Table 17 lists the components of the Login VSI launcher VM configuration. Table 17) Login VSI launcher VM configuration. Login VSI Launcher VM Configuration VM quantity 80 OS Windows Server 2008 R2 (64-bit) VM hardware version 10 vcpu Memory Network adapter type 2 vcpus 4GB VMXNET3 Network adapters 1 Hard disk size Hard disk type 60GB Thin 4.9 Windows Infrastructure VM In the tested configuration, two VMs were provisioned and configured to serve Active Directory, Domain Name System (DNS), and Dynamic Host Configuration Protocol (DHCP) services for the reference architecture. The servers provided these services to both infrastructure and desktop VMs. Table 18 lists the components of the Windows infrastructure VM. Table 18) Windows infrastructure VM configuration. Microsoft Windows Infrastructure VM Configuration VM quantity 2 OS Windows Server 2008 R2 (64-bit) VM hardware version 10 vcpu Memory Network adapter type 2 vcpus 8GB VMXNET3 Network adapters 2 Hard disk size Hard disk type 60GB Thin 35 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

36 5 Storage Design This section provides an overview of the storage design, the aggregate and volume layout, and the VSC. 5.1 Storage Design Overview For the tested configuration shown in Figure 14, we used a 6U AFF8060 controller and two DS2246 disk shelves that are 2U per shelf, for a total of 10U. Note that the image in Figure 14 is a logical view, with the nodes separated to illustrate multipath HA. In actuality, however, both nodes reside in a single 6U enclosure. Figure 14) Multipath HA to DS2246 shelves of SSD. 5.2 Aggregate Layout In this reference architecture, we used forty-eight 400GB SSDs divided across two nodes of an AFF8060 controller. As shown in Figure 15, advanced drive partitioning was used, so each node owned half of the disks and the root volume was distributed across the aggregate. Figure 15) Advanced drive partitioning disk layout. 5.3 Volume Layout All VVOLs were provisioned with NetApp VASA Provider. During these tests, only 1.3TB was consumed of the total 8TB. Figure 16 shows the volume layout. 36 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

37 Figure 16) VVOL layout. Note: A rootvol for the VDI SVM was present but is not depicted in Figure 16. The rootvol volume was 1GB in size with 28MB consumed. 5.4 Always-On Deduplication Typical storage sizing for VDI environments includes sizing for headroom to prevent the end-user experience from being affected by a storage failover. This extra CPU headroom for storage failover typically is not used during normal operations. Storage architectures that do not use true active-active HA configurations do not have this benefit. With an AFF8000 system, it is possible to use deduplication with a very aggressive deduplication schedule to maintain storage efficiency all the time. To eliminate any potential concerns that always-on deduplication might cause additional wear on the SSDs, NetApp provides up to 7 years of support at point-of-sale pricing. This support includes 3 years of standard and years of extended support, regardless of the number of drive writes per day. 5.5 Requirements for Always-On Deduplication The following components are required in order to use always-on deduplication: AFF8000 Data ONTAP or later Best Practices Size the storage controller properly so that users are not affected if a storage failover occurs. NetApp recommends testing storage failover during normal operations. Stagger patching activities over a period of time. Have at least eight volumes per node for maximum deduplication performance. Set the efficiency policy schedule to one minute. Set the QoS policy for the storage efficiency policy to Background. Monitor the storage system performance with NetApp OnCommand Performance Manager, OnCommand Insight, or OnCommand System Manager in Data ONTAP Also use a desktop monitoring utility such as Liquidware Labs Stratusphere UX to measure the client experience. Disable deduplication in the event of a storage failover if client latencies increase. 37 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

38 For this reference architecture, we enabled always-on deduplication on all of the volumes used in testing. We created a storage efficiency policy that scheduled deduplication to run once every minute, and we set the QoS policy to background. Figure 17 shows a sample PowerShell script to configure always-on deduplication on the volumes specified in $volumes. Figure 17) PowerShell script to configure always-on deduplication. $controller = " " $vserver = "VDI_Vserver" $volumes Import-Module DataONTAP Connect-NcController $controller -Credential admin Add-NcJobCronSchedule "Always-On Deduplication" -Minute -1 New-NcSisPolicy "Always-On Deduplication" -Comment "Always-On Deduplication" -VserverContext $vserver -Schedule "Always-On Deduplication" -QosPolicy background ForEach ($volume in $volumes){ Set-NcSis -VserverContext $vserver -Name $volume -Policy "Always-On Deduplication" } Figure 18 shows editing of the Add Efficiency Policy user interface from OnCommand System Manager. Figure 18) Configuring the efficiency policy for always-on deduplication. 5.6 Inline Deduplication of Zeros in Data ONTAP 8.3 Inline deduplication of zeros is a storage efficiency technology introduced in Data ONTAP 8.3. There are a couple of different situations in which zeros are commonly written to storage in large quantities. The first and most common is when using VMDKs on VMFS. Each time a thin or lazy zeroed thick VMDK is extended, additional blocks must be zeroed before the data is written. For the best performance on VMFS, VMware recommends the use of eager zeroed thick (EZT) virtual disks to reduce the number of locks on the VMFS file system and eliminate waiting on zeroing operations. Without EZT on VMFS, ESXi has to lock the file system before each write by using the atomic test and set (ATS) VAAI primitive. Because VVOL data disks do not use VMFS, which is a shared file system, there is no need to perform locking or to write zeros beforehand. Therefore, thin provisioning can be used. 38 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

39 The second case is for normal data zeros. The elimination of any write to media helps to improve performance and extend media life span. Table 19 shows VMDK disk types and protocols. Table 19) Disk types and protocols. VMDK Type NFS VMFS Thin Zeroed on use Lazy zero thick Reserved Reserved and zeroed on use Eager zero thick Reserved and zeroed Reserved and zeroed Inline deduplication of zeros is a way to reduce writes to disk; instead of writing the zero and then performing always-on deduplication, it is a metadata update only. Deduplication must be turned on for the volume, at a minimum. By enabling deduplication, Data ONTAP inline deduplication of zeros provides approximately 20% faster cloning when cloning eager zeroed thick VMDKs. It eliminates the need to deduplicate the zeros from the VMs, thus increasing disk longevity. Best Practices Put the templates in the destination datastore. Enable deduplication on the volume; a schedule is not required. When using NFS, thin-provisioned disks are best because they provide end-to-end utilization transparency and have no up-front reservation that drives higher storage utilization. When using VMFS, eager zeroed thick disks are the best format. Using this format conforms with VMware s best practice for getting the best performance from your virtual infrastructure. Cloning time is faster with eager zeroed thick provisioning than with thin provisioning on VMFS datastores. When using VVOLS, thin-provisioned disks are the best because they provide end-to-end utilization transparency and have no upfront reservation that drives higher storage utilization. 5.7 NetApp Virtual Storage Console for VMware vsphere The NetApp VSC was used to register VASA Provider, and it interacted with VASA during the creation, deletion, power on, and power off of the VMs. 5.8 NetApp VASA Provider Virtual Appliance The NetApp VASA Provider virtual appliance is the heart of the NetApp VVOL solution. It is the intermediary between the ESXi hosts and vcenter and the NetApp AFF system. It advertises the storage capabilities to vcenter, handles the container and VM creation, and checks for policy compliance. 6 Horizon 6 Design This section provides an overview of the VMware Horizon 6 design, and it explains user assignment, automated desktop pools, linked-clone desktops, and the creation of desktop pools. 6.1 Overview In a typical large-scale virtual desktop deployment, the upper limit of the VMware Horizon 6 View Connection Server is reached when each Connection Server instance supports up to 2,000 simultaneous connections. Two thousand VMs is also the certification target for vsphere VVOLs. Exceeding the 2,000- seat maximum is as simple as adding more Connection Server instances and building additional VMware Horizon 6 desktop infrastructures to support more virtual desktops. Each such desktop infrastructure is referred to as a pool of desktops (POD). 39 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

40 A POD is a building-block approach to architecting a solution. The size of the POD is defined by the VMware Horizon 6 desktop infrastructure (the desktop VMs) plus any additional VMware Horizon 6 infrastructure resources necessary to support the desktop infrastructure PODs. In some cases, it might be best to design PODs that are smaller than the maximum size to allow growth in each POD or to reduce the size of the fault domain. Using a POD-based design gives IT a simplified management model and a standardized way to scale linearly and predictably. By using clustered Data ONTAP, customers can have smaller fault domains that result in higher availability. In this reference architecture, the number of Horizon 6 Connection Server instances was limited to one so that the POD-based design limits could be scaled. However, the results of the testing show that it might have been possible to deploy multiple PODs on this platform. VMware Horizon 6 groups desktops into discrete management units called pools. Policies and entitlements can be set for each pool so that all desktops in a pool have the same provisioning methods, user assignment policies, logout actions, display settings, data redirection settings, data persistence rules, and so forth. 6.2 User Assignment Each desktop pool can be configured with a different user assignment. User assignments can be either dedicated or floating. Dedicated Assignment Through the dedicated assignment of desktops, users log in to the same virtual desktop each time they log in. Dedicated assignment allows users to store data either on a persistent disk (when using linked clones) or locally (when using full clones). These assignments are usually considered and used as persistent desktops; however, it is the act of refreshing or recomposing that makes them nonpersistent. The process for user-to-desktop entitlement can be manual or automatic. The administrator can entitle a given desktop to a user or opt to allow VMware Horizon 6 to automatically entitle the user to a desktop at first login. Floating Assignment With floating user assignment, users are randomly assigned to desktops each time they log in. These assignments are usually considered and used as nonpersistent desktops; however, a user who does not log out of the desktop would always return to the same desktop. 6.3 Automated Desktop Pools An automated desktop pool dynamically provisions virtual desktops. With this pool type, VMware Horizon 6 creates a portion of the desktops immediately and then, based on demand, provisions additional desktops to the limits that were set for the pool. An automated pool can contain dedicated or floating desktops. These desktops can be full clones or linked clones. A major benefit of using VMware Horizon 6 with automated pools is that additional desktops are created dynamically on demand. This automation greatly simplifies the repetitive administrative tasks associated with provisioning desktops. 6.4 Linked-Clone Desktops To the end user, a linked-clone desktop looks and feels like a normal desktop, but it is storage efficient, consuming a fraction of the storage required for a full desktop. Because of the nonpersistent nature of linked clones, three unique maintenance operations can be performed to improve the storage efficiency, performance, security, and compliance of the virtual desktop environment: Refresh 40 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

41 Recompose Rebalance These maintenance operations can be used regardless of whether VVOLs, VCAI, or hypervisor-based snapshot linked clones are used. 6.5 Creating VMware Horizon 6 Desktop Pools Figure 19 shows how the VMs, pools, and datastores were designed in the tested reference architecture. The design used four pools with 250 VMs per pool. Each node of the NetApp AFF cluster had four VM datastores. Each pool used one datastore to host both the replica and the OS disk. Using a single datastore for both the replica and the OS disk made it possible to report on the workload as a whole for each VM. Splitting them up would have provided results for each, but because both were still required, it was better to report holistically. Keeping them together is more taxing on the storage during provisioning because a replica must be created for each datastore, and more storage controller cache is used during steady state. Figure 19) VMware Horizon 6 pool and desktop-to-datastore relationship. The Windows PowerShell script shown in Figure 20 creates four pools named vdi0#n0#. In the tested reference architecture, these four pools were created across two nodes of the NetApp AFF cluster. This 41 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

42 approach allowed the best parallelism across the storage system. The Login VSI Active Directory group was then entitled to the created pools. This Windows PowerShell script was run from the VMware Horizon 6 PowerCLI located on the VMware Horizon 6 server. Figure 20) Windows PowerShell script to create 8 pools of 250 desktops each. $vcserver = " " $domain = "ra.rtp.netapp.com" $username = "administrator@vsphere.local" $numvms = "250" $parentvmpath = "/RA/vm/Discovered virtual machine/vvolvm" $parentsnapshotpath = "/HORIZON" $vmfolderpath = "/RA/vm" $resourcepoolpath = "/RA/host/Desktops/Resources" $overcommit = "Unbounded" $persistance = "Persistent" $OrganizationalUnit = "OU=Computers,OU=LoginVSI" Connect-VIserver $vcserver Username $administrator #Create pools below for ($j=1; $j -le 2; $j++){ Write-Host "Creating $numvms desktops" Get-ViewVC -servername $vcserver Get-ComposerDomain -domain $domain -Username administrator Add-AutomaticLinkedCLonePool -pool_id vdi01n0$j -displayname vdi01n0$j -nameprefix "vdi01n0$j- {n:fixed=3}" -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath -vmfolderpath $vmfolderpath -resourcepoolpath $resourcepoolpath -datastorespecs "[$overcommit,os,data]/ra/host/desktops/vdi01n0$j" -HeadroomCount $numvms -minimumcount $numvms - maximumcount $numvms -OrganizationalUnit $OrganizationalUnit -UseTempDisk $false -UseUserDataDisk $false -PowerPolicy "AlwaysOn" -SuspendProvisioningOnError $false Write-Host "Creating $numvms desktops" Get-ViewVC -servername $vcserver Get-ComposerDomain -domain $domain -Username administrator Add-AutomaticLinkedCLonePool -pool_id vdi02n0$j -displayname vdi02n0$j -nameprefix "vdi02n0$j- {n:fixed=3}" -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath -vmfolderpath $vmfolderpath -resourcepoolpath $resourcepoolpath -datastorespecs "[$overcommit,os,data]/ra/host/desktops/vdi02n0$j" -HeadroomCount $numvms -minimumcount $numvms - maximumcount $numvms -OrganizationalUnit $OrganizationalUnit -UseTempDisk $false -UseUserDataDisk $false -PowerPolicy "AlwaysOn" -SuspendProvisioningOnError $false Write-Host "Creating $numvms desktops" Get-ViewVC -servername $vcserver Get-ComposerDomain -domain $domain -Username administrator Add-AutomaticLinkedCLonePool -pool_id vdi03n0$j -displayname vdi03n0$j -nameprefix "vdi03n0$j- {n:fixed=3}" -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath -vmfolderpath $vmfolderpath -resourcepoolpath $resourcepoolpath -datastorespecs "[$overcommit,os,data]/ra/host/desktops/vdi03n0$j" -HeadroomCount $numvms -minimumcount $numvms - maximumcount $numvms -OrganizationalUnit $OrganizationalUnit -UseTempDisk $false -UseUserDataDisk $false -PowerPolicy "AlwaysOn" -SuspendProvisioningOnError $false Write-Host "Creating $numvms desktops" Get-ViewVC -servername $vcserver Get-ComposerDomain -domain $domain -Username administrator Add-AutomaticLinkedCLonePool -pool_id vdi04n0$j -displayname vdi04n0$j -nameprefix "vdi04n0$j- {n:fixed=3}" -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath -vmfolderpath $vmfolderpath -resourcepoolpath $resourcepoolpath -datastorespecs "[$overcommit,os,data]/ra/host/desktops/vdi04n0$j" -HeadroomCount $numvms -minimumcount $numvms - maximumcount $numvms -OrganizationalUnit $OrganizationalUnit -UseTempDisk $false -UseUserDataDisk $false -PowerPolicy "AlwaysOn" -SuspendProvisioningOnError $false } #Entitle pools below sleep 300 Add-PoolEntitlement -Pool_id vdi01n01 -Sid S Add-PoolEntitlement -Pool_id vdi02n01 -Sid S Add-PoolEntitlement -Pool_id vdi03n01 -Sid S Add-PoolEntitlement -Pool_id vdi04n01 -Sid S Add-PoolEntitlement -Pool_id vdi01n02 -Sid S Add-PoolEntitlement -Pool_id vdi02n02 -Sid S Add-PoolEntitlement -Pool_id vdi03n02 -Sid S Add-PoolEntitlement -Pool_id vdi04n02 -Sid S NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

43 Prerequisites Before testing began, the following requirements were met: We created 2,000 users and a group in Active Directory by using the Login VSI scripts. We created datastores on the NetApp storage by using the NetApp VASA plug-in. 7 Login VSI Workload Login VSI is an industry-standard workload-generation utility for VDI. The Login VSI tool works by replicating a typical user s behaviors. Different workloads can be selected, and the workload can be customized for specific applications and user profiles. 7.1 Login VSI Components As shown in Figure 21, Login VSI includes many different components to run and analyze user workloads. We used the Login VSI server to configure the components (such as Active Directory, the user workload profile, and the test profile) and to gather the data. In addition, we created a CIFS/SMB share on the Login VSI server that shared the user files that the workload would use. When the test was executed, the Login VSI share logged in to the launcher servers, which in turn logged in to the target desktops and began the workload. Figure 21) Login VSI components. Login VSI Launcher The tested reference architecture followed the Login VSI best practice of having 25 VMs per launcher server. PCoIP was used as the display protocol between the launcher servers and the virtual desktops. Figure 22 shows the relationship between the desktops and the launcher server. 43 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

44 Figure 22) Desktop-to-launcher relationship. Workload These tests used the Login VSI office worker workload to simulate users working. The office worker workload, which is available in Login VSI 4.1.3, is based on a knowledge worker workload. The team from Login VSI recommended using this workload with Login VSI because it is very similar to the medium workload in Login VSI 3.7. The applications that were used are listed in Table 15 under the Desktop Software subheading. 8 Testing and Validation This section describes the testing and validation of 2,000 desktops. 8.1 Overview During testing, the VMware Horizon 6 configuration listed in Table 20 was used. As stated previously, a Windows PowerShell script was used for provisioning. The 2,000 desktops were provisioned with the options listed in Table NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

45 Table 20) VMware Horizon 6 configuration options. Component Pool type User assignment Enable automatic assignment Clone type Maximum number of desktops Number of spare (powered-on) desktops View Composer disks Replica disks (separate datastores for replica and OS disks) User data disk User views storage accelerator Reclaim VM disk space Datastore selection Storage overcommit Customization method Power policy Configuration Option Automated pool Dedicated Yes Horizon 6 View Composer linked clones (on VVOL datastores) 250 per pool 250 per pool Do not redirect disposable files No No No No (deselect other options) 1 datastore per pool Unbounded VMware QuickPrep Always on Dedicated Desktops The reference architecture used dedicated desktops with automated assignment so that any workload issues could be easily pinpointed. This approach also allowed users to be assigned specific desktops and enabled the measurement of the login with the profile creation, which would represent either a fresh desktop or a floating desktop, as well as the second login to a desktop. The measured behaviors are referred to as Monday morning login and Tuesday morning login, as referenced in NetApp TR-3949: NetApp and VMware View 5,000-Seat Performance Report. 8.2 Test Results Overview Table 21 lists the high-level results that were achieved during the reference architecture testing. 45 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

46 Table 21) Test results overview. Test Time to Complete Peak IOPS Peak Throughput Average Storage Latency Provisioning 2,000 desktops 92 min 89, GBps 1.04ms Boot storm (VMware vcenter power-on operations) 6 min, 17 sec 156, GBps 1.15ms Boot storm (VMware Horizon 50 concurrent power-on operations) 27 min, 29 sec 56, GBps 0.49ms Boot storm during storage failover 8 min, 45 sec 91, GBps 2.42ms Login VSI Monday morning login and workload 8.7 sec/vm 37, GBps 0.92ms Login VSI Tuesday morning login and workload 8.2 sec/vm 31, GBps 0.91ms Login VSI Tuesday morning login and workload during storage failover 8.6 sec/vm 29, GBps 1.29ms Refresh operation 71 min 66, GBps 0.74ms Recompose operation 92 min 89, GBps 0.97ms Throttled patching of 2,000 desktops 189 min 124, GBps 1.36ms Throttled virus scan of 1,000 desktops 80 min 55, MBps 0.41ms Note: Latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. 8.3 Storage Efficiency During the tests, always-on storage efficiencies were enabled to provide continual storage efficiency. Initial storage efficiency after the environment was provisioned was 100:1. Because of the synthetic nature of the data used to perform these tests, these numbers are not typical of real-world savings. In addition, although we used thin provisioning for each volume and LUN, thin provisioning is not a storagereduction technology and therefore we did not report on it. Typical savings might vary from 30:1 to 5:1, depending on the amount of unique data in the VDI environment. Figure 23 shows the capacity and storage savings for each volume, and Table 22 lists the efficiency results obtained from the testing. Figure 23) Capacity and storage savings by volume. Table 22) Efficiency results. Point of Measurement Total Used Total Savings Percent Savings Ratio After 2,000 desktops were provisioned 36,978GB 296GB 36,682GB 99% 100:1 46 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

47 8.4 Provisioning 2,000 VMware Horizon 6 Desktops This section provides the test objectives and methodology for and the results from testing the provisioning of 2,000 VMware Horizon 6 desktops. Test Objectives and Methodology The objective of this test was to determine how long it would take to provision 2,000 VMware Horizon 6 virtual desktops. This scenario is most applicable to the initial deployment of a new POD or the reprovisioning of an existing environment. To set up for the test, 2,000 VMware Horizon 6 desktops were created. For simplicity and repeatability, we used a Windows PowerShell script. Figure 24 shows one line of the script completely filled out to demonstrate what was done for one pool of 250 VMs. The script shown in Figure 20 (in section 6.5, Creating VMware Horizon 6 Desktop Pools ) contains the entire script that was used to create the pools. Figure 24) Creating 250 VMs in one pool named vdi01n01. Get-ViewVC -servername "vc1.ra.rtp.netapp.com" Get-ComposerDomain -domain "ra.rtp.netapp.com"- Username "administrator" Add-AutomaticLinkedCLonePool -pool_id vdi01n01 -displayname vdi01n01 -nameprefix "vdi01n01-{n:fixed=3}" -parentvmpath "/RA/vm/Discovered virtual machine/vvolvm" - parentsnapshotpath "/HORIZON" -vmfolderpath "/RA/vm" -resourcepoolpath "/RA/host/Desktops/Resources" -datastorespecs "[ Unbounded,OS,data]/RA/host/Desktops/vdi01n01" - HeadroomCount 250 -minimumcount 250 -maximumcount 250 -OrganizationalUnit "OU=Computers,OU=LoginVSI" -UseTempDisk $false -UseUserDataDisk $false -PowerPolicy "AlwaysOn"" - SuspendProvisioningOnError $false For this testing, NetApp chose specific pool and provisioning settings that would stress the storage while providing the most granular reporting capabilities. NetApp does not advocate using or disabling these features because each might provide significant value in the correct use case. NetApp recommends that customers test these features to understand their impacts before deploying with these features enabled. These features include, but are not limited to, persona management, replica tiering, user data disks, disposable file disks, space reclamation, and Horizon 6 View Storage Accelerator. Table 23 lists the provisioning data that was gathered. Table 23) Results for desktop provisioning. Measurement Time to provisioning 2,000 desktops Average storage latency (ms) Data 92 min (all desktops had the status Available in VMware Horizon 6) 1.04ms Peak IOPS 89,443 Average IOPS 41,579 Peak throughput Average throughput 2068MBps 927MBps Peak storage CPU utilization 85% Average storage CPU utilization 52% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. 47 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

48 Throughput and IOPS During the provisioning test, the storage controllers had a combined peak of 89,443 IOPS and 2068MBps throughput, and an average of 52% utilization per storage controller with an average latency of 1.04ms. Figure 25 shows the throughput and IOPS for the creation of 2,000 desktops. Figure 25) Throughput and IOPS for the creation of 2,000 desktops. Storage Controller CPU Utilization Figure 26 shows the storage controller CPU utilization across both nodes of the two-node NetApp cluster. The utilization average was 52%, with a peak of 85%. Figure 26) Storage controller CPU utilization for the creation of 2,000 desktops. Customer Impact (Test Conclusions) During the provisioning of 2,000 VMware desktops, the storage controller had enough headroom to perform a significantly greater number of concurrent provisioning operations. 8.5 Boot Storm Test This section provides the test objectives and methodology for and the results from boot storm testing. 48 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

49 Test Objectives and Methodology The objective of this test was to determine how long it would take to boot 2,000 virtual desktops, which might happen, for example, after maintenance activities and server host failures. This test was performed by powering on all 2,000 VMs from within the VMware vcenter Server and observing when the status of all VMs in VMware Horizon 6 changed to Available. Table 24 lists the boot storm data that was gathered. Table 24) Results for a boot storm of 2,000 desktops. Measurement Time to boot 2,000 desktops Average storage latency (ms) Data 6 min, 17 sec (all desktops had the status Available in VMware Horizon 6) 1.15ms Peak IOPS 156,686 Average IOPS 84,340 Peak throughput Average throughput 3482MBps 1676MBps Peak storage CPU utilization 90% Average storage CPU utilization 53% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. Throughput and IOPS During the boot storm test, the storage controllers had a combined peak of 156,686 IOPS and 3482MBps throughput, and an average of 53% CPU utilization per storage controller with an average latency of 1.15ms. Figure 27 shows the throughput and IOPS for the 2,000-desktop boot storm. Figure 27) Throughput and IOPS for a 2,000-desktop boot storm. 49 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

50 Storage Controller CPU Utilization Figure 28 shows the storage controller CPU utilization across both nodes of the two-node NetApp cluster. The utilization average was 53%, with a peak of 90%. Figure 28) Storage controller CPU utilization for a 2,000-desktop boot storm. Read/Write IOPS Figure 29 shows the read/write IOPS for the boot storm test. Figure 29) Read/write IOPS for a 2,000-desktop boot storm. Read/Write Ratio Figure 30 shows the read/write ratio for the boot storm test. Figure 30) Read/write ratio for a 2,000-desktop boot storm. 50 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

51 Customer Impact (Test Conclusions) During the boot of 2,000 desktops, the storage controller had enough headroom to perform a significantly greater number of concurrent boot operations. The data indicates that the storage controller could boot approximately 4,000 desktops in about 10 minutes. Note: For this test, we set the number of concurrent power-on tasks very high so that we could perform the boot in the shortest amount of time without regard to storage latency. When this value was set to 50 concurrent power-on operations and VMware Horizon 6 was used to perform the power-on operation, we achieved longer boot times but lower latencies. The objective was to see how quickly we could power on the VMs. Customers can reduce the impact on other VMs by using VMware Horizon 6 to throttle the number of simultaneous power-on operations. Table 25 lists the results for storage latency and boot time. Table 25) Power-on method, storage latency, and boot time. Power-On Method Concurrent Power-On Operations Storage Latency Boot Time for 2,000 VMs From VMware vcenter No throttle 1.15ms 6 min, 17 sec From VMware Horizon ms 27 min, 29 sec 8.6 Boot Storm During Storage Failover Test This section provides the test objectives and methodology for and the results from boot storm testing during storage controller failover. Test Objectives and Methodology The objective of this test was to determine how long it would take to boot 2,000 virtual desktops if the storage controller had a problem and was failed over. This test used the same methodologies and process that were used in section 8.5, Boot Storm Test. Table 26 shows the data that was gathered for the boot storm during storage failover. Table 26) Results for a 2,000-desktop boot storm during storage failover. Measurement Time to boot 2,000 desktops during storage failover Average storage latency (ms) Data 8 min, 45 sec (all desktops had the status Available in VMware Horizon 6) 2.42ms Peak IOPS 91,575 Average IOPS 58,754 Peak throughput Average throughput 2335MBps 1335MBps Peak storage CPU utilization 95% Average storage CPU utilization 71% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. 51 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

52 Throughput and IOPS During the boot storm failover test, the storage controllers had a combined peak of 91,575 IOPS and 2335MBps throughput, and an average of 71% physical CPU utilization per storage controller with an average latency of 2.42ms. Figure 31 shows the throughput and IOPS. Figure 31) Throughput and IOPS for a 2,000-desktop boot storm during storage failover. Storage Controller CPU Utilization Figure 32 shows the storage controller CPU utilization on one node of the two-node NetApp cluster while it was failed over. The utilization average was 71%, with a peak of 95%. Figure 32) Storage controller CPU utilization for a 2,000-desktop boot storm during storage failover. Read/Write IOPS Figure 33 shows the read/write IOPS for the boot storm test during storage failover. 52 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

53 Figure 33) Read/write IOPS for a desktop boot storm during storage failover. Read/Write Ratio Figure 34 shows the read/write ratio for the boot storm test during storage failover. Figure 34) Read/write ratio for a 2,000-desktop boot storm during storage failover. Customer Impact (Test Conclusions) During the boot of 2,000 desktops, the storage controller was able to boot 2,000 desktops on one node in 8 minutes and 45 seconds. Therefore, a storage controller running 2,000 VMs on each node (for a total of 4,000 VMs) would still take 8 minutes and 45 seconds to boot. 8.7 Steady-State Login VSI Test This section provides the test objectives and methodology for and the results from steady-state Login VSI testing. Test Objectives and Methodology The objective of this test was to run a Login VSI office worker workload to determine how the storage controller would perform and what the end-user experience would be. This Login VSI workload 53 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

54 first had the users log in to their desktops and begin working. The login phase occurred over a 30-minute period. Three different login scenarios were included because each had a different I/O profile. We measured storage performance as well as login time and VSImax, a Login VSI value that represents the maximum number of users who can be deployed on the given platform. VSImax was not reached in any of the Login VSI tests. The following sections define the login scenarios. Monday Morning Login and Workload Test In this scenario, 2,000 users logged in after the VMs had been rebooted. During this type of login, user and profile data, application binaries, and libraries had to be read from disk because they were not already contained in the VM memory. Table 27 shows the results. Table 27) Results for a 2,000-desktop Monday morning login and workload. Measurement Desktop login time Average storage latency (ms) Data 8.7 sec 0.92ms Peak IOPS 37,806 Average IOPS 16,356 Peak throughput Average throughput 756MBps 392MBps Peak storage CPU utilization 70% Average storage CPU utilization 33% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. Login VSI VSImax Results Because the Login VSI VSImax v4.1 was not reached, more VMs could be deployed on this infrastructure. Figure 35 shows the VSImax results for Monday morning login and workload. Figure 35) VSImax results for a 2,000-desktop Monday morning login and workload. 54 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

55 Desktop Login Time The average desktop login time was 8.7 seconds, which is considered to be good. Figure 36 shows a scatter plot of the Monday morning login times. Figure 36) Scatter plot of 2,000-desktop Monday morning login times. Throughput, Latency, and IOPS During the Monday morning login test, the storage controllers had a combined peak of 37,806 IOPS and 756MBps throughput, and an average of 33% CPU utilization per storage controller with an average latency of 0.92ms. Figure 37 shows the throughput, latency, and IOPS for Monday morning login and workload. Figure 37) Throughput, latency, and IOPS for a 2,000-desktop Monday morning login and workload. 55 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

56 Storage Controller CPU Utilization Figure 38 shows the storage controller CPU utilization across both nodes of the two-node NetApp cluster. The utilization average was 33%, with a peak of 70%. Figure 38) Storage controller CPU utilization for a 2,000-desktop Monday morning login and workload. Read/Write IOPS Figure 39 shows the read/write IOPS for Monday morning login and workload. Figure 39) Read/write IOPS for a 2,000-desktop Monday morning login and workload. Read/Write Ratio Figure 40 shows the read/write ratio for Monday morning login and workload. 56 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

57 Figure 40) Read/write ratio for a 2,000-desktop Monday morning login and workload. Customer Impact (Test Conclusions) During the Monday morning login test, the storage controller performed very well. The CPU utilization was not high during this test, latencies were under 1ms, and desktop performance was excellent. These results suggest that it might be possible to double the storage controller workload to 4,000 users or more and still maintain excellent end-user performance. The Tuesday morning login during the storage failover test described in the following section reinforces that point. Tuesday Morning Login and Workload Test In this scenario, 2,000 users logged in to virtual desktops that had been logged into previously and that had not been power-cycled. In this situation, VMs retain user and profile data, application binaries, and libraries in memory, which reduces the impact on storage. Table 28 lists the results for Tuesday morning login and workload. Table 28) Results for a 2,000-desktop linked-clone Tuesday morning login and workload. Measurement Desktop login time Average storage latency (ms) Data 8.2 sec 0.91ms Peak IOPS 31,926 Average IOPS 12,435 Peak throughput Average throughput 793MBps 318MBps Peak storage CPU utilization 71% Average storage CPU utilization 31% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. 57 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

58 Login VSI VSImax Results Because the Login VSI VSImax v4.1 was not reached, more VMs could be deployed on this infrastructure. Figure 41 shows the VSImax results for Tuesday morning login and workload. Figure 41) VSImax results for a 2,000-desktop Tuesday morning login and workload. Desktop Login Time The average desktop login time was 8.2 seconds, which is considered good. Figure 42 shows a scatter plot of the Tuesday morning login times. Figure 42) Scatter plot of 2,000-desktop Tuesday morning login times. Throughput, Latency, and IOPS During the Tuesday morning login test, the storage controllers had a combined peak of 31,926 IOPS and 793MBps throughput, and an average of 31% CPU utilization per storage controller with an average latency of 0.91ms. Figure 43 shows throughput, latency, and IOPS for Tuesday morning login and workload. 58 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

59 Figure 43) Throughput, latency, and IOPS for a 2,000-desktop Tuesday morning login and workload. Storage Controller CPU Utilization Figure 44 shows the storage controller CPU utilization across both nodes of the two-node NetApp cluster. The utilization average was 31%, with a peak of 71%. Figure 44) Storage controller CPU utilization for a 2,000-desktop Tuesday morning login and workload. 59 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

60 Read/Write IOPS Figure 45 shows the read/write IOPS for Tuesday morning login and workload. Figure 45) Read/write IOPS for a 2,000-desktop Tuesday morning login and workload. Read/Write Ratio Figure 46 shows the read/write ratio for Tuesday morning login and workload. Figure 46) Read/write ratio for a 2,000-desktop Tuesday morning login and workload. Customer Impact (Test Conclusions) The purpose of this test was to demonstrate an ordinary login and workload for a noncached profile and noncached binaries. This test case is one of the easier workloads for any storage controller to perform. 60 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

61 Tuesday Morning Login and Workload During Storage Failover Test In this scenario, 2,000 users logged in to virtual desktops that had been logged into previously and that had not been power-cycled, and the storage controller was failed over. In this situation, VMs retain user and profile data, application binaries, and libraries in memory, which reduces the impact on storage. Table 29 lists the results for Tuesday morning login and workload during storage failover. Table 29) Results for a 2,000-desktop linked-clone Tuesday morning login and workload during storage failover. Measurement Desktop login time Average storage latency (ms) Data 8.6 sec 1.29ms Peak IOPS 29,922 Average IOPS 12,469 Peak throughput Average throughput 748MBps 314MBps Peak storage CPU utilization 91% Average storage CPU utilization 62% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. Login VSI VSImax Results Because the Login VSI VSImax v4.1 was not reached, more VMs could be deployed on this infrastructure. Figure 47 shows the VSImax results for Tuesday morning login and workload during storage failover. Figure 47) VSImax results for a 2,000-desktopTuesday morning login and workload during storage failover. 61 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

62 Desktop Login Time The average desktop login time was 8.6 seconds, which is considered good. Figure 48 shows a scatter plot of the Tuesday morning login times during storage failover. Figure 48) Scatter plot of 2,000-desktop Tuesday morning login times during storage failover. Throughput, Latency, and IOPS Throughout the test of Tuesday morning login during storage failover, the storage controllers had a combined peak of 29,922 IOPS and 748MBps throughput, and an average of 62% CPU utilization per storage controller with an average latency of 1.29ms. Figure 49 shows throughput, latency, and IOPS for Tuesday morning login and workload during storage failover. Figure 49) Throughput, latency, and IOPS for a 2,000-desktop Tuesday morning login and workload during storage failover. Storage Controller CPU Utilization Figure 50 shows the storage controller CPU utilization on one node of the two-node NetApp cluster while it was failed over. The utilization average was 62%, with a peak of 91%. 62 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

63 Figure 50) Storage controller CPU utilization for a 2,000-desktop Tuesday morning login and workload during storage failover. Read/Write IOPS Figure 51 shows the read/write IOPS for Tuesday morning login and workload during storage failover. Figure 51) Read/write IOPS for a 2,000-desktop Tuesday morning login and workload during storage failover. Read/Write Ratio Figure 52 shows the read/write ratio for Tuesday morning login and workload during storage failover. 63 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

64 Figure 52) Read/write ratio for a 2,000-desktop Tuesday morning login and workload during storage failover. Customer Impact (Test Conclusions) The purpose of this test was to demonstrate that an ordinary login can be performed during a failover event. 8.8 Refresh Test This section provides the test objectives and methodology for and the results from refresh operation testing. Test Objectives and Methodology One objective of this test was to determine how long it would take to perform the refresh maintenance operation on all 2,000 desktops. Another objective was to determine the impact on the storage system. For this test, we used Windows PowerShell cmdlets for simplicity and repeatability. Figure 53 shows the syntax that was used to perform the refresh. Note: We used the optional stoponerror $false flag so that if an error did occur, it would not halt the entire operation; however, there were no errors during the refresh operation, so this flag could have been omitted. Figure 53) Windows PowerShell commands to refresh all eight pools of desktops. Get-DesktopVM -pool_id vdi01n01 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi01n02 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi02n01 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi02n02 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi03n01 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi03n02 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi04n01 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false Get-DesktopVM -pool_id vdi04n02 Send-LinkedCloneRefresh -schedule "June :35" - stoponerror $false 64 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

65 Table 30 lists the results for the refresh operation. Table 30) Results for a 2,000-desktop refresh operation. Measurement Time to refresh 2,000 desktops Average storage latency (ms) Data 71 min (all desktops had the status Available in VMware Horizon 6) 0.74ms Peak IOPS 66,472 Average IOPS 27,815 Peak throughput Average throughput 1515MBps 606MBps Peak storage CPU utilization 76% Average storage CPU utilization 40% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. Throughput and IOPS During the refresh test, the storage controllers had a combined peak of 66,472 IOPS and 1515MBps throughput, and an average of 40% CPU utilization per storage controller with an average latency of 0.74ms. Figure 54 shows the throughput and IOPS for the refresh operation. Figure 54) Throughput and IOPS for a 2,000-desktop refresh operation. 65 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

66 Storage Controller CPU Utilization Figure 55 shows the storage controller CPU utilization across both nodes of the two-node NetApp cluster. The utilization average was 40%, with a peak of 76%. Figure 55) Storage controller CPU utilization for a 2,000-desktop refresh operation. Read/Write IOPS Figure 56 shows the read/write IOPS for the refresh operation. Figure 56) Read/write IOPS for a 2,000-desktop refresh operation. 66 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

67 Read/Write Ratio Figure 57 shows the read/write ratio for the refresh operation. Figure 57) Read/write ratio for a 2,000-desktop refresh operation. Customer Impact (Test Conclusions) A refresh operation can be performed on all 2,000 desktops in 71 minutes. Given the low utilization on the storage controller, it might be possible to perform the refresh operation during a storage failover event without affecting controller performance. There are limits to how quickly the refresh operation can occur, but this test demonstrated that storage performance was not the limiting factor. 8.9 Recompose Test This section provides the test objectives and methodology for and the results from recompose operation testing. Test Objectives and Methodology One objective of this test was to determine how long it would take to perform the recompose maintenance operation on all 2,000 desktops. Another objective was to determine the impact to the storage system. For this test we used the VMware Horizon 6 Administrator interface and recomposed all eight pools by setting a schedule for the task. Figure 58 shows the Windows PowerShell commands used to recompose all eight pools of desktops. Table 31 lists the results for the recompose operation. Note: We used the optional stoponerror $false flag so that if an error did occur, it would not halt the entire operation; however, there were no errors during the recompose operation, so this flag could have been omitted. 67 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

68 Figure 58) Windows PowerShell commands to recompose all eight pools of desktops. Get-DesktopVM -pool_id vdi01n01 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi01n02 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi02n01 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi02n02 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi03n01 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi03n02 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi04n01 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Get-DesktopVM -pool_id vdi04n02 Send-LinkedCloneRecompose -schedule "June :30" - stoponerror $false -parentvmpath $parentvmpath -parentsnapshotpath $parentsnapshotpath Table 31) Results for a 2,000-desktop recompose operation. Measurement Time to recompose 2,000 desktops Average storage latency (ms) Data 92 min (all desktops had the status Available in VMware Horizon 6) 0.97ms Peak IOPS 89,241 Average IOPS 37,265 Peak throughput Average throughput 2181MBps 798MBps Peak storage CPU utilization 81% Average storage CPU utilization 47% Note: CPU and latency measurements are based on the average across both nodes of the cluster. IOPS and throughput are based on a combined total of each. Throughput and IOPS During the recompose test, the storage controllers had a combined peak of 89,241 IOPS and 2181MBps throughput, and an average of 47% CPU utilization per storage controller with an average latency of 0.97ms. Figure 59 shows the throughput and IOPS for the recompose operation. 68 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

69 Figure 59) Throughput and IOPS for a 2,000-desktop recompose operation. Storage Controller CPU Utilization Figure 60 shows the storage controller CPU utilization for the recompose operation. Figure 60) Storage controller CPU utilization for a 2,000-desktop recompose operation. 69 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

70 Read/Write IOPS Figure 61 shows the read/write IOPS for the recompose operation. Figure 61) Read/write IOPS for a 2,000-desktop recompose operation. Read/Write Ratio Figure 62 shows the read/write ratio for the recompose operation. Figure 62) Read/write ratio for a 2,000-desktop recompose operation. Customer Impact (Test Conclusions) A recompose operation can be performed on all 2,000 desktops in 92 minutes. It might be possible to perform the recompose operation during a storage failover event without affecting controller performance. There are limits to how quickly the recompose operation can occur, but this test demonstrated that storage performance was not the limiting factor. 70 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

71 8.10 Throttled Patching of 2,000 Desktops This section provides the test objectives and methodology for and the results from patch testing. Test Objectives and Methodology In this test, we patched 2,000 desktops. We were cautious and wanted to avoid having the server hosts become a bottleneck during this test. For testing, we used Windows Server Update Services (WSUS) to download and install patches to the 2,000 desktops. A total of 843MB of patches were downloaded and installed on each machine. The patch update was initiated from a Windows PowerShell script that directed each VM to find available updates from the WSUS server, apply the patches, and reboot the VMs. For this test, we staggered the patching process by inserting a 45-second delay between patch commands. Table 32 lists the test results for the throttled patching of 2,000 desktops. Table 32) Results for throttled patching of 2,000 desktops. Measurement Time to patch 2,000 desktops Average storage latency (ms) Data 189 min 1.36ms Peak IOPS 124,776 Average IOPS 29,859 Peak throughput Average throughput 1352MBps 766MBps Peak storage CPU utilization 80% Average storage CPU utilization 52% Note: CPU and latency measurements are based on both nodes of the cluster. 71 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

72 Throughput and IOPS During the throttled patching test, the storage controller had a peak of 124,776 IOPS and 1352MBps throughput, and an average of 61% CPU utilization per storage controller with an average latency of 1.36ms. Figure 63 shows the throughput, latency, and IOPS for the throttled patching of 2,000 desktops. Figure 63) Throughput, latency, and IOPS for throttled patching of 2,000 desktops. Storage Controller CPU Utilization Figure 64 shows the storage controller CPU utilization on the NetApp cluster. The utilization average was 52%, with a peak of 80%. Figure 64) Storage controller CPU utilization for throttled patching of 2,000 desktops. 72 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

73 Read/Write IOPS Figure 65 shows the read/write IOPS for the throttled patching of 2,000 desktops. Figure 65) Read/write IOPS for throttled patching of 2,000 desktops. Read/Write Ratio Figure 66 shows the read/write ratio for the throttled patching of 2,000 desktops. Figure 66) Read/write ratio for throttled patching of 2,000 desktops. 73 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

74 Always-On Deduplication Figure 67 shows the storage efficiency over time from using always-on deduplication. It compares the latencies for patch and postprocess deduplication (in blue) and for patch and always-on deduplication (in red). The average latencies with always-on deduplication were under 1ms. Figure 67) Always-on deduplication storage efficiency over time. Customer Impact (Test Conclusions) The throttled patching of 2,000 (or 4,000) virtual desktops with 843MB per VM took approximately 189 minutes for installing the patches and rebooting the VM. Neither latency nor CPU was a concern during this test. In production environments, NetApp recommends staggering patching over a longer period of time to reduce latency and CPU utilization Throttled Virus Scan of 1,000 Desktops on One Node This section provides the test objectives and methodology for and the results from throttled virus scan testing. Test Objectives and Methodology In this test, we performed a virus scan on the desktop infrastructure in a staggered fashion to reduce the overall end-user impact. Because of server CPU limitations, only 1,000 VMs could be scanned on a single node of the HA pair. All 1,000 desktops were on one node of the storage cluster, so from the storage perspective the effect was the same as scanning 2,000 desktops across both nodes. For testing, we used standard physical asset virus scan software, and the test was orchestrated by initiating scripts that remotely executed a full virus scan on each desktop. We ran four scripts, with each run executing the command and then sleeping for 15 seconds as set by the choice command. Figure 68 shows the virus scan script. Figure 68) Throttled virus scan script sample. c:\psexec.exe -d -accepteula \\vdi01n "C:\Program Files\McAfee\VirsuScan Enterprise\scan32.exe" /PRIORITY=LOW /ALL /ALWAYSEXIT choice /T 15 /D y c:\psexec.exe -d -accepteula \\vdi01n "C:\Program Files\McAfee\VirsuScan Enterprise\scan32.exe" /PRIORITY=LOW /ALL /ALWAYSEXIT choice /T 15 /D y c:\psexec.exe -d -accepteula \\vdi01n "C:\Program Files\McAfee\VirsuScan Enterprise\scan32.exe" /PRIORITY=LOW /ALL /ALWAYSEXIT choice /T 15 /D y 74 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

75 Note: NetApp does not recommend that customers use this method to scan for viruses because there are more VDI-friendly ways of performing a virus scan. In addition, NetApp recommends using VDI-aware virus scanning software and extending the test to a longer period of time to lessen the impact on the infrastructure. Table 33 lists the results for the throttled virus scan operation on one node. Table 33) Results for the throttled virus scan operation on one node. Measurement Time to virus-scan 1,000 desktops on one node Average storage latency (ms) Data ~80 min (artificially throttled) 0.41ms Peak IOPS 55,328 Average IOPS 21,827 Peak throughput Average throughput 582MBps 1,894MBps Peak storage CPU utilization 66% Average storage CPU utilization 33% Throughput and IOPS During the throttled virus scan test, the storage controllers had a peak of 55,328 IOPS and 1,894MBps throughput, and an average of 33% CPU utilization with an average latency of 0.41ms. Figure 69 shows the throughput and IOPS for the throttled virus scan operation. Figure 69) Throughput and IOPS for throttled virus scan operation on one node. Storage Controller CPU Utilization Figure 70 shows the storage controller CPU utilization. The utilization average was 33%, with a peak of 66%. 75 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

76 Figure 70) Storage controller CPU utilization for throttled virus scan operation on one node. Read/Write IOPS Figure 71 shows the read/write IOPS for the throttled virus scan operation. Figure 71) Read/write IOPS for throttled virus scan operation on one node. Read/Write Ratio Figure 72 shows the read/write ratio for the throttled virus scan operation. 76 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

77 Figure 72) Read/write ratio for throttled virus scan operation on one node. Customer Impact (Test Conclusions) A throttled virus scan operation can be performed on 1,000 desktops in 80 minutes on one node. 9 Conclusion In all tests, end-user login time, guest response time, and maintenance activities performance were excellent. The NetApp All Flash FAS system performed very well, reaching peak IOPS of 156,686 during a boot storm while averaging 53% CPU utilization. All test categories demonstrated that with the 2,000- user workload and maintenance operations, the AFF8060 storage system should be capable of doubling the workload to 4,000 users while still being able to fail over in the event of a failure. 9.1 Key Findings The following key findings were observed during the reference architecture testing: The Login VSI VSImax was never reached for any of the login or workload scenarios. During boot storm testing, VMware vcenter did not throttle the boot process, and it produced an excellent boot time of 6 minutes and 17 seconds for all 2,000 VMs. For all of the nonfailover tests, almost twice as many users could have been deployed with the same results. Only in the cases of the failed-over boot storm and Tuesday login and workload during storage failover did the CPU utilization average over 55%, and both of these situations are extreme corner cases. 77 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

78 References This report references the following documents and resources: TR-3982: NetApp Clustered Data ONTAP 8.3 and 8.2.x: An Introduction TR-3705: NetApp and VMware View Solution Guide TR-4181: VMware Horizon View 5 Solutions Guide TR-3949: NetApp and VMware View 5,000-Seat Performance Report TR-4068: VMware vsphere 5 on NetApp Clustered Data ONTAP Best Practices VMware Horizon 6 with View Performance and Best Practices VMware Horizon 6 Documentation TR-4307: NetApp All-Flash FAS Solution for Nonpersistent Desktops with VMware Horizon View TR-4335: NetApp All-Flash FAS Solution for Persistent Desktops with VMware Horizon View TR-4400: Applying VMware Virtual Volumes on NetApp Clustered Data ONTAP Version History Version Date Document Version History Version 1.2 August 2015 Added virus scan workload test information Version 1.1 July 2015 Designated as technical preview Version 1.0 June 2015 Initial reference architecture release Acknowledgements The authors thank Scott Gentry, Dan Isaacs, Glenn Sizemore, Andrew Sullivan, and Eric Wagar (NetApp) and Bhumik Patel (VMware) for their contributions to this document. 78 NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.

79 Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications. Copyright Information Copyright NetApp, Inc. All rights reserved. Printed in the U.S. No part of this document covered by copyright may be reproduced in any form or by any means graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system without prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS (October 1988) and FAR (June 1987). Trademark Information NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity, SecureShare, Simplicity, Simulate ONTAP, SnapCenter, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, WAFL and other names are trademarks or registered trademarks of NetApp Inc., in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. A current list of NetApp trademarks is available on the web at TR NetApp All Flash FAS Solution for VMware Horizon 6 and vsphere Virtual Volumes 2015 NetApp, Inc. All rights reserved.