Descargar para leer sin conexión
Más contenido relacionado
Similar a Wserver2012r2 techday madridv3
Wserver2012r2 techday madridv3
- 2. Samuel Miguel López Hernández Datos ponente MVP-Virtual MVPTwitter Facebook Windows Machine Correo Expert IT-Pro @samuelltr @hyperher samuellt@samuellt.com mhernandez@zerkana.com http://blogs.itpro.es/samuellt http://blogs.itpro.es/mhernandez
- 3. • • • • • Novedades en Wserver2012 Escalabilidad Hyper-V Networking Storage
- 6. June 2008 October 2008 October2009 Storage Spaces Live Migration Metering & QoS Cluster Shared Volumes Mejoras en live migration Dynamic Processor Compatibility Memory Network Virtualization Hot-Add Storage RemoteFX Hyper-V Replica Mejoras en redimiento y Mejoras notables en los February 2011 September 2012 Escalabilidad sistemas guest soportados y escalabilidad
- 7. Número Máximo System Recurso Factor deMejora Windows 2008 R2 W. Server 2012 R2 64 320 5× Memoria Física 1 TB 4 TB 4× Procesadores virtuales por Host 512 2,048 4× Procesadores Virtuales por VM 4 64 16× 64 GB 1 TB 16× Capacidad del virtual disk 2 TB 64 TB 32x Máquinas virtuales activas 384 1,024 2.7× Nodos 16 64 4× 1,000 8,000 8× Procesadores lógicos en hardware Host Maquina Virtual Cluster Memoria por VM Maquinas Virtuales
- 8. • Las vmsde generación 2 soportan windows 8 (x64) , windows8.1 (x64) Server 2012 y server 2012 R2 como S.O guest
- 9. • Soporta todaslas funcionalidades de remote desktop – Clipboard compartido – Redirección de Audio – Mejoras en el login (2 factores de autentiación) • Mejoras en el redimiento de las conexiones a las vms por RDP • Totalmente integrado en Hyper-V Management Console
- 10. Soporte VHDX Gestion • • • Discos de hasta64TB Redimensionamiento Online Aprovisionamiento dinámico • • • Se despliega como role en el server manager 544 sesiones por destino 256 unidades logicas por servidor
- 11. • Compresión – livemigration el doble de rápidas – No requiere cambios en el hardware – Hablitada por defecto • SMB Direct – Soporta SMB Multichannel y hace uso de multiple interfaces – Requiere tarjetas de red de 10 Gbps con soporte RMDA
- 14. Compatilibidad total entrenodos corriendo Hyper-V 2012 y nodos corriendo Hyper-V 2012 R2 • Live Migrations • Estados guardados • Snapshots • Migración sin parada de servicio
- 15. Solo el hardwarey tu marcas los limites
- 16. Soporte VHDX Gestion • • • Discos de hasta64TB Redimensionamiento Online Aprovisionamiento dinámico • • • Se despliega como role en el server manager 544 sesiones por destino 256 unidades logicas por servidor
- 17. • Ahora esposible tanto aumentar como disminuir el tamaño de los discos duros virtuales vhdx incluso con la máquina virtual encendida
- 18. • • • • Soporta Dynamic memory Onlinebackup Redimensionamiento online VHDX Nuevo y optimizado controlador de video
- 19. • Nos permiteconfigurar IOPs máximos o minimos de una vm • Configuración dinámica con la vm encendida • Permite garatinzar el SLA de almacenamiento en el que se alojan las vms Windows Server 2008 R2 Windows Server 2012 250,000 IOPs 1,000,000+ IOPs
- 20. Soporte VHDX Gestion • • • Discos de hasta64TB Redimensionamiento Online Aprovisionamiento dinámico • • • Se despliega como role en el server manager 544 sesiones por destino 256 unidades logicas por servidor
- 21. Nuevas funcionalidades enWSERVER 2012 R2
- 22. Soporte VHDX Gestion • • • Discos de hasta64TB Redimensionamiento Online Aprovisionamiento dinámico • • • Se despliega como role en el server manager 544 sesiones por destino 256 unidades logicas por servidor
- 23. Networking Hyper-V Network Virtualization andmultitenant site-to-site VPN gateway inbox NIC teaming with increased load-balancing performance QoS management
- 24. S2S Tunnel S2S Tunnel Blue GW S2STunnel Orange Corp site1 Orange Corp site2 Green GW S2S Tunnel S2S Tunnel Orange GW Orange Virtual Network
- 25. BGP Provides multitenantS2S gateway Includes guest clustering for HA Uses BGP for dynamic routes update Provides multitenant-aware NAT for Internet access Active-Standby S2S Tunnel Orange Corp site1 Orange Virtual Network Orange Corp site2
- 26. • Automatic DHCPfailover based on DHCP failover IETF spec • Provides multi-site IP address continuity to clients by helping eliminate single points of failure • Provides in-box support for failover, without the need for clustering • Uses a failover setup consisting of two servers located across different geographic locations • Includes active/active or active/passive behavior • Simple provisioning and configuration of DHCP server using PowerShell
- 27. • Automatic detectionand use of multiple network connections between SMB client and server SMB client • Helps server applications be resilient to network failure • Transparent Failover with recovery of network failure if another connection is unavailable SMB server NIC NIC File copy File copy • Improved throughput • Bandwidth aggregation through NIC Teaming • Multiple nodes/CPUs for network processing with RSS-capable network adapters NIC NIC • Automatic configuration with very little administrative overhead 27
- 28. Soporte VHDX Gestion • • • Discos de hasta64TB Redimensionamiento Online Aprovisionamiento dinámico • • • Se despliega como role en el server manager 544 sesiones por destino 256 unidades logicas por servidor
- 29. Nuevas funcionalidades enWSERVER 2012 R2 • • • • • • • • • Almacenamiento en Capas Deduplicación mejorada (VDI) Agrupaciones Flexibles 3 Niveles de Mirror Cache Persistente Snapshot Colocación de ficheros calientes en SSD Redimensionamiento vhdx en caliente Iscsi 544 sesiones (lun) por servidor Hot Data Cold Data
- 31. Soporte VHDX Gestion • • • Discos de hasta64TB Redimensionamiento Online Aprovisionamiento dinámico • • • Se despliega como role en el server manager 544 sesiones por destino 256 unidades logicas por servidor
Notas del editor
- #2 Samuel
- #9 SamuelSe haneliminado los componentes LegacyBasadas en UEFI Se haneliminado la mayoría de los dispositivosemuladosBoots desde SCSI Virtual o adaptador de red sinteticoHabilita UEFI secure boot como standardSistemasoperativos guest soportados:Windows 8 y Windows Server 2012 (Versiones de 64-bit)Windows 8.1 y Windows Server 2012 R2 (Versiones de 64-bit)
- #24 In a hybrid cloud world, customers are looking at their datacenters as datacenters without boundaries – i.e., datacenters that can grow beyond one physical geographic location either into other datacenters they own, datacenters that are part of a service provider cloud or the public cloud with Windows Azure. To enable hybrid clouds for them, they need networking infrastructure that scales to growing demand and changes and that can support workload mobility cross datacenters. IT demands: Simplified use of network resources in a multitenant, cross-premises environmentTo enable multi-tenant IT services and/or hybrid clouds, there is a need to simplify the network complexity involved in migrating virtual machines – from changing IP addresses, modifying applications, changing network ACLs etc.WS12R2 delivers: Software-defined network infrastructureSoftware-defined networking enhances the management of modern networks by providing the ability for applications to control access to network resources dynamically. A key enabler of SDN is that it uses networking functionality that has been moved to the virtual switch, providing the ability to modify packets in transit and enabling integration of more advanced switch extensions. Finally, SDN also brings the benefit of unifying the management of both the physical and virtual infrastructure. Among other things, new features and updates in Windows Server 2012 R2 include:- Hyper-V Network Virtualization:With Hyper‑V Network Virtualization in Windows Server 2012 R2, you can isolate network traffic from different business units or customers on a shared infrastructure and not be required to use VLANs. Hyper‑V Network Virtualization also lets you move virtual machines as needed within your virtual infrastructure while preserving their virtual network assignments. Finally, you can even use Hyper‑V Network Virtualization to transparently integrate these private networks into a preexisting infrastructure on another site.Hyper‑V Network Virtualization extends the concept of server virtualization to allow multiple virtual networks, potentially with overlapping IP addresses, to be deployed on the same physical network. With Hyper‑V Network Virtualization, you can set policies that isolate traffic in your dedicated virtual network independently of the physical infrastructure. On the same physical network, with Hyper-V Network Virtualization, you can run multiple virtual network infrastructures and you can have overlapping IP addresses with each virtual network infrastructure acting as if it was the only one running on the shared physical network infrastructure.- Hyper-V Extensible SwitchMulti-tenant site-to-site VPN gateway:In Windows Server 2012, we introduced a feature called cross-premises connectivity, with provides VPN site-to-site functionality (within the remote access role) to help establish cross-premises connectivity between enterprises and hosting service providers. Cross-premises connectivity enables enterprises to connect to private subnets in a hosted cloud network. It also enables connectivity between geographically separate enterprise locations. However, some of the limitations of this feature were that you needed one gateway per tenant (two for HA), you could only do host-level clustering, there were limited routing capabilities and a lack of Internet NAT.Consider the situation where a hoster needs to be able to connect customers to their own resources provisioned within the hoster's cloud environment. In Windows Server 2012, the hoster would have to provide a separate server to server (S2S) virtual private networking (VPN) virtual machine for each customer or implement a third-party multi-tenant VPN gateway. Now with Windows Server 2012 R2, you no longer require a separate third-party multi-tenant VPN gateway, as this feature is now built in to the operating system. This function can provide a seamless connection over a S2S VPN link between multiple external organizations and the resources that those organizations own in a hosted cloud. It also enables connectivity between physical and virtual networks, enterprise data centers, and hosting organizations, and between enterprise networks and Windows Azure. High availability is provided through guest clustering using a hot standby node available. A dynamic link library ensures any routing configuration is synced from the active node to the hot standby, and when the standby becomes active, the routing configuration is applied. To ensure that routes are updated dynamically, Windows Server 2012 R2 implements Border Gateway Protocol and incorporates multitenant-aware Network Address Translation (NAT) for Internet access.- Standards-based switch configuration:Today’s datacenters are made up of different classes of devices – e.g. load balancers, power distribution units, baseboard management controllers (BMCs), top-of-rack (TOR) switches, routers, etc. - from a variety of device manufacturers. With the explosion of datacenters the need to automate management of such devices in a consistent way is more important than ever. Since most of these devices are managed via different protocols and schemas, and in some instances, proprietary solutions, customers are asking for a consistent developer abstraction layer for interacting with the wide array of devices & vendors, similar to the Hardware Abstraction Layer that Windows provides to application developers.One of the core innovations of Windows Server 2012 was Standards Based Management. As part of this effort, a significant amount of work was done in the management stack of Windows Server 2012 to make WMI + WSMan + PowerShell work with devices that implement DMTF's CIM standards. As a continuation of this effort, Windows Server 2012 R2 includes a device management abstraction layer – referred to as the datacenter abstraction layer (DAL) - that further reduces the complexity of heterogeneous device management., with the goal that devices can be easily managed and configured using standards technologies and based on the same DAL architecture. Windows Server 2012 R2 will allow customers to 1) enable device management using a common abstraction layer, working over standard protocol and schema; 2) move from a complex datacenter device world into a world of well-defined, standard based components; and 3) build ready to use solution for device management right in Windows.IT demands: Continuously available and resilient network infrastructure:IT needs to help ensure that services are running continuously without any interruption. This means that there is automatic recovery from both software and hardware failures, with the need for an IT Pro or network administrator to fix issues in the middle of night now eliminated. Imagine multiple services sharing common infrastructure and having the ability to get a consistent bandwidth for each of these services and finally provide a common infrastructure that supports a heterogeneous/multi vendor environment.WS12R2 delivers: High-performance networking:Customers want to get the best performance out of the hardware they have – whether they are industry standard hardware or high end hardware that they have already invested in. Poor network performance are primarily because of two reasons – limitations in network bandwidth, limitations in the processing power -, and these typically affect availability and resiliency of the network infrastructure directly. A considerable amount of work has been done in Windows Server 2012 R2 to extract great and predictable performance inbox, as well as to make the most out of next generation hardware.Among other things, new features and updates in Windows Server 2012 R2 include:SMB Direct (RDMA)Single Root I/O Virtualization:Single Root I/O Virtualization (SR-IOV) is a standard introduced by the PCI-SIG, the special-interest group that owns and manages PCI specifications as open industry standards. SR-IOV works in conjunction with system chipset support for virtualization technologies that provide remapping of interrupts and Direct Memory Access, and allows SR-IOV-capable devices to be assigned directly to a virtual machine. Introduced with Windows Server 2012, Hyper-V enables support for SR‑IOV-capable network devices and allows an SR‑IOV virtual function of a physical network adapter to be assigned directly to a virtual machine. This increases network throughput and reduces network latency while also reducing the host CPU overhead required for processing network traffic. You can configure your systems to maximize the use of host system processors and memory to effectively handle the most demanding workloads.These Hyper-V features let enterprises take full advantage of the largest available host systems to deploy mission-critical, tier-1 business applications with large, demanding workloads. And unlike with competitive implementations of SR-IOV, key features such as live migration, high availability and fault tolerance are still supported.Virtual Receive-Side ScalingNIC Teaming:see separate slideIT demands: Greater control and more extensibility:Better manageability and controlis one of the most important challenges customers face. This spans from the ability to automate regular tasks to having the control over the entire IP address infrastructure, no matter what the size of your organization is, to having the ability to get the best performance on a multi-site environment, and finally to providing enterprises and hosting providers with a way to track resource usage and build chargeback/show-back solutions.WS12R2 delivers: Improved manageability and diagnostics:Windows Server 2012 R2 builds on the networkingadvances in Windows Server 2012 with an array of new and enhanced features that help reduce networking complexity while lowering costs and simplifying management tasks. With Windows Server 2012 R2, IT administrators have tools to automate and consolidate networking processes and resources. Among other things, new features and updates in Windows Server 2012 R2 include:Resource metering:Hyper-V in Windows Server 2012 R2 helps providers build a multitenant environment in which virtual machines can be served to multiple clients in a more isolated and secure way.Because a single client may have many virtual machines, aggregation of resource use data can be a challenging task. However, Windows Server 2012 R2 simplifies this task by using resource pools, a feature available in Hyper-V. Resource pools are logical containers that collect the resources of the virtual machines that belong to one client, permitting single-point querying of the client’s overall resource use.Resource Metering in Windows Server 2012 R2 can measure the following:The average CPU, in megahertz, used by a virtual machine over a period of time.The average physical memory, in megabytes, used by a virtual machine over a period of time.The lowest amount of physical memory, in megabytes, assigned to a virtual machine over a period of time.The highest amount of physical memory, in megabytes, assigned to a virtual machine over a period of time. The highest amount of disk space capacity, in megabytes, allocated to a virtual machine over a period of time.The total incoming network traffic, in megabytes, for a virtual network adapter over a period of time. The total outgoing network traffic, in megabytes, for a virtual network adapter over a period of time.Virtual IP Address Management:See separate slideQoS management:Since Windows Server 2012, you canmanage QoS policies and settings dynamically with Windows PowerShell. The QoScmdlets support both the QoS functionalities available in Windows Server 2008 R2—such as maximum bandwidth and priority tagging—and new features that became available in Windows Server 2012, such as minimum bandwidth. QoS minimum bandwidth benefits vary from public cloud hosting providers to enterprises. Most hosting providers and enterprises today use a dedicated network adapter and a dedicated network for a specific type of workload such as storage or live migration to help achieve network performance isolation on a server running Hyper‑V. For service providers, QoS management allows them to host customers on a server running Hyper‑V and still be able to provide a certain level of performance based on SLAs. It also helps them to ensure that customers won’t be affected or compromised by other customers on their shared infrastructure, which includes computing, storage, and network resources. For enterprises, QoS management allows them to run multiple application servers on a server running Hyper‑V and be confident that each application server will deliver predictable performance, eliminating the fear of virtualization due to lack of performance predictability.DNS traffic management:There has been increasing demand for a feature where the customer can control the resolution of certain DNS records based on the client information. With the advent of global markets and hosted server farms serving to different part of the world, providing geo-politically apt answers to DNS queries is required for better Quality of Service to end users. For the enterprise customers who want to deploy split-horizon DNS to separate the internal and external queries, maintaining two different versions of the server is a management headache. A solution to this problem is to allow customers to maintain the records at the same place while deciding resolution policies based on the incoming query. In Windows Server 2012 R2, DNS traffic management enhances the existing DNS Server Plugin to Custom Policy Plugin and uses ZoneScopes to provide DNSSEC support (including online signing and automation of key creation and rollover) for DNS data served by a Customer Logic.
- #27 Dynamic Host Configuration Protocol (DHCP) Server Failover allows two DHCP servers to synchronize lease information almost instantaneously and to provide high availability of DHCP service. If one of the servers becomes unavailable, the other server assumes responsibility for servicing clients for the same subnet. Now you can also configure failover with load balancing, with client requests distributed between the two DHCP servers. DHCP Server Failover in Windows Server 2012 R2 Previewprovides support for two DHCPv4 servers.Administrators can deploy Windows Server 2012 R2 PreviewDHCP servers as failover partners in either hot standby mode or load-sharing mode.Hot standby modeIn this mode, two servers operate in a failover relationship in which an active server leases IP addresses and configuration information to all clients in a scope or subnet. (Note that the two DHCP servers in a failover relationship do not themselves need to be on the same subnet. DHCP service can be provided to the subnet by DHCP Relay.) The secondary server assumes this responsibility if the primary server becomes unavailable. A server is primary or secondary in the context of a subnet, so a server that is primary for one subnet could be secondary for another.The hot standby mode of operation is best suited to deployments in which a central office or data center server acts as a standby backup server to a server at a remote site that is local to the DHCP clients. In this hub-and-spoke deployment, it is undesirable to have a remote standby server service clients unless the local DHCP server becomes unavailable.Load-sharing modeIn load-sharing mode, which is the default mode, the two servers simultaneously serve IP addresses and options to clients on a particular subnet. (Again, the two DHCP servers in a failover relationship do not themselves need to be on the same subnet.) The client requests are load balanced and shared between the two servers. This mode is best suited to deployments in which both servers in a failover relationship are located at the same physical site. Both servers respond to DHCP client requests based on the load distribution ratio configured by the administrator.
- #28 Note to presenter: 3 clicks to complete build.With SMB MultiChannel, network path failures are automatically and transparently handled without application service disruption. Windows Server 2012 R2 Preview now scans, isolates, and responds to unexpected server problems that allow network fault tolerance, if multiple paths are available between the SMB client and the SMB server. SMB Multichannel also provides aggregation of network bandwidth from multiple network interfaces when multiple paths exist. Server applications can then take full advantage of all available network bandwidth and become resilient to a network failure. In the animation, you see data getting transferred from an SMB client and server. Notice the red ball. Now lets assume that there is a failure in the path in which the red ball/packet was travelling. Without any manual intervention now, the red ball packet was sent again through a different route. So as you can see with SMB multichannel, server workloads are now resilient to underlying network changes/failures.
- #32 Initially we have a bunch of standard disks [CLICK]This block based storage is exposed to Windows Server through [CLICK] Storage Spaces. Storage Spaces groups these disks into pools and presents each Storage Space as a standard drive in Windows. This gives you benefits in performance, flexibility, scalability, and availability.Scale-Out File Server [CLICK] is an Active-Active server cluster that can benefit from the performance and availability of Storage Spaces. Scale-Out File Server itself will provide the reliability, availability, performance and manageability of a SAN for application data.The Scale-Out File Server cluster is ideal for storage of application data including [CLICK] virtual machines. Hyper-V will communicate with the Scale-Out File Server using the [CLICK] SMB protocol using its transparent failover functionality.This solution provides very high levels of availability, performance, scalability, and manageability, and is built without the need for specialist hardware.