Excelente documento para que podamos planificar la instalación de Lync Server 2013 en un entorno de virtualización
 Document |
This paper provides guidance for deploying Lync Server 2013 on virtual servers. It includes recommendations for the configuration of host servers and guest servers, key health indicators to watch during testing and deployment, and observations from Microsoft performance testing of Lync Server 2013 in a…
|
FREE
Release Date:
2/18/2014
|
Os dejo el punto 2 con algunas cosas que debemos tener muy presente:
Designing and operating an enterprise-grade Lync Server infrastructure requires involvement from several teams. Adding virtualization provides a new dimension of complexity and reliance on another team for support.
Virtualization also introduces a new layer of configuration and optimization techniques for each guest that must be determined and tested for Lync Server. Many virtualization techniques that can lead to consolidation and optimization for other applications cannot be used with Lync Server. Shared resource techniques, including processor oversubscription, memory overcommitment, and I/O virtualization, cannot be used because of their negative impact on Lync scale and call quality.
Virtual machine portability—the capability to move a virtual machine guest server from one physical host to another—breaks the inherent availability functionality in Lync Server pools. Moving a guest server while operating is not supported in Lync Server 2013. Lync Server 2013 has a rich set of application-specific failover techniques, including data replication within a pool and between pools. Virtual machine-based failover techniques break these application-specific failover capabilities.
The testing we completed revealed some specific configuration items that we recommend when you run Lync Server on a virtualization platform:
Processor
· You should disable hyperthreading on all hosts.
· Do not use processor oversubscription; maintain a 1:1 ratio of virtual CPU to physical CPU.
· Make sure your host servers support nested page tables (NPT) and extended page tables (EPT).
· Disable non-uniform memory access (NUMA) spanning on the hypervisor, as this can reduce guest performance.
Memory
· Do not configure dynamic memory or memory overcommitment on host servers.
Network
· Use Virtual Machine Queue (VMQ) to optimize synthetic NIC performance.
· Use physical NIC segregation for host versus guest communications.
· Single-root I/O virtualization (SR-IOV) is recommended. The specific configuration you should use depends on the host chipset and network adapter/driver.
Storage
· Use fixed or pass-through disks rather than dynamic disks.
Hypervisor
· Virtual machine portability or failover techniques such as live migration are not supported.
Ahora toca leerlo enterito y verlo con detalle
Espero que os sea de utilidad como lo será para mi!!!
Leave a Reply