Hyper-V Migration

Hi.
I just really want to double check that what I am about to do wont break everything.
I have a 2 node Hyper-V 2008R2 cluster, with 15 VM's).
I have purchased a 3rd server where I will install Server 2012R2 and Hyper-v.
the idea build 1 server and connect up to the Shared storage. Shut down all VM's
Import them into the New Hyper-V server
Break the old cluster, rebuild server to 2012R2 and create highly available cluster. power on the VM's.
rebuild final server to 2012R2 and then have a 3 node cluster.
Does this seem correct in terms of order or should I switch around any steps
thanks

Hi Sir,
For cluster , to avoid potential issues Microsoft recommend that you use a set of matching computers that contain the same or similar components.
Actually , G8 and G9 can not meet the requirement "same/similar components" .
Also please refer to the similar thread:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/b771b281-3d02-4377-85f2-9c18ba082f5d/different-hardware-for-hyperv-failover-cluster?forum=winserverhyperv
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Similar Messages

Migration of VMs from WS2012 Hyper-V Hosts Cluster to WS2012 R2 Hyper-V Hosts Cluster

Hello All,
We’re currently running our production VMs on a Failover Cluster of Windows Server 2012 Hyper-V Hosts. We’re planning to migrate these VMs to the cluster of
Windows Server 2012 R2 Hyper-V Hosts.
I have created a failover cluster of Windows Server 2012 R2 Hyper-V Hosts, and successfully tested the HA of my new test VMs on this new cluster.
Anyone please tell me the procedure, steps and best practices to migrate these VMs from Windows Server 2012 Hyper-V Hosts to Windows Server 2012 R2 Hyper-V
Hosts.
Thank you.
Regards,
Hasan Bin Hasib

Hi Hasan Bin Hasib,
You can refer the following related cross-version live migration KB:
Hyper-V: Migration Options
https://technet.microsoft.com/en-us/library/dn486792.aspx?f=255&MSPPError=-2147217396
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

VM migration (VMWare to Hyper-V) with the help of Orchestrator

Hello There,
I am planning to Automate the migration process with the help of scripts.
But not sure how to make a flow on Orchestrator for the same.
I have following things which can be used with Orchestartor:
1. Script to perform VMware to Hyper-V Migration.
2. Script to perform VM Status check post migration.
So how can i use these script with Orchstartor to automate migration?
Looking forward to hear from you.
Regards,
Prashant Sahane

if you have the scripts there is not necessarily any reason to involve Orchestrator.
If you want to ex. put a migration offering on the SM portal you could use Orchestrator. As Powershell and Orchestrator does not play well you may want to consider having Orchestrator write key data to a file, then have a scheduled script pick up these files
and start the migration using the scripts you have.
You could also have a script to monitor new requests and launch the script from there. This is one case where a customized service request class could come into play.
http://codebeaver.blogspot.dk/

Hyper-V - 2 node cluster goes down if one server shutsdown

Hi all,
I built a 2 node cluster with tiered storage and then I started doing some tests:
* Drain one node and all the VMs moved to the other node, perfect
* shutdown the drained node.
The entire cluster crashed!!! The remaining node is trying to re-connect to the iSCSI SAN without success.
* I booted the drained node. And it would not re-connect to the iSCSI SAN either. I had to force the reconnect in the iscsi control panel to make it re connect.
So why would shutting down one node kill the cluster ? Sure it was the node that had the tiered pool online, but even then, isn't failover cluster supposed to put that one back and working on the other node ?
Why did the active node lose the iSCSI connection too ? It had VMs running on it prior to the shutdown of the other node. My DC that was running on that other node is also now un available, can't ping it or anything.
So what did I miss in the configuration of the cluster ? I followed the msdn 2 node hyper-v cluster doc.
I am really worried atm since I had over the past 3 months a ton of issues with hyper-v going from using tiered storage, shutting down nodes, MAC address on the VMs and the hosts,... I thought that after hyper-v 2008, Microsoft had really made some progress
with Hyper-V but I truly regret not going with VMWare again this time around.
That cluster was supposed to go into homologation phase tomorrow at the datacenter but now I am unsure if I ll ever be able to trust it to work.
The SAN is an MD3200i which is reported as Hyper-V ready.
Any hint on where I have gone wrong would be appreciated.
Regards,
Edit: even from the host with powershell I was not able to shutdown the DC and reboot it clean. Said the integration services were not reachable... it is a 2012 R2 servers...
Edit2: One of my VM is gone ! Can't even find the file on the disks either locally on the hosts or on the SAN. WTF!!!

Actually comes across very reasonable. And I think you are right. I tend to compare Hyper-V to vSphere with vCenter included. I have not seen nor used VMM. Also true that Storage Pools and iSCSI is not Hyper-V, but to me it comes as a package just as much
as ESXi 'comes' with it.
As for burning personnal hours and money on books, I have, just as much as I go to conferences when I can and can afford it. And the only thing I would envy you, is the fact you have your colleagues to bounce idea of / lay on if necessary.
As for the few hundred box for the management suite. I believe the stack you speak of would actually cost my current company about 14k$, that is not a few hundred box. That is pretty much the cost of one of the 2 SANs. By 14k$, I mean that
we have 6 servers with 2 sockets each, running a lot of VMs, which means Datacenter licences which list price is 3.6k$. I am not even including the CALs. Or am I mistaken on the licensing ?
If VMWare, I would be going with essentials which, at the same server perimeter, would be 30% less expensive. We don't really need the full blown one at our level.
I am also locked by hardware that was ordered by my predecessor which do not provide the service we need them for. (I blame the vendor on that one, my predecessor was not an infrastructure guy). As for storage, if you are referring to SMB3 and using
a failover cluster to provide the disks to the hyper-v hosts, I agree. I am just not too sure on the technology yet and went more for safety until I can test it thoroughly in the dev environment.
I also hope Microsoft will add an easier way to set the media type on disks as well as allow for more than just SSD and HDD or even allow us to define our own.
I actually fooled the system this time around because SSD are too expensive and too high a failure rate compared to 15kRPM (yes the performance are lovely) at the moment. So I made the 15kRPMs into SSD.
For the remote management issue, i meant that actually, at this time, I have to disable the domain firewall to be able to manage the hyper-v 2012 R2. I tried hvremote, adding all the necessary rules, etc... What I did for 2012 worked perfectly fine and I
had full controls. 2012 R2 does not. I have another thread on this in the forum and I ll come back to it as soon as I can.
I don't really care for the no interface thingy, I enjoy Powershell and scripting fine :) Does a lot of automation for me :) I am used to scripting anyway and it is faster to reproduce steps that way. You do it once, and you got something you can apply with
little changes to everything.
I joined the company in November last year and I got dropped a full stack to upgrade in 6 months while maintaining the current one. Encountering the problem now is better and is, fundamentally, good, though it is time consumming.
By full stack I mean:
* Help the dev re-design the apps so it handles load better. Get out of Windows 2003 and migrate to 2012 and validate all the applications on 2012 as well as improve security.
* Implementing a monitoring system for the infrastructure and the applications.
* Upgrade SQL Server 2005 to, in this case 2012 Standard (no choice and enterprise not in the price range of the company). Converge our current test and prod environments. Optimize all the queries... And naturally validate the applications.
* Upgrade the certificate authorities so they are available on all sites. Haven't scratched that one yet.
* Design a fully site redundant architecture so that if a site goes dark we have no impact. If there is partial failure on one site, no issue either, and so on XD. I wish I had AG :)
* Implement a single windows domain on all the sites, that will be a relief :) Running 4 domains and about 10 different workgroups atm
* Upgrade the firewalls, switches, servers hardware, ... Implement the necessary networks for virtualization and improved security rules... (Don't buy SonicWalls, had a worse headache with them than Hyper-V :) )
* Migrate the users from old domain to new one. Windows 8 does not have the user migration tool anymore :(
* Plan the DR tests and processes :)
* Gotta get Hyper-V replica working as well as backups.
* And naturally make all the documentation so that if I happen to get under a bus, anyone in the company can just follow the documentation in case of an emergency.
And I am sure I am still missing some part of the environment no one knows about at some places :) Found a new network today XD.
As for the mixed VM management, I mean some that are in HA on the cluster and others that don't need and must not failover. Am sure there is a way to configure them in the failover cluster so they don't failover. I just need to spend the 15 minutes looking
into it :)
Since I have had that SAN, I spent about 5 days on the phone with Dell support. That iSCSI issue is not the first one I got :( But in the production environment, that issue has disappeared. So at this time, i have switched working on other issues. And with
the information you provided, I'll be able to know if one of the node of the cluster lose the connectivity which will help avoid this issue in the future.
And it is a very good and interesting challenge. I am just running in way to many issues doing a 10 year old system upgrade :) I was expecting to have an easier time with Microsoft Virtualization than I've had.
Oh and just for the fun, I also had VM disappear, no more file, no nothing, just poof. Have not figured how that happened yet. Had the backup so not much of an issue, but still, it went poof when the original issue happened.
Thanks for the time and the tips :)

Windows Server 2012 R2 Connection Broker migration

Hi All,
I'm in the process of a VMware to Hyper-V migration and whilst in the process rather than migrating the 2012 RDS VM's over to Hyper-V I have decided to setup a bunch of 2012 R2 VMs. My original setup was
1 x Windows Server 2012 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 VMs running RDSSH
My new environment runs
1 x Windows Server 2012 R2 VM running RDSCB, RDSGW & RDSWA
2 x Windows Server 2012 R2 running RDSSH
I have the connection broker running in HA mode for SSO purposes and publishing the correct name. This also made life easier when running the upgrade as I joined the new 2012 R2 VM to connection broker group which worked fine.
I then set the new 2012 R2 RDSCB VM as the active connection broker. At this point the old 2012 VM was decommissioned (Without the RDS roles removed). As the old 2012 VM is now offline and un contactable when I add any new session hosts to the collection
I see an error stating it can't contact the old 2012 RDSCB.
I have been through the RDS connection broker database and removed any reference to the old RDSCB VM but this hasn't helped. Does anybody have any other ideas or would you suggest re creating the collections from scratch?
Alex

Hi Alex,
To avoid future problems I recommend you wipe out the RDS deployment and recreate it again so that you will have a fresh database. There is no need to switch to HA mode just so that you can change the published name. I created a cmdlet that allows
you to change it in non-HA environments:
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
-TP

Hyper-v 2012 r2 slow throughputs on network / live migrations

Hi, maybe someone can point me in the right direction, I have 10 servers 5 Dell r210s and 5 Dell R320's, I have basically converted these servers to standalone hyper-v 2012 servers, so there is no clustering on any at the moment.
Each server is configured with 2 1Gb nics teamed via a virtual switch, now when I copt files between server 1 and 2 for example I see 100MBs throughput, but if I copy a file to server 3 at the same time the file copy load splits the 100MBs throughput between
the 2 copy processes. I was under the impression if I copied 2 files to 2 totally different servers the load would basically be split across the 2 nics effectively giving me 2Gbs throughput but this does not seem to be the case. I have played around with tcpip
large send offloads, jumbo packets, disabled vmq on the cards, they are broadcoms. :-( but it doesn't really seem to make a difference with all of these settings.
The other issue is If I live migrate a 12Gb vm machine running only 2gb ram, effectively just an o/s it takes between 15 to 20 minutes to migrate, I have played around with the advanced settings, smb, compression, tcpip not real game changers, BUT if I shut
town the vm and migrate it, it takes, just under 3 and a half minutes to move across.
I am really stumped here, I am busy in a test phase of hyper-v but cant find any definitive documents relating to this stuff.

Hi Mark,
The servers (hyper-v 2012 r2) are all basically configured with ssvmm2012R2 where they all have teamed 1Gb pNics, into a virtual switch, then there are vNics for the Vmcloud, live migration etc. The physical network is 2 Netgear Gs724T switches which
are interlinked and each servers 1st nic is plugged into the switch1 and the second nic is plugged into the switch2.See Below Image) The hyper-v port is set to independent Hyper-v load balancing.
The R320 servers are running raid 5 sas drives, the R210s have 1Tb drives mirrored. The servers all are using DAS storage, we have not moved to looking at using iscsi and san is out the question at the moment.
I am currently testing between 2x 320s and 2x R210s, I am not copying data to the vm's yets, I am basically testing the transfer between the actual hosts at the moment by copying a 4Gb file manually, After testing the live migrations I decided to test to
see the transfer rates between the servers first, I have been playing around with the offload settings and rss, what I don't understand is yesterday, the copy between the servers was running up to 228Mbs ie (using both nics) when copying
the file between the servers, and then a few hours later it only was copying at 50/60Mbs, but its now back at 113Mbs seemingly to be only using one nic.
I was under the impression if you copy a file between 2 servers the nicks could use the 2gb bandwidth, but after reading many posts they say only one nic, so how did the copies get up to 2Gb yesterday. Then again if you copy files between 3 servers, then
each copy would use one nic, basically giving you 2Gbs, but this is again not being seen.
Regards Keith

Live Migration Fails with error Synthetic FiberChannel Port: Failed to finish reserving resources on an VM using Windows Server 2012 R2 Hyper-V

Hi, I'm currently experiencing a problem with some VMs in a Hyper-V 2012 R2 failover cluster using Fiber Channel adapters with Virtual SAN configured on the hyper-v hosts.
I have read several articles about this issues like this ones:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baca348d-fb57-4d8f-978b-f1e7282f89a1/synthetic-fibrechannel-port-failed-to-start-reserving-resources-with-error-insufficient-system?forum=winserverhyperv
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
But haven't been able to fix my issue.
The Virtual SAN is configured on every hyper-v host node in the cluster. And every VM has 2 fiber channel adapters configured.
All the World Wide Names are configured both on the FC Switch as well as the FC SAN.
All the drivers for the FC Adapter in the Hyper-V Hosts have been updated to their latest versions.
The strange thing is that the issue is not affecting all of the VMs, some of the VMs with FC adapters configured are live migrating just fine, others are getting this error.
Quick migration works without problems.
We even tried removing and creating new FC Adapters on a VM with problems, we had to configure the switch and SAN with the new WWN names and all, but ended up having the same problem.
At first we thought is was related to the hosts, but since some VMs do work live migrating with FC adapters we tried migrating them on every host, everything worked well.
My guess is that it has to be something related to the VMs itself but I haven't been able to figure out what is it.
Any ideas on how to solve this is deeply appreciated.
Thank you!
Eduardo Rojas

Hi Eduardo,
How are things going ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V replica vs Shared Nothing Live Migration

Shared Nothing Live Migration allows to transport your VM over the WAN without shutting it down (how much time it takes on io intensive vm is another story)
  Hyper-V replica does not allow to perform the DR switch without shutdown operation on primary site VM !
why can't it take the VM live to the DR ?
that's because if we use Shared Nothing across the WAN, we don't use the data that Hyper-V replica can and then it also breaks everything hyper-V replica does.
Point is: how to take the VM to DR in running state, what is the best way to do that ?
Shahid Roofi

Hi Shahid,
Hyper-V Replica is designed as a DR technology, not as a technique to move VMs. It assumes that should you require it, the source VM would probably be offline and therefore you would be powering up the passive copy from a previous point in time
as its not a true synchronous replica copy. It does give you the added benefit to be able to run a planned failover which as you say, powers of the VM first, runs a final Sync then powers the new VM up. Obviously you cant have the duplicate copy of this VM
running all the time at the remote site, otherwise you would have a split brain situation for network traffic.
Like the live migration the shared nothing live migration is a technology aimed at moving a VM, but as you know offers the ability to do this without having shared storage and only requires a network connection. When initiated moves the whole
VM, well copies the virtual drive and memory before sending machine writes to both, then only to the new VM when they both match. With regards to the speed, I assume you have the SNLM setup to compress data before sending across the wire?
If you want a true live migration between remote sites, one way would be to have a SAN array between both sites synchronously replicating data, then stretch the Hyper-V cluster across both sites. Obviously this is a very expensive solution but perhaps
the perfect scenario.
Kind Regards
Michael Coutanche
Blog:
Twitter:   LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hyper-V guest SQL 2012 cluster live migration failure

I have two IBM HX5 nodes connected to IBM DS5300. Hyper-V 2012 cluster was built on blades. In HV cluster was made six virtual machines, connected to DS5300 via HV Virtual SAN. These VMs was formed a guest SQL Cluster. Databases' files are placed on
DS5300 storage and available through VM FibreChannel Adapters. IBM MPIO Module is installed on all hosts and VMs.
SQL Server instances work without problem. But! When I try to live migrate SQL VM to another HV node an SQL Instance fails. In SQL error log I see:
2013-06-19 10:39:44.07 spid1s      Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.07 spid1s      SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.07 spid1s      Write error during log flush.
2013-06-19 10:39:44.07 spid55      Error: 9001, Severity: 21, State: 4.
2013-06-19 10:39:44.07 spid55      The log for database 'Admin' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2013-06-19 10:39:44.07 spid55      Database Admin was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.33 spid36s     Starting up database 'Admin'.
2013-06-19 10:39:44.58 spid36s     349 transactions rolled forward in database 'Admin' (6:0). This is an informational message only. No user action is required.
2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail (failure): alignBuf 0x000000001A75D000, writeSize 0x400, filePos 0x156adc00
2013-06-19 10:39:44.58 spid36s     blankSize 0x3c0000, blkOffset 0x1056e, fileSeqNo 1313, totBytesWritten 0x0
2013-06-19 10:39:44.58 spid36s     fcb status 0x42, handle 0x0000000000000BC0, size 262144 pages
2013-06-19 10:39:44.58 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.58 spid36s     Error: 5159, Severity: 24, State: 13.
2013-06-19 10:39:44.58 spid36s     Operating system error 170(The requested resource is in use.) on file "v:\MSSQL\log\Admin\Log.ldf" during FixupLogTail.
2013-06-19 10:39:44.58 spid36s     Error: 3414, Severity: 21, State: 1.
2013-06-19 10:39:44.58 spid36s     An error occurred during recovery, preventing the database 'Admin' (6:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected,
contact Technical Support.
In windows system log I see a lot of warnings like this:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Microsoft-Windows-Ntfs" Guid="{3FF37A1C-A68D-4D6E-8C9B-F79E8B16C482}" />
<EventID>140</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000008</Keywords>
<TimeCreated
SystemTime="2013-06-19T06:39:44.314400200Z" />
<EventRecordID>25239</EventRecordID>
<Correlation
/>
<Execution
ProcessID="4620" ThreadID="4284" />
<Channel>System</Channel>
<Computer>sql-node-5.local.net</Computer>
<Security
UserID="S-1-5-21-796845957-515967899-725345543-17066" />
</System>
- <EventData>
<Data Name="VolumeId">\\?\Volume{752f0849-6201-48e9-8821-7db897a10305}</Data>
<Data Name="DeviceName">\Device\HarddiskVolume70</Data>
<Data Name="Error">0x80000011</Data>
</EventData>
</Event>
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{752f0849-6201-48e9-8821-7db897a10305}, DeviceName: \Device\HarddiskVolume70.
({Device Busy}
The device is currently busy.)
There aren't any error or warning in HV hosts.

Hello,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support

Hyper-V Server 2012 Migration Questions

Hello All,
This is my first post here, but I have used these forums many times for information. Sorry in advance for the long post.
I have a few questions regarding migration to Hyper-V server 2012 for my production environment. I have done quite a bit of reading, but I have a few direct questions and I would like to get some direct answers.
My current production environment consists of one PowerEdge 2900 with 2 Xeon X5460 Quad Core 3.16GHz CPUs, 24 GB of RAM and a RAID 10 consisting of 8, 500 GB HDDs for a total of 2TB of storage. I am currently running Server 2008 R2 Enterprise w/ GUI as the
Hyper-V host OS. I have 4 virtual machines all also running Server 2008 R2 Enterprise. The 4 virtual machines consist of 1 domain controller, 1 Exchange Server with Exchange 2010 Standard, 1 Server running SharePoint 2010 Enterprise and the remaining server
running IIS with FTP and HTTP.
The network topology is as follows….
Hopefully it is clear from my diagram that the Hyper-V host OS is connected to the same physical network as the domain, but is not a joined to the domain. I set it up this way because I had concerns about connectivity and manageability because the domain
controller is a guest VM. Also, the IIS server is on a completely different physical network independent of the domain.
What I would like to accomplish is the migration of the above environment to Hyper-V Server 2012 as is. I want to keep my existing guest VMs unchanged and running Server 2008 R2 for now as well as keep the existing network topology intact.
I have 3 additional servers in a separate test environment that would be able to serve as temporary storage or whatever is needed for the migration process.
Here are the two main things I would like to accomplish with this migration…
1. Make the transition from Server 2008 R2 to Hyper-V Server 2012 as a host OS.
2. Migrate virtual hard disks from .VHD to the new .VHDX format.
All that being said, I have finally come to my questions regarding this process.
First and foremost, I would obviously need to back up my current setup in case something goes horribly wrong during the migration. My question regarding the initial backup is would it be better to do a bare metal backup of the Hyper-V host or should I do
individual backups (bare-metal?) of the Guest VMs from within their operating systems?
Second, since I plan to use Hyper-V Server 2012, I will have to manage the host OS using the RSAT from a domain joined client running Windows 7 Professional. How much of a pain is it going to be to setup RSAT and manage the non-domain joined host from a
domain joined client? Is there a better way without using SCVMM or using Server 2012 w/ a GUI as the host OS?
Third, are there any concerns I should have, precautions I should take or procedures I need to do before, during or after the migration regarding the existing VMs and the new virtualized hardware environment on the same physical host?
Forth, should I use the trial version of SCVMM 2012 SP1 (or another previous version) to perform the migration? What should I be aware of using SCVMM for the migration and then discontinuing its use after the migration is complete and moving to management
using the RSAT?
Fifth, if I don’t use SCVMM for the migration, what is the best procedure for moving the VMs? Should I just copy the VHDs to a temporary storage location, install Hyper-V server 2012, copy the VHDs back, create new VMs and attach the VHDs or should I use
the export/import process?
Number six, when is the best time to migrate the VHDs to VHDX format and what would be the best method?
And finally, do I need to worry about USN rollback with a single domain controller? From my reading, this seems to be a point of disagreement. Some people say it could happen while others say it won’t. Is there any point during the migration process where
it could occur either during the copying of VHDs or from the switch to VHDX?
Again, sorry for the long post and thanks for staying with me this far. Any information would be much appreciated

1) As Jens said below with Windows Server 2012 you can simple copy the configuration files and VHDs from a 2008 R2 server to a 2012 server and import them - they one caveat to this is that any vlan configuration is lost and you have to simply re-create it.
Optionally you can also export the virtual machines from Windows Server 2008 R2 and then import them on Windows Server 2012.
2) Remote management in a workgroup does have some caveat's associated with it - take a look at
http://blogs.technet.com/b/jhoward/archive/2009/08/07/hvremote-refresh.aspx. Generally I would recommend joining the Hyper-V management operating system to the domain - not just because of these issues but for a number of other features to work properly
(see below)
3) I always recommend validating the hardware and environment after the installation before migrating critical workloads to it - testing networking, backup etc... to make sure they function as expected. Also ensure that you upgrade the integration
components in the VM's after the migration.
4) That is an option - though you might find you like SCVMM
5) Recreating VM's using existing VHD's has some issues for example the BIOS GUID changes, all of the NIC's are re-plug and played etc... When possible copying the configuration or using export is much better.
6) The sooner the better - VHDx has a number of significant advantages, you can do the migration using the Hyper-V manager UI (edit disk) or via powershell with Convert-VHD. Do keep in mind that during the conversation you need 2x the space (for the
original and the new VHDx).
7) In the past you could get into trouble if you for example snapshotted an AD virtual machine and than reverted it - taking one offline and then brining it back online was never a problem. In Windows Server 2012 we addressed this with a feature called
generation ID's.
Domain considerations... A few things to keep in mind regarding the choice to not domain join the Hyper-V server.
- You can't live migrate virtual machines
- You can't utilize Hyper-V over SMB
- Management is more difficult and less secure
-Taylor Brown -Program Manager, Hyper-V -http://blogs.msdn.com/taylorb

Hyper V Lab and Live Migration

Hi Guys,
I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
The problem I have is my shared storage is a bit of a cheat as I have one disk assigned in each host and each host has starwinds virtual SAN installed. The hostA has an iscsi connection to hostB storage and visa versa.
The issue this causes is when the hosts shutdown (because this is a lab its only on when required), the cluster is in a mess when it starts up eg VMs missing etc. I can recover from it but it takes time. I tinkered with the HA settings and the VM settings
so they restarted/ didnt restart etc but with no success.
My question is can I use something like SMB3 shared storage on one of the hosts to perform live migrations but without a full on cluster? I know I can do Shared Nothing Live Migrations but this takes time.
Any ideas on a better solution (rather than actually buying proper shared storage ;-) ) Or if shared storage is the only option to do this cleanly, what would people recommend bearing in mind I have SSDs in the hyper V hosts.
Hope all that makes sense

Hi Sir,
>>I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
As you mentioned , you have 2 hyper-v host and use starwind to provide ISCSI target (this is same as my first lab environment ) , then I realized that I need one or more host to simulate more production scenario .
But ,if you have more physical computers you may try other's progects .
Also please refer to this thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e9f81a9e-0d50-4bca-a24d-608a4cce20e8/2012-r2-hyperv-cluster-smb-30-sofs-share-permissions-issues?forum=winserverhyperv
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Storage Live Migration: Copy instead of move?

Have a 2012 R2 Hyper-V Cluster with a HP MSA 2000 Storage. No storage pools or storage spaces, just 4 LUN's with NTFS Volumes that are all converted to CSV's.
Have to perform VM migration from VM's that resides on a CSV with an underlying RAID 5 volume to another CSV with an underlying RAID 50 volume. Could perform the operation without any error from the failover cluster manager (move - virtual machine storge) on
the VM.
The problem is that when I check C:\ClusterStorage\Volume1 (the old place of the VM) and C:\ClusterStorage\Volume2 (the new place of the VM), all VM files are still in both locations! Apparently, a "Copy" operation instead of a "move" operation
was performed.
- Why are the source files not have been deleted after the successful storage migration?
- Is it safe to manually delete the VM files in C:\ClusterStorage\Volume1?
Thank you in advance for any help.
Franz

Hi FranzSchenk,
To perform a move, FOCM first copys the files over to the new location and then moves the mahine over to the new location with all memory and machine writes before then removing the old files. If the files haven't been removed (this does happen)
it could be permission's that stop the files being removed.
It would be worth checking the running VMs and checking where its pointing for the virtual drives and perhaps look at where its BIN file is for memory and where the XML machine configuration is located. If all are pointing to the new location
then it would be safe to delete the old files.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Hi Michael
Do you have more specific information what kind of permission issue you mean, and how we can correct that? And why is no warning or error message visible or in the eventlogs that the source files have not been deleted during the live strorage migration?
Kind regards, Franz

Hyper-V Live Migration Compatibility with Hyper-V Replica/Hyper-V Recovery Manager

Hi,
Is Hyper-V Live Migration compatible with Hyper-V Replica/Hyper-V Recovery
Manager?
I have 2 Hyper-V clusters in my datacenter - both using CSVs on Fibre Channel arrays. These clusters where created and are managed using the same "System Center 2012 R2 VMM" installation. My goal it to eventually move one of these clusters to a remote
DR site. Both sites are connected/will be connected to each other through dark fibre.
I manually configured Hyper-V Replica in the Fail Over Cluster Manager on both clusters and started replicating some VMs using Hyper-V
Replica.
Now every time I attempt to use SCVMM to do a Live Migration of a VM that is protected using Hyper-V Replica to
another host within the same cluster,
the Migration VM Wizard gives me the following "Rating Explanation" error:
"The virtual machine virtual machine name which
requires Hyper-V Recovery Manager protection is going to be moved using the type "Live". This could break the recovery protection status of the virtual machine.
When I ignore the error and do the Live Migration anyway, the Live migration completes successfully with the info above. There doesn't seem to be any impact on the VM or it's replication.
When a Host Shuts-down or is put into maintenance, the VM Migrates successfully, again, with no noticeable impact on users or replication.
When I stop replication of the VM, the error goes away.
Initially, I thought this error was because I attempted to manually configure
the replication between both clusters using Hyper-V Replica in Failover Cluster Manager (instead of using Hyper-V Recovery Manager).
However, even after configuring and using Hyper-V Recovery Manager, I still get the same error. This error does not seem to have any impact on the high-availability of
my VM or on Replication of this VM. Live migrations still occur successfully and replication seems to carry on without any issues.
However, it now has me concern that Live Migration may one day occur and break replication of my VMs between both clusters.
I have searched, and searched and searched, and I cannot find any mention in official or un-official Microsoft channels, on the compatibility of these two features.
I know vMware vSphere replication and vMotion are compatible with each otherhttp://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-8006BF58-6FA8-4F02-AFB9-A6AC5CD73021.html.
Please confirm to me: Are Hyper-V Live Migration and Hyper-V Replica compatible
with each other?
If they are, any link to further documentation on configuring these services so that they work in a fully supported manner will be highly appreciated.
D

This can be considered as a minor GUI bug.
Let me explain. Live Migration and Hyper-V Replica is supported on both Windows Server 2012 and 2012 R2 Hyper-V.
This is because we have the Hyper-V Replica Broker Role (in a cluster) that is able to detect, receive and keep track of the VMs and the synchronizations. The configuration related to VMs enabled with replications follows the VMs itself.
If you try to live migrate a VM within Failover Cluster Manager, you will not get any message at all. But VMM will (as you can see), give you an
error but it should rather be an informative message instead.
Intelligent placement (in VMM) is responsible for putting everything in your environment together to give you tips about where the VM best possible can run, and that is why we are seeing this message here.
I have personally reported this as a bug. I will check on this one and get back to this thread.
Update: just spoke to one of the PMs of HRM and they can confirm that live migration is supported - and should work in this context.
Please see this thread as well: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/29163570-22a6-4da4-b309-21878aeb8ff8/hyperv-live-migration-compatibility-with-hyperv-replicahyperv-recovery-manager?forum=hypervrecovmgr
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Hyper-v Live Migration not completing when using VM with large RAM

hi,
i have a two node server 2012 R2 cluster hyper-v which uses 100GB CSV, and 128GB RAM across 2 physical CPU's (approx 7.1GB used when the VM is not booted), and 1 VM running windows 7 which has 64GB RAM assigned, the VHD size is around 21GB and the BIN file
is 64GB (by the way do we have to have that, can we get rid of the BIN file?).
NUMA is enabled on both servers, when I attempt to live migrate i get event 1155 in the cluster events, the LM starts and gets into 60 something % but then fails. the event details are "The pending move for the role 'New Virtual Machine' did not complete."
however, when i lower the amount of RAM assigned to the VM to around 56GB (56+7 = 63GB) the LM seems to work, any amount of RAM below this allows LM to succeed, but it seems if the total used RAM from the physical server (including that used for the
VMs) is 64GB or above, the LM fails.... coincidence since the server has 64GB per CPU.....
why would this be?
many thanks
Steve

Hi,
I turned NUMA spanning off on both servers in the cluster - I assigned 62 GB, 64GB and 88GB and each time the VM started up no problems. with 62GB LM completed, but I cant get LM to complete with 64GB+.
my server is a HP DL380 G8, it has the latest BIOS (I just updated it today as it was a couple of months behind), i cant see any settings in BIOS relating to NUMA so i'm guessing it is enabled and cant be changed.
if i run the cmdlt as admin I get ProcessorsAvailability : {0, 0, 0, 0...}
if i run it as standard user i get ProcessorsAvailability
my memory and CPU config are as follows, hyper-threading is enabled for the CPU but I dont
think that would make a difference?
Processor 1 1 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 4 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 9 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 12 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 1 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 4 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 9 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 12 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor Name
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
Processor Status
OK
Processor Speed
2400 MHz
Execution Technology
12/12 cores; 24 threads
Memory Technology
64-bit Capable
Internal L1 cache
384 KB
Internal L2 cache
3072 KB
Internal L3 cache
30720 KB
Processor 2
Processor Name
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
Processor Status
OK
Processor Speed
2400 MHz
Execution Technology
12/12 cores; 24 threads
Memory Technology
64-bit Capable
Internal L1 cache
384 KB
Internal L2 cache
3072 KB
Internal L3 cache
30720 KB
thanks
Steve

Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
I've been searching for a "best practices" article for this but have been coming up short. The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
to different hardware without failover cluster volumes.
If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
Currently, my approach is as follows:
1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
3. Stop the VMMS service on the 2008 r2 hostnodes
4. copy the virtual machine files and folders over to the new failover cluster volumes
5. Import vm's into server 2012 r2 hyper-v.
Any feedback on the opertain I have in mind would be helpful.
Thank you,
Rob

Hi Rob,
Yes , I agree with that "file copy " can achieve migration.
Also you can try "copy cluster wizard " :
https://technet.microsoft.com/en-us/library/dn530779.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Hyper-V Migration

Similar Messages

Maybe you are looking for