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 2012. 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 2012 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 Adapter Adapter

Windows Server 2012 Hyper-V Component Architecture

Network
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 2012. 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 2012 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 2012, 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-IOVcapable 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-IOVcapable 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 machinesbypassing 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 2012, 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 enoughyou 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 isolatedeven 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 serverthese 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 flexiblythis resources, support for Offloaded Data BitLocker Drive Encryption. You can permitted to replicate virtual machines to your Replica
Maximum Number of Recovery Snapshots
Test Failover to a Replica Server
(SR-IOVcapable )
Physical
customized tools using Window
PowerShell for managing a virtual switch.
server.
environments. includes migrating outside a clustered Transfer, and improved Quality of also use Hyper-V Replica, which Replication Storage 1 15
You also have the ability to test a Replica virtual machine on the Replica
server. The test failover operation does not interrupt ongoing replication.
Network
Adapter Unified Tracing and Enhanced Diagnostics

environment and fully automating Service (QoS) to enforce minimum replicates virtual machines to an offsite Hyper-V Replica allows you to designate a specific location to store This will create and start a virtual machine with the name <virtual
machine name> - Test. Server Running Hyper-V
Unified Tracing helps identify and resolve
network connectivity issues. It provides a
management tasks, which reduces the bandwidth requirements (including location and provides failover to that your recovery virtual machine filesfor example, on a SAN, on an
SMB file server, or using direct-attached storage. Unplanned Failover to a Replica Server
clean and simple interface to diagnose
networking issues without the need for a
site if a failure at the primary site
VSS Snapshot Replication Interval
network storage requirements). Replication Firewall Rules
Server Running
Hyper-V debugger.
administrative overhead in your occurs. To allow any incoming virtual machine replication traffic for 1 Hour 12 Hours In the event of a failure in the primary site, you can bring up the Replica
virtual machine on the Replica server. You can choose the most recent
External Physical Switch
SR-IOV requires support from the network adapter, firmware, system chipset, and driver.
environment. configured replication ports, you must ensure an inbound firewall
rule is created.
replication or an earlier recovery point. Legend: Microsoft Partner Networking Hyper-V Hardware

Hyper-V Virtual Machine Mobility Hyper-V Storage Hyper-V and Failover Clustering Hyper-V Scalability
Live Migration Without Shared Storage Storage Migration Virtual Fibre Channel for Virtual Machines Clustered Virtual Machines for High Availability Physical Hardware and Virtual Machine Scalability
Live migration without shared storage (also known as Shared Nothing Live Migration) Hyper-V storage migration enables you to move virtual machine storage (virtual hard disks) Hyper-V virtual Fibre Channel for virtual machines enables virtual machines to access Fibre Channelbased storage. This feature allows you to virtualize workloads that require Fibre Channel storageand Virtual Machine Live Migrations Failover Cluster Validation Hyper-V in Windows Server 2012 provides enhanced enterprise hosting capabilities, with
enables you to migrate virtual machines and their associated storage between servers running without downtime. This enables new servicing scenarios. For example, you can add more also allows you to cluster guest operating systems in virtual machines using Fibre Channel. MPIO Connectivity to Fibre Channel Storage Virtual expanded support for both physical and virtual processors, and physical and virtual memory.
Hyper-V within the same domain. This kind of live migration uses only an Ethernet connection. physical disk storage to a non-clustered computer or a Hyper-V cluster and then move the Failover Clustering supports concurrent live migrations of Virtual Windows Server 2012 provides an It also makes it easier to virtualize high-performance workloads by supporting the
Virtual Fibre Channel Adapters Virtual Fibre Live Migration Support Hyper-V in Windows Server 2012 can use Multipath I/O virtual machines. The cluster initiates as many live migrations Machine improved wizard to help you validate
Validate
virtual machines to the new storage while the virtual machines continue to run. WWN Channel HBAs Machine networking configuration of large, high-performance virtual machines.
Virtual Hard Disks (VHDs) Virtual machine file and data WWN Hyper-V in Windows Server 2012 supports live (MPIO) functionality to ensure continuous connectivity to as possible at the same time, and then queues the remaining hardware and software for use in a
Configuration Files This live migration solution does not storage can be located in one Virtual Hard Disks (VHDs)
Virtual machine configuration files Virtual Fibre Channel adapters provide port migration of virtual machines across Fibre Channel storage from within a virtual machine. live migrations. failover cluster on a server running Virtual Machine Scalability
Snapshots provide high availabilitythere is no or multiple locations. Configuration Files
and data storage can be located in virtualization by exposing host bus adapter Hyper-V. Virtual Machines Hyper-V supports virtual machines with up to 64 virtual
Hyper-V Smart Paging File Requirements one or multiple locations. computers running Hyper-V while maintaining MPIO on the Virtual Machine Live
shared storage. Snapshots (HBA) ports in the guest operating system. Fibre Channel connectivity (live migration with Using the Failover Cluster Manager, you can Validate
Virtual processors and up to 1 TB of memory, and supports 1024
Hyper-V migrations Validation tests indicate whether hardware Memory
This provides the virtual machine with direct failover clusters). To accomplish this, each You can configure multiple virtual Fibre Channel monitor the detailed status of on going or Processors running virtual machines.

Support for More Processors and Memory

Storage: Block or file-based storage can be cluster nodes are compatible for
1 and unfiltered access to a storage area virtual fibre channel adapter is configured with adapters inside a virtual machine, and use a separate queued live migrations. Hyper-V operations, including Failover Cluster Scalability
queued. 64 1 TB
1

network (SAN) using a standard World Wide copy of Multipath I/O (MPIO) within the guest
0 1

two World Wide Names (WWNs). The Failover Clustering feature supports up to 8,000 virtual
1 0

support for the failover of virtual

1 1 0
0 1
Validate
1

operating system of the virtual machine to connect to

0 1
Name (WWN) that is associated with the
0

Virtual
1
machines (or other clustered roles) and 64 nodes in a single
1 0 00

machines from one host to another.

1
Hyper-V automatically changes between Set A
1
storage
0 1 0 1
0

virtual machine. the LUNs that the virtual machine can access.
00 1 0
1
0 1
00 (NPIV Ports) Machines and Set B WWN addresses during a live failover cluster.
Cluster Node C Multiple Concurrent Live Cluster Node D
Up to four virtual Fibre Channel adapters can migration. Hyper-V ensures that all logical unit Switch
Requirements: numbers (LUNs) are available on the SAN Server Running Hyper-V Migrations of Virtual Machines Server Running Hyper-V
Hyper-V Original Storage Move storage Destination Storage be assigned to each virtual machine. Physical HBA
(NPIV-capable) destination computer and then performs the Use custom
live migration. No downtime occurs during the Failover Cluster Manager Setting Virtual Machine Priorities
Storage Migration Operations Virtual machine read and write operations go to migration views to Startup Priorities Available
Source Computer Destination Computer 1 the VHD on the source device. Switch manage With Failover Cluster Manager, you can manage In Windows Server 2012, you can for Virtual Machines
Running Hyper-V Running Hyper-V Server Running Hyper-V N_Port ID Virtualization (NPIV) Support Server Running high-performance, large-scale clustered virtual control the way a cluster handles virtual Physical Hardware
The VHD is copied from the source VHD storage WWN Set A (Active) WWN Set B (Active)
Using live migration without shared storage, your virtual machine continues to run while all of Virtual 2 Virtual Fibre Channel for virtual machines Hyper-V machines. machines by assigning a priority. Logical Memory Multiple Nodes...
device to the destination VHD storage device.
its storage is mirrored across to the destination server running Hyper-V. After the Hyper-V Machine utilizes N_Port ID Virtualization (NPIV) WWN Set B WWN Set A New functionality enables you to: Priorities can be set as High, Medium, Processors
storage is synchronized on both sides, the live migration completes its remaining tasks. Finally, After the storage is copied, all write operations (Passive) (Passive) MPIO on the Server Running Hyper-V
3 technology. Fibre Channel Low, or No Auto Start. When a virtual High 320 4 TB
the mirror is broken and the source Hyper-V storage is deleted. VHD Stack are mirrored to the source and destination You can also install multiple Fibre Channel ports on the Search, filter, and create custom views
1 3 storage devices. An NPIV port is created on the server Switch Select machine is made highly available, the 2 64 Nodes
(NPIV-capable server running Hyper-V, and can use Multipath I/O to manage clustered virtual machines default priority is set to Medium.
If a failure or a problem occurs during live migration without shared storage, a working running Hyper-V and is associated with the multiple
2 After the source and destination storage are (MPIO) to provide highly available connectivity to the or other clustered roles.
virtual machine is always retained. 4 synchronized, access to the virtual machine VHD virtual Fibre Channel adapter. The World SAN Switch)
LUNs that are accessible by the server. virtual
Priorities control the order in
Live migration without shared storage can migrate virtual machines between clusters, and is transferred to the VHD on the destination Wide Name (WWN) assigned to the NPIV machines Select multiple virtual machines, and which virtual machines are Medium
from a non-clustered computer to a cluster. 5 4 device. port allows all I/O to be redirected to a Device-Specific Modules then perform any needed operation started and ensure that
Hardware Scalability
High
5 The VHD from the source device is deleted. specific virtual Fibre Channel adapter in a across themincluding live migration, lower-priority virtual Hyper-V supports up to 320 logical processors and 4 TB of
Live migration without shared storage can migrate virtual machines between different virtual machine. You can also use different Device-Specific Modules save, shutdown, or start. Medium memory in a server running Hyper-V.
storage types. Source Destination (DSMs) for the server running Hyper-V or each virtual machines automatically
You can perform storage migration when the virtual machine is running or when it is SAN Computer Computer machine (not shown in the diagram). View and configure clustered virtual release resources if they are Low Support for More Virtual Machines and Cluster Nodes
You can also initiate live migration without shared storage using Windows PowerShell. Low
turned off. Storage migration moves the storage, not the virtual machine state. needed for higher priority
machine settings, such as live migration No
virtual machines. Auto-Start
queuing.
Live Migration with SMB Shared Storage Live Migration with Failover Clusters New Virtual Hard Disk Format Hyper-V Using Server Message Block (SMB) When the No Auto Start NUMA and Virtual Machines
Quickly perform live migrations. priority is applied to a NUMA (Non-Uniform Memory Access) is a multiprocessor architecture that groups memory and
Live migration with Server Message Block (SMB) shared storage enables you to move virtual Hyper-V live migration with failover clusters (first introduced in Windows Server 2008 R2) VHD is a virtual hard disk file format that enables you to represent a physical hard disk Hyper-V can store virtual machine files (configuration files, virtual hard disk files, and snapshots) on file servers virtual machine, it will not
machines between servers running Hyper-V within the same domain while the virtual machine enables you to move running virtual machines from one cluster node running Hyper-V to drive in a file, and it is used as the hard disk of a virtual machine. Hyper-V in Windows using Server Message Block (SMB) 2.2. This is supported for both non-clustered and clustered servers running processors into compute nodes. The time required for a processor to access memory within a
automatically start in the node is faster than the time required to access memory across nodes. Hyper-V supports
storage remains on the SMB-based file server. Concurrent live migrations are supported. This another node, without any disruption or perceived loss of service. Live migration is initiated by Server 2012 contains an update to the virtual hard disk format called VHDX. Hyper-V where file storage is used as shared storage for the failover cluster. event of a cluster node
kind of live migration does not require configuration of a failover cluster. the administrator and is a planned operation. projecting a virtual NUMA topology within a virtual machine, which enables virtual machines
VHDX Requirements: Server Running Hyper-V failure. with multiprocessors to scale better.
In Windows Server 2012, you can select multiple virtual machines within the failover VHDX Format File Server Cluster Node A
Requirements: Windows Server 2012
cluster and perform multiple simultaneous live migrations of those virtual machines. Windows 8 Management Operating Virtual Server Running Hyper-V Cluster Node B The guest operating system and applications can take advantage of any NUMA performance
Hyper-V, SMB shared storage Supports up to 64 TB of storage capacity. System Machine optimizations. By default, the virtual NUMA topology within a virtual machine is optimized to
You can also select and queue live migrations of multiple virtual machines. Live migration Cluster Shared Volumes Server Running Hyper-V
SMB VHD Application match the NUMA topology in the server running Hyper-V .
Virtual
queuing is only supported within a failover cluster. Logs updates to the VHDX metadata structures. SMB Server Using the Cluster Shared Volumes (CSV) feature, multiple clustered Cluster-Aware Updating Virtual Virtual Virtual Virtual
Virtual This provides added resiliency to the VHDX file Client Stack virtual machines can use the same disk and still be able to live migrate
Machine Machine Cluster-Aware Updating (CAU) enables you to NUMA Node A NUMA Node B NUMA Node A NUMA Node B
Requirements: in the case of power outages. NTFS from node to node independently of one another.
SCSI/IDE automatically update a failover cluster while Server
Shared storage: Serial-Attached SCSI (SAS), Internet Supports larger block sizes for dynamic and Network Windows Server 2012 provides the following enhancements to CSV maintaining a high level of service availability. Updates
Virtual Virtual
Virtual hard disks are stored on SMB shared storage. SCSI (iSCSI), Server Message Block (SMB), Fibre Channel NTFS (RDMA Network architecture and functionality: Machines Machines
differencing disks, which allows the disks to be (RDMA Storage Storage
tuned to the needs of virtualized workloads. Option) VSP VSC
A new NTFS-compatible file system, known as the Cluster Shared CAU takes a cluster node offline, installs
Virtual Virtual Option) any required updates, performs a restart if
Machine Machine Increases performance for applications and Volume File System (CSVFS). Volumes appear as "CSVFS" so that Failover Cluster
applications can discover that they are running on a CSV. necessary, brings the cluster node back
workloads, especially on physical disks that online, and moves on to service the next
have a larger sector size than 512 bytes. Virtual Machine Bus Support for SMB 2.2 file-based storage for Hyper-V. cluster node.
Source Computer Destination Computer (VMBus) Guest NUMA nodes are matched with
Virtual Hard
.VHDX File Supports storing custom metadata. For CAU arranges cluster updating resources on the server running Hyper-V.
Running Hyper-V Running Hyper-V
Disks example, you might want to record your Enhanced backup and restore of CSVs. operations using a computer running
operating system version or any patches you Network Windows Server 2012. This computer NUMA Node 1 NUMA Node 2 NUMA Node 3 NUMA Node 4
File-based Server Storage (SMB) Adapter Network
have applied. Adapter Multiple-subnet configuration. is referred to as an Update
For this live migration, the virtual hard disk (VHD) resides on an SMB 2.2based file server. SMB 2.2 allows you to use your file storage resources across virtualization environments. Storing Hyper-V Coordinatorand is not a cluster
The actual running state of the virtual machine is migrated from one server to another. It Source Computer Destination Computer You can also configure and manage virtual node. The orchestrator scans and
hard disks on a computer running Hyper-V data on inexpensive, easy-to-manage file servers provides the benefits that you would expect from a Security and Encryption
is important to note that the connection to the SMB storage is migrated, but the virtual Running Hyper-V Running Hyper-V storage area network (SAN)continuous availability, high performance, and manageability. downloads updates for cluster nodes. Update Coordinator
hard disk never moves. using Windows PowerShell commands. Failover Clustering supports BitLocker Drive Encryption for both
Shared Storage You can also improve performance using network adapters with remote direct memory access (RDMA) traditional clustered disks and CSVs. Decryption is performed by Cluster Shared Volume CAU is integrated into the existing Windows Update management
You can also initiate live migration with SMB shared storage using Windows PowerShell capability. They can function at full speed with very low latency and low CPU usage. For Hyper-V
(see the move-vm cmdlet). VHDX Architecture each cluster node using the cluster name object (CNO). infrastructure. You can extend and automate it with Windows PowerShell.
You can initiate live migration with failover clusters using Windows PowerShell. workloads, this allows a remote file server to have performance that compares to local storage. Server Running Hyper-V
2012 Microsoft Corporation. Microsoft, Hyper-V, Windows, Windows PowerShell, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All rights reserved. Other trademarks or trade names mentioned herein are the property of their respective owners.
The information contained in this document relates to a pre-release product which may be substantially modified before it is commercially released. Microsoft makes no warranties, express or implied with respect to the information presented here. Author: Martin McClean (Server and Cloud Division Information Experience) email: virtua@microsoft.com