Windows Server “8” Beta Hyper-V Component Architecture Poster

1,123 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,123
On SlideShare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Windows Server “8” Beta Hyper-V Component Architecture Poster

  1. 1. Hyper-V Hyper-V Replica Hyper-V Networking Virtual Machine Replication Load Balancing and Failover Quality of Service Bandwidth Management Hyper-V Replica is an asynchronous virtual machine replication technology that is included in Windows Server “8” Beta. It is designed for business continuity and disaster recovery. It works with any server, Network adapter teaming, also known as NIC teaming or load balancing and failover (LBFO), enables Windows Server “8” Beta includes new Quality of Service (QoS) bandwidth management network, or storage vendor. It does not require any shared storage. It enables you to replicate individual or multiple virtual machines. Hyper-V Replica is tightly integrated with Hyper-V and Failover multiple network adapters to be placed into a team interface. This provides bandwidth aggregation and functionality that allows you to converge multiple types of network traffic through a Clustering. You can replicate virtual machines from one computer running Hyper-V at a primary site (the primary server) to another computer running Hyper-V at a Replica site (the Replica server). The traffic failover, which prevents loss of connectivity in the event of a network adapter failure. Network single network adapter with a predicable level of service to each type. You can configure Replica server accepts incoming replication traffic from one or more primary servers. bandwidth management features through the virtual machine settings or by using adapter teaming supports multivendor implementations. Windows PowerShell commands. Supports teamed Configurations for Network Adapter Teaming To architect bandwidth management, you can specify a maximum and minimum virtual adapters Operating System Switch-independent mode does not require the bandwidth limit. These limits allow you to manage bandwidth allocations depending on Initial Replication Mode physical switch to participate in teaming. The your type of network traffic. Before virtual machine replication can start, an initial copy of all virtual hard disks (VHDs) Virtual Virtual Primary Server must be transferred to the Replica server. Hyper-V Replica supports three methods of Replica Server Team Interface switch is not aware that network adapters are part It is important to note that Management Machine #1 Machine #2 Running Hyper-V initial replication. Running Hyper-V of a team on the server, so the network adapters the new minimum Operating System Network Network (Primary Site) (Replica Site) can be connected to different switches if required. bandwidth feature allows Use network replication: each network service (such Network Traffic Network Adapter Adapter Windows Server “8” Beta Hyper-V Component Architecture You can transfer selected VHDs over the network to the Replica server, either Replica Server Requirements Switch-dependent modes require a physical switch as management, storage, live Type A Adapter immediately or at a specified time. Hardware that is certified for Windows to participate in teaming. Typically, all the migration, and virtual Virtual Hard Disks Server “8” Beta. interfaces of the team are connected to the same machine traffic) to get an Network Traffic Use a backup copy on the Replica server: allocated share of bandwidth Network Hyper-V Virtual Selected for You can transfer a backup copy of your production virtual machine to your Replica Sufficient storage to host the files used Virtual switch. Type B Adapter Replication by virtualized workloads. Machine when the network Switch server. bandwidth is heavily utilized Sufficient network bandwidth between Teamed Virtual Network Adapters Network Traffic Multiple Physical and contended. When Network Use external media: the locations hosting the primary and Network Adapters Hyper-V supports network adapter teaming within bandwidth is freely available, Type C Adapter Team Interface You can copy selected VHDs to external media and deliver the external media to the Replica servers and sites. a virtual machine. To provide redundancy, virtual Replica site. each of these network Secure multitenancy Flexible infrastructure Scalability, performance, High availability machines should have multiple virtual network services gets as much adapters, each connected to a different external bandwidth as required. After Initial Replication virtual switch. The virtual machine will have There are two mechanisms to enforce minimum bandwidth. and density After completing the initial replication, Hyper-V Replica sends virtual machine connectivity even if a physical network adapter fails. You can use QoS software in your server running Hyper-V, or Windows-certified network adapters that support Data Physical Network Adapters Center Bridging (DCB). changes on a frequent schedule. Virtual Machine Windows Server “8” Beta supports up to 32 Virtual Machines These changes are tracked in a log file, which is compressed before it is sent Copies Server Running Hyper-V network adapters within a team. Hyper-V Virtual Switch to the Replica server. On the primary In Windows Server “8” Beta, the Hyper-V virtual switch is extensible. This allows new server, changes are maintained in an capabilities to be added to the virtual switch so that you can view and manage the traffic 01001001 01010101 .hrl file that is in the same location as .hrl Files 01001001 Single Root I/O Virtualization on your server running Hyper-V. This includes traffic generated between virtual machines running on the same computer. 01001001 the VHDs that are being replicated. Primary Server (Compressed) Replica Server 01010101 01010101 SR-IOV is a standard that allows PCI Express devices to be shared among multiple virtual machines by 01001001 01010101 01001001 01010101 providing them a direct hardware path for I/O. Hyper-V provides support for SR-IOV–capable network Using the extensible capabilities in a virtual switch, Microsoft partners can add their own 01001001 01001001 monitoring, filtering, and forwarding functionality. Any extensions that are created are 01001001 01010101 01010101 01001001 01010101 adapters. SR-IOV reduces network latency, reduces CPU utilization for processing network traffic, and implemented using Network Driver Interface Specification (NDIS) filter drivers or Windows 01001001 01010101 01001001 Data transferred across the You can schedule initial 01001001 increases network throughput. 01010101 Filtering Platform (WFP) callout drivers. 01001001 01010101 01010101 01001001 network can be compressed. Initial Virtual replication to occur 01010101 01010101 01001001 Machine Copy immediately or at a later time. 01001001 01010101 SR-IOV–capable networking devices have hardware surfaces called virtual functions that can be securely You can use NDIS filter drivers to monitor or modify network packets in Windows. You can assigned to virtual machines—bypassing the virtual switch in the management operating system for 01001001 Replica Server Storage use WFP to create firewall or intrusion detection functionality. 01010101 01001001 01010101 01001001 01010101 01001001 01010101 01010101 Create initial copy of virtual machine 01001001 sending and receiving data. Policy and control remains under the management operating system. 01001001 01001001 01010101 Application- Management Operating System 01010101 01010101 consistent snapshots SR-IOV is fully compatible with live migration because software-based networking is available at all times. Virtual Machine Data is replicated over LAN/WAN to a remote site. No additional replication technologies are required. (Volume Shadow During live migration, virtual functions are temporarily removed. This enables live migration using network Windows Management Copy Service (VSS)) adapters from different vendors, or in a situation where SR-IOV is not available on the destination Provider Application computer. Replica virtual Replicate virtual machine changes Virtual Machine #1 Virtual Machine #2 You can configure and manage machines Management Virtual Machine Log File Updates Virtual Machine Replica servers using Hyper-V (Write Changes) Virtual machine Operating System Virtual Network TCP/IP Virtual Network TCP/IP Management Worker Process Network Protocols Manager or Windows PowerShell. snapshots Adapter Adapter Service (VMWP) Virtual Virtual (VMMS) Function Function Hyper-V In Windows Server® “8” Beta, Hyper-V® Flexible infrastructure, when and where Hyper-V provides support for up to 32 Just being able to scale and perform is Hyper-V Replica Server Configuration Recovery History Hyper-V Replica Failover Operations Virtual Switch Virtual Network Adapter provides new security and multitenant you need it, is key to easily managing processors and 1 terabyte (TB) of not enough—you need to ensure that Configuring a Replica Server Hyper-V Replica frequently replicates changes to Using Hyper-V Replica, you can fail over to a protected virtual machine on Virtual Switch VMBus isolation capabilities to keep virtual and accessing your virtualized network. memory for guest operating systems. It your virtual machines are available To enable replication, you must configure your Hyper-V Replica your virtual machine, which ensures that your Replica virtual machine is a close match to your the Replica server at any time. There are three main options. Planned Failover to a Replica Server Virtual Function machines isolated—even when they are also offers a new virtual hard disk when they are needed. Hyper-V server to be a Replica server. This server can accept primary virtual machine. Capture or Filter Extension stored on the same physical server. You With Hyper-V, you can scale beyond format with larger disk capacity that provides a wide variety of high incoming replication traffic from the virtual machines on your primary (or multiple primary) servers. Hyper-V Replica can maintain multiple recovery A planned failover operation enables you to fail over your production virtual machine to a Replica server as part of a predetermined schedule. Virtual Function points on the server—these are used to restore a Windows can expand this with a fully extensible virtual local area networks (VLANs) supports up to 64 TB per virtual disk, availability options. These include Replica Server Authentication virtual machine. The recovery points contain one Planned failover means no data will be lost. It should be planned for off- business hours. Physical Function Windows Filtering Platform Filter Extension Callout Filtering Platform You can set specific authentication types and ports for or more snapshots. Recovery points are created Two prerequisites are required to perform virtual switch, which enables Microsoft using network virtualization and can and provides additional resiliency to simple incremental backup support, incoming replication traffic. Options include: every hour. a planned failover: partners to develop plug-ins for place a virtual machine on any node, enable you to virtualize large-scale enhancements in clustered Kerberos authentication (HTTP) - data sent across the network will not be encrypted. If multiple recovery points are not configured, the server maintains only the latest point-in-time The virtual machine must be shut down before initiating failover. Forwarding Extension Virtual Switch Management enhanced networking and security regardless of its IP address. You can workloads. Other new functionalities environments to support up to 4000 Certificate-based authentication (HTTPS) - data sent recovery point for the Replica virtual machine. The server running Hyper-V at the Windows PowerShell Support capabilities. These functionalities provide include resource metering to measure virtual machines, parallel live across the network will be encrypted. You can also choose to take application-consistent primary site must be enabled to receive replication traffic. A planned failover Windows PowerShell cmdlets are available for creating, configuring, and a solution that addresses the complex migrate your virtual machines and and track consumption of physical migrations, and encryption with Replica Server Authorization snapshots at a specified interval. They use the Volume Shadow Copy Service (VSS). Primary Server Replica Server also initiates reverse replication. Physical Network Adapter monitoring a Hyper-V virtual switch. Microsoft partners can now build Hyper-V Replica allows you to specify which servers are security requirements of virtual virtual machine storage flexibly—this resources, support for Offloaded Data BitLocker® Drive Encryption. You can permitted to replicate virtual machines to your Replica VSS Snapshot Replication Interval Test Failover to a Replica Server (SR-IOV–capable ) Physical customized tools using Window PowerShell for managing a virtual switch.

×