Technical data

Solution Architectural Overview
VMware Horizon View 5.3 and VMware vSphere for up to 2,000 Virtual
Desktops Enabled by Brocade Network Fabrics, EMC VNX, and EMC Next-
Generation Backup
100
Implementing the reference architectures
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.
The 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 Avamar backup solution for VSPEX, do not schedule all
backups at once; instead, stagger them across your backup window.
Scheduling all resources to back up at the same time could cause the
consumption of all available host CPU.
In any running system, monitor the utilization of resources and adapt as
needed. The reference virtual desktop and required hardware resources in
the solutions assume that there will be no more than eight virtual CPUs for
each physical processor core (8:1 ratio). In most cases, this provides an
appropriate level of resources for the hosted virtual desktops; however, this
ratio may not be appropriate in all use cases. EMC recommends
monitoring the CPU utilization at the hypervisor layer to determine if more
resources are required.
Each virtual desktop in the solution is defined to have 2 GB of memory. In a
virtual environment, because of budget constraints, it is common to
provision virtual desktops with more memory than the hypervisor physically
has. The memory over-commitment technique takes advantage of the
fact that each virtual desktop does not fully utilize the amount of memory
allocated to it. It makes business sense to oversubscribe the memory usage
Overview
Resource types
CPU resources
Memory
resources