EMC VSPEX END-USER COMPUTING

Transcription

1 EMC VSPEX END-USER COMPUTING VMware Horizon View 5.2 and VMware vsphere 5.1 for up to 250 Virtual Desktops Enabled by EMC VNXe and EMC Next-Generation Backup EMC VSPEX Abstract This guide describes the EMC VSPEX end-user computing solution using VMware Horizon View with EMC VNXe and EMC Next-Generation Backup for up to 250 virtual desktops. July 2013

2 Copyright EMC Corporation. All rights reserved. Published in the USA. Published July 2013 EMC believes the information in this publication is accurate of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC 2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website. Part Number H

3 Contents Chapter 1 Executive Summary 13 Introduction Target audience Document purpose Business needs Chapter 2 Solution Overview 17 Solution overview Desktop broker Virtualization Compute Network Storage Chapter 3 Solution Technology Overview 21 Technology solution Summary of key components Desktop broker Overview VMware Horizon View VMware View Composer VMware View Persona Management VMware View Storage Accelerator Virtualization VMware vsphere VMware vcenter VMware vsphere High Availability EMC Virtual Storage Integrator for VMware VNXe VMware vstorage API for Array Integration support

4 Contents Compute Network Storage Overview EMC VNXe series Backup and recovery Overview EMC Avamar Security RSA SecurID two-factor authentication SecurID authentication in the VSPEX end-user computing environment Required components Compute, memory, and storage resources Other components VMware vshield Endpoint VMware vcenter Operations Manager for Horizon View Chapter 4 Solution Stack Architectural Overview 37 Solution overview Solution architecture Overview Architecture for up to 250 virtual desktops Key components Hardware resources Software resources Sizing for validated configuration Server configuration guidelines Overview VMware vsphere memory virtualization for VSPEX Memory configuration guidelines Network configuration guidelines Overview VLAN Enable jumbo frames Link aggregation Storage configuration guidelines Overview VMware vsphere storage virtualization for VSPEX Storage layout for 250 virtual desktops

5 Contents High availability and failover Introduction Virtualization layer Compute layer Network layer Storage layer Validation test profile Profile characteristics Antivirus and antimalware platform profile Platform characteristics vshield architecture vcenter Operations Manager for Horizon View platform profile Platform characteristics vcenter Operations Manager for View architecture Backup and recovery configuration guidelines Backup characteristics Backup layout Sizing guidelines Reference workload Define the reference workload Applying the reference workload Concurrency Heavier desktop workloads Implementing the reference architectures Overview Resource types CPU resources Memory resources Network resources Storage resources Backup resources Implementation summary Quick assessment Overview CPU requirements Memory requirements Storage performance requirements Storage capacity requirements Determining equivalent reference virtual desktops

6 Contents Fine tuning hardware resources Chapter 5 VSPEX Configuration Guidelines 69 Configuration overview Pre-deployment tasks Overview Deployment prerequisites Customer configuration data Prepare switches, connect network, and configure switches Overview Configure infrastructure network Configure VLANs Complete network cabling Prepare and configure storage array Overview Prepare VNXe Set up the initial VNXe configuration Setup VNXe networking Provision storage for NFS datastores Provision optional storage for user data Provision optional storage for infrastructure virtual machines Install and configure vsphere hosts Overview Install vsphere Configure vsphere networking Jumbo frames Connect VMware datastores Plan virtual machine memory allocations Install and configure SQL Server database Overview Create a virtual machine for Microsoft SQL Server Install Microsoft Windows on the virtual machine Install SQL Server Configure database for VMware vcenter Configure database for VMware Update Manager Configure database for VMware View Composer Configure database for VMware View Manager Configure the VMware View and View Composer database permissions VMware vcenter Server deployment Overview

7 Contents Create the vcenter host virtual machine Install vcenter guest OS Create vcenter ODBC connections Install vcenter Server Apply vsphere license keys Deploy the vstorage APIs for Array Integration (VAAI) plug-in Install the EMC VSI plug-in Set up VMware View Connection Server Overview Install the VMware View Connection Server Configure the View event log database connection Add a second View Connection Server Configure the View Composer ODBC connection Install View Composer Link VMware Horizon View to vcenter and View Composer Prepare master virtual machine Configure View Persona Management group policies Configure folder redirection group policies for Avamar Configure View PCoIP group policies Set up Avamar Avamar configuration overview GPO modifications for Avamar GPO additions for Avamar Master image preparation for EMC Avamar Define datasets Define schedules Adjust maintenance window schedule Define retention policies Group and group policy creation EMC Avamar Enterprise Manager activate clients Set up VMware vshield Endpoint Overview Verify desktop vshield Endpoint driver installation Deploy vshield Manager appliance Install the vsphere vshield Endpoint service Deploy an antivirus solution management server Deploy vsphere Security Virtual Machines Verify vshield Endpoint functionality Set up VMware vcenter Operations Manager for Horizon View Overview

8 Contents Create vsphere IP pool for vcenter Operations Manager Deploy vcenter Operations Manager vapp Specify the vcenter Server to monitor Update virtual desktop settings Create the virtual machine for the vcenter Operations Manager for Horizon View Adapter server Install the vcenter Operations Manager for Horizon View Adapter software Import the vcenter Operations Manager for Horizon View PAKFile Verify vcenter Operations Manager for Horizon View functionality Summary of VSPEX configuration guidelines Chapter 6 Validating the Solution 119 Overview Post-install checklist Deploy and test a single virtual desktop Verify the redundancy of the solution components Provision remaining virtual desktops Appendix A Bills of Materials 125 Bill of material for 250 virtual desktops Appendix B Customer Configuration Data Sheet 127 Overview of customer configuration data sheets Appendix C References 131 References EMC documentation Other documentation Appendix D About VSPEX 135 About VSPEX

9 Figures Figure 1. Solution components Figure 2. Example of compute layer flexibility Figure 3. Example of Highly-Available network design Figure 4. Authentication control flow for Horizon View access requests originating Figure 5. on an external network Logical architecture: VSPEX end-user computing for VMware Horizon View with RSA Figure 6. Logical architecture for 250 virtual desktops Figure 7. Hypervisor memory consumption Figure 8. Required networks Figure 9. VMware virtual disk types Figure 10. Core storage layout 250 virtual desktops Figure 11. Optional storage layout 250 virtual desktops Figure 12. High availability at the virtualization layer Figure 13. Redundant power supplies Figure 14. Network layer high availability Figure 15. VNXe series high availability Figure 16. Sample Ethernet network architecture Figure 17. Virtual machine memory settings Figure 18. Persona Management modifications for Avamar Figure 19. Configuring Windows folder redirection Figure 20. Create a Windows network drive mapping for user files Figure 21. Configure drive mapping settings Figure 22. Configure drive mapping common settings Figure 23. Create a Windows network drive mapping for user profile data Figure 24. Avamar Tools menu Figure 25. Avamar Manage All Datasets window Figure 26. Avamar New Dataset window Figure 27. Configure Avamar Dataset settings Figure 28. User profile data dataset Figure 29. User profile data dataset Exclusion settings Figure 30. User profile data dataset Options settings Figure 31. User Profile data dataset Advanced Options settings Figure 32. Avamar default backup/maintenance windows schedule Figure 33. Avamar modified backup/maintenance windows schedule Figure 34. Create new Avamar backup group Figure 35. New backup group settings Figure 36. Select backup group dataset Figure 37. Select backup group schedule

10 Figures Figure 38. Select backup group retention policy Figure 39. Avamar Enterprise Manager Figure 40. Avamar Client Manager Figure 41. Avamar activate client window Figure 42. Avamar activate client menu Figure 43. Avamar Directory Service configuration Figure 44. Avamar Client Manager post configuration Figure 45. Avamar Client Manager Virtual desktop clients Figure 46. Select virtual desktop clients in Avamar Client Manager Figure 47. Select Avamar groups to add virtual desktops Figure 48. Activate Avamar clients Figure 49. Commit Avamar client activation Figure 50. The first information prompt in Avamar client activation Figure 51. The second information prompt in Avamar client activation Figure 52. Avamar Client Manager Activated clients Figure 53. View Composer Disks page

11 Tables Table 1. Solution hardware Table 2. Solution software Table 3. Server hardware Table 4. Storage hardware Table 5. Validated environment profile Table 6. Platform characteristics Table 7. Platform characteristics Table 8. Profile characteristics Table 9. Virtual desktop characteristics Table 10. Blank worksheet row Table 11. Reference virtual desktop resources Table 12. Example worksheet row Table 13. Example applications Table 14. Server resource component totals Table 15. Blank customer worksheet Table 16. Deployment process overview Table 17. Tasks for pre-deployment Table 18. Deployment prerequisites checklist Table 19. Tasks for switch and network configuration Table 20. Tasks for storage configuration Table 21. Tasks for server installation Table 22. Tasks for SQL Server database setup Table 23. Tasks for vcenter configuration Table 24. Tasks for VMware View Connection Server setup Table 25. Tasks for Avamar integration Table 26. Tasks required to install and configure vshield Endpoint Table 27. Tasks required to install and configure vcenter Operations Manager 115 Table 28. Tasks for testing the installation Table 29. Common server information Table 30. vsphere server information Table 31. Array information Table 32. Network infrastructure information Table 33. VLAN information Table 34. Service accounts

12 Tables 12

13 Chapter 1 Executive Summary This chapter presents the following topics: Introduction Target audience Document purpose Business needs

14 Executive Summary Introduction Target audience Document purpose EMC VSPEX validated and modular architectures are built with proven technologies to create complete virtualization solutions that enable you to make an informed decision in the hypervisor, compute, and networking layers. VSPEX eliminates server virtualization planning and configuration burdens. When embarking on server virtualization, virtual desktop deployment or IT consolidation, VSPEX accelerates your IT transformation by enabling faster deployment, greater choice, higher efficiency, and lower risk. This proven infrastructure guide is intended to be a comprehensive guide to the technical aspects of this solution. Server capacity is provided in generic terms for required minimums of CPU, memory, and network interfaces; the customer is free to select the server and networking hardware of their choice that meet or exceed the stated minimums. The readers of this guide are expected to have the necessary training and background to install and configure an VSPEX end-user computing solution based on VMware Horizon View with VMware vsphere as a hypervisor, EMC VNXe series storage systems, and associated infrastructure as required by this implementation. External references are provided where applicable and EMC recommends that the readers be familiar with these documents. Readers are also expected to be familiar with the infrastructure and database security policies of the customer installation. Individuals focused on selling and sizing a VSPEX end-user computing for VMware Horizon View solution should pay particular attention to the first four chapters of this document. After the purchase, implementers of the solution will want to focus on the configuration guidelines in Chapter 5, the solution validation in Chapter 6, and the appropriate references and appendices. This proven infrastructure guide is an initial introduction to the VSPEX end-user computing architecture, an explanation on how to modify the architecture for specific engagements, and instructions on how to effectively deploy the system. The VSPEX end-user computing architecture provides the customer with a modern system capable of hosting a large number of virtual desktops at a consistent performance level. This solution executes on VMware s vsphere virtualization layer backed by the highly available VNX storage family for storage and VMware s Horizon View desktop broker. The compute and network components are vendor definable, redundant, and sufficiently powerful to handle the processing and data needs of a large virtual desktop environment. The 250 virtual desktop environments discussed are based on a defined desktop workload. While not every virtual desktop has the same requirements, this guide contains methods and guidance to adjust your system to be cost effective when the 14

15 Business needs Executive Summary system is deployed. For larger environments, solutions for up to 2000 virtual desktops are described in the proven infrastructure guide EMC VSPEX END-USER COMPUTING VMware Horizon View 5.2 and VMware vsphere 5.1 for up to 2000 Virtual Desktops. An end-user computing or virtual desktop architecture is a complex system offering. This guide facilitates the architecture s setup by providing up front software and hardware material lists, step-by-step sizing guidance and worksheets, and verified deployment steps. After the last component is installed, there are validation tests to ensure that your system is up and running properly. Following this guide will ensure an efficient and painless desktop deployment. Business applications are moving into the consolidated computing, network, and storage environment. EMC VSPEX end-user computing using VMware reduces the complexity of configuring every component of a traditional deployment model. The challenge of integration management is reduced while maintaining the application design and implementation options. Administration is unified, while process separation can be adequately controlled and monitored. The following are the business needs for the VSPEX end-user computing for VMware architectures: Provide an end-to-end virtualization solution to use the capabilities of the unified infrastructure components. Provide a VSPEX end-user computing for VMware Horizon View solution for efficiently virtualizing 250 virtual desktops for varied customer use cases. Provide a reliable, flexible, and scalable reference design. 15

16 Executive Summary 16

17 Chapter 2 Solution Overview This chapter presents the following topics: Solution overview Desktop broker Virtualization Compute Network Storage

18 Solution Overview Solution overview Desktop broker Virtualization Compute The EMC VSPEX end-user computing for VMware Horizon View 5.2 on VMware vsphere 5.1 solution provides a complete systems architecture capable of supporting up to 250 virtual desktops with a redundant server/network topology and highly available storage. The core components that make up this particular solution are desktop broker, virtualization, storage, server computer, and networking. Horizon View is the virtual desktop solution from VMware that enables virtual desktops to run on a VMware vsphere virtualization environment. It enables the centralization of desktop management and provides increased control for IT organizations. Horizon View enables end users to connect to their desktop from multiple devices across a network connection. vsphere is the leading virtualization platform in the industry. It provides flexibility and cost savings to end users by enabling the consolidation of large, inefficient server farms into quick, reliable cloud infrastructures. The core vsphere components are the VMware vsphere Hypervisor and the VMware vcenter Server for system management. The VMware hypervisor runs on a dedicated server and enables multiple operating systems to execute on the system at the same time as virtual machines. These hypervisor systems can be connected to operate in a clustered configuration. These clustered configurations are then managed as a larger resource pool through the vcenter product and allow for dynamic allocation of CPU, memory, and storage across the cluster. Features such as vmotion, which enables a virtual machine to move between different servers with no disruption to the operating system, and Distributed Resource Scheduler (DRS) which uses vmotions to automatically balance load, make vsphere a good business choice. With the release of vsphere 5.1, a VMware virtualized environment can host virtual machines with up to 64 virtual CPUs and 1 TB of virtual RAM. VSPEX enables the flexibility of designing and implementing the vendor s choice of server components. The infrastructure has to conform to the following attributes: Sufficient RAM, cores and memory to support the required number and types of virtual desktops Sufficient network connections to enable redundant connectivity to the system switches Excess capacity to withstand a server failure and failover in the environment 18

19 Solution Overview Network VSPEX enables the flexibility of designing and implementing the vendor s choice of network components. The infrastructure has to conform to the following attributes: Redundant network links for the hosts, switches and storage Support for Link Aggregation Traffic isolation based on industry accepted best practices Storage The VNXe storage family is one of the foremost-shared storage platforms in the industry. Its ability to provide both file and block access with a broad feature set make it an ideal choice for any end-user computing implementation. The VNXe storage components include the following, which are sized for the stated reference architecture workload: Host adapter ports Provide host connectivity through fabric into the array. Storage processors (SPs) The compute component of the storage array, responsible for all aspects of data moving into, out of, and between arrays and protocol support. Disk drives Physical spindles that contain the host/application data and their enclosures The 250 Virtual Desktop solution discussed in this document is based on the VNXe3300 storage array. The VNXe3300 can host up to 150 drives. The EMX VNXe series supports a wide range of business class features that are ideal for the end-user computing environment including: Thin Provisioning Replication Snapshots File Deduplication and Compression Quota Management and many more 19

20 Solution Overview 20

21 Chapter 3 Solution Technology Overview This chapter presents the following topics: Technology solution Summary of key components Desktop broker Virtualization Compute Network Storage Backup and recovery Security Other components

22 Solution Technology Overview Technology solution This solution uses EMC VNXe3300 and VMware vsphere 5.1 to provide the storage and computing resources for a VMware Horizon View environment of Microsoft Windows 7 virtual desktops provisioned by VMware View Composer. Figure 1. Solution components In particular, planning and designing the storage infrastructure for VMware Horizon View environments is a critical step because the shared storage must absorb large bursts of input/output (I/O) that occur over the course of a workday. These bursts can lead to periods of erratic and unpredictable virtual desktop performance. Users might adapt to slow performance, but unpredictable performance frustrates them and reduces efficiency. To provide predictable performance for end-user computing, the storage system must handle the peak I/O load from the clients while keeping response time to minimum. Designing for this workload involves the deployment of many disks to handle brief periods of extreme I/O pressure, which is expensive to implement. EMC Next-Generation Backup enables protection of user data and end-user recoverability. This is accomplished by using EMC Avamar and its desktop client within the desktop image. 22

23 Solution Technology Overview Summary of key components This section briefly describes the key components of this solution. Desktop broker The Desktop Virtualization broker manages the provisioning, allocation, maintenance, and eventual removal of the virtual desktop images that are provided to users of the system. This software is critical to enable on-demand creation of desktop images, to enable maintenance of the image without affecting user productivity, and prevent the environment from growing in an unconstrained way. Virtualization The virtualization layer enables the physical implementation of resources to be decoupled from the applications that use them. The application s view of the resources available to it is no longer directly tied to the hardware. This enables many key features in the end-user computing concept. Compute The compute layer provides memory and processing resources for the virtualization layer software and for the applications running in the infrastructure. The VSPEX program defines the minimum amount of compute layer resources required, but enables the customer to implement using any server hardware, which meets these requirements. Network The network layer connects the users of the environment to the resources they need and connects the storage layer to the compute layer. The VSPEX program defines the minimum number of network ports required for the solution and provides general guidance on network architecture, but enables the customer to implement the requirements using any network hardware that meets these requirements. Storage The storage layer is a critical resource for the implementation of the end-user computing environment. Due to the way desktops are used, the storage layer must absorb large bursts of activity as they occur, without unduly affecting the user experience. Backup and recovery The optional Backup and recovery components of the solution provide data protection in the event that the data in the primary system is deleted, damaged, or otherwise unusable. Security The optional Security components of the solution from RSA provides customers with additional options to control access to the environment and ensure that only authorized users are permitted to use the system. 23

24 Solution Technology Overview Desktop broker Other components There are additional, optional, components, which may improve the functionality of the solution depending on the specifics of the environment. Solution architecture provides details on all the components that make up the reference architecture. Overview Desktop virtualization is a technology encapsulating and delivering desktops to a remote client device, which can be thin clients, zero clients, smart phones, or tablets. It enables subscribers from different locations access to virtual desktops hosted on centralized computing resources at remote data centers. In this solution, VMware Horizon View is used to provision, manage, broker and monitor desktop virtualization environments. VMware Horizon View 5.2 VMware Horizon View 5.2 is a leading desktop virtualization solution that enables desktops to deliver cloud-computing services to users. VMware Horizon View 5.2 integrates effectively with vsphere 5.1 to provide: Performance optimization and tiered storage support View Composer optimizes storage utilization and performance by reducing the footprint of virtual desktops. It also supports the use of different tiers of storage to maximize performance and reduce cost. Thin provisioning support VMware Horizon View 5.2 enables efficient allocation of storage resources when virtual desktops are provisioned. This results in better use of storage infrastructure and reduced capital expenditure (CAPEX)/operating expenditure (OPEX). This solution requires the VMware Horizon View 5.2 Bundle. The VMware Horizon View Bundle includes access to all View features, such as vsphere Desktop, vcenter Server, View Manager, View Composer, View Persona Management, vshield Endpoint, VMware ThinApp, and VMware View Client with Local Mode. The VMware Horizon View 5.2 release includes the following enhancements for improving the user experience. Support for Hardware accelerated 3-D graphics by virtualizating the Graphics Processing Unit (GPU) Desktop access through HTML5, and ios and Android applications Support for Microsoft Windows 8 For more information, refer to What s New in VMware Horizon View

25 Solution Technology Overview VMware View Composer View Composer works directly with vcenter Server to deploy, customize, and maintain the state of the virtual desktops when using linked clones. Desktops provisioned as linked clones share a common base image within a desktop pool and as such have a minimal storage footprint. View Composer also enables the following capabilities: Tiered storage support to enable the use of dedicated storage resources for the placement of both the read-only replica and linked clone disk images. An optional standalone View Composer server used to minimize the impact of virtual desktop provisioning and maintenance operations on the vcenter Server. This solution uses View Composer to deploy 250 dedicated virtual desktops running Windows 7 as linked clones. VMware View Persona Management View Persona Management preserves user profiles and dynamically synchronizes them with a remote profile repository. View Persona Management does not require the configuration of Windows roaming profiles, thus eliminating the need to use Active Directory to manage View user profiles. View Persona Management provides the following benefits compared to traditional Windows roaming profiles: With View Persona Management, a user s remote profile is dynamically downloaded when the user logs in to a View desktop. View downloads persona information only when the user needs it. During login, View downloads only the files that Windows requires, such as user registry files. Other files are copied to the local desktop when the user or an application opens them from the local profile folder. View copies recent changes in the local profile to the remote repository at a configurable interval. During logout, only files that are updated since the last replication are copied back to the remote repository. Configure View Persona Management to store user profiles in a secure, centralized repository. VMware View Storage Accelerator View Storage Accelerator reduces the storage load associated with virtual desktops by caching the common blocks of desktop images into local vsphere host memory. Storage Accelerator uses a feature of VMware vsphere 5.1 called Content Based Read Cache (CBRC), which is implemented inside the vsphere hypervisor. When enabled for the View virtual desktop pools, the host hypervisor scans the storage disk blocks to generate digests of the block contents. When these blocks are read into the hypervisor, they are cached in the host based CBRC. Subsequent reads of blocks with the same digest are served directly from the in-memory cache. This significantly improves the performance of the virtual desktops, especially during boot storms, user login storms, or antivirus scanning storms when reading a large number of blocks with identical content. 25

26 Solution Technology Overview Virtualization VMware vsphere 5.1 VMware vsphere 5.1 is the market-leading virtualization platform that is used across thousands of IT environments around the world. VMware vsphere 5.1 transforms a computer s physical resources by virtualizing the memory, storage, and network. This transformation creates fully functional virtual desktops that run isolated and encapsulated operating systems and applications just like physical computers. The high-availability features of VMware vsphere 5.1 are coupled with DRS and VMware vmotion which enables the seamless migration of virtual desktops from one vsphere server to another with minimal or no impact to the customer s usage. This solution uses VMware vsphere Desktop Edition for deploying desktop virtualization. It provides the full range of features and functionalities of the vsphere Enterprise Plus edition, enabling customers to achieve scalability, high availability, and optimal performance for all of their desktop workloads. vsphere Desktop also comes with unlimited vram entitlement. vsphere Desktop edition is intended for customers who want to purchase only vsphere licenses to deploy desktop virtualization. VMware vcenter VMware vcenter is a centralized management platform for the VMware virtual infrastructure. It provides administrators with a single interface for all aspects of monitoring, managing, and maintaining of the virtual infrastructure and can be accessed from multiple devices. VMware vcenter also manages some of the more advanced features of the VMware virtual infrastructure, such as vsphere High Availability (HA) and DRS, along with vmotion and Update Manager. VMware vsphere High Availability The VMware vsphere HA feature enables the virtualization layer to restart virtual machines automatically in various failure conditions. If the virtual machine operating system has an error, the virtual machine can be automatically restarted on the same hardware. If the physical hardware has an error, the impacted virtual machines can be automatically restarted on other servers in the cluster. Note In order to restart virtual machines on different hardware those servers need to have resources available. vsphere HA enables you to configure policies to determine which machines are restarted automatically, and under what conditions these operations should be attempted. 26

27 Solution Technology Overview EMC Virtual Storage Integrator for VMware EMC Virtual Storage Integrator (VSI) for VMware vsphere is a plug-in to the vsphere client that provides a single management interface that is used for managing EMC storage within the vsphere environment. Features can be added and removed from VSI independently, which provides flexibility for customizing VSI user environments. Features are managed with the VSI Feature Manager. VSI provides a unified user experience, which enables new features to be introduced quickly in response to changing customer requirements. Apply the following features during the validation testing: Storage Viewer (SV) Extends the vsphere client to facilitate the discovery and identification of VNXe storage devices that are allocated to VMware vsphere hosts and virtual machines. SV presents the underlying storage details to the virtual data center administrator, merging the data of several different storage mapping tools into a few seamless vsphere client views. Unified Storage Management Simplifies storage administration of the VNX unified storage platform. It enables VMware administrators to provision new Network File System (NFS) and Virtual Machine File System (VMFS) datastores, and Raw Device Mapping (RDM) volumes seamlessly within vsphere client. The EMC VSI for VMware vsphere product guides on EMC Online Support have more information. VNXe VMware vstorage API for Array Integration support Hardware acceleration with VMware vstorage API for Array Integration (VAAI) is a storage enhancement in vsphere that enables vsphere to offload specific storage operations to compatible storage hardware such as the VNXe series platforms. With storage hardware assistance, vsphere performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth. Compute The choice of a server platform for an VSPEX infrastructure is not only based on the technical requirements of the environment, but on the supportability of the platform, existing relationships with the server provider, advanced performance and management features, and many other factors. For this reason, VSPEX solutions are designed to run on a wide variety of server platforms. Instead of requiring a given number of servers with a specific set of requirements, VSPEX documents a number of processor cores and an amount of RAM that must be achieved. This can be implemented with two servers or twenty and still be considered the same VSPEX solution. For example, assume that the compute layer requirements for a given implementation are 25 processor cores, and 200GB of RAM. One customer wants to implement these using white-box servers containing 16 processor cores, and 64 GB of RAM; while a second customer chooses a higher-end server with 20 processor cores and 144 GB of RAM. Figure 2 shows this example. 27

28 Solution Technology Overview Figure 2. Example of compute layer flexibility The first customer needs four of the servers they chose, while the second customer needs two. Note To enable high availability at the compute layer each customer needs one additional server so if a server fails the system has enough capability to maintain business operations. Observe the following best practices in the compute layer: Use a number of identical or at least compatible servers. By implementing VSPEX on identical server units, you can minimize compatibility problems in this area. If you are implementing hypervisor layer high availability, then the largest virtual machine you can create is constrained by the smallest physical server in the environment. 28

29 Solution Technology Overview EMC recommends that you implement the high availability features available in the virtualization layer, and ensure that the compute layer has sufficient resources to accommodate at least single server failures. This enables you to implement minimal-downtime upgrades, and tolerate single unit failures. Within the boundaries of these recommendations and best practices, the compute layer for EMC VSPEX can be very flexible to meet your specific needs. The key constraint is that you provide sufficient processor cores and RAM per core to meet the needs of the target environment. Network The infrastructure network requires redundant network links for each vsphere host, the storage array, the switch interconnect ports, and the switch uplink ports. This configuration provides both redundancy and additional network bandwidth. This configuration is required regardless of whether the network infrastructure for the solution already exists, or is being deployed alongside other components of the solution. An example of this kind of highly available network topology is depicted in Figure 3. 29

30 Solution Technology Overview Figure 3. Example of Highly-Available network design This validated solution uses virtual local area networks (VLANs) to segregate network traffic of various types to improve throughput, manageability, application separation, high availability and security. EMC unified storage platforms provide network high availability or redundancy by using link aggregation. Link aggregation enables multiple active Ethernet connections to appear as a single link with a single MAC address, and potentially multiple IP addresses. In this solution, Link Aggregation Control Protocol (LACP) is configured on VNXe, combining multiple Ethernet ports into a single virtual device. If a link is lost in the Ethernet port, the link fails over to another port. All network traffic is distributed across the active links. 30

31 Solution Technology Overview Storage Overview EMC VNXe series The storage layer is a key component of any cloud infrastructure solution that serves data generated by applications and operating systems in a data center storage processing system. This increases storage efficiency, management flexibility and total cost of ownership (TCO). In this solution, VNXe series arrays are used to provide virtualization at the storage layer. The VNX family is optimized for virtual applications delivering innovation and enterprise capabilities for file, block, and object storage in a scalable, easy-to-use solution. This next-generation storage platform combines powerful and flexible hardware with advanced efficiency, management, and protection software to meet the demanding needs of today s enterprises. The VNXe series is powered by Intel Xeon processor for intelligent storage that automatically and efficiently scales in performance, while ensuring data integrity and security. The VNXe series is a purpose-built platform for IT managers in smaller environments and the VNX series is designed to meet the high-performance, high-scalability requirements of midsize and large enterprises. VNXe customer benefits VNXe supports the following features: Next-generation unified storage, optimized for virtualized applications Capacity optimization features including compression, deduplication, thin provisioning, and application-centric copies High availability, designed to deliver five 9s availability Multiprotocol support for file and block Simplified management with EMC Unisphere for a single management interface for all NAS, SAN, and replication needs VNXe software suites available The following VNXe software suites are available: Remote Protection Suite Protects data against localized failures, outages, and disasters. Application Protection Suite Automates application copies and proves compliance. Security and Compliance Suite Keeps data safe from changes, deletions, and malicious activity. VNXe software packs available The following VNXe software pack is available: Total Value Pack Includes all the protection software suites and the Security and Compliance Suite. 31

32 Solution Technology Overview Backup and recovery Overview EMC Avamar Backup and recovery is another import component in this VSPEX solution, which provides data protection by backing up data files or volumes with defined schedule and restoring data from backup in case recovery is happening after disaster. In this VSPEX solution, EMC Avamar is used for backup/recovery, supporting up to 250 virtual desktops. EMC Avamar provides methods to back up virtual desktops using either image-level or guest-based operations. Avamar runs the deduplication engine at the virtual machine disk (VMDK) level for image backups and at the file-level for guest-based backups. Image-level protection enables backup clients to make a copy of all the virtual disks and configuration files associated with the particular virtual desktop, to be used in the event of hardware failure, corruption, or accidental deletion of a virtual desktop. Avamar significantly reduces the backup and recovery time of the virtual desktop by using change block tracking (CBT) on both backup and recovery. Guest-based protection runs like traditional backup solutions. Guest-based backup can be used on any virtual machine running an operating system for which an Avamar backup client is available. It enables fine-grained control over the content and inclusion and exclusion patterns. This can be used to prevent data loss due to user errors, such as accidental file deletion. Installing the desktop or laptop agent on the system to be protected enables end-user self-service recoverability of data. This solution is tested with guest-based backups. Security RSA SecurID twofactor authentication RSA SecurID two-factor authentication can provide enhanced security for the VSPEX end-user computing environment by requiring the user to authenticate with two pieces of information, collectively called a passphrase, consisting of: Something the user knows: a PIN, which is used like any other PIN or password. Something the user has: A token code, provided by a physical or software token, which changes every 60 seconds. The typical use case deploys SecurID to authenticate users accessing protected resources from an external or public network. Access requests originating from within a secure network are authenticated by traditional mechanisms involving Active Directory or LDAP. A configuration description for implementing SecurID is available for the VSPEX end-user computing solutions. SecurID functionality is managed through RSA Authentication Manager, which also controls administrative functions such as token assignment to users, user management, high availability, and so on. 32

33 Solution Technology Overview SecurID authentication in the VSPEX enduser computing environment SecurID support is built into VMware Horizon View, providing a simple activation process. Users accessing a SecurID-protected Horizon View environment are initially authenticated with a SecurID passphrase, following by a normal authentication against Active Directory. In a typical deployment, one or more View Connection servers are configured with SecurID for secure access from external or public networks, with other Connection servers accessed within the local network retaining Active Directory-only authentication. Figure 4 shows placement of the Authentication Manager servers in the Horizon View environment. Figure 4. Authentication control flow for Horizon View access requests originating on an external network Required components The following components are required to enable SecurID: RSA SecurID Authentication Manager (version 8.0) Used to configure and manage the SecurID environment and assign tokens to users. Authentication Manager 7.1 SP4 is available as a virtual appliance running on VMware ESXi. SecurID tokens for all users SecurID requires something the user knows (a PIN) with a constantly-changing code from a token the user has in 33

34 Solution Technology Overview possession. SecurID tokens may be physical, displaying a new code every 60 seconds which the user must then enter with a PIN, or software-based, where the user supplies a PIN and the token code is supplied programmatically. Hardware and software tokens are registered with Authentication Manager through token records supplied on a CD or other media. For more information about enabling SecurID for VSPEX end-user computing architecture for VMware Horizon View, refer to the design guide Securing EMC VSPEX End-User Computing With RSA SecurID - VMware Horizon View 5.2 and VMware vsphere 5.1 for up to 2,000 Virtual Desktops. Compute, memory, and storage resources Figure 5 shows the VSPEX end-user computing for VMware Horizon View environment with two infrastructure virtual machines added to support Authentication Manager. Figure 5. Logical architecture: VSPEX end-user computing for VMware Horizon View with RSA The minimum hardware resources needed to support SecurID are: Two CPU (cores) 4 GB memory 100 GB disk space Requirements are minimal and can be drawn from the overall infrastructure resource pool. For more information, refer to the RSA Authentication Manager 8.0 Performance and Scalability Guide. 34

35 Solution Technology Overview Other components VMware vshield Endpoint VMware vcenter Operations Manager for Horizon View VMware vshield Endpoint offloads virtual desktop antivirus and antimalware scanning operations to a dedicated secure virtual appliance delivered by VMware partners. Offloading scanning operations improves desktop consolidation ratios and performance by eliminating antivirus storms, while also streamlining antivirus and antimalware deployment and monitoring and satisfying compliance and audit requirements through detailed logging of antivirus and antimalware activities. VMware vcenter Operations Manager for Horizon View provides end-to-end visibility into the health, performance and efficiency of virtual desktop infrastructure (VDI). It enables desktop administrators to proactively ensure the best end-user experience, avert incidents and eliminate bottlenecks. Designed for VMware Horizon View, this optimized version of vcenter Operations Manager improves IT productivity and lowers the cost of owning and operating VDI environments. Traditional operations-management tools and processes are inadequate for managing large View deployments, because: The amount of monitoring data and quantity of alerts overwhelm desktop and infrastructure administrators. Traditional tools provide only a silo view and don t adapt to the behavior of specific environments. Lack of end-to-end visibility into the performance and health of the entire stack including servers, storage and networking stalls large VDI deployments. IT productivity suffers from reactive management and the inability to ensure quality of service proactively. VMware vcenter Operations Manager for Horizon View addresses these challenges and delivers higher team productivity, lower operating expenses and improved infrastructure utilization. Key features include: Patented self-learning analytics that adapt to your environment, continuously analyzing thousands of metrics for server, storage, networking and end-user performance. Comprehensive dashboards that simplify monitoring of health and performance, identify bottlenecks, and improve infrastructure efficiency of your entire View environment. Dynamic thresholds and smart alerts that notify administrators earlier in the process and provide more-specific information about impending performance issues. Automated root-cause analysis, session lookup and event correlation for faster troubleshooting of end- user problems. Integrated approach to performance, capacity and configuration management that supports holistic management of VDI operations. 35

36 Solution Technology Overview Design and optimizations specifically for VMware Horizon View. Availability as a virtual appliance for faster time to value. 36

37 Chapter 4 Solution Stack Architectural Overview This chapter presents the following topics: Solution overview Solution architecture Server configuration guidelines Network configuration guidelines Storage configuration guidelines High availability and failover Validation test profile Antivirus and antimalware platform profile vcenter Operations Manager for Horizon View platform profile Backup and recovery configuration guidelines Sizing guidelines Reference workload Applying the reference workload Implementing the reference architectures Quick assessment

38 Solution Stack Architectural Overview Solution overview Solution architecture solutions are built with proven technologies to create a complete virtualization solution that enables you to make an informed decision when choosing and sizing the hypervisor, compute, and networking layers. VSPEX eliminates many server virtualization planning and configuration burdens by using extensive interoperability, functional, and performance testing by EMC. VSPEX accelerates your IT Transformation to cloud-based computing by enabling faster deployment, greater choice, higher efficiency, and lower risk. This section is intended to be a comprehensive guide to the major aspects of this solution. Server capacity is specified in generic terms for required minimums of CPU, memory and network interfaces; you are free to select the server and networking hardware of your choice that meet or exceed the stated minimums. The specified storage architecture, along with a system meeting the server and network requirements outlined, has been validated by EMC to provide high levels of performance while delivering a highly available architecture for your end-user computing deployment. Each balances the storage, network, and compute resources needed for a set number of virtual machines, which have been validated by EMC. In practice, each virtual machine has its own set of requirements that rarely fit a pre-defined idea of what a virtual machine should be. In any discussion about virtual infrastructures, it is important to first define a reference workload. Not all servers perform the same tasks, and it is impractical to build a reference that takes into account every possible combination of workload characteristics. Overview Below is a detailed description of the VSPEX end-user computing solution for up to 250 virtual desktops. Note VSPEX uses the concept of a Reference Workload to describe and define a virtual machine. Therefore, one physical or virtual desktop in an existing environment may not be equal to one virtual desktop in a VSPEX solution. Evaluate your workload in terms of the reference to arrive at an appropriate point of scale. A detailed process is described in Applying the reference workload. 38

39 Solution Stack Architectural Overview Architecture for up to 250 virtual desktops The architecture diagrams in this section show the layout of major components comprising the solution. Figure 6 shows the overall logical architecture of the solution. Figure 6. Logical architecture for 250 virtual desktops Key components This section lists the key components used in this solution. VMware View Manager Server Provides virtual desktop delivery, authenticates users, manages the assembly of users' virtual desktop environments, and brokers connections between users and their virtual desktops. In this solution, VMware View Manager 5.2 is installed on Windows Server 2008 R2 and hosted as a virtual machine on a VMware vsphere 5.1 server. Two VMware View Manager Servers were used in this solution. Virtual desktops Two hundred and fifty persistent virtual desktops running Windows 7 are provisioned as VMware View Linked Clones. VMware vsphere 5.1 Provides a common virtualization layer to host a server environment that contains the virtual machines. The specifics of the validated environment are listed in Table 1. vsphere 5.1 provides highly available infrastructure through such features as: vmotion Provides live migration of virtual machines within a virtual infrastructure cluster, with no virtual machine downtime or service disruption. 39

40 Solution Stack Architectural Overview Storage vmotion Provides live migration of virtual machine disk files within and across storage arrays with no virtual machine downtime or service disruption. vsphere High Availability Detects and provides rapid recovery for a failed virtual machine in a cluster. Distributed Resource Scheduler (DRS) Provides load balancing of computing capacity in a cluster. Storage Distributed Resource Scheduler (SDRS) Provides load balancing across multiple datastores, based on space use and I/O latency. VMware vcenter Server 5.1 Provides a scalable and extensible platform that forms the foundation for virtualization management for the VMware vsphere 5.1 cluster. All vsphere hosts and their virtual machines are managed through vcenter. VMware vshield Endpoint Offloads virtual desktop antivirus and antimalware scanning operations to a dedicated secure virtual appliance delivered by VMware partners. Offloading scanning operations improves desktop consolidation ratios and performance by: Eliminating antivirus storms Streamline antivirus and antimalware deployment Monitoring and satisfying compliance and audit requirements through detailed logging of antivirus and antimalware activities VMware vcenter Operations Manager for Horizon View Monitors the virtual desktops and all of the supporting elements of the VMware Horizon View virtual infrastructure. VSI for VMware vsphere Plug-in to the vsphere client that provides storage management for EMC arrays directly from the client. VSI is highly customizable and helps provide a unified management interface. SQL Server vcenter Server requires a database service to store configuration and monitoring details. A Microsoft SQL Server 2008 R2 is used for this purpose. DHCP server Centrally manages the IP address scheme for the virtual desktops. This service is hosted on the same virtual machine as the domain controller and DNS server. The Microsoft DHCP Service running on a Windows 2012 server is used for this purpose. DNS Server Required for the various solution components to perform name resolution. The Microsoft DNS Service running on a Windows Server 2012 server is used for this purpose. Active Directory Server Required for the various solution components to function properly. The Microsoft AD Directory Service running on a Windows Server 2012 server is used for this purpose. Shared Infrastructure DNS and authentication or authorization services like Microsoft Active Directory can be provided through existing infrastructure or set up as part of the new virtual infrastructure. 40

41 Solution Stack Architectural Overview IP/Storage Networks All network traffic is carried by standard Ethernet network with redundant cabling and switching. User and management traffic is carried over a shared network while NFS storage traffic is carried over a private, non-routable subnet. EMC VNXe3300 series Provides storage by using IP (NFS) connections for virtual desktops, and infrastructure virtual machines such as VMware View Manager servers, VMware vcenter Servers, Microsoft SQL Server databases, and other supporting services. Optionally, user profiles and home directories are redirected to CIFS network shares on VNXe3300. VNXe series storage arrays include the following components: Storage processors (SPs) support block and file data with UltraFlex I/O technology that supports iscsi, CIFS and NFS protocols. The SPs provide access for all external hosts and for the file side of the VNXe array. Battery backup units are battery units within each storage processor and provide enough power to each storage processor to ensure that any data in flight is de-staged to the vault area in the event of a power failure. This ensures that no writes are lost. On restart of the array, the pending writes are reconciled and persisted. Disk-array enclosures (DAE) house the drives used in the array. EMC Avamar Provides the platform for protection of virtual machines. This protection strategy uses persistent virtual desktops. It can use both image-level and guestbased protection. Hardware resources Table 1 lists the hardware used in this solution. Table 1. Solution hardware Hardware Configuration Notes Servers for virtual desktops Memory: 2 GB RAM per desktop (500 GB RAM across all servers) CPU: 1 vcpu per desktop (eight desktops per core:32 cores across all servers) Network: Six 1 GbE NICs per server Additional CPU and RAM as needed for the VMware vshield Endpoint and Avamar AVE components. Note: To implement vsphere HA functionality and to meet the listed minimums, the infrastructure should have one additional server. Total server capacity required to host 250 virtual desktops Refer to vendor documentation for specific details concerning vshield Endpoint and Avamar AVE resource requirements NFS and CIFS network infrastructure Minimum switching capability: Six 1 GbE ports per vsphere server Two 10 GbE ports per storage processor Redundant LAN configuration 41

42 Solution Stack Architectural Overview Hardware Configuration Notes EMC VNXe3300 Two storage processors (active/active) Two 10 GbE interfaces per storage processor Twenty-two 300 GB, 15k rpm 3.5-inch SAS disks (three RAID 5 performance packs and one hot spare disk) For throughput requirement, 1 GbE may be sufficient for 250 basic desktops, while 10 GbE is preferred for applications and systems with higher I/O needs. Servers for customer infrastructure Thirteen 2 TB, 7,200 rpm 3.5-inch NL-SAS disks Seven 300 GB, 15k rpm 3.5-inch SAS disks (one RAID 5 performance pack) Seven 300 GB, 15k rpm 3.5-inch SAS disks (one RAID 5 performance pack) Minimum number required: Two physical servers 20 GB RAM per server Four processor cores per server Two 1 GbE ports per server Additional CPU and RAM as needed for the VMware vshield Endpoint components. Optional for user data Optional for infrastructure storage Optional for vcenter Operations Manager for Horizon View These servers and the roles they fulfill may already exist in the customer environment Refer to vendor documentation for specific details concerning vshield Endpoint resource requirements Software resources Table 2 lists the software used in this solution. Table 2. Solution software Software Configuration VNXe3300 (shared storage, file systems) Software version VMware Horizon View Desktop Virtualization VMware View Manager 5.2 Operating system for View Manager Microsoft SQL Server Windows Server 2008 R2 Standard Edition Version 2008 R2 Standard Edition EMC Avamar Next-Generation Backup Avamar Virtual Edition (2TB) Avamar Agent 6.1 SP1 6.1 SP1 42

43 Solution Stack Architectural Overview Software VMware vsphere Configuration vsphere Server 5.1* vcenter Server vshield Manager (includes vshield Endpoint Service) Operating System For Vcenter Server 5.1.0a 5.1 Windows Server 2008 R2 Standard Edition VMware vcenter Operations Manager for Horizon View VMware vcenter Operations Manager vcenter Operations Manager for Horizon View plug-in 1.5 Virtual desktops Note: Aside from the base operating system, this software is used for solution validation and is not required Base operating system Microsoft Windows 7 Standard (32-bit) SP1 Microsoft Office Office Enterprise 2007 Microsoft Internet Explorer Adobe Reader X (10.1.3) VMware vshield Endpoint (component of VMware Tools) build Adobe Flash Player 11 Bullzip PDF Printer FreeMind Login VSI (VDI workload generator) 3.6 Professional Edition * Patch ESXi needed for support Horizon View 5.2 Sizing for validated configuration When selecting servers for this solution, the processor core must meet or exceed the performance of the Intel Nehalem family at 2.66 GHz. As servers with greater processor speeds, performance, and higher core density become available, servers can be consolidated as long as the required total core and memory count is met and a sufficient number of servers are incorporated to support the necessary level of high availability. As with the selection of servers, selecting network interface card (NIC) speed and quantity should also be consolidated as long as the overall bandwidth requirement for this solution and sufficient redundancy necessary to support high availability are maintained. 43

44 Solution Stack Architectural Overview The following represents a sample server configuration required to support this 250- desktop solution. Four servers each with: Two quad-core processors (total eight cores) 128 GB of RAM This server configuration provides 32 cores and 512 GB of RAM. As shown in Table 1, a minimum of one core is required to support eight virtual desktops and a minimum of 2 GB of RAM is required for each. The correct balance of memory and cores for the expected number of virtual desktops to be supported by a server must also be taken into account. Additional CPU resources and RAM are required to support the VMware vshield Endpoint components. IP network switches used to implement this solution must have a minimum backplane capacity of 48 Gb/s non-blocking and support the following features: IEEE 802.1x Ethernet flow control 802.1q VLAN tagging Ethernet link aggregation using IEEE 802.1ax (802.3ad) Link Aggregation Control Protocol Simple Network Management Protocol (SNMP) management capability Jumbo frames The quantity and type of switches chosen should support high availability. A network vendor must be chosen based on the availability of parts, service, and support contracts. The network configuration should also include the following: A minimum of two switches to support redundancy Redundant power supplies A minimum of forty 1-GbE ports (distributed for high availability) Appropriate uplink ports for customer connectivity Use of 10 GbE ports should align with the ports on the server and storage while keeping in mind the overall network requirement for this solution and a level of redundancy to support high availability. Additional server NICs and storage connections should also be considered based on customer or specific implementation requirements. The management infrastructure (Active Directory, DNS, DHCP, and SQL Server) can be supported on two servers similar to those previously defined, but will require a minimum of 20 GB RAM instead of 128 GB. Disk storage layout is explained in Storage configuration guidelines. 44

45 Solution Stack Architectural Overview Server configuration guidelines Overview When designing and ordering the compute/server layer of the VSPEX solution described below, several factors may alter the final purchase. From a virtualization perspective, if a systems workload is well understood, features like Memory Ballooning and Transparent Page Sharing can reduce the aggregate memory requirement. If the virtual machine/desktop pool does not have a high level of peak or concurrent usage, the number of vcpus is reduced. Conversely, if the applications deployed are highly computational in nature, the number of CPUs and memory purchased may need to be increased. Table 3 lists the server hardware and the configurations. Table 3. Server hardware Hardware Configuration Notes Servers for virtual desktops Memory: 2 GB RAM per desktop (500 GB RAM across all servers) CPU: 1 vcpu per desktop (eight desktops per core:32 cores across all servers) Network: Six 1 GbE NICs per server Additional CPU and RAM as needed for the VMware vshield Endpoint and Avamar AVE components. Note: To implement VMware vsphere HA functionality and to meet the listed minimums, the infrastructure should have one additional server. Total server capacity required to host 250 virtual desktops Refer to vendor documentation for specific details concerning vshield Endpoint and Avamar AVE resource requirements VMware vsphere memory virtualization for VSPEX VMware vsphere 5.1 has a number of advanced features that help to maximize performance and overall resource utilization. The most important of these are in the area of memory management. This section and Figure 7 describes some of these features and the items you need to consider when using them in the environment. In general, you can consider virtual machines on a single hypervisor consuming memory as a pool of resources. 45

46 Solution Stack Architectural Overview Figure 7. Hypervisor memory consumption This basic concept is enhanced by understanding the technologies described in this section. Memory over-commitment Memory over-commitment occurs when more memory is allocated to virtual machines than is physically present in a VMware vsphere host. Using sophisticated techniques, such as ballooning and transparent page sharing, vsphere is able to handle memory over-commitment without any performance degradation. If more memory than that is present on the server that is being actively used, vsphere may resort to swapping out portions of a virtual machine s memory. 46

47 Non-Uniform Memory Access (NUMA) Solution Stack Architectural Overview vsphere uses a NUMA load-balancer to assign a home node to a virtual machine. Because memory for the virtual machine is allocated from the home node, memory access is local and provides the best performance possible. Applications that do not directly support NUMA benefit from this feature. Transparent page sharing Virtual machines running similar operating systems and applications typically have identical sets of memory content. Page sharing enables the hypervisor to reclaim the redundant copies and keep only one copy, which frees up the total host memory consumption. If most of your application virtual machines run the same operating system and application binaries then total memory usage can be reduced to increase consolidation ratios. Memory ballooning By using a balloon driver loaded in the guest operating system, the hypervisor can reclaim host physical memory if memory resources are under contention. This is done with little to no impact to the performance of the application. Memory configuration guidelines This section provides guidelines for allocating memory to virtual machines. The guidelines outlined here take into account vsphere memory overhead and the virtual machine memory settings. vsphere memory overhead There is some associated overhead for the virtualization of memory resources. The memory space overhead has two components: The system overhead for the VMkernel Additional overhead for each virtual machine The amount of additional overhead memory for the VMkernel is fixed while each virtual machine depends on the number of virtual CPUs and configured memory for the guest operating system. Allocating memory to virtual machines The proper sizing of memory for a virtual machine or desktop in VSPEX architectures is based on many factors. With the number of application services and use cases available determining a suitable configuration for an environment requires creating a baseline configuration, testing, and adjustments, as discussed later in this guide. In this solution, each virtual desktop gets 2 GB memory, as listed in Table 1. Network configuration guidelines Overview This section provides guidelines for setting up a redundant, high-availability network configuration. The guidelines outlined here take into account jumbo frames, VLANs, and LACP on EMC unified storage. For details on the network resource requirement, refer to Table 1. 47

48 Solution Stack Architectural Overview VLAN The best practice is to isolate network traffic so that the traffic between hosts and storage, hosts and clients, and management traffic all move over isolated networks. In some cases physical isolation may be required for regulatory or policy compliance reasons; but in many cases logical isolation using VLANs is sufficient. This solution requires a minimum of three VLANs. Client access Storage Management These VLANs are shown in Figure 8. Figure 8. Required networks The client access network is for users of the system, or clients, to communicate with the infrastructure. The storage network is used for communication between the compute layer and the storage layer. The management network is used for administrators to have a dedicated way to access the management connections on the storage array, network switches, and hosts. Note Figure 8 demonstrates the network connectivity requirements for a VNXe3300 using 1-GbE network connections. A similar topology should be created when using the VNXe3150 array, or 10 GbE network connections. 48

49 Solution Stack Architectural Overview Enable jumbo frames Link aggregation This solution for EMC VSPEX end-user computing recommends MTU be set at 9,000 (jumbo frames) for efficient storage and migration traffic. A link aggregation resembles an Ethernet channel, but uses the Link Aggregation Control Protocol (LACP) IEEE 802.3ad standard. The IEEE 802.3ad standard supports link aggregations with two or more ports. All ports in the aggregation must have the same speed and be full duplex. In this solution, LACP is configured on VNXe, combining multiple Ethernet ports into a single virtual device. If a link is lost in the Ethernet port, the link fails over to another port. All network traffic is distributed across the active links. Storage configuration guidelines Overview vsphere allows more than one method of utilizing storage when hosting virtual machines. The solutions in Table 4 were tested utilizing NFS and the storage layout described adheres to all current best practices. An educated customer or architect can make modifications based on their understanding of the systems usage and load if required. Table 4. Storage hardware Hardware Configuration Notes EMC VNXe3300 Two storage processors (active/active) Two 10 GbE interfaces per storage processor Twenty-two 300 GB, 15k rpm 3.5-inch SAS disks (three RAID 5 performance packs) For throughput requirement, 1 GbE may be sufficient for 250 basic desktops, while 10 GbE is preferred for applications and systems with higher I/O needs. Thirteen 2 TB, 7,200 rpm 3.5-inch NL-SAS disks Seven 300 GB, 15k rpm 3.5-inch SAS disks (one RAID 5 performance pack) Seven 300 GB, 15k rpm 3.5-inch SAS disks (one RAID 5 performance pack) Optional for user data Optional for infrastructure storage Optional for vcenter Operations Manager for Horizon View This section provides guidelines for setting up the storage layer of the solution to provide high availability and the expected level of performance. VMware vsphere storage virtualization for VSPEX VMware ESXi provides host-level storage virtualization. It virtualizes the physical storage and presents the virtualized storage to virtual machine. A virtual machine stores its operating system and all other files related to the virtual machine activities in a virtual disk. Figure 9 shows VMware virtual disk types. The 49

50 Solution Stack Architectural Overview virtual disk itself is one or multiple files. VMware uses a virtual SCSI controller to present the virtual disk to guest operating systems running inside virtual machines. A virtual disk resides in a datastore. Depending on the type used, it can be either a VMware Virtual Machine File system (VMFS) datastore or an NFS datastore. Figure 9. VMware virtual disk types VMFS VMFS is a cluster file system that provides storage virtualization optimized for virtual machines. It can be deployed over any SCSI-based local or networked storage. Raw Device Mapping In addition, VMware also provides a mechanism named Raw Device Mapping (RDM). RDM enables a virtual machine to access a volume on the physical storage directly, and can only be used with Fibre Channel or iscsi. NFS VMware supports using NFS file systems from external NAS storage system or device as virtual machine datastore. 50

51 Solution Stack Architectural Overview Storage layout for 250 virtual desktops Core storage layout Figure 10 shows the layout of the disks that are required to store 250 virtual desktops. This layout does not include space for user profile data. For more information, refer to VNXe shared file systems. Figure 10. Core storage layout 250 virtual desktops Core storage layout overview The following core configuration is used in the solution. Twenty-one SAS disks are allocated in RAID 5 (6+1) group to contain virtual desktop datastores. One SAS disk is a hot spare and is contained in the VNXe hot spare pool. Note Seven of the disks used (one RAID 5 (6+1) group) may contain VNXe system storage, which reduces user storage. VNXe provisioning wizards perform disk allocation and do not allow user selection. If more capacity is required, larger drives may be substituted. To satisfy the load recommendations, the drives will all need to be 15k rpm and the same size. If differing sizes are used, storage layout algorithms may give sub-optimal results. Optional user data storage layout In solution validation testing, storage space for user data is allocated on the VNXe array, as shown in Figure 11. This storage is in addition to the core storage shown in Figure 10. If storage for user data exists elsewhere in the production environment, this storage is not required. 51

52 Solution Stack Architectural Overview Figure 11. Optional storage layout 250 virtual desktops Optional storage layout overview The following optional configuration is used in the solution: Twelve NL-SAS disks are allocated in RAID 6 (4+2) groups to store user data and profiles. One NL-SAS disk is a hot spare. Seven SAS disks configured as a RAID 5 (6+1) group are used to store the infrastructure virtual machines. Seven SAS disks configured as RAID 5 (6+1) group are used to store the vcenter Operations Manager for Horizon View virtual desktops and databases. Remaining disks are unbound or drive bays may be empty, as no additional drives were used for testing this solution. Note The actual disk selection is done by the VNXe provisioning wizards and may not match the allocation. VNXe shared file systems The virtual desktops use two shared filed systems one for user profiles, and the other to redirect user storage that resides in home directories. In general, redirecting user data out of the base image of VNXe for file usage enables centralized administration, backup, and recovery, and makes the desktops more stateless. Each file system is exported to the environment through a CIFS share. High availability and failover Introduction Virtualization layer This VSPEX solution provides a highly available virtualized server, network, and storage infrastructure. When implemented in accordance with this guide it provides the ability to survive most single-unit failures with minimal to no impact to business operations. As indicated earlier, EMC recommends that you configure high availability in the virtualization layer and allow the hypervisor to restart automatically any virtual machines that fail. Figure 12 shows the hypervisor layer responding to a failure in the compute layer: 52

53 Solution Stack Architectural Overview Figure 12. High availability at the virtualization layer By implementing high availability at the virtualization layer, it ensures that, even in the event of a hardware failure the infrastructure attempts to keep as many services running as possible. Compute layer While the choice of servers to implement in the compute layer is flexible, EMC recommends that you use enterprise class servers designed for the data center. This type of server has redundant power supplies, which should be connected to separate power distribution units (PDUs) in accordance with your server vendor s best practices. Figure 13. Redundant power supplies EMC also recommends you configure high availability in the virtualization layer. This means configuring the compute layer with enough resources so that the total number of available resources meets the needs of the environment, even with a server failure, shown in Figure

54 Solution Stack Architectural Overview Network layer The advanced networking features of the VNX family provide protection against network connection failures at the array. Each vsphere host has multiple connections to user and storage Ethernet networks to guard against link failures. These connections should be spread across multiple Ethernet switches to guard against component failure in the network. These connections are also shown in Figure 14. Figure 14. Network layer high availability By ensuring that there are no single points of failure in the network layer, you can ensure that the compute layer is able to access storage, and communicate with users even if a component fails. Storage layer The VNX family is designed for five 9s availability by using redundant components throughout the array, as shown in Figure 15. All of the array components are capable of continued operation in case of hardware failure. The RAID disk configuration on the array provides protection against data loss due to individual disk failures, and the available hot spare drives are dynamically allocated to replace a failing disk. 54

55 Solution Stack Architectural Overview Figure 15. VNXe series high availability Validation test profile EMC storage arrays are designed to be highly available by default. When configured according to the directions in their installation guides there are no single unit failures that result in data loss or unavailability. Profile characteristics Table 5 shows the solution has a validated environment profile. Table 5. Validated environment profile Profile characteristic Value Number of virtual desktops 250 Virtual desktop operating system CPU per virtual desktop Windows 7 Enterprise (32-bit) SP1 1 vcpu Number of virtual desktops per CPU core 8 RAM per virtual desktop Desktop provisioning method Average storage available for each virtual desktop Average I/O per second (IOPS) per virtual desktop at steady state Average peak IOPS per virtual desktop during boot storm 2 GB Linked clone 18 GB (vmdk and vswap) 9.3 IOPS 40 IOPS Number of datastores to store virtual desktops 2 Number of virtual desktops per datastore

56 Solution Stack Architectural Overview Profile characteristic Disk and RAID type for datastores Disk and RAID type for CIFS shares to host user profiles and home directories Value RAID 5, 300 GB, 15k rpm, 3.5 inch SAS disks RAID 6, 2 TB, 7,200 rpm, 3.5 inch NL-SAS disks Antivirus and antimalware platform profile Platform characteristics The solution is sized based on the vshield Endpoint platform requirements, as shown in Table 6. Table 6. Platform characteristics Platform component VMware vshield Manager appliance VMware vshield Endpoint service VMware Tools vshield Endpoint component vshield Endpoint thirdparty security plug-in Technical information Manages the vshield Endpoint service installed on each vsphere host. 1 vcpu, 3 GB RAM, and 8 GB hard disk space. Installed on each desktop vsphere host. The service uses up to 512 MB of RAM on the vsphere host. A component of the VMware tools suite that enables integration with the vsphere host vshield Endpoint service. Installed as an optional component of the VMware tools software package and should be installed on the master virtual desktop image. Requirements vary based on individual vendor specifications. Note: A third-party plug-in and associated components are required to complete the vshield Endpoint solution. vshield architecture The individual components of the VMware vshield Endpoint platform and the vshield partner security plug-ins each have specific CPU, RAM, and disk space requirements. The resource requirements vary based on a number of factors, such as the number of events logged, log retention needs, the number of desktops being monitored, and the number of desktops on each vsphere host. 56

57 vcenter Operations Manager for Horizon View platform profile Solution Stack Architectural Overview Platform characteristics Table 7 shows how the solution was sized based on the vcenter Operations Manager for Horizon View platform requirements. Table 7. Platform characteristics Platform component VMware vcenter Operations Manager vapp VMware vcenter Operations Manager for Horizon View Adapter Technical information The vapp consists of a user interface (UI) virtual appliance and an Analytics virtual appliance. UI appliance requirements: 2 vcpu, 5 GB RAM, and 25 GB hard disk space Analytics appliance requirements: 2 vcpu, 7 GB RAM, and 150 GB hard disk space vcenter Operations Manager enables integration between vcenter Operations Manager and VMware View and requires a server running Microsoft Windows 2008 R2. The adapter gathers View related status information and statistical data. Server requirements: 2 vcpu, 6 GB RAM, and 30 GB hard disk space. vcenter Operations Manager for View architecture The individual components of vcenter Operations Manager for Horizon View have specific CPU, RAM, and disk space requirements. The resource requirements vary based on the number of desktops being monitored. The numbers provided in Table 7 assume that 250 desktops are monitored. Backup and recovery configuration guidelines Backup characteristics Table 8 shows the solution sizing with the application environment profile. Table 8. Profile characteristics Profile characteristic Value Number of virtual desktops 250 User data 2.5 TB (10.0 GB per desktop) Daily change rate for user data User data 2% Retention per data types Daily 30 daily 57

58 Solution Stack Architectural Overview Profile characteristic Weekly Monthly Value 4 weekly 1 monthly EMC Avamar AVE requirements 0.5 TB AVE 1.0 TB AVE 2.0 TB AVE 6 GB dedicated RAM and 850 GB disk space 8 GB dedicated RAM and 1,600 GB disk space 16 GB dedicated RAM and 3,100 GB disk space Two dedicated 2 GHz processors and one 1 GbE connection Backup layout EMC Avamar provides various deployment options depending on the specific use case and recovery requirements. In this case, the solution is deployed with two 2 TB Avamar Virtual Edition machines. This enables the unstructured user data to be backed up directly to the Avamar system for simple file-level recovery. The solution also enables customers to unify their backup process with industry-leading deduplication backup software, and achieve the highest levels of performance and efficiency. Sizing guidelines In the following sections, the readers will find definitions of the reference workload used to size and implement the VSPEX. Guidance is provided on how to correlate those reference workloads to actual customer workloads and how that may change the end delivery from the server and network perspective. Modification to the storage definition is made by adding drives for greater capacity and performance. The disk layouts are created to provide support for the appropriate number of virtual desktops at the defined performance level. Decreasing the number of recommended drives or stepping down an array type can result in lower IOPS per desktop and a reduced user experience due to higher response times. 58

59 Solution Stack Architectural Overview Reference workload Each balances the storage, network, and compute resources needed for a set number of virtual desktops that have been validated by EMC. In practice, each virtual desktop has its own set of requirements that rarely fit a pre-defined idea of what a virtual desktop should be. In any discussion about virtual infrastructures, it is important to first define a reference workload. Not all servers perform the same tasks, and it is impractical to build a reference that takes into account every possible combination of workload characteristics. Define the reference workload To simplify the discussion, we have defined a representative customer reference workload. By comparing the actual customer usage to this reference workload, you can extrapolate which solution to choose. For the VSPEX end-user computing solutions, the reference workload is defined as a single virtual desktop. Table 9 shows the characteristics of this virtual desktop. Table 9. Virtual desktop characteristics Characteristic Virtual desktop operating system Value Microsoft Windows 7 Enterprise Edition (32-bit) SP1 Virtual processors per virtual desktop 1 RAM per virtual desktop Available storage capacity per virtual desktop Average IOPS per virtual desktop at steady state 2 GB 18 GB (vmdk and vswap) 10 This desktop definition is based on user data that resides on shared storage. The I/O profile is defined by using a test framework that runs all desktops concurrently, with a steady load generated by the constant use of office-based applications like browsers, office productivity software, the Avamar backup agent and other standard task worker utilities. Applying the reference workload In addition to the supported desktop numbers, there may be other factors to consider when deciding which end-user computing solution to deploy. Concurrency The workloads used to validate VSPEX solutions assume that all desktop users will be active at all times. In other words, the 250 desktop architecture is tested with 250 desktops, all generating workload in parallel, all booted at the same time, and so on. If the customer expects to have 300 users, but only 50 percent of them are logged on at any given time due to time zone differences or alternate shifts, the 150 active users out of the total 300 users can be supported by the 250 desktop architecture. 59

60 Solution Stack Architectural Overview Heavier desktop workloads The workload is defined in Table 9 and used to test this VSPEX end-user computing configuration is considered a typical office worker load. However, some customers may feel that their users have a more active profile. If a company has 200 users, and due to custom corporate applications, each user generates 15 IOPS as compared to 10 IOPS used in the VSPEX workload. This customer needs 3,000 IOPS (200 users * 15 IOPS per desktop). This 250 desktop configuration would be underpowered in this case because it has been rated to 2,500 IOPS (250 desktops * 10 IOPS per desktop). This customer should refer to the VMware Horizon View 5.2 and VMware vsphere 5.1 for 500 Virtual Desktops document and consider moving up to the 500 desktops solution. Implementing the reference architectures Overview Resource types The solutions architectures require a set of hardware to be available for the CPU, memory, network, and storage needs of the system. In the solutions architectures, these are presented as general requirements that are independent of any particular implementation. This section describes some considerations for implementing the requirements. The solution architectures define the hardware requirements for the solution in terms of five basic types of resources: CPU resources Memory resources Network resources Storage resources Backup resources This section describes the resource types, how they are used in the solution, and key considerations for implementing them in a customer environment. CPU resources The solution architectures define the number of CPU cores that are required, but not a specific type or configuration. It is intended that new deployments use recent revisions of common processor technologies. It is assumed that these will perform as well as, or better than, the systems used to validate the solution. When using the Avamar backup solution for VSPEX, do not schedule all backups at once, but stagger them across your backup window. Scheduling all resources to back up at the same time could cause the consumption of all available host CPUs. In any running system, it is important to monitor the utilization of resources and adapt as needed. The reference virtual desktop and required hardware resources in the solutions architectures assume that there are no more than eight virtual CPUs for each physical processor core (8:1 ratio). In most cases, this provides an appropriate 60

61 Solution Stack Architectural Overview level of resources for the hosted virtual desktop. This ratio may not be appropriate in all use cases. Monitor the CPU utilization at the hypervisor layer to determine if more resources are required. Memory resources Each virtual desktop in the solution is defined to have 2 GB of memory. In a virtual environment, it is common to provision virtual desktops with more memory than the hypervisor physically has due to budget constraints. The memory over-commitment technique takes advantage of the fact that each virtual desktop does not fully use the amount of memory allocated to it. It makes business sense to oversubscribe the memory usage to some degree. The administrator should proactively monitor the oversubscription rate such that it does not shift the bottleneck away from the server and become a burden to the storage subsystem. If VMware vsphere runs out of memory for the guest operating systems, paging will begin to take place, resulting in extra I/O activity going to the vswap files. If the storage subsystem is sized correctly, occasional spikes due to vswap activity may not cause performance issues as transient bursts of load can be absorbed. However, if the memory oversubscription rate is so high that the storage subsystem is severely impacted by a continuing overload of vswap activity, more disks need to be added not because of capacity requirement, but due to the demand of increased performance. The administrator must now decide whether it is more cost effective to add more physical memory to the server, or to increase the amount of storage. With memory modules being a commodity, it is possibly less expensive to choose the former option. This solution was validated with statically assigned memory and no over-commitment of memory resources. If memory over-commit is used in a real-world environment, regularly monitor the system memory utilization and associated page file I/O activity to ensure that a memory shortfall does not cause unexpected results. When using the Avamar backup solution for VSPEX, you should stagger the scheduling of backups across your backup window. Do not schedule all backups to occur simultaneously. Scheduling all resources to back up at the same time could cause the consumption of all available host memory. Network resources The solution outlines the minimum needs of the system. If additional bandwidth is needed, it is important to add capability at both the storage array and the hypervisor host to meet the requirements. The options for network connectivity on the server will depend on the type of server. The storage arrays have a number of included network ports, and have the option to add ports using EMC FLEX I/O modules. For reference purposes in the validated environment, EMC assumes that each virtual desktop generates 10 IOs per second with an average size of 4 KB. Each virtual desktop is generating at least 40 KB/s of traffic on the storage network. For an environment rated for 250 virtual desktops, this comes out to a minimum of approximately 8 MB/sec. This is well within the bounds of modern networks. However, this does not consider other operations. For example, additional bandwidth is needed for: User network traffic Virtual desktop migration 61

62 Solution Stack Architectural Overview Administrative and management operations The requirements for each of these will vary depending on how the environment is being used. It is not practical to provide concrete numbers in this context. The network described in the solution for each solution should be sufficient to handle average workloads for the above use cases. Regardless of the network traffic requirements, always have at least two physical network connections that are shared for a logical network so that a single link failure does not affect the availability of the system. The network should be designed so that the aggregate bandwidth in the event of a failure is sufficient to accommodate the full workload. Storage resources The solution contains a layout for the disks used in the validation of the system. The layout balances the available storage capacity with the performance capability of the drives. There are a few layers to consider when examining storage sizing. Specifically, the array has a collection of disks that are assigned to a storage pool. From that storage pool, you can provision datastores to the VMware vsphere Cluster. Each layer has a specific configuration that is defined for the solution and documented in the Chapter 5 VSPEX Configuration Guidelines. It is generally acceptable to replace drive types with a type that has more capacity with the same performance characteristics or with ones that have higher performance characteristics and the same capacity. Similarly, it is acceptable to change the placement of drives in the drive shelves in order to comply with updated or new drive shelf arrangements. In other cases where there is a need to deviate from the proposed number and type of drives specified, or the specified pool and datastore layouts, ensure that the target layout delivers the same or greater resources to the system. Backup resources Implementation summary The solution outlines the backup storage (initial and growth) and retention needs of the system. Additional information can be gathered to size Avamar further including tape-out needs, RPO and RTO specifics, as well as multi-site environment replication needs. The requirements stated in the solution are what EMC considers the minimum set of resources to handle the workloads required based on the stated definition of a reference virtual desktop. In any customer implementation, the load of a system will vary over time as users interact with the system. If the customer s virtual desktops differ significantly from the reference definition, and vary in the same resource, then you may need to add more of that resource to the system. 62

63 Solution Stack Architectural Overview Quick assessment Overview An assessment of the customer environment helps to ensure that you implement the correct VSPEX solution. This section provides an easy-to-use worksheet to simplify the sizing calculations, and help assess the customer environment. First, summarize the user types planned for migration into the VSPEX end-user computing environment. For each group, determine the number of virtual CPUs, the amount of memory, the required storage performance, the required storage capacity, and the number of reference virtual desktops required from the resource pool. Applying the reference workload provides examples of this process. Fill out a row in the worksheet for each application, as shown in Table 10. Fill out the resource requirements for the user type. The row requires inputs on three different resources: CPU, memory, and IOPS. Table 10. Blank worksheet row Application CPU (virtual CPUs) Memory (GB) IOPs Equivalent reference virtual desktops Number of users Total reference desktops User type example Resource requirements Equivalent reference desktops CPU requirements Memory requirements The reference virtual desktop assumes most desktop applications are optimized for a single CPU. If one type of user requires a desktop with multiple virtual CPUs, modify the proposed virtual desktop count to account for the additional resources. For example, if you have virtualized 100 desktops, but 20 users require two CPUs instead of one, consider that your pool needs to provide for 120 virtual desktops. Memory plays a key role in ensuring application functionality and performance. Therefore, each application process has different targets for the acceptable amount of available memory. Like the CPU calculation, if a group of users require additional memory resources, simply adjust the number of desktops you are planning for to accommodate the additional resource requirements. For example, if you have 100 desktops to be virtualized, but each one needs 4 GB of memory instead of the 2 GB that is provided in the reference virtual desktop, plan for 200 reference virtual desktops. Storage performance requirements The storage performance requirements for desktops are usually the least understood aspect of performance. The reference virtual desktop uses a workload generated by an industry-recognized tool to execute a wide variety of office productivity 63

64 Solution Stack Architectural Overview applications and should be representative of the majority of virtual desktop implementations. Storage capacity requirements Determining equivalent reference virtual desktops The storage capacity requirement for a desktop can vary widely depending on the types of applications in use and specific customer policies. The virtual desktops in this solution rely on additional shared storage for user profile data and user documents. This requirement is covered as an optional component that can be met with the addition of specific storage hardware defined in the solution. It can also be covered with existing file shares in the environment. With all of the resources defined, determine an appropriate value for the equivalent reference virtual desktops by using the relationships in Table 11. Round up all values to the closest whole number. Table 11. Reference virtual desktop resources Resource Value for reference virtual desktop Relationship between requirements and equivalent reference virtual desktops CPU 1 Equivalent reference virtual desktops = Resource requirements Memory 2 Equivalent reference virtual desktops = (Resource requirements)/2 IOPS 10 Equivalent reference virtual desktops = (Resource requirements)/10 For example, 50 users each need two virtual CPUs, 12 IOPS per desktop, 8 GB of memory. Enter this in the Resource requirements row. They need two reference desktops of CPU, four reference desktops of memory, and two reference desktops of IOPS based on the virtual desktop characteristics in Table 11. Enter these figures in the Equivalent reference desktops row, as shown in Table 12. Use the maximum value in the row to fill in the Equivalent reference virtual desktops column. Multiply the number of equivalent reference virtual desktops by the number of users for the total resource needs for that user type. 64

65 Solution Stack Architectural Overview Table 12. Example worksheet row User type CPU (virtual CPUs) Memory (GB) IOPS Equivalent reference virtual desktops Number of users Total reference desktops Heavy users Resource requirements Equivalent reference virtual desktops After the worksheet is filled out for each user type that the customer wants to migrate into the virtual infrastructure, calculate the total number of reference virtual desktops required in the pool by calculating the sum of the total column on the right side of the worksheet, as shown in Table 13. Table 13. Example applications User type Heavy users Moderate users Typical users Resource requirements Equivalent reference virtual desktops Resource requirements Equivalent reference virtual desktops Resource requirements Equivalent reference virtual desktops CPU (virtual CPUs) Memory (GB) IOPS Equivalent reference virtual desktops Number of users Total reference desktops Total 240 The VSPEX end-user computing solutions define discrete resource pool sizes. For this solution set, the pool contains 250 desktops. In the case of Table 13, the customer requires 240 virtual desktops from the pool. Therefore, this 250 virtual desktop resource pool provides sufficient resources for the current needs as well as some room for growth. Fine tuning hardware resources In most cases, the recommended hardware for servers and storage is sized appropriately based on the process described. In some cases, there is a desire to customize the hardware resources available to the system beyond the recommended sizing. A complete description of system architecture is beyond the scope of this document. Additional customization can be done at this point. 65

66 Solution Stack Architectural Overview Storage resources In some applications, there is a need to separate some storage workloads from other workloads. The storage layouts in the VSPEX architectures put all of the virtual desktops in a single resource pool. In order to achieve workload separation, purchase additional disk drives for each group that needs workload isolation, and add them to a dedicated pool. It is not appropriate to reduce the size of the main storage resource pool in order to support isolation, or to reduce the capability of the pool without additional guidance beyond the scope of this guide. The storage layouts presented in the solutions are designed to balance many different factors in terms of high availability, performance, and data protection. Changing the components of the pool can have significant and difficult to predict impacts on other areas of the system. Server resources For the server resources in the VSPEX end-user computing solution, you can customize the hardware resources more effectively. To do this, first total the resource requirements for the server components as shown in Table 14. Table 14. Server resource component totals User type CPU (virtual CPUs) Memory (GB) Number of users Total CPU resources Total memory resources Heavy users Moderate users Typical users Resource requirements Resource requirements Resource requirements Total In this example, the target architecture required 210 virtual CPUs and 480 GB of memory. With an assumption of eight desktops per physical processor core, and no memory over-provisioning, this translates to 27 physical processor cores and 480 GB of memory. In contrast, this 250 virtual desktop resource pool as documented in the solution requires 500 GB of memory and at least 32 physical processor cores. In this environment, the solution is effectively implemented with fewer server resources. Note Consider high availability requirements when customizing the resource pool hardware. Table 15 shows a blank customer worksheet. 66

67 Solution Stack Architectural Overview Table 15. Blank customer worksheet User type CPU (virtual CPUs) Memory (GB) IOPS Equivalent reference virtual desktops Number of users Total reference desktops Resource requirements Equivalent reference virtual desktops Resource requirements Equivalent reference virtual desktops Resource requirements Equivalent reference virtual desktops Resource requirements Equivalent reference virtual desktops Resource requirements Equivalent reference virtual desktops Total 67

68 Solution Stack Architectural Overview 68

69 Chapter 5 VSPEX Configuration Guidelines This chapter presents the following topics: Configuration overview Pre-deployment tasks Customer configuration data Prepare switches, connect network, and configure switches Prepare and configure storage array Install and configure vsphere hosts Install and configure SQL Server database VMware vcenter Server deployment Set up VMware View Connection Server Set up Avamar Set up VMware vshield Endpoint Set up VMware vcenter Operations Manager for Horizon View Summary of VSPEX configuration guidelines

70 VSPEX Configuration Guidelines Configuration overview The deployment process is divided into the stages shown in Table 16. On completion of the deployment, the VSPEX infrastructure is ready for integration with the existing customer network and server infrastructure. Table 16 also includes references to chapters where relevant procedures are provided. Table 16. Deployment process overview Stage Description Reference 1 Verify prerequisites Pre-deployment tasks 2 Obtain the deployment tools Pre-deployment tasks 3 Gather customer configuration data 5 Configure the switches and networks, connect to the customer network Customer configuration data Prepare switches, connect network, and configure switches 6 Install and configure the VNXe Prepare and configure storage array 7 Configure virtual desktop datastores Prepare and configure storage array 8 Install and configure the servers Install and configure vsphere hosts 9 Set up SQL Server (used by vcenter and Horizon View) 10 Install and configure vcenter and virtual machine networking Install and configure SQL Server database VMware vcenter Server deployment 11 Set up View Connection Server Set up VMware View Connection Server 12 Set up Avamar Set up Avamar 13 Set up vshield Endpoint Set up VMware vshield Endpoint 14 Set up vcenter Operations Manager for Horizon View Set up VMware vcenter Operations Manager for Horizon View 70

71 VSPEX Configuration Guidelines Pre-deployment tasks Overview Pre-deployment tasks, as listed in Table 17, include procedures that do not directly relate to environment installation and configuration, but whose results are needed at the time of installation. Examples of pre-deployment tasks are the collection of hostnames, IP addresses, VLAN IDs, license keys, installation media, and so on. Perform these tasks before the customer visit to decrease the time required onsite. Table 17. Tasks for pre-deployment Task Description Reference Gather Gather the related documents EMC documentation documents listed in the Preface. These are Other documentation used throughout the text of this document to provide detail on setup procedures and deployment best practices for the various components of the solution. Gather tools Gather data Gather the required and optional tools for the deployment. Use Table 18 to confirm that all equipment, software, and appropriate licenses are available before the deployment process. Collect the customer-specific configuration data for networking, naming, and required accounts. Enter this information into the Customer Configuration Data worksheet for reference during the deployment process. Table 18 Appendix B Deployment prerequisites Complete the VNXe Series Configuration Worksheet, available on the EMC Online Support website, to provide the most comprehensive array-specific information. Table 18 itemizes the hardware, software, and license requirements to configure the solution. 71

72 VSPEX Configuration Guidelines Table 18. Deployment prerequisites checklist Requirement Description Reference Hardware Physical servers to host virtual desktops: Sufficient physical server capacity to host 250 virtual desktops. VMware vsphere 5.1 servers to host virtual infrastructure servers. Note: This requirement may be covered by existing infrastructure. Networking: Switch port capacity and capabilities as required by the enduser computing. EMC VNXe3300: Multiprotocol storage array with the required disk layout. Software VMware vsphere 5.1 installation media. VMware vcenter Server 5.1.installation media. VMware vshield Manager Open Virtualization Appliance (OVA) file. VMware vcenter Operations Manager OVA file. VMware vcenter Operations for Horizon View Adapter. VMware Horizon View 5.2 installation media. vshield Endpoint partner antivirus solution management server software. vshield Endpoint partner security virtual machine software. EMC VSI for VMware vsphere: Unified Storage Management EMC VSI for VMware vsphere: Storage Viewer. EMC Online Support Microsoft Windows Server 2008 R2 installation media (suggested OS for VMware vcenter and VMware View Connection Server). Microsoft Windows 7 SP1 installation media. Microsoft SQL Server 2008 or later installation media. 72

73 Requirement Description Reference Note: This requirement might be covered in the existing infrastructure. VSPEX Configuration Guidelines EMC vstorage API for Array Integration Plug-in. EMC Online Support Licenses VMware vcenter 5.1 license key. VMware vsphere 5.1 Desktop license keys. VMware View Premier 5.1 license keys. vshield Endpoint license keys (VMware). vshield Endpoint license keys (vshield Partner). VMware vcenter Operations for Horizon View. Microsoft Windows Server 2008 R2 Standard (or later) license keys. Note: This requirement might be covered in the existing Microsoft Key Management Server (KMS) Microsoft Windows 7 license keys. Note: This requirement might be covered in the existing Microsoft Key Management Server (KMS). Microsoft SQL Server license key. Note: This requirement might be covered in the existing infrastructure. 73

74 VSPEX Configuration Guidelines Customer configuration data To reduce the onsite time, information such as IP addresses and hostnames should be assembled as part of the planning process. Appendix A provides a table to maintain a record of relevant information. This form can be expanded or contracted as required, and information may be added, modified, and recorded as deployment progresses. Additionally, complete the VNXe Series Configuration Worksheet, available on the EMC online support website, to provide the most comprehensive array-specific information. Prepare switches, connect network, and configure switches Overview This section provides the requirements for network infrastructure required to support this solution. Table 19 provides a summary of the tasks to be completed and references for further information. Table 19. Tasks for switch and network configuration Task Description Reference Configure the infrastructure network Configure storage array and vsphere host infrastructure networking as specified in the solution document. Configure the VLANs Complete the network cabling Configure private and public VLANs as required. Connect switch interconnect ports. Connect VNXe ports. Connect vsphere server ports. Vendor s switch configuration guide Configure infrastructure network The infrastructure network requires redundant network links for each vsphere host, the storage array, the switch interconnect ports, and the switch uplink ports. This configuration provides both redundancy and additional network bandwidth. This configuration is required regardless of whether the network infrastructure for the solution already exists, or is being deployed alongside other components of the solution. 74

75 VSPEX Configuration Guidelines Figure 16 shows a sample redundant Ethernet infrastructure for this solution, and shows the use of redundant switches and links to ensure that no single points of failure exist in network connectivity. Figure 16. Sample Ethernet network architecture Configure VLANs Ensure there are adequate switch ports for the storage array and vsphere hosts that are configured with a minimum of three VLANs for: Virtual machine networking, vsphere management, and CIFS traffic (customer-facing networks, which may be separated if required) NFS networking (private network) vmotion (private network) 75

76 VSPEX Configuration Guidelines Complete network cabling Ensure that all solution servers, storage arrays, switch interconnects, and switch uplinks have redundant connections and are plugged into separate switching infrastructures. Ensure that there is complete connection to the existing customer network. Note At this point, the new equipment is being connected to the existing customer network. Ensure that unforeseen interactions do not cause service issues on the customer network. Prepare and configure storage array Overview This section describes how to configure the VNXe storage array. In this solution, the VNXe series provides NFS data storage for VMware hosts. Table 20 lists the tasks for the storage configuration. Table 20. Tasks for storage configuration Task Description Reference Set up the initial VNXe configuration Setup VNXe Networking Provision storage for NFS datastores Configure the IP address information and other key parameters on the VNXe. Configure LACP on the VNXe and network switches. Create NFS file systems presented to the vsphere servers as NFS datastores hosting the virtual desktops. EMC VNXe3300 System Installation Guide EMC VNXe Series Configuration Worksheet Vendor s switch configuration guide Provision optional storage for user data Provision optional storage for infrastructure virtual machines Create CIFS file systems that used to store roaming user profiles and home directories. Create optional NFS datastores to host the SQL Server, domain controller, vcenter Server, and View Manager virtual machines. Prepare VNXe Set up the initial VNXe configuration EMC VNXe3300 System Installation Guide provides instructions for assembly, racking, cabling, and powering the VNXe. There are no specific setup steps for this solution. After completing the initial VNXe setup, you need to configure key information about the existing environment so that the storage array can communicate. Configure the following items in accordance with your IT data center policies and existing infrastructure information: DNS NTP 76

77 Storage network interfaces Storage network IP address CIFS services and Active Directory Domain membership VSPEX Configuration Guidelines The reference documents listed in Table 20 provide more information on how to configure the VNXe platform. Storage configuration guidelines provide more information on the disk layout. Setup VNXe networking The VNXe supports Ethernet port aggregation so that users can bind Ethernet ports together as a single logical interface. The interfaces must be on the same IP subnet and connected to the same physical or logical switch. For NFS datastores used in this solution, LACP must be used to provide additional network cable redundancy rather than to increase overall throughput. The following steps show how to configure LACP on VNXe if more than one network interface is available. 1. In the VNXe Unisphere dashboard, select Settings. 2. Click More configuration. The More Configuration page appears. 3. Click Advanced Configuration. The Advanced Configuration page appears. 4. In the Advanced Configuration, select the port you want to aggregate. Note Ports can be aggregated only with eth2 from the base port list and only with eth10 from the list of I/O modules. 5. Select Aggregate with eth2 or eth10, and then click Apply changes. The changes are applied and the aggregation is complete. Note There may be additional configuration required on the network switch. These steps are available in the configuration materials from the switch vendor. Provision storage for NFS datastores Complete the following steps in Unisphere to configure NFS file systems on VNXe to store virtual desktops: 1. Create a pool with the appropriate number of disks. a. In Unisphere, navigate to System > Storage Pools, and then select Configure Disks. b. Create a new pool manually by disk type. When prompted to select a storage type, select SAS disk type and Balanced Perf/Capacity storage profile. Note The validated configuration uses a single pool with 21 drives. In other scenarios, creating separate pools may be advisable. Hot spare disks must be created at this point. For additional information, refer to the EMC VNXe3300 System Installation Guide. Figure 10 shows the target core storage layout for the solution. 2. Create an NFS shared folder server. 77

78 VSPEX Configuration Guidelines Access this wizard in Unisphere by navigating to Settings > Shared Folder Server Settings > Add Shared Folder Server. For detailed instructions, refer to the VNXe3300 System Installation Guide. 3. Create a VMware storage resource. a. In Unisphere, navigate to Storage > VMware > Create. b. Create two NFS datastores on the pool and shared folder server created above. The size of the datastore is determined by the number of virtual desktops it contains. The validated configuration used 1 TB datastores each. Note Thin Provisioning should not be enabled. 4. Finally, add the required vsphere hosts to the list of hosts allowed to access the new datastore. Provision optional storage for user data If the storage required is for user data (that is, roaming user profiles or View Persona Management repositories and user or home directories) does not exist in the production environment already and the optional user data disk pack has been purchased, complete the following steps in Unisphere to configure two CIFS file systems on VNXe: 1. Create a RAID 6 storage pool that consists of twelve 2 TB NL-SAS drives. Figure 11 shows the target optional user data storage layout. 2. Create two file systems from the storage pool and export them as CIFS shares on a CIFS server. Provision optional storage for infrastructure virtual machines If the storage required for infrastructure virtual machines (that is, SQL Server, domain controller, vcenter Server, vcenter Operations Manager for Horizon View, and VMware View Connection Servers) does not exist in the production environment and the optional user data disk pack is purchased, configure an NFS file system on VNXe. This will be used as the NFS datastore in which the infrastructure virtual machines reside. To provision the optional storage, repeat the configuration steps shown in Provision storage for NFS datastores, while taking into account the smaller number of drives. 78

79 VSPEX Configuration Guidelines Install and configure vsphere hosts Overview This section provides information about installation and configuration of vsphere hosts and infrastructure servers required to support the architecture. Table 21 describes the tasks to be completed. Table 21. Tasks for server installation Task Description Reference Install vsphere Install the vsphere hypervisor on the physical servers deployed for the solution. VMware vsphere Installation and Setup Guide Configure vsphere networking Connect VMware datastores Configure vsphere networking including NIC trunking, VMkernel ports, virtual machine port groups, and jumbo frames. Connect the VMware datastores to the vsphere hosts deployed for the solution. VMware vsphere Networking VMware vsphere Storage Guide Install vsphere Upon initial power up of the servers being used for vsphere, confirm or enable the hardware-assisted CPU virtualization and the hardware-assisted MMU virtualization setting in each server s BIOS. If the servers are equipped with a RAID controller, EMC recommends that you configure mirroring on the local disks. Start up the vsphere 5.1 installation media and install the hypervisor on each of the servers. vsphere hostnames, IP addresses, and a root password are required for installation. Appendix B provides appropriate values. Configure vsphere networking During the installation of vsphere, a standard virtual switch (vswitch) is created. By default, vsphere chooses only one physical NIC as a vswitch uplink. To maintain redundancy and bandwidth requirements, an additional NIC must be added either by using the vsphere console or by connecting to the vsphere host from the vsphere client. Each vsphere server should have multiple interface cards for each virtual network to ensure redundancy and provide for the use of network load balancing, link aggregation, and network adapter failover. vsphere networking configuration, including load balancing, link aggregation, and failover options is described in vsphere Networking. Choose the appropriate loadbalancing option based on what is supported by the network infrastructure. Create VMkernel ports as required, based on the infrastructure configuration: VMkernel port for NFS traffic VMkernel port for vmotion Virtual desktop port groups (used by the virtual desktops to communicate on the network) 79

80 VSPEX Configuration Guidelines vsphere Networking describes the procedure for configuring these settings. For more information, refer to the list of documents in the Preface of the document. Jumbo frames A jumbo frame is an Ethernet frame with a payload greater than 1,500 bytes and up to 9,000 bytes. This is also known as the Maximum Transmission Unit (MTU). The generally accepted maximum size for a jumbo frame is 9,000 bytes. Processing overhead is proportional to the number of frames. Therefore, enabling jumbo frames reduces processing overhead by reducing the number of frames to be sent. This increases the network throughput. Jumbo frames must be enabled end-to-end. This includes the network switches, vsphere servers, and VNXe storage processors. EMC recommends enabling jumbo frames on the networks and interfaces used for carrying NFS traffic. Jumbo frames can be enabled on the vsphere server into two different levels. If all the portals on the vswitch need to be enabled for jumbo frames, this can be achieved by selecting properties of vswitch and editing the MTU settings from the vcenter. If specific VMkernel ports are to be jumbo frames-enabled, edit the VMkernel port under network properties from vcenter. To enable jumbo frames on the VNXe in Unisphere, navigate to Settings > More Configuration > Advanced Configuration. Select the appropriate IO module and Ethernet port, and then set the MTU to 9,000. Jumbo frames may also need to be enabled on each network switch. Consult your switch configuration guide for instructions. Connect VMware datastores Connect the datastores configured in Prepare and configure storage array to the appropriate vsphere servers. These include the datastores configured for: Virtual desktop storage Infrastructure virtual machine storage (if required) SQL Server storage (if required) vsphere Storage Guide provides instructions on how to connect the VMware datastores to the vsphere host. For more information, refer to the list of documents in Appendix C of this document. The vsphere vstorage APIs for Array Integration (VAAI) plug-in for NFS must be installed after VMware Virtual Center has been deployed as described in VMware vcenter Server deployment. Plan virtual machine memory allocations Server capacity is required for two purposes in the solution: To support the new virtualized desktop infrastructure. Support the required infrastructure services such as authentication/authorization, DNS, and databases. For information on minimum infrastructure services hosting requirements, refer to Table 1. If existing infrastructure services meet the requirements, the hardware listed for infrastructure services is not required. 80

81 Memory configuration VSPEX Configuration Guidelines Proper sizing and configuration of the solution requires that you are careful when you configure the server memory. The following section provides general guidance on memory allocation for the virtual desktops and factors in vsphere overhead and the virtual machine configuration. We begin with an overview of how memory is managed in a VMware environment. ESX/ESXi memory management Memory virtualization techniques enable the vsphere hypervisor to abstract physical host resources such as memory in order to provide resource isolation across multiple virtual machines while avoiding resource exhaustion. In cases where advanced processors (for example, Intel processors with EPT support) are deployed, this abstraction takes place within the CPU. Otherwise, this process occurs within the hypervisor itself through a feature known as shadow page tables. vsphere uses the following memory management techniques: Allocation of memory resources greater than those physically available to the virtual machine is known as memory over-commitment. Identical memory pages that are shared across virtual machines are merged through a feature known as transparent page sharing. Duplicate pages are returned to the host-free memory pool for reuse. Memory compression - ESXi stores pages, which would otherwise be swapped out to disk through host swapping, is located in a compression cache in the main memory. Host resource exhaustion can be relieved through a process known as memory ballooning. This process requests free pages be allocated from the virtual machine to the host for reuse. Hypervisor swapping causes the host to force arbitrary virtual machine pages out to disk. For more information, refer to the VMware white paper Understanding Memory Resource Management in VMware vsphere

82 VSPEX Configuration Guidelines Virtual machine memory concepts Figure 17 shows the memory settings parameters in the virtual machine. Figure 17. Virtual machine memory settings Configured memory Physical memory allocated to the virtual machine at the time of creation. Reserved memory Memory that is guaranteed to the virtual machine. Touched memory Memory that is active or in use by the virtual machine. Swappable Memory that can be de-allocated from the virtual machine if the host is under memory pressure from other virtual machines through ballooning, compression or swapping. EMC recommends the following best practices: Do not disable the default memory reclamation techniques. These are lightweight processes that enable flexibility with minimal impact to workloads. Intelligently size memory allocation for virtual machines. Over-allocation wastes resources, while under-allocation causes performance impacts that can affect other virtual machines sharing resources. Over-committing can lead to resource exhaustion if the hypervisor cannot procure memory resources. In severe cases when hypervisor swapping is encountered, the virtual machine performance will likely be adversely affected. Having performance baselines of your virtual machine workloads assists in this process. For more information on esxtop, refer to the VMware community topic Interpreting esxtop Statistics. 82

83 VSPEX Configuration Guidelines Install and configure SQL Server database Overview This section and Table 22 describe how to set up and configure a SQL Server database for the solution. At the end of this section, you will have SQL Server on a virtual machine, with the databases required by vcenter, Update Manager, VMware Horizon View, and View Composer configured for use. Table 22. Tasks for SQL Server database setup Task Description Reference Create a virtual machine for Microsoft SQL Server Create a virtual machine to host SQL Server. Verify that the virtual machine meets the hardware and software requirements. Install Microsoft Windows on the virtual machine Install Microsoft SQL Server Configure database for VMware vcenter Configure database for VMware Update Manager Configure database for VMware View Composer Configure database for VMware View Manager Configure the VMware View and View Composer database permissions Configure VMware vcenter database Install Microsoft Windows Server 2008 R2 Standard Edition on the virtual machine created to host SQL Server. Install Microsoft SQL Server on the virtual machine designated for that purpose. Create the database required for the vcenter Server on the appropriate datastore. Create the database required for Update Manager on the appropriate datastore. Create the database required for View Composer on the appropriate datastore. Create the database required for VMware View Manager event logs on the appropriate datastore. Configure the database server with appropriate permissions for the VMware View and VMware View Composer databases. Configure the database server with appropriate permissions for the Preparing vcenter Server Databases Preparing the Update Manager Database VMware Horizon View 5.2 Installation VMware Horizon View 5.2 Installation VMware Horizon View 5.2 Installation Preparing vcenter Server Databases 83

84 VSPEX Configuration Guidelines Task Description Reference permissions VMware vcenter. Configure VMware Update Manager database permissions Configure the database server with appropriate permissions for the VMware Update Manager. Preparing the Update Manager Database Create a virtual machine for Microsoft SQL Server Install Microsoft Windows on the virtual machine Create the virtual machine with enough computing resources on one of the Windows servers designated for infrastructure virtual machines, and use the database designated for the shared infrastructure. Note The customer environment may already contain an SQL Server designated for this role. In that case, refer to Configure database for VMware vcenter. The SQL Server service must run on Microsoft Windows. Install Windows on the virtual machine by selecting the appropriate network, time, and authentication settings. Install SQL Server Install SQL Server on the virtual machine from the SQL Server installation media. One of the installable components in the SQL Server installer is the SQL Server Management Studio (SSMS). You can install this component on SQL Server directly as well as on an administrator s console. Install SSMS on at least one system. In many implementations, an option is to store data files in locations other than the default path. To change the default path, right-click on the server object in SSMS and select Database Properties. This action opens a properties interface from which you can change the default data and log directories for new databases created on the server. Note For high availability, SQL Server can be installed in a Microsoft Failover Clustering or on a virtual machine protected by vsphere HA clustering. It is not recommended to combine these technologies. Configure database for VMware vcenter To use VMware vcenter in this solution, create a database for the service to use. The requirements and steps to configure the vcenter Server database correctly are covered in Preparing vcenter Server Databases. For more information, refer to the list of documents in Appendix C of this document. Note Do not use the Microsoft SQL Server Express-based database option for this solution. It is a best practice to create individual login accounts for each service accessing a database on SQL Server. 84

85 VSPEX Configuration Guidelines Configure database for VMware Update Manager Configure database for VMware View Composer Configure database for VMware View Manager Configure the VMware View and View Composer database permissions To use Update Manager in this solution, create a database for the service to use. The requirements and steps to configure the Update Manager database correctly are covered in Preparing the Update Manager Database. For more information, refer to the list of documents in Appendix C of this document. It is a best practice to create individual login accounts for each service accessing a database on SQL Server. Consult your database administrator for your organization s policy. To use View Composer in this solution, create a database for the service to use. The requirements and steps to configure the Update Manager database correctly are covered in the VMware Horizon View 5.2 Installation documentation. For more information, refer to the list of documents in Appendix C of this document. It is a best practice to create individual login accounts for each service accessing a database on SQL Server. Consult your database administrator for your organization s policy. To retain View event logs create a database for the View Manager to use. The requirements and steps to configure the VMware View event database correctly are covered in the VMware Horizon View 5.2 Installation documentation. For more information, refer to the list of documents in Appendix C of this document. It is a best practice to create individual login accounts for each service accessing a database on SQL Server. Consult your database administrator for your organization s policy. At this point, your database administrator must create user accounts that are used for the View Manager and View Composer databases and provide them with the appropriate permissions. It is a best practice to create individual login accounts for each service accessing a database on SQL Server. Consult your database administrator for your organization s policy. The required permissions are available in the VMware Horizon View 5.2 Installation documentation. 85

86 VSPEX Configuration Guidelines VMware vcenter Server deployment Overview This section provides information on how to configure vcenter. Table 23 describes the tasks to be completed. Table 23. Tasks for vcenter configuration Task Description Reference Create the vcenter host virtual machine Create a virtual machine to be used for the VMware vcenter Server. VMware vsphere Virtual Machine Administration Install vcenter guest OS Update the virtual machine Create vcenter ODBC connections Install vcenter Server Install vcenter Update Manager Create a virtual data center Apply vsphere license keys Add vsphere hosts Configure vsphere clustering Perform array vsphere host discovery Install the vcenter Update Manager plugin Deploy the vstorage APIs for Array Integration Install Windows Server 2008 R2 Standard Edition on the vcenter host virtual machine. Install VMware Tools, enable hardware acceleration, and allow remote console access. Create the 64-bit vcenter and 32-bit vcenter Update Manager ODBC connections. Install vcenter Server software. Install vcenter Update Manager software. Create a virtual data center. Type the vsphere license keys in the vcenter licensing menu. Connect vcenter to vsphere hosts. Create a vsphere cluster and move the vsphere hosts into it. Perform vsphere host discovery within the Unisphere console. Install the vcenter Update Manager plug-in on the administration console. Using VMware Update Manager, deploy the VAAI plugin to all vsphere hosts. VMware vsphere Virtual Machine Administration vsphere Installation and Setup Installing and Administering VMware vsphere Update Manager VMware vsphere Installation and Setup Installing and Administering VMware vsphere Update Manager VMware vcenter Server and Host Management VMware vsphere Installation and Setup VMware vcenter Server and Host Management VMware vsphere Resource Management Using EMC VNX Storage with VMware vsphere TechBook Installing and Administering VMware vsphere Update Manager EMC VNX VAAI NFS plug-in installation how-to video VMware vsphere Storage APIs 86

87 VSPEX Configuration Guidelines Task Description Reference (VAAI) plug-in for Array Integration (VAAI) Plug-in Installing and Administering VMware vsphere Update Manager Install the EMC VSI plug-in Install the EMC Virtual Storage Integration plug-in on the administration console. EMC VSI for VMware vsphere: Unified Storage Management Product Guide. Create the vcenter host virtual machine If the vcenter Server is to be deployed as a virtual machine on a vsphere server installed as part of this solution, connect directly to an Infrastructure vsphere server using the vsphere client. Create a virtual machine on the vsphere server with the guest OS configuration, using the infrastructure server datastore presented from the storage array. The memory and processor requirements for the vcenter Server are dependent on the number of vsphere hosts and virtual machines being managed. The requirements are outlined in the vsphere Installation and Setup Guide. For more information, refer to the list of documents in Appendix C of this document. Install vcenter guest OS Install the guest OS on the vcenter host virtual machine. VMware recommends using Windows Server 2008 R2 Standard Edition. Refer to the vsphere Installation and Setup Guide to ensure that adequate space is available on the vcenter and vsphere Update Manager installation drive. For more information, refer to the list of documents in Appendix C of this document. Create vcenter ODBC connections Before installing the vcenter Server and vcenter Update Manager, create the ODBC connections required for database communication. These ODBC connections will use SQL Server authentication for database authentication. Appendix B provides SQL login information. For details about instructions on how to create the necessary ODBC connections, refer to the vsphere Installation and Setup and Installing and Administering VMware vsphere Update Manager. For more information, refer to the list of documents in Appendix C of this document. Install vcenter Server Install vcenter by using the VMware VIMSetup installation media. Use the customerprovided username, organization, and vcenter license key when installing vcenter. Apply vsphere license keys To perform license maintenance, log in to the vcenter Server and select the Administration - Licensing menu from the vsphere client. Use the vcenter license console to enter the license keys for the vsphere hosts. After this, they can be applied to the vsphere hosts as they are imported into vcenter. Deploy the vstorage APIs for Array Integration (VAAI) plug-in The VAAI plug-in enables support for the vsphere 5.1 NFS primitives. These primitives reduce the load on the hypervisor from specific storage-related tasks to free resources for other operations. Additional information about the VAAI for NFS plug-in 87

88 VSPEX Configuration Guidelines is available in the plug-in download vsphere Storage APIs for Array Integration (VAAI) Plug-in. For more information, refer to the list of documents in Appendix C of this document. The VAAI for NFS plug-in is installed using vsphere Update Manager. Refer to the process for distributing the plug-in as demonstrated in the EMC VNX VAAI NFS plug-in installation how-to video. To enable the plug-in after installation, restart the vsphere server. Install the EMC VSI plug-in The VNXe storage system can be integrated with VMware vcenter using EMC Virtual Storage Integrator (VSI) for VMware vsphere Unified Storage Management plug-in. Set up VMware View Connection Server Overview This section provides information on how to set up and configure View Connection Server for the solution. For a new installation of Horizon View, VMware recommends that you complete the tasks in the order shown in Table 24: Table 24. Tasks for VMware View Connection Server setup Task Description Reference Create virtual machines for VMware View Connection Server Create two virtual machines in vsphere client. These virtual machines are used as View Connection Servers. VMware Horizon View 5.2 Installation Install guest OS for VMware View Connection Server Install VMware View Connection Server Enter the View license key Configure the View event log database connection Add a replica View Connection Server Configure the View Composer ODBC connection Install View Composer Install Windows Server 2008 R2 guest OS. Install View Connection Server software on one of the previously prepared virtual machines. Enter the View license key in the View Manager web console. Configure the View event log database settings using the appropriate database information and login credentials. Install View Connection Server software on the second server. On either the vcenter Server or a dedicated Windows Server 2008 R2 server, configure an ODBC connection for the previously configured View Composer database. Install VMware View Composer on the server identified in the previous step. VMware Horizon View 5.2 Installation Connect VMware View to Use the View Manager web interfaces VMware Horizon 88

89 VSPEX Configuration Guidelines Task Description Reference vcenter and View Composer to connect View to the vcenter Server and View Composer. View 5.2 Administration Prepare a master virtual machine Configure View Persona Management Group Policies Configure View PCoIP Group Policies Create a master virtual machine as the base image for the virtual desktops. Configure AD Group Policies to enable View Persona Management. Configure AD Group Policies for PCoIP protocol settings. Install the VMware View Connection Server Install the View Connection Server software using the instructions from the VMware document, VMware Horizon View 5.2 Installation. Select Standard when prompted for the View Connection Server type. Configure the View event log database connection Configure the VMware View event log database connection using the database server name, database name, and database login credentials. For specific instructions on how to configure the event log, refer to the VMware Horizon View 5.2 Installation Guide. For more information, refer to the list of documents in Appendix C of this document. Add a second View Connection Server Repeat the View Connection Server installation process on the second target virtual machine. When prompted for the connection server type, specify Replica and then provide the VMware View administrator credentials to replicate the View configuration data from the first View Connection Server. Configure the View Composer ODBC connection On the server that will host the View Composer service, create an ODBC connection for the previously configured View Composer database. For specific instructions on how to configure the ODBC connection, refer to the VMware Horizon View 5.2 Installation Guide. For more information, refer to the list of documents in Appendix C of this document. Install View Composer On the server that will host the View Composer service, install the View Composer software. Specify the previously configured ODBC connection when prompted during the installation process. For specific instructions on how to configure the ODBC connection, refer to the VMware Horizon View 5.2 Installation Guide. For more information, refer to the list of documents in Appendix C of this document. Link VMware Horizon View to vcenter and View Composer Using the VMware View Manager web console, create the connection between Horizon View and both the vcenter Server and View Composer. For specific instructions on how to create the connections, refer to the VMware Horizon View 5.2 Administration Guide. For more information, refer to the list of documents in Appendix C of this document. When presented with the option, enable vsphere host caching (also known as View Storage Accelerator or Content Based Read Cache) and set the cache amount at 2 GB, the maximum amount supported. 89

90 VSPEX Configuration Guidelines Prepare master virtual machine Optimize the master virtual machine to avoid unnecessary background services generating extraneous I/O operations that adversely affect the overall performance of the storage array. Complete the following steps to prepare the master virtual machine: 1. Install Windows 7 guest OS. 2. Install appropriate integration tools such as VMware Tools. 3. Optimize the OS settings by referring to the following document: Deploying Microsoft Windows 7 Virtual Desktops with VMware View Applied Best Practices white paper. 4. Install the Avamar desktop or laptop client (refer to Set up Avamar for details). 5. Install the VMware View agent. Note If the View Persona Management feature is used, the Persona Management component of the VMware View agent should be installed at this time. Ensure that the Persona Management option is selected during the installation of the View agent. Configure View Persona Management group policies Configure folder redirection group policies for Avamar Configure View PCoIP group policies View Persona Management is enabled using AD Group Policies that are applied to the Organizational Unit (OU) containing the virtual desktop computer accounts. The View Group Policy templates are located in the \Program Files\VMware\VMware View\Server\extras\GroupPolicyFiles directory on the View Connection Server. Folder redirection is enabled using AD Group Policies that are applied to the OU containing the virtual desktop user accounts. AD folder redirection is used (instead of View Persona Management folder redirection) to ensure that the folders maintain the naming consistencies required by the Avamar software. Refer to Set up Avamar for details. View PCoIP protocol settings are controlled using Active Directory (AD) Group Policies that are applied to the OU containing the VMware View Connection Servers. The View Group Policy templates are located in the \Program Files\VMware\VMware View\Server\extras\GroupPolicyFiles directory on the View Connection Server. The group policy template pcoip.adm should be used to set the following PCoIP protocol settings: Maximum Initial Image Quality value: 70 Maximum Frame Rate value: 24 Turn off Build-to-Lossless feature: Enabled Higher PCoIP session frame rates and image qualities can adversely affect server resources. 90

91 VSPEX Configuration Guidelines Set up Avamar Avamar configuration overview This section provides information about installation and configuration of Avamar that is required to support in-guest backup of user files. There are other Avamar-based methods for backing up user files; however, this method provides end-user restore capabilities through a common GUI. For this configuration, it is assumed that only a user s files and profile are being backed up. Table 25 describes the tasks that must be completed. Note The backups produced by the procedure described here should be supplemented by regular backups of the data center infrastructure components required by Horizon View virtual desktops. A full disaster recovery requires the ability to restore the Horizon View infrastructure in combination with the ability to restore Horizon View virtual desktop user data and files. Table 25. Tasks for Avamar integration Task Description Reference Microsoft Active Directory preparation: Create Group Policy Object (GPO) modifications for Avamar Create GPO additions for Avamar Create and configure the GPO to enable VMware View Persona Management Create and configure the GPO to enable Avamar backups of user files and profiles. VMware Horizon View Persona Management Deployment Guide VMware Horizon View Master (Gold) image preparation: Install master image preparation for Avamar Install and configure the Avamar client to run in user mode. Avamar Client for Windows on VMware View Virtual Desktops EMC Avamar preparation Define datasets Define schedules Create and configure Avamar datasets to support user files and profiles. Create and configure an Avamar backup schedule to support virtual desktop backups. EMC Avamar 6.1 SP1 Administrator Guide EMC Avamar 6.1 SP1 Operational Best Practices Adjust Maintenance Window schedule Define retention policies Create group and group policy Modify the Maintenance Window schedule to support virtual desktop backups. Create and configure Avamar s retention policy. Create and configure Avamar s group and group policy. 91

92 VSPEX Configuration Guidelines Task Description Reference Post desktop deployment: Activate clients (desktops) Activate Horizon View virtual desktops using Avamar Enterprise Manager. EMC Avamar 6.1 SP1 Administrator Guide GPO modifications for Avamar This section assumes the CIFS share has been created, the VMware View Persona Management Active Directory administrative template has already been implemented, and the required GPO has been created and configured. You must review and modify two GPO configurations if not set properly to support Avamar client backups. To ensure Universal Naming Convention (UNC) path-naming conventions are maintained, configure the Persona Repository Location share path as \\cifs_server\folder\, as shown in Figure 18. Figure 18. Persona Management modifications for Avamar To ensure Universal Naming Convention (UNC) path naming conventions are maintained, do not use VMware View Persona Management portion of the GPO to configure Folder Redirection. This will be completed in the next section, GPO additions for Avamar. GPO additions for Avamar Due to current Avamar limitations and to reduce management burden, mapped drives must be used. Additionally, you need to configure Windows Folder Redirection to create the UNC paths needed for the mapped drives. The GPO created to support VMware View Persona Management can be used, or a new GPO can be created. 92

93 VSPEX Configuration Guidelines Folder redirection To configure Windows Folder redirection: 1. Edit the GPO by navigating to User Configuration > Policies > Windows Settings > Folder Redirection policy setting. 2. Right-click Documents. 3. Select Properties. 4. Select Basic Redirect everyone s folder to the same location from the settings dropdown list. 5. Type \\CIFS_server\folder in Root Path, as shown in Figure 19. Figure 19. Configuring Windows folder redirection Mapped drives Create two mapped drive configurations one for the user s files and one for the user s profile. Do the following procedure twice, changing three variables each time (Location, Label As, and Drive Letter Used) to create the two mapped drives. To configure drive mappings: 1. Edit the GPO and navigate to User Configuration > Preferences > Windows Settings > Drive Maps. 2. Right-click anywhere on the white area in the window. 3. Select New > Mapped Drive from the menu that appears, as shown in Figure

94 VSPEX Configuration Guidelines Figure 20. Create a Windows network drive mapping for user files The mapped drive Properties window appears as shown in Figure 21. To create the user s files mapped drive: 1. Select Create from the Action list box. 2. Type \\cifs_server\folder\%username% in Location. 3. Select Reconnect. 4. Type User_Files in the Label as. 5. Under Drive Letter, select Use, and then select U from the list box. 6. Under Hide/Show this drive, select Hide this drive. Figure 21. Configure drive mapping settings 94

95 VSPEX Configuration Guidelines 7. Click the Common tab at the top of the Properties window, and select Run in logged-on user s security context (user policy option), as shown in Figure 22. Figure 22. Configure drive mapping common settings Repeat the steps above to create the user s profile mapped drive using the following variables. Figure 23 shows a sample configuration: 1. Type \\cifs_server\folder\%username%.domain.v2 in the Location field, where domain is the Active Directory domain name. 2. Type User_Profile in the Label as field. 3. Under Drive Letter, select Use, and then select P. Figure 23. Create a Windows network drive mapping for user profile data 95

96 VSPEX Configuration Guidelines Close the Group Policy Editor to ensure that the changes are saved. Master image preparation for EMC Avamar This section provides information about using the Avamar client for Windows to provide backup and restore support for VMware Horizon View virtual desktops that store user-generated files in VNXe home directories. For details, refer to the Avamar Client for Windows on VMware View Virtual Desktops, and the remainder of this section for configurations specific to VMware View Persona Management. The Avamar client for Windows installs and runs as a Windows service named Backup Agent. Backup and restore capabilities are provided by this server service. Windows security limits the access of services logged on using the Local System account to local resources only. In its default configuration, Backup Agent logs on using the local system account and cannot access network resources including the VMware Horizon View user s profile or data file shares. To access VMware Horizon View user profile and data file shares, the Backup Agent must instead run as the currently logged in user. This is accomplished by using a batch file that starts Backup Agent and logs it on as a user when the user logs in. Details on how to prepare the master image and create the batch file mentioned above are described in Avamar Client for Windows on VMware View Virtual Desktops. Some minor modifications are required when using VMware View Persona Management. Avamar Client for Windows on VMware View Virtual Desktops contains the following note: The commands in this batch file assume that the drive letter of the user data disk for the redirected Avamar Client for Windows var directory is D. When a different drive letter is assigned, replace D in all instances of D:\ with the correct letter. Redirection of the var directory is described in Re-direct the Avamar Client for Windows var directory. Replace D with P according to the mapped drive configuration. Additionally, modify the vardir path value within the Avamar.cmd file located in C:\Program Files\avs\var to --vardir=p:\avs\var. Define datasets For the next several sections, assume the Avamar Grid is up and functional, and that you have logged into Avamar Administrator. For information on accessing Avamar Administrator, refer to the EMC Avamar 6.1 SP1 Administration Guide. Avamar datasets are a list of directories and files to backup from a client. Assigning a dataset to a client or group enables you to save backup selections. For additional information about datasets, refer to the EMC Avamar 6.1 SP1 Administration Guide. 96

97 VSPEX Configuration Guidelines This section provides VMware Horizon View virtual desktop specific dataset configuration information that is required to ensure successful backups of user files and user profiles. Create two datasets one for the user s files and the other for the user s profile. Repeat the following procedure twice, changing two variables each time (Name and Drive Letter Used). When you create the User Profile dataset, there are additional steps. 1. Click Tools within the Avamar Administrator window and select Manage Datasets, as shown in Figure 24. Figure 24. Avamar Tools menu The Manage All Datasets dialog box appears as shown in Figure Click New. Figure 25. Avamar Manage All Datasets window The New Dataset dialog box appears as shown in Figure 26, and the custom settings selected are shown in Figure

98 VSPEX Configuration Guidelines Figure 26. Avamar New Dataset window 3. Remove all other plug-ins from the list by selecting each and clicking the - button. 4. Type View-User-Files for the name of the new Dataset. 5. Select Enter Explicitly. 6. Select Windows File System from the Select Plug-in Type list box. 7. Type U:\ in the Select Files and/or Folders: field, and click the + button. Figure 27. Configure Avamar Dataset settings 8. Click OK to save the dataset. 98

99 VSPEX Configuration Guidelines Repeat the steps above to create a new dataset for user profile data; however, use the following values as shown in Figure 28: Type View-User-Profile for the name of the new Dataset. Type P:\ in the Select Files and/or Folders: field. Figure 28. User profile data dataset Additional configurations are required to back up User Profile data properly; a sample configuration is shown in Figure Click the Exclusions tab. 10. Select Windows File System from the Select Plug-in Type list box. 11. Type P:\avs in Select Files and/or Folders:, and click the + button. Figure 29. User profile data dataset Exclusion settings 99

100 VSPEX Configuration Guidelines 12. Click the Options tab as shown in Figure Select Windows File System from the Select Plug-in Type list box. 14. Select Show Advanced Options. Figure 30. User profile data dataset Options settings 15. Navigate to Volume Freezing Options as shown in Figure Select None from the Method to freeze volumes list box. 17. Click OK to save the dataset. Figure 31. User Profile data dataset Advanced Options settings 100

101 VSPEX Configuration Guidelines Define schedules Adjust maintenance window schedule Avamar schedules are reusable objects that control when group backups and custom notifications occur. Define a recurring schedule that satisfies your recovery point objectives (RPO). For additional information about datasets, refer to the EMC Avamar 6.1 SP1 Administration Guide. Avamar server maintenance comprises three essential activities: Checkpoint a snapshot of the Avamar server taken for the express purpose of facilitating server rollbacks. Checkpoint validation an internal operation that validates the integrity of a specific checkpoint. After a checkpoint passes validation, it can be considered reliable enough to be used for a server rollback. Garbage collection an internal operation that recovers storage space from deleted or expired backups. Each 24-hour day is divided into three operational windows, during which various system activities are performed: Backup Window reserved to perform normal scheduled backups. No maintenance activities are performed during the backup window. Blackout Window reserved to perform server maintenance activities, primarily garbage collection, that require unrestricted access to the server. No backup or administrative activities are allowed during the blackout window. However, you can perform restores. Maintenance Window reserved to perform routine server maintenance activities, primarily checkpoint creation and validation. Figure 32 shows the default Avamar backup, blackout and maintenance windows. Figure 32. Avamar default backup/maintenance windows schedule 101

102 VSPEX Configuration Guidelines User files and profile data should not be backed up during the day while the users are logged onto their virtual desktop. Adjust the backup window start time to prevent backups from occurring during that time. Figure 33 shows modified backup, blackout, and maintenance windows for backing up VMware Horizon View virtual desktops. Figure 33. Avamar modified backup/maintenance windows schedule To adjust the schedule to appear as shown above, change the Backup Window Start Time from 8:00 PM to 8:00 AM, and click OK to save the changes. For additional information about Avamar server maintenance activities, refer to the EMC Avamar 6.1 SP1 Administration Guide. Define retention policies Avamar backup retention policies enable you to specify how long to keep a backup in the system. A retention policy is assigned to each backup when the backup occurs. Specify a custom retention policy to perform an on-demand backup, or create a retention policy that is assigned automatically to a group of clients during a scheduled backup. When the retention for a backup expires, then the backup is automatically marked for deletion. The deletion occurs in batches during times of low system activity. For additional information on defining retention policies, refer to the EMC Avamar 6.1 SP1 Administration Guide. Group and group policy creation Avamar uses groups to implement various policies to automate backups and enforce consistent rules and system behavior across an entire segment, or group, of the user community. Group members are client machines that have been added to a particular group for the purpose of performing scheduled backups. 102

103 VSPEX Configuration Guidelines In addition to specifying which clients belong to a group, groups also specify: Datasets Schedules Retention Polices These three objects comprise the group policy. Group policy controls backup behavior for all members of the group unless you override these settings at the client level. For additional information about groups and group policies, refer to the EMC Avamar 6.1 SP1 Administration Guide. This section provides group configuration information that is required to ensure proper backups of user files and user profiles. Now create two groups and their respective group policy one for the user s files and one for the user s profile. Repeat the following procedure twice, changing two variables each time (Name, and Dataset Used). 1. Select Actions in the menu bar, and then New Group, as shown in Figure 34. Figure 34. Create new Avamar backup group The New Group dialog box appears, as shown in Figure Type View_User_Data in the Name field. Disabled should not be selected. 3. Click Next. 103

104 VSPEX Configuration Guidelines Figure 35. New backup group settings 4. Select VMware-View-User-Data from the Select An Existing Dataset list box, as shown in Figure Click Next. Figure 36. Select backup group dataset 6. Select a schedule from the Select An Existing Schedule list box as shown in Figure Click Next. 104

105 VSPEX Configuration Guidelines Figure 37. Select backup group schedule 8. Select a retention policy from the Select An Existing Retention Policy dropdown list as shown in Figure Click Finish. Note If you click Next, it takes you to the final New Group window where you can select the clients to be added to the group. You do not need to do this step, as clients are added to the group during activation. Figure 38. Select backup group retention policy 105

106 VSPEX Configuration Guidelines EMC Avamar Enterprise Manager activate clients Avamar Enterprise Manager is a web-based multi-system management console application that provides centralized Avamar system administration capabilities, including the ability to add and activate Avamar clients in mass. In this section, we will assume you know how to log into Avamar Enterprise Manager (EM), and that the VMware Horizon View desktops are created. After successfully authenticating into Avamar EM, the dashboard appears as shown in Figure Click Client Manager to continue. The Avamar Client Manager window appears. Figure 39. Avamar Enterprise Manager 2. Click Activate as shown in Figure 40 to continue. Figure 40. Avamar Client Manager 3. Next, click the inverted triangle symbol, as shown in Figure

107 VSPEX Configuration Guidelines Figure 41. Avamar activate client window 4. Select Directory Service from the menu, as shown in Figure 42. Figure 42. Avamar activate client menu A Directory Service window appears, requesting user credentials (this assumes an Active Directory service has been configured within Avamar. For additional information on enabling LDAP Management, refer to the EMC Avamar 6.1 SP1 Administration Guide). 5. Select a directory service domain from the User Domain list box as shown in Figure Enter credentials (User Name and Password) for directory service authentication. 7. Select a Directory Domain to query for client information, and click OK. 107

108 VSPEX Configuration Guidelines Figure 43. Avamar Directory Service configuration Assuming the credentials entered in the previous step authenticate properly, the intended Active Directory information appears on the left side of the Avamar Client Manager window, as shown in Figure 44. Figure 44. Avamar Client Manager post configuration 8. Navigate the Active Directory tree structure until the VMware Horizon View virtual desktops is found. In this example, an OU is created named VSPEX, as shown in Figure

109 VSPEX Configuration Guidelines Figure 45. Avamar Client Manager Virtual desktop clients 9. Highlight the virtual machine desktops you want to add to the Avamar server as shown in Figure 46 (noted by light-blue shading). Figure 46. Select virtual desktop clients in Avamar Client Manager 10. Click on the highlighted list and drag it over and on top of the Avamar Domain already created, and release the mouse button. The Select Groups window appears as shown in Figure Select (by clicking on the check box to the left) the Groups you wish to add these desktops to, and click the Add button. 109

110 VSPEX Configuration Guidelines Figure 47. Select Avamar groups to add virtual desktops The Avamar Client Manager window appears. 12. Click the Avamar Domain just added to the Horizon View desktops, and click Activate, as shown in Figure 48. Figure 48. Activate Avamar clients 13. The Show Clients for Activation dialog box appears. Click Commit, as shown in Figure

111 VSPEX Configuration Guidelines Figure 49. Commit Avamar client activation You will receive two informational prompts. The first prompt indicates the client activation is performed as a background process. 14. Click OK, as shown in Figure 50. Figure 50. The first information prompt in Avamar client activation The second prompt indicates the activation process has been initiated and to check the logs for status. 111

112 VSPEX Configuration Guidelines 15. Click OK, as shown in Figure 51. Figure 51. The second information prompt in Avamar client activation The Avamar Client Manager window appears, and immediately some clients have been activated, as shown in Figure 52 (as noted by the green checkmarks). Figure 52. Avamar Client Manager Activated clients 16. Log out of Avamar Enterprise Manager. 112

113 VSPEX Configuration Guidelines Set up VMware vshield Endpoint Overview This section provides information on how to set up and configure the VMware-specific components of vshield Endpoint. Table 26 describes the tasks to be completed. Table 26. Tasks required to install and configure vshield Endpoint Task Description Reference Verify desktop vshield Endpoint driver installation Verify that the vshield Endpoint driver component of VMware Tools are installed on the virtual desktop master image. Deploy vshield Manager appliance Register the vshield Manager plug-in. Apply vshield Endpoint licenses Install vsphere vshield Endpoint service Deploy an antivirus solution management server Deploy vsphere security virtual machines Verify vshield Endpoint functionality Deploy and configure the VMware vshield Manager appliance. Register the vshield Manager plug-in with the vsphere client. Apply the vshield Endpoint license keys using the vcenter license utility. Install the vshield Endpoint service on the desktop vsphere hosts. Deploy and configure an antivirus solution management server. Deploy and configure security virtual machines (SVMs) on each desktop vsphere host. Verify functionality of vshield Endpoint components using the virtual desktop master image. vshield Quick Start Guide vshield Quick Start Guide Note: The antivirus management server software and SVMs are provided by vshield Endpoint partners. Consult with the vendor documentation for specific details concerning installation and configuration. Consult with the vendor documentation for specific details on how to verify vshield Endpoint integration and functionality. 113

114 VSPEX Configuration Guidelines Verify desktop vshield Endpoint driver installation The vshield Endpoint driver is a subcomponent of the VMware Tools software package that is installed on the virtual desktop master image. The driver is installed using one of the following two methods: Select the Complete option during VMware Tools installation. Select the Custom option during VMware Tools installation. From the VMware Device Drivers list, select VMCI Driver, and then select vshield Driver. Note To install the vshield Endpoint driver on a virtual machine that already has VMware Tools installed, simply initiate the VMware Tools installation again and select the appropriate option. Deploy vshield Manager appliance The vshield Manager appliance is provided by VMware as an OVA file that is imported through the vshield client using the File Deploy OVF template menu option. The vshield Manager appliance is preconfigured with all required components. For more information, refer to the list of documents in Appendix C of this document. Install the vsphere vshield Endpoint service The vsphere vshield Endpoint service must be installed on all vsphere virtual desktop hosts. The service is installed on the vsphere hosts by the vshield Manager appliance. The vshield Manager web console is used to initiate the vshield Endpoint service installation and verify that the installation is successful. For more information, refer to the list of documents in Appendix C of this document. Deploy an antivirus solution management server Deploy vsphere Security Virtual Machines Verify vshield Endpoint functionality The antivirus solution management server is used to manage the antivirus solution and is provided by vshield Endpoint partners. The management server and associated components are a required component of the vshield Endpoint platform. The vsphere security virtual machines are provided by the vshield Endpoint partners and are installed on each vsphere virtual desktop host. The security virtual machines perform security-related operations for all virtual desktops that reside on their vsphere host. The security virtual machines and associated components are required components of the vshield Endpoint platform. After all required components of the vshield Endpoint platform have been installed and configured, the functionality of the platform should be verified prior to the deployment of virtual desktops. Using documentation provided by the vshield Endpoint partner, verify the functionality of the vshield Endpoint platform with the virtual desktop master image. 114

115 Set up VMware vcenter Operations Manager for Horizon View VSPEX Configuration Guidelines Overview This section provides information on how to set up and configure vcenter Operations Manager for Horizon View. Table 27 describes the tasks that must be completed. Table 27. Tasks required to install and configure vcenter Operations Manager Task Description Reference Create vsphere IP pool for vcenter Operations Manager Create an IP pool with two available IP addresses. Deploy vcenter Operations Manager vsphere Application Services Specify the vcenter Server to monitor Assign the vcenter Operations Manager license Configure SNMP and SMTP settings Update virtual desktop settings Create the virtual machine for the vcenter Operations Manager for View Adapter server Install guest OS for the vcenter Operations Manager for Horizon View Adapter server Install the vcenter Operations Manager for Horizon View Adapter software Deploy and configure the vcenter Operations Manager vsphere Application Services (vapp). From the vcenter Operations Manager main web interface, specify the name of the vcenter Server that manages the virtual desktops. Apply the vcenter Operations Manager for Horizon View license keys using the vcenter license utility. From the vcenter Operations Manager main web interface, configure any required SNMP or SMTP settings for monitoring purposes. Note: Optional. Update virtual desktop firewall policies and services to support vcenter Operations Manager for View desktop-specific metrics gathering. Create a virtual machine in the vsphere client. The virtual machine is used as the vcenter Operations Manager for Horizon View Adapter server. Install Windows Server 2008 R2 guest OS. Deploy and configure the vcenter Operations Manager for View Adapter software. Deployment and Configuration Guide vcenter Operations Manager 5 vcenter Operations Manager for View Integration Guide vcenter Operations Manager for View Integration Guide 115

116 VSPEX Configuration Guidelines Task Description Reference Import the vcenter Operations Manager for View PAK file Import the vcenter Operations Manager for View Adapter PAK file using the vcenter Operations Manager main web interface. Verify vcenter Operations Manager for View functionality Verify functionality of vcenter Operations Manager for View using the virtual desktop master image. Create vsphere IP pool for vcenter Operations Manager Deploy vcenter Operations Manager vapp vcenter Operations Manager requires two IP addresses for use by the vcenter Operations Manager analytics and user interface (UI) virtual machines. These IP addresses are assigned to the servers automatically during the deployment of the vcenter Operations Manager vapp. The vcenter Operations Manager vapp is provided by VMware as an OVA file that is imported through the vshield client using the File Deploy OVF template menu option. The vapp must be deployed on a vsphere cluster with DRS enabled. The specifications of the two virtual servers that comprise the vcenter Operations Manager vapp must be adjusted based on the number of virtual machines being monitored. For detailed information on the resource requirements of the vcenter Operations Manager virtual servers, refer to the Deployment and Configuration Guide vcenter Operations Manager 5. Specify the vcenter Server to monitor Access the vcenter Operations Manager web interface using the web address: where <IP> is the IP address or fully qualified host name of the vcenter Operations Manager vapp. Log in using the default credentials of user name admin and password admin. Complete the vcenter Operations Manager First Boot Wizard to complete the initial vcenter Operations Manager configuration and specify the appropriate vcenter Server to monitor. For detailed information about the information needed and steps required to complete the vcenter Operations Manager First Boot Wizard, refer to the Deployment and Configuration Guide vcenter Operations Manager 5. Update virtual desktop settings vcenter Operations Manager for Horizon View requires the ability to gather metric data directly from the virtual desktop. To enable this capability, the virtual desktop service and firewall settings must be adjusted either by using Windows group policies or by updating the configuration of the virtual desktop master image. The following virtual desktop changes should be made to support vcenter Operations Manager for Horizon View: Add the following programs to the Windows 7 firewall allow list: File and Printer Sharing Windows Management Instrumentation (WMI) 116

117 VSPEX Configuration Guidelines Enable the following Windows 7 services: Remote Registry Windows Management Instrumentation Create the virtual machine for the vcenter Operations Manager for Horizon View Adapter server Install the vcenter Operations Manager for Horizon View Adapter software Import the vcenter Operations Manager for Horizon View PAKFile Verify vcenter Operations Manager for Horizon View functionality The vcenter Operations Manager for Horizon View Adapter server is a Windows Server 2008 R2 system that gathers information from several sources related to Horizon View performance. The server is a required component of the vcenter Operations Manager for Horizon View platform. The specifications for the server vary based on the number of desktops being monitored. For detailed information about the resource requirements for the vcenter Operations Manager for Horizon View adapter server, refer to the vcenter Operations Manager for Horizon View Integration Guide. For more information, refer to the list of documents in Appendix C. Install the vcenter Operations Manager for Horizon View Adapter software on the server prepared in the previous step. For detailed information about the permissions needed by the Horizon View Adapter within the components that it monitors, refer to the vcenter Operations Manager for Horizon View Integration Guide. For more information, refer to the list of documents in Appendix C. The vcenter Operations Manager for Horizon View PAK file provides Horizon View specific dashboards for vcenter Operations Manager. The PAK file is located in the Program Files\VMware\vCenter Operations\View Adapter folder on the vcenter Operations Manager for Horizon View Adapter server, and is installed using the main vcenter Operations Manager web interface. For detailed instructions on how to install the PAK file and access the vcenter Operations Manager for View dashboards, refer to the vcenter Operations Manager for Horizon View Integration Guide. For more information, refer to the list of documents in Appendix C. On configuration of all required components of the vcenter Operations Manager for Horizon View platform, be sure to verify the functionality of the vcenter Operations Manager for Horizon View prior to deployment into production. For detailed instructions on how to navigate the vcenter Operations Manager for Horizon View dashboard and observe the operation of the Horizon View environment, refer to the vcenter Operations Manager for Horizon View Integration Guide. For more information, refer to the list of documents in Appendix C. Summary of VSPEX configuration guidelines In this chapter, we presented the requisite steps required to deploy and configure the various aspects of the VSPEX solution, which included both the physical and logical components. At this point, you should have a fully functional VSPEX solution. The following chapter describes post-installation and validation activities. 117

118 VSPEX Configuration Guidelines 118

119 Chapter 6 Validating the Solution This chapter presents the following topics: Overview Post-install checklist Deploy and test a single virtual desktop Verify the redundancy of the solution components Provision remaining virtual desktops

120 Validating the Solution Overview This chapter provides a list of items that should be reviewed after the solution is configured. The goal of this chapter is to verify the configuration and functionality of specific aspects of the solution, and ensure that the configuration supports core availability requirements. Table 28 describes the tasks to be completed. Table 28. Tasks for testing the installation Task Description Reference Post install checklist Verify that adequate virtual ports exist on each vsphere host virtual switch. Verify that each vsphere host has access to the required datastores and VLANs. VMware vsphere Networking VMware vsphere Storage Guide VMware vsphere Networking Deploy and test a single virtual machine Verify redundancy of the solution components Provision remaining virtual desktops Verify that the vmotion interfaces are configured correctly on all vsphere hosts. Deploy a single virtual machine using the vsphere interface by utilizing the customization specification. Restart each storage processor in turn, and ensure that LUN connectivity is maintained. Disable each of the redundant switches in turn and verify that the vsphere host, virtual machine, and storage array connectivity remains intact. On a vsphere host that contains at least one virtual machine, enable maintenance mode and verify that the virtual machine can successfully migrate to an alternate host. Provision desktops using View Composer linked clones. VMware vsphere Networking VMware vcenter Server and Host Management VMware vsphere Virtual Machine Management Verify the redundancy of the solution components provides the steps Vendor s documentation VMware vcenter Server and Host Management VMware Horizon View 5.2 Administration 120

121 Validating the Solution Post-install checklist The following configuration items are critical to functionality of the solution, and should be verified prior to deployment into production. On each vsphere server used as part of this solution, verify that: The vswitches hosting the client VLANs are configured with sufficient ports to accommodate the maximum number of virtual machines that vswitch may host. All required virtual machine port groups are configured and that each server has access to the required VMware datastores. An interface is configured correctly for vmotion using the material in the vsphere Networking guide. For more information, refer to the list of documents in Appendix C of this document. Deploy and test a single virtual desktop To verify the operation of the solution, it is important deploy a virtual desktop to verify the procedure completes as expected. Verify that the virtual desktop is joined to the applicable domain, has access to the expected networks, and that it is possible to log in. Verify the redundancy of the solution components To ensure that the various components of the solution maintain availability requirements, it is important to test specific scenarios related to maintenance or hardware failure. 1. Restart each VNXe storage processor in turn and verify that connectivity to VMware datastores is maintained during each operation. Complete the following steps: a. In Unisphere, navigate to Settings > Service System. b. In the System Components pane, select Storage Processor SPA. c. In the Service Actions pane, select Reboot. d. Click Execute service action. e. During the reboot cycle, check for presence of datastores on vsphere hosts. f. Wait until the SP finishes rebooting and shows as available within Unisphere. g. Repeat steps b to e for Storage Processor SPB. 2. To verify that network redundancy features function as expected, disable each of the redundant switching infrastructures in turn. While each of the switching infrastructures is disabled, verify that all the components of the solution maintain connectivity to each other and to any existing client infrastructure. 121

122 Validating the Solution 3. On a vsphere host that contains at least one virtual machine, enable maintenance mode and verify that the virtual machine can successfully migrate to an alternate host. Provision remaining virtual desktops Complete the following steps to deploy the virtual desktops using View Composer in the VMware Horizon View console: 1. Create an automated desktop pool. 2. Specify the preferred User Assignment: a. Dedicated: Users receive the same desktop every time they log in to the pool. b. Floating: Users receive desktops picked randomly from the pool each time they log in. 3. Specify View Composer linked clones. 4. Specify a value for the Pool ID. 5. Configure Pool Settings as required. 6. Configure Provisioning Settings as required. 7. Accept the default values for View Composer Disks or edit as required. If View Persona Management is used, select Do not redirect Windows profile in the Persistent Disk section. Configure the Active Directory Group Policy for VMware View Persona Management. Figure 53. View Composer Disks page 8. Select Select separate datastores for replica and OS disk. 9. Select the appropriate parent virtual machine, virtual machine snapshot, folder, vsphere hosts or clusters, vsphere resource pool, linked clone, and replica disk datastores. 122