OS = Windows 2012 Name = Hyp1 IP = VM = Domain: Contoso.com IP = os = windows2012

Size: px

Start display at page:

Download "OS = Windows 2012 Name = Hyp1 IP = VM = Domain: Contoso.com IP = os = windows2012"

Oswin Garrison
6 years ago
Views:

1 1 P a g e

2 LAB: Server 1 OS = Windows 2012 Name = Hyp1 IP = VM = Domain: Contoso.com IP = os = windows2012 Server 2 OS = Windows 2012 Name = Hyp2 IP = VM = Domain Client IP = OS = windows 8 64 Bit Professional ) 2 U Domain Client HYP1 HYP2 Microsoft introduced shared nothing for Live Migrations in Server This is simply the ability to move a running virtual machine/guest from one hypervisor host system to another with no requirement for shared 2 P a g e

3 storage between the two hosts. This means you no longer have to have a fancy, expensive storage device like a SAN or even a cluster of hosts to be able to take advantage of the Live Migration functionality. Windows Server 2012 now also allows multiple simultaneous live migrations to occur, and they can also leverage higher speed network connections (like 10Gb). The requirements for share nothing live migration are pretty simple and straightforward: Need 2 or more servers running Hyper-V o must support hardware virtualization o must have like processor family (like Intel) o must be part of the same domain or be part of separate domains that have established trust between domains The VM s which will be part of the live migration cannot use physical disks. They must use either: o Virtual hard disks o Virtual fibre channel disks And that s it. No shared storage or cluster requirements to use shared nothing configuration. Microsoft does recommend using a private network for the live migration traffic, and I d say that s a pretty good idea. This is kind of like how Unitrends recommends configuring separate subnets or backup networks if the IT infrastructure can support it. With physical servers, this sometimes means installing or configuring an additional NIC, but it s simplified to a configuration and setup parameter with the Hyper-V private network feature. This keeps backup traffic (or live migration traffic) off your primary user network, which can impact performance during a heavy load. Here s a link to a pretty good demo video on how to configure a Shared Nothing Live Migration with Windows Server I think this is a pretty cool feature, and it allows IT shops with small budgets to leverage some of the more powerful features available in virtualization. Don t forget Unitrends Enterprise Backup free software also runs on Hyper-V 2012 and can protect up to 4 VMs for free forever! Requirements are here but include: Hyper-V host OS: Windows Server 2012 Windows 2008 R2 SP1 Windows 2008 R2 SP1 Server Core Hyper V Server 2008 R2 SP1 Resources: Requires 64 bit hypervisor / environment 100 GB of provisioned disk space 2 processors for the virtual machine 4 GB Memory for the virtual machine Enable the Hyper-V migration Features For shared nothing migration required 2 or more Hyper-v Servers with Hyper-v live migration features enabled.. 3 P a g e

4 To enable live migration features on Hyper-v open hyper-v console - Right click the Hyper-v machine Hyper-v settings / or click the Hyper-v machine in Hyper-v console on the right side of console Hyper-v settings - Select Live migration enable incoming and outgoing live migrations. Use Kerberos (for AD authentication) Either enable use any or Use this IP addresses for live migration which need to add IP s in the network, and need setting in firewall Apply- 4 P a g e

5 Client Compatibility Configuration If the both machines are having non similar processors must do the compatibility configuration on the client machines. To do the compatibility configuration right click the VM settings 5 P a g e

6 Expand Processor tab click compatibility in compatibility configuration check box Migrate to a physical computer with a different processor version. 6 P a g e

7 Move the Virtual Machine from One Hyper-V server to another Hyper-v server Select the vm right click move - Select - next 7 P a g e

8 Move the virtual machine / move the virtual machine s storage Move the virtual machine: it ll move the complete virtual machine from one Hyper-v machine to another Hyper-v machine. move the virtual machine s storage: it s move only the VHDX from one Hyper-v machine to another Hyper-v machine but the vm still remains on the same location. Select - move the virtual machine - Next 8 P a g e

Select the Target machine where you want to move the VM Browse or you can type the name of the machine - next Move options: Move the virtual machine s data to a single location: this will move the

9 Select the Target machine where you want to move the VM Browse or you can type the name of the machine - next Move options: Move the virtual machine s data to a single location: this will move the entire vm to selected destination single location Move virtual machine s data by selecting where to move the items: this will move the vm data to selected destination multiple locations, i.e : snapshots to a different location, VHDX on different location Move only the virtual machine: it ll move only the vm but the vm data remain at the same location 9 P a g e

10 Select the destination folder on destination machine browse and select Imp: the destination folder should have full access right to the source machine Create a folder on destination machine right click assign access permission to the source machine - 10 P a g e

11 Here we showed the path only for Hyper-v server but actually need to show the shared folder path where we are moving the source machine (the source machine folder name where Hyper-v stored on the source machine and destination machine folder where we are moving the client should be same identical name) Say next - 11 P a g e

$Here it ll ask for the Destination path as the destination path where we created a folder on c:\ drive$

12 Here it ll ask for the Destination path as the destination path where we created a folder on c:\ drive named WIN8(SNM) and given security permission of the destination machine. Say - Next Finish 12 P a g e

13 If this error appears : this is the connection on which you want to move the machine in our scenario we have a single external network configured - click the drop down list and select the connection - next Finish - 13 P a g e

We can see the performing move As well as on the destination folder you can see the files copying on it and the size increments till the complete move.

14 We can see the performing move As well as on the destination folder you can see the files copying on it and the size increments till the complete move. After Complete the moving the machine will appear on Destination Hyper-V server same running status and on the source it will be deleted automatically that s what it s called Shared Nothing live migration Thanks Sajid Shaik 14 P a g e

SMB Live. Modernize with Hybrid Cloud. Lab 1: Exploring Windows Server 2012 R2 & Hyper-V

SMB Live. Modernize with Hybrid Cloud. Lab 1: Exploring Windows Server 2012 R2 & Hyper-V SMB Live Modernize with Hybrid Cloud Lab 1: Exploring Windows Server 2012 R2 & Hyper-V Terms of Use 2013 Microsoft Corporation. All rights reserved. Information in this document, including URL and other