e-guide microsoft hyper-v: improving...

MMiiccrroossoofftt HHyyppeerr--VV::IImmpprroovviinngg AAvvaaiillaabbiilliittyy,,MMaannaaggeemmeenntt aannddPPeerrffoorrmmaanncceeDespite the obvious advantages associated with MicrosoftHyper-V, this virtualization platform does not come withoutits availability and resiliency challenges. In this expert E-Guide, brought to you by SearchWindowsServer.com, Delland Microsoft, you will gain insight into the improvementsmade to Hyper-V by Windows Server 2008 R2. Discover thedistinct advantages of Windows Server 2008 R2, includingLive Migration, reduced costs and improved Hyper-V management. Explore why Hyper-V R2 should be consideredin your platform decision process and learn how your organization can effectively implement Live Migration.

Sponsored By:

E-Guide

TechTarget Data Center Media

www.dell.com

www.dell.com

Microsoft Hyper-V: Improving Availability, Management and Performance

Table of Contents

Sponsored by: of 14

Table of Contents:

Hyper-V gains new resiliency features with Windows Server 2008 R2

Live Migration in Hyper-V R2

An overview of Windows Server 2008 R2 and Hyper-V R2

New features in Microsoft's SCVMM R2 improve Hyper-V management

Resources from Dell, Inc.

MMiiccrroossoofftt HHyyppeerr--VV::IImmpprroovviinngg AAvvaaiillaabbiilliittyy,,MMaannaaggeemmeenntt aannddPPeerrffoorrmmaannccee

E-Guide

Hyper-V gains new resiliency features with Windows Server2008 R2

Greg Shields, Contributor

Windows Server 2008 R2 provides several improvements to Hyper-V that have been in high demand ever since its

initial release. These updates to Microsoft's low-cost virtualization platform include cost-effective high availability as

well as enhancements to virtual machine disk management. As a result, if you've been sitting on the sidelines

waiting for Microsoft's second move in the virtualization space, R2 is your time to jump.

Live Migration … finally!

The most notable of Hyper-V's improvements is the upgrade from Quick Migration to the zero-downtime Live

Migration. Microsoft was incorrect with its assertion that administrators were OK with a few seconds of downtime

during virtual machine re-hosting. The original Quick Migration capabilities, while acceptable to some, became a

source of ridicule and scorn for many.

Comparing Microsoft's original less-than-a-minute mini-downtimes to its closest competitor's single-ping-packet

outages drove many would-be Hyper-V deployers toward other products. As such, Microsoft's primary goal with the

next version of Hyper-V was to eliminate that downtime during motioning events.

From a technical perspective, updating Hyper-V's architecture to enable live migration involves substantially more

moving parts than its original design. To quote from a recent article of mine on Hyper-V, "At the point when Quick

Migration is initiated, a VM is immediately placed in a saved state. The saved state is not a power-down, nor is it

the same as a paused state. In the saved state, a VM releases its memory reservation on the host machine and

stores the contents of its memory pages to disk. Once this has been completed, the target host can take over

ownership of a VM and bring it back into operation. With Quick Migration, putting the VM in a saved state is the

most time-consuming aspect of a migration."

This process of saving the state of the virtual machine prior to re-hosting it was the source of Quick Migration's

original time delay. To eliminate that delay, Microsoft had to develop a sort of pre-copy mechanism that migrates

the majority of the virtual machine over, while still allowing it to operate as a functioning VM.

Prior to initiating this pre-copy mechanism, the equivalent of a snapshot of the VM is taken, providing a basis by

which changes are logged during the pre-copy event. Once the initial copy completes, Live Migration pauses the

VM, copies over any mid-copy changes, and finally transfers ownership to the new host. Because this pause-and-

delta-copy architecture involves dramatically less data transfer, the result is true Live Migration just like other

virtualization platforms.



Sponsored by: of 14

Cluster-awareness with disks

Another mechanism that was necessary for Live Migration involved rethinking how Windows Failover Clustering

works with disk resources. Both the original and R2 versions of Hyper-V rely on Windows Failover Clustering as the

service for high availability. The result is that virtual machines exist as cluster resources and are failed over as such

when problems occur.

In early versions of Windows Failover Clustering, however, Microsoft's architecture did not provide for disk resources

that were cluster-aware. As a result, a problem that mandated a failover event required the entire disk resource to

fail over. If multiple virtual machines were homed on that disk resource, they would all fail over at once. Because of

this limitation, Microsoft's guidelines for highly-available disk resources in the original version of Hyper-V was to

limit virtual machines to one per LUN. This created massive administrative headaches, as admins were tasked with

keeping virtual machines and LUNs correctly configured at the storage, server and application layers.

In Hyper-V R2, Microsoft announced the availability of Cluster Shared Volumes (CSVs). These cluster-aware

volumes are the company's first foray into cluster awareness for disk resources, and although they can be enabled

on any generic Windows Failover Cluster, they're currently designed for use specifically with Hyper-V.

CSVs are unique in that they still use the core NTFS file system that Microsoft operating systems have used for

years. Natively, this file system doesn't have the locking mechanisms in place for multiple hosts and simultaneous

access. With CSVs, an additional layer of management is placed atop the default file system to ensure that all

cluster nodes are aware of who owns – and thus manages and modifies – which files and folders. Cluster nodes

consult the CSV management layer prior to making changes to files and folders on a CSV, enabling true multiple-

server access to a single NTFS volume.

The effect to your environment is that multiple virtual machines can now be homed on a single LUN, dramatically

reducing your number of LUNs as well as administrative overhead. The cluster will fail over individual virtual

machines as necessary without affecting the entire disk resource.

As you can probably guess, this management layer requires the precise orchestration of ownership information

among all the files and folders on the disk as well as between each node in the cluster. The files associated with

Hyper-V's virtual machines tend to be small in number and large in size, which dramatically reduces the number of

objects to keep track of. For this reason, CSVs are currently supported for Hyper-V clusters only.

Staying cost-free with Hyper-V Server 2008 R2

With the recent release of VMware's vSphere 4.0, the virtualization wars heated up. This update to VMware's

virtualization platform brought about an evolutionary jump in features and capabilities. Unfortunately, it brought a

major increase in costs along with it, particularly for small- and medium-sized businesses that are just now dipping

their toes in the virtual pond.



Sponsored by: of 14

Along with the release of Windows Server 2008 R2 comes an accompanying release of Hyper-V Server 2008 R2.

This functionally similar product -- with a name that's too similar for many IT pros to keep straight -- enables a

completely free virtualization platform for Windows shops. For the record – and because many IT pros still don't

understand the difference -- Hyper-V is the role you install to a "full" instance of Windows Server 2008. Hyper-V

Server is the freeware edition that arrives as a trimmed-down Windows Server Core instance.

You can compare virtual vendors at their low-end price points because Hyper-V Server 2008 R2 now includes high

availability and live migration for no extra cost in its already low-cost price point. The result is a shot across the

bow toward VMware's pricing for SMB environments.

If you're in a small environment and looking to bring virtualization forces to bear, Hyper-V Server 2008 R2 brings

all of the high-availability features in the "regular" product to its affordable freeware package. Like the full instance,

the second version of Hyper-V Server can be managed via the Hyper-V Manager and Failover Cluster Manager

toolsets, or it can be integrated into a System Center Virtual Machine Manager infrastructure.

Other niceties

While these updates head the list of top new capabilities, Microsoft has added a few extra goodies to the package

as well. It calls the first one Dynamic Virtual Machine Storage, which is shorthand for the hot-plug and hot-removal

of disks from virtual machines, which enables you to add and remove disks from your VMs without having to power

them down.

You'll also find support for the latest edition of hypervisor extensions that are in the processors of today's bleeding

edge servers. These new processor extensions for virtualization are generically referred to as Intel EPT and AMD

RVI. Both provide a dramatic performance boost over the previous-generation Intel VT and AMD-V extensions but

require hardware that supports their new instruction sets. For servers that enjoy such benefits, Microsoft supports

their use through what it calls SLAT, or Second Level Address Translation. The net effect is a substantial

improvement of raw VM performance when hosted on hardware that supports these extensions, particularly for VMs

that run memory-intensive workloads.

CPU Core Parking and the enhanced networking support for jumbo frames are two more features. CPU Core Parking

is a power management feature of Windows Server 2008 R2 that enables Hyper-V and other workloads to offload

processing to fewer cores when needs are light. Cores that aren't needed are simply shut down, reducing power

usage of the server during periods of low use. Jumbo frame is a networking feature that improves performance for

certain types of workloads. Its enlarged frame size was previously available for non-virtualized workloads, but

support has been added for Hyper-V in this release.

Clearly, there's plenty to be excited about in Hyper-V for Windows Server 2008 R2. Greater levels of administrator-

friendly high availability are the big upgrades, while cluster-aware volumes will also improve your life when you're

managing virtual machines. Microsoft's recent announcement about its free Hyper-V version makes the whole

package that much cheaper to deploy. If you're one of the many who are on the fence when it comes to

virtualization, R2 may be the clincher that kick-starts your move.



Sponsored by: of 14



Is it me, or is virtualization less sexy than it used to be? Consolidating virtual machines (VMs) onto physical hosts

was going to solve the world's data center power problems while freeing administrators from the bonds of physical

infrastructure. But nowadays, virtualization has become so commonplace that it is nearly a panacea.

Nowhere is this more noticeable than in the improvements to Microsoft's Hyper-V. Rising from an astonishingly

feature-complete version 1.0 that arrived shortly after the release of Windows Server 2008, Microsoft is poised to

reach new heights with its improvements to Hyper-V in Windows Server 2008 R2. One of the most anticipated

improvements to Hyper-V version 2.0 is an upgrade from Quick Migration to a fully functional Live Migration feature

set. This tip covers the differences between Quick Migration and Live Migration and how to get started with Live

Migration for VM host relocation with zero downtime.

Differences between Quick Migration and Live Migration

Now you may be asking, "What is the difference between Quick Migration and the new Live Migration?" Simply put:

Migration speed.

Hyper-V's initial release enabled a Hyper-V virtual machine to be relocated from one virtual host to another with

minimum downtime, a feature known as Quick Migration. The downtime was directly related to the amount of

memory assigned to the VM, along with the speed of the connection between virtual hosts and shared storage. VMs

with higher levels of assigned virtual memory and slow networks took longer to complete a migration from one host

to another, while those with less virtual memory and faster networks could complete a migration in less time.

For example, a VM with 2 GB of memory that runs on top of a 1 Gigabit Ethernet iSCSI connection takes upward of

32 seconds to complete a host-to-host migration. Although a VM in the process of being migrated technically never

has to restart or power down, it is unavailable during the migration. During this period, the VM will not respond to

clients or be available on the network.

For many environments, 32 seconds of downtime is too long . VM migrations that involve this amount of downtime

exceed the typical norms for client timeouts, which means that many clients will experience a migration as an

outage. For environments with high-availability needs, this is unacceptable.

With Live Migration, however, the length of downtime for a migration has been effectively reduced to zero. Although

a slight delay occurs -- similar to the delay during a VMotion event with VMware ESX -- it's insignificant and doesn't

affect the clients on the network.



Sponsored by: of 14

Quick Migration in Hyper-V's version 1.0 and Live Migration in Hyper-V's version 2.0 require Hyper-V to be installed

on servers that host the Windows Server Failover Clustering feature. What is not widely understood is that the

cluster itself contains most of the technology responsible for failover from virtual host to virtual host. As a result,

this "new Hyper-V feature" is as much a new set of clustering features as it is an improvement on core

virtualization capabilities.

Perhaps the biggest difference between the two functionalities, though, is the process by which the migrations take

place. Let's start with Quick Migration. At the point when Quick Migration is initiated, a VM is immediately placed in

a saved state. The saved state is not a power-down, nor is it the same as a paused state. In the saved state, a VM

releases its memory reservation on the host machine and stores the contents of its memory pages to disk. Once

this has been completed, the target host can take over ownership of a VM and bring it back into operation. With

Quick Migration, putting the VM in a saved state is with the most time-consuming aspect of a migration.

To reduce this delay, Microsoft developed a mechanism that would pre-copy a VM's memory from the source to the

target host. At the same time, the pre-copy logged changes to memory pages that occur during the copy period.

Live Migration addresses these needs. Although the changes themselves are relatively few in number, they make

the delta copy significantly smaller -- and thus faster -- than the original copy. Once the initial copy is completed,

Live Migration pauses the VM, copies the memory deltas and then transfers ownership to the target host. Since the

amount of data being transferred during the VM's outage is significantly smaller, the time required to complete the

transfer is dramatically reduced.

Getting started with Live Migration

If you want to implement Live Migration, the process requires a wholesale migration from an existing Hyper-V

cluster to one that is hosted on top of Windows Server 2008 R2. At present, there is no guidance from Microsoft on

a direct-upgrade path. That said, you should complete the following steps to get started:

• Install Windows Server 2008 R2 on two or more servers that will host Hyper-V virtual machines.

• Enable the Windows Server Failover Clustering feature on each server. Failover Clustering has

specific requirements for hardware and network configuration. For full support, each component that

comprises your cluster should be certified by Microsoft. The Windows Server Catalog features additional

information on this certification.

• Configure your nodes as a Failover Cluster. Doing so requires passing each of the tests in the built-in

Validate a Cluster configuration wizard.

• Configure connected shared storage as Cluster Shared Volumes (CSVs). This is done in R2's

Failover Cluster Manager by navigating to CSVs and adding the appropriate storage. Cluster Shared

Volumes is a new technology in R2 and is one of the major reasons why Windows Failover Clustering works

so well. I'll discuss Cluster Shared Volumes further in another article, but for now be aware that CSVs

enable multiple cluster nodes to better identify which node owns which files and folders in a disk resource.



Sponsored by: of 14

• Set up cluster networks for Live Migration. Live Migration needs a high-speed, isolated network to

transfer memory pages between cluster nodes. R2's Failover Cluster Manager includes the ability to identify

a network resource as a "network for live migration".

• Build virtual machines and test Live Migration. Once these steps are complete, build a new VM and

attempt to migrate it to another server from within the Failover Cluster Manager console.

"Hyper-V: Step-by-Step Guide to Using Live Migration in Windows Server 2008 R2" offers detailed information on

each step. Also, if you're unfamiliar with the basics of Windows Failover Clustering, you should read Microsoft's

"Getting Started: Failover Clustering" guide.

So even with all these new features in Hyper-V version 2.0, virtualization in my mind still isn't as sexy as it used to

be. But it remains exciting and Hyper-V 2.0 has the potential for major impact on your data center. With R2's

upgrades to Hyper-V and Failover Clustering, Microsoft is bringing feature parity to a market full of similar -- and

soon to be commonplace -- technologies.



Sponsored by: of 14


Rick Vanover, Contributor

Both Windows Server 2008 R2 and the highly anticipated update to Hyper-V are still in beta, but Microsoft is mak-

ing it clear that this is a virtualization platform you need to consider. I've recently tinkered with the Hyper-V R2

beta and am inclined to agree. This tip highlights new features in Hyper-V R2 that may prompt you to consider it in

your platform decision process.

Hyper-V R2 overview for Windows

For Hyper-V 1.0 users, the process of adding Hyper-V R2 is the same because it's a role that has to be added from

the server management console. Windows Server 2008 R2 allows the role to be scripted as well. To add Hyper-V R2

to a server, simply type the following command:

start ocsetup Microsoft-Hyper-V

Hyper-V Manager remains the default management interface in Hyper-V R2 and is the same in general appearance

and installation. The only difference concerning Hyper-V Manager in Hyper-V R2 is that there aren't any required

Windows updates.

If you haven't worked with Windows Server 2008, there are several versions to consider. With Hyper-V, choosing

the right version is critical for planning out your evaluation or implementation. First, Windows Server 2008 R2 is

available only in x64 editions, essentially making x86 obsolete. In fact, the Hyper-V role on the base release of

Windows Server 2008 was available only on x64 editions. With this in mind, the following beta versions of Hyper-V

R2 are available for download from Microsoft:

• Windows Server 2008 R2 Beta Standard. This version is suitable for a basic hypervisor

implementation. This version is managed with Hyper-V Manager.

• Windows Server 2008 R2 Beta Enterprise. This is a solid option for any deployment that will use

System Center Virtual Machine Manager (SCVMM) or implement advanced features such as clustered file

systems. There are important changes with clustering in Hyper-V R2 related to the file system which I'll

mention later.

• Windows Server 2008 R2 Beta Datacenter. This version has the same features as the previous two

options but also allows unlimited virtualization rights.

Each version of Hyper-V R2 is available from the Microsoft website, including evaluation product keys. The base

release of Hyper-V is also available as a standalone download commonly known as the free version of Hyper-V. This

was a core version of the standard edition, but unfortunately there isn't a public beta equivalent to this offering yet.



Sponsored by: of 14

Support for Live Migration in Hyper-V R2

For many administrators, Hyper-V's most distinctive feature is its virtual machine (VM) migration technology. While

Hyper-V offers Quick Migration in the base release, the R2 beta introduces Live Migration for Hyper-V systems. Live

Migration basically provides the same functionality that's present in VMware's vCenter Server. The biggest difference

between Quick Migration and Live Migration is the amount of time needed to complete a VM migration. Greg Shields

covers this topic in an article on Live Migration in Hyper-V.

Other new features in Hyper-V R2

Hyper-V R2 is chock full of new features that enhance its hypervisor. Some of the more significant changes include

the following:

• Jumbo frame support for VMs. This feature allows the network interface to work with a larger frame

size, bumping up the default 1,518 byte frame to a 9,000 byte frame. Be sure that your network gear is

configured to support jumbo frames, or there is no benefit to the configuration. Jumbo frames can benefit

any high-transfer system, including backups of VMs from a host server. It should be noted, though, that

Windows Server 2008 hosts have offered support for jumbo frames since its initial release.

• Clustered shared volumes and enhanced clustering. One of the problems with managing a large

number of VMs with Hyper-V is the lack of a clustered file system. Thankfully, Windows Server 2008 R2

addresses this issue by introducing clustered shared volumes. In addition, this feature extends to the

cluster validation tool and provides special provisioning for Virtual Hard Disk (VHD) files that run VMs. Greg

Shields takes a detailed look at this technology in an article on on Microsoft's Cluster Shared Volumes.

• VHD booting. Windows Server 2008 R2 introduces a slick mechanism for servers and Virtual Desktop

Infrastructure (VDI) deployments that allow a computer to be booted from a local VHD file. This VHD

booting mechanism works with physical and virtual systems. This TechNet blog post on VHD booting is a

good place to get a feel for the potential of this technology.

Remote Desktop Services in Hyper-V R2

Windows Server 2008 R2 offers more than server virtualization with Hyper-V. Among the other tools in the bundle,

Microsoft has included cutting-edge terminal services features. Remote Desktop Services, formerly RemoteApp, is a

presentation and application virtualization technology.

Remote Desktop Services' functionality has improved in R2. Specifically, it can now deliver applications transparent-

ly to clients. Remote Desktop Services is a critical component of another effort that Microsoft is working on: a VDI

technology. Little has been said about this project, but rest assured that it's in the works. In fact, many

organizations may turn to this technology as a VDI option because it will provide solid client environment support.

A good place to start with Remote Desktop Services is the Windows Server 2008 Terminal Services homepage.

Terminal Server Client Access Licenses (TSCALs) for Windows Server 2008 has undergone significant licensing

revisions. Because of these changes, and the fact that TSCALs from prior versions cannot be transferred to

Windows Server 2008,check your entire environment's licensing status before upgrading to Windows Server 2008

R2.



Sponsored by: of 14

Hyper-V R2: Big steps forward but are they enough?

Hyper-V R2 brings much-needed functionality to the Microsoft virtualization portfolio. With the highly competitive

virtualization landscape , Microsoft has taken steps in the right direction with this beta. What's unclear is whether

the industry will embrace Hyper-V R2 once it delves into the details and performs the necessary internal

comparisons.



Sponsored by: of 14

New features in Microsoft's SCVMM R2 improve Hyper-V management


While Microsoft's Hyper-V has proved its ability to fulfill enterprise-level needs, Hyper-V version 1.0 featured

significant shortcomings, such as its management toolsets and a Hyper-V Manager console that is rough around the

edges. Luckily, Microsoft designed System Center Virtual Machine Manager (SCVMM) to overcome these obstacles.

In this continuation of our three-part series on SCVMM R2, we discuss some of the upgrade's new features and

their improvements to Hyper-V management, including logical unit number (LUN) management and Live Migration

support. In part one, we explored the top seven features justifying an upgrade to SCVMM .

Drawbacks of Hyper-V version 1.0

Hyper-V's hypervisor has proven it can keep pace with or even outperform its competitors, including VMware and

XenServer. Hyper-V is an easy sell for single-OS environments because it relies on Windows Server 2008 as its

platform. So if you understand how to manage Windows Server, the jump to managing virtualized Windows Server

environments isn't a big step.

The problem with Hyper-V version 1.0 is the Hyper-V Manager console. Hyper-V Manager focuses on the

management of individual virtual machines (VMs) instead of groups of VMs. In addition, working with virtual

machines in a high-availability (HA) environment is a chore, with commands spread across multiple consoles.

Although it performs basic administrative actions for individual VMs, Hyper-V Manager doesn't offer much else.

New features in SCVMM 2008 R2

Enter SCVMM 2008 R2. The new console was designed to address the shortcomings of Hyper-V Manager by

facilitating several functionalities that admins have clamored for since adopting Hyper-V v1.0. The most important

features in SCVMM 2008 R2 include the following:

• Live Migration support. Since the initial release of Hyper-V, the most requested improvement is parity

with VMware on virtual machine migration. Hyper-V version 2.0 includes the ability to migrate VMs from

one host to another with zero downtime. This feature not only offers the ability to relocate VMs for

maintenance but also enables VM load balancing on par with ESX and VirtualCenter.

Hyper-V's reliance on Windows Failover Clustering increases the complexity associated with migrations and

failover. SCVMM addresses this problem by removing the reliance on the Failover Cluster Manager for

initializing migrations. Both manual and automated migrations are incorporated into the SCVMM console.

• Improved LUN management and configuration. The initial release of SCVMM 2008 supports only

initiator-based connections to iSCSI targets. Hyper-V version 1.0 environments not only lack a cross-host

locking mechanism for shared drives but also are limited to a single VM per LUN. This isn't a major problem

in small environments, but it's an operational nightmare for large environments.


New features in Microsoft’s SCVMM R2 improve Hyper-V management

Sponsored by: of 14

With Hyper-V version 2.0 and SCVMM 2008 R2, you can create large LUNs containing more than one VM

because of two new features: Cluster Shared Volumes and LUN-masking support. Masking enables a LUN to

be available to some hosts and unavailable to others, ensuring that the right hosts see the right disk

resources.

Cluster Shared Volumes is a new capability in Windows Failover Clustering. It creates shared ownership of

specific files on a disk between all hosts in a Windows Cluster, whereas clusters in Hyper-V v1.0 were

aware only of resource ownership bound by the disk itself. Cluster Shared Volumes enables hosts to share -

- and therefore determine ownership of -- individual files on a disk resource. Cluster Shared Volumes has a

certain elegance in that it isn't a new file system but instead a protocol layered on top of a standard New

Technology File System (NTFS) that enables the sharing functionality on cluster disks. For more information

check out this tip on Cluster Shared Volumes.

• Management enhancements. SCVMM 2008 R2 enables you to migrate VMs from one cluster to another

within its interface. In addition, it can migrate VMs from single hosts to clusters for HA purposes. If you

manage multiple clusters because of operational requirements or resource limitations, this feature

facilitates the process of relocating VMs.

SCVMM 2008 R2 also offers support for domains that have disjoined name spaces. While most

environments share the same Domain Name Server name space as their domain name, some organizations

don't because of mergers or political reasons. Organizations that don't follow this practice require custom

Server Principal Names (SPNs) to be manually created in Active Directory. SCVMM R2 automatically creates

custom SPNs when necessary.

• Network optimization. Keeping multiple VMs on a single host increases the amount of network traffic

going through that host dramatically. Network optimization tools such as Microsoft's Virtual Machine Queue

and TCP Chimney Offload are available in SCVMM 2008 R2 to assist environments with the hardware to

support these protocols. In high-traffic situations, enabling either of these tools improves overall network

performance. Another SCVMM also features the networking improvement for load balancing Media Access

Control (MAC) address spoofing, which is a new setting exposed in the console.

• Disk improvements. An improvement to disk resources in SCVMM 2008 R2 is the ability to add and

remove disks from running virtual machines. This feature allows you to add additional disks to your

production servers before you run out of space without incurring downtime.

• Maintenance mode. Another management improvement is the ability to move a host into maintenance

mode. When maintenance mode is activated on a host, all running VMs on that host are automatically

migrated to other hosts in the cluster. Also any new VMs in the cluster will not be positioned on that host

while it's in maintenance mode.

Conclusion

So while the interface appears the same in SCVMM 2008 and SCVMM 2008 R2, the underlying capabilities have

matured. SCVMM 2008 R2 is currently a release candidate, with a release date coming later in 2009. In the final

article in this series, we cover some of the prerequisites and gotchas involved in installing SCVMM 2008 R2 and run

through the installation process.


New features in Microsoft’s SCVMM R2 improve Hyper-V management

Sponsored by: of 14

A Guide to Utilizing Virtualization in a Disaster Recovery Strategy


Sponsored by: of 14


Hyper-V workarounds: How to ensure high availability

Intro to Virtualization eBook, Chapter 4: Making Virtual Infrastructures Highly Available

Dell™ High Availability Solutions Guide for Microsoft® Hyper-V™

About Dell, Inc.

Dell Inc. (NASDAQ: DELL) listens to customers and delivers innovative technology and servicesthey trust and value. Uniquely enabled by its direct business model, Dell is a leading global systems and services company and No. 34 on the Fortune 500. For more information, visitwww.dell.com, or to communicate directly with Dell via a variety of online channels, go towww.dell.com/conversations. To get Dell news direct, visit www.dell.com/RSS.

www.dell.com

www.dell.com/RSS

www.dell.com/conversations

www.dell.com

http://www.bitpipe.com/detail/RES/1229019703_924.html



e-guide microsoft hyper-v: improving...

Documents