Khám phá windowns server 2008 - p 37 pot

The Migrate Virtual Machine Action The Migrate Virtual Machine Wizard enables the administrator to migrate a VM to another host using a VMM wizard, as follows: 1.. On the Select Virtual

11 Using Vir tual Machine Manager 2008 for Provisioning

NOTE

The progress of the VM deployment can be monitored by selecting the VM in the

self-ser vice por tal and clicking Proper ties in the Actions pane Then click the Latest

Job tab

Migrating a VM

VMM provides the capability to move, or migrate, VMs quickly and easily between hosts

There are three ways this can be accomplished in VMM

The Migrate Virtual Machine Action

The Migrate Virtual Machine Wizard enables the administrator to migrate a VM to

another host using a VMM wizard, as follows:

1 Open the VMM Administrator console using the shortcut on the Windows desktop

or via the Start menu under Microsoft System Center, VMM 2008, VMM

Administrator console

A Connect to Server window may open, prompting for the VMM server to connect

to Enter the server name and connection port (the default is port 8100) using the

format VMMserver:port

NOTE

You may choose to always open a connection to this ser ver by selecting the Make This

Ser ver My Default check box Doing so prevents this connection window from

display-ing when the Administrator console is run

2 Go to the Virtual Machines view by clicking the Virtual Machines button

3 Select the VM to migrate and click Migrate Virtual Machine from the Actions pane

NOTE

If the selected VM is currently running, VMM will display a pop-up dialog warning the

administrator that migrating the VM will cause the VM to be stopped, resulting in a

temporar y loss of ser vice to all users of the machine The VM is not stopped until the

migration actually begins Click Yes to continue or No to quit

4 On the Select Virtual Machine Host page, select the host to migrate the VM to Use

the star ratings to determine a suitable host Review the Additional Information tabs

in the Results pane for further information about the host’s star rating Click Next

to continue

5 On the Select Path page, type the path on the host where the VM, and its associated

files should be stored on the host

NOTE

The path entered must be a valid and already exist on the host

Optionally, the administrator can check the Add This Path to the List of Host

Default Paths check box to add the path to the default paths on the host

If SAN transfers are enabled the VM is transferred to the host over the SAN, by

default If the administrator does not want to perform a SAN transfer, check the

Transfer over the Network Even if a SAN Transfer Is Available check box This check

box is not available if SAN transfers are not available for this deployment

Click Next to continue

6 On the Select Network page, select the appropriate network that exists on the

selected host If the administrator does not want to configure a network, select Not

Connected Click Next

7 On the Summary page, carefully review the settings and click Move to proceed with

the migration The administrator can also choose to select the Start the Virtual

Machine Immediately After Deploying It to the Host check box, if desired

The Migrate Virtual Machine Wizard offers a View Script button This option allows the

administrator to view, modify, and save the PowerShell commands that the wizard will

execute to migrate the VM, as shown in the following example:

# ———————————————————————————————————————

# Migrate Virtual Machine Wizard Script

# ———————————————————————————————————————

# Script generated on Sunday, June 22, 2008 3:18:31 AM by Virtual Machine Manager

#

# For additional help on cmdlet usage, type get-help <cmdlet name>

# ———————————————————————————————————————

$VirtualNetworkAdapter = Get-VirtualNetworkAdapter -VMMServer vmm2008 | where

{$_.Name -eq “EDGE STD x64”}

Set-VirtualNetworkAdapter -VirtualNetworkAdapter $VirtualNetworkAdapter

-RunAsyn-chronously -VirtualNetwork “Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC

(NDIS 6.0) - Virtual Network” -NetworkTag ““ -Location ““ -JobGroup

3b72ecf7-ee0a-4d5b-b84b-844505c3a7ed -VLanEnabled $false

$VM = Get-VM -VMMServer vmm2008 -Name “EDGE STD x64” | where {$_.VMHost.Name -eq

“DC1.companyabc.com”}

$VMHost = Get-VMHost -VMMServer vmm2008 | where {$_.Name -eq “DC1.companyabc.com”}

MoveVM VM $VM VMHost $VMHost Path “C:\ProgramData\Microsoft\Windows\HyperV”

-RunAsynchronously -UseLAN -JobGroup 3b72ecf7-ee0a-4d5b-b84b-844505c3a7ed

This code can be saved and edited to facilitate migrating other VMs using the VMM

11 Using Vir tual Machine Manager 2008 for Provisioning

NOTE

Running the wizard in this way is an easy way to create the PowerShell scripts

neces-sar y to per form migrations using the VMM command shell After the scripts have been

saved, the administrator can cancel the Migrate Vir tual Machine Wizard

Drag and Drop the VM onto a Host

Adding a guest virtual session onto an existing Hyper-V host server requires the process of

associating the virtual session to the host This is done by dragging and dropping the

virtual guest session onto the host by doing th following:

1 Open the VMM Administrator console using the shortcut on the Windows desktop

or via the Start menu under Microsoft System Center, VMM 2008, VMM

Administrator console

A Connect to Server window may open, prompting for the VMM server to connect

to Enter the server name and connection port (the default is port 8100) using the

format VMMserver:port

NOTE

You may choose to always open a connection to this ser ver by selecting the Make This

Ser ver My Default check box Doing so prevents this connection window from

display-ing when the Administrator console is run

2 Go to the Virtual Machines view by clicking the Virtual Machines button

3 Expand the Host Groups in the Properties pane to display the host upon which the

VM will be migrated, as shown in Figure 11.8

4 Select the VM to migrate and drag and drop it onto the new host The VM will be

migrated to the new host

NOTE

If the selected VM is currently running, VMM will display a pop-up dialog warning the

administrator that migrating the VM will cause the VM to be stopped, resulting in a

temporar y loss of ser vice to all users of the machine The VM is not stopped until the

migration actually begins Click Yes to continue or No to quit

Drag and Drop the VM onto a Host Group

This process is the same as dragging and dropping the VM onto a host, as described

previ-ously, with a few differences Instead of dropping the VM onto a specific host, the VM is

dropped onto a host group that contains one or more hosts

FIGURE 11.8 Selecting the host on which to migrate the VM

Automatic Placement, explained earlier in this chapter, will automatically place the VM on

the most suitable host in the selected host group Host selection is based on the host

ratings defined either through the VMM global settings or by override settings in the VM’s

Properties page

Summary

In this chapter, we discussed VM placement and host ratings to help the administrator

select the appropriate host for VM deployment User roles provide a good deal of

granular-ity of administration within the VMM Administrator console and the self-service portal

VMs can easily be deployed using both the VMM Administrator console and the

self-service portal Migrations of VM can be performed easily using the Administrator console,

via wizards, or simple drag-and-drop methods, or from the VMM command console

Best Practices

The following are best practices from this chapter:

Use roles-based access control (RBAC) to define the administrator roles in VMM

Because the Administrator user role has full access to the VMM infrastructure, limit

the number of members of this group as much as possible

Use delegate administrators to scope administrators to a specific set of objects in

VMM

Create a VMM Administrators group in the Active Directory and add that group to

the Administrator role in VMM This is better than adding an individual user

account, in case that user account is deleted

Create security groups in the Active Directory and use these groups to define

members of Delegated Administrator and Self-Service User roles in VMM

Monitor the members of Delegated Administrator groups, because delegated

admin-istrators can manage the groups they are members of

Add administrators or delegated administrators to the Self-Service User role if

self-service portal access is required

Delegated Administrator and Self-Service User groups can be pre-created without

members, and the members can be added later

Run wizards, such as the Create Virtual Machine Wizard, to view, customize, and

save the PowerShell scripts that the wizard will run

Build a collection of PowerShell cmdlets that perform commonly used VMM

admin-istration tasks

Use the Look For box, present in many of the VMM wizards, to filter the results of

collections of VMM objects

Scope the VMM library resources that self-service users can access by creating their

own folders in the VMM Library share

Use Automatic Placement to automatically deploy VMs to the best-suited host

Customize the global host rating to match the organization’s needs and environment

Only use the Make This VM Highly Available option on VMs you plan to deploy to

host clusters

Use a common VM path on all host servers to ensure that VM migrations will

succeed

Use quota points for self-service users to control the number of VMs they can deploy

to hosts

11 Using Vir tual Machine Manager 2008 for Provisioning

Monitor the progress of VM migrations using the Jobs view in the Administrator

console or the Properties page of the VM in the self-service portal

Notify users of an active VM before migrating it to a new host, because the VM will

temporarily be stopped during the migration

Use Automatic Placement of migrated VMs by using the “drag and drop onto a host

group” method

This page intentionally left blank

Managing Guest

Sessions with Uptime in

a Hyper-V Environment

IN THIS PART

CHAPTER 12 Application-Level Failover and

Disaster Recovery in a Hyper-V Environment 349 CHAPTER 13 Debugging and Problem Solving

the Hyper-V Host and Guest OS 385

This page intentionally left blank

Application-Level Failover and Disaster

Recovery in a Hyper-V

Environment

Choosing the Best Fault Tolerance and Recover y Method

Failover Clustering in Windows Ser ver 2008

Over view of Failover Clustering

in a Hyper-V Host Environment Deploying a Failover Cluster for Hyper-V Hosts

Backing Up and Restoring Failover Clusters

Organizations have expanded their implementation of

clustered servers and recovery solutions for physical server

systems But now, with virtualization and several guest

sessions depending on the operation of a single host

system, the interest to implement highly available host

servers has grown dramatically The failure of a single host

server can simultaneously bring down the services of several

systems, so the proper implementation of high-availability

technologies becomes extremely important If properly

implemented, virtual servers can actually improve an

orga-nization’s ability to create highly available and

fault-toler-ant environments, because the creation of a redundfault-toler-ant

guest session does not require the purchase of an addition

physical server for each replicated server

However, the biggest challenge most organizations have in

creating a highly available virtualized environment is to

choose which technology to implement There are many

ways to create fault tolerance, including the following:

Clustering the host server

Clustering the guest session

Using native high-availability functionality of the

application being protected

Purchasing and using a third-party application

An administrator must choose which failover or

disaster-recovery method to implement The key is to choose the

best solution to meet the needs of the organization and to

try to minimize the number of methods implemented so