Moving VMs from Standalone Hyper-V to Hyper-v Failover Cluster

Hello All.................I need to move Virtual Machines from Standalone Hyper-V based on Windows Server 2012 R2 to a Hyper-V Failover Cluster based on Windows Server 2012 R2.
- The VMs OS is Windows Server 2012 R2
- Applications installed on VMs are SCCM, SCOM, SharePoint, etc.
1. I am looking for a Checklist that I can run through and move them. To make sure I do not miss out anything.
2. Would a downtime be required in this scenario while the VM is being moved?
3. What requires special attention in this scenario?

Thanks for the reply.
So, I do not need to do anything and just simply add both the cluster and standalone into VMM and then simply use the Move option. Please, confirm if I have understood it correct.
Yes. But be carefull. First shut down your VM's
if possible and configure them in such a way they don't automatically start. If you install the SCVMM Agent, some Hyper-V related services are restarted, when some VMs start during that process you system may stall. I have seen this multipe times.
There is another dirty option that worked of us perfectly. Export the VMs. Then import those VMs to a local disk on one Hyper-V Server. Refresh the Hyper-V Server and Virtual Machines on that Hyper-V Server. Give it a few minutes. Then do
a Live Migration while at the same time makeing it "Highly Available" by moving it to your CSV. Works flawlessly. DO NOT IMPORT THE VMS TO YOUR CSV, otherwise you can't change it to "Highly Avaiable" unless you have
two CSVs. Importing it straight to a CSV does not make them Highly Available.
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

Similar Messages

Moving VMs From One Hyper-v 2012 R2 to Another Hyper-v 2012 R2

Hi everyone, was hoping for some help in something I am confused about
Currently I have SERVER1 running hyper-v 2012 R2
I want to move all my VMs (around 20) to SERVER2 also running Hyper-v 2012 R2
But I am confused on the best way to do this
1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
2) Should I do an export and then import
3) should I setup replication from Server1 to Server2 and then do a failover?
4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
thanks

Hi everyone, was hoping for some help in something I am confused about
Currently I have SERVER1 running hyper-v 2012 R2
I want to move all my VMs (around 20) to SERVER2 also running Hyper-v 2012 R2
But I am confused on the best way to do this
1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
2) Should I do an export and then import
3) should I setup replication from Server1 to Server2 and then do a failover?
4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
thanks
It all depends on your environment and your current Hyper-V configuration.
I asume both servers are domain-member of the same domain and don't use SCVMM. If so, then make sure you do the following:
First enable the "Live Migration" feature in the Hyper-V settings on both Hyper-V Servers.
Make sure both Hyper-V Servers have a vSwitch configured with the same display name and connectivity. They must be somewhat identical, but not everything. As long as the connectivity is the same.
Make sure you have a location to store the VM files on SERVER2.
Then do a Live Migration from SERVER1 to SERVER2, follow the wizard. By using the Hyper-V Manager console on SERVER1.
NOTE1: Without computer certificates and Kerberos configuration on your Live Migration settings you cannot initiate a Live Migration from the Hyper-V Manager cconsole on SERVER2. With the default configuration, you have to login on (or connect
to) SERVER1 en then initiate the Live Migration.
NOTE2: If you can't configure the vSwitches the same. Then you have to shut down the VMs and do a Quick Migration. Then re-configure the VM network properties and power on the VMs.
I hope this information will help you goin on. If you need more detailed information use the following link:
Configure Live Migration and Migrating Virtual Machines without Failover Clustering
http://technet.microsoft.com/nl-nl/library/jj134199.aspx
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

Manually Moving VMS from HOST to HOST *WITH* Shared SAS Storage

Hi,
Environment will be 2 Windows 2012 R2 Hyper-V servers.
They will be connect via shared SAS. These are two identical IBM servers with shared SAS storage
I am hoping to eliminate using MS Clustering of the Hyper-V servers just to keep things straight forward.
In the event, I had a complete failure of one of the physical server Hyper V hosts, I was hoping be able to manually add/import (not sure what the terminology is here) and run the virtual machines on the second host until the first is repaired.
If there is third party software that can do this, I would entertain it.
In VMware (I had two hosts and would manually remove them from inventory on one server and add them to a second server).
Ideally, if I could keep both Hyper-V hosts in a Windows Workgroup and as vanilla as possible.
Thanks in Advance,
G

Hi,
Sorry for the late reply. I have been researching all I can. And thanks to all for your patience and help!
Let's start with the hardware to help paint the picture:
2 @ IBM X3550 M4
1 @ IBM V3700
The two X3550's are going to be connected via 6GB SAS Cards (2/server for redundacy)
Current environment (residing on VMWare with older IBM Xseries servers DS3524 connect via SAS connections) 40 users total.
Windows servers are:
1 @ SBS 2011 (One and only AD/PDC)
2 @ Windows 2008 Servers that are CRM (these are Windows Member Servers)
5 @ Windows 2003 servers that are going to be replace with Windows 2008 Servers (these are Windows Member servers) (low usage servers)
Just to recap:
The current environment running VMware 4.1 has both IBM X3500 servers able to see a single 1.5 TB lun (SAS connected) presented by the DS3524.
Currently, in VMware, I can see the same LUN on both servers. I have all my VM's on HOSTA, if HOSTA should suffer a system board failure, I manually connect to HOSTB with the VMware client and add the VMs that I can see on the shared LUN
and add them to HOSTB.
My understanding is that its strongly recommend that my DC (not sure if they are implying PDC or BDC) on a physical server. My hesitation is now I have to introduce a DC to SBS 2011 and manage a physical server and deal with with SBS 2011's quirks.
So I was hoping that if I presented a LUN to both my HyperV hosts (In a Workgroup), and created on my VMs on hostA, if something went very bad with HOSTA, I could connect to HOSTB and "Import" them and manually start the VMs, especially since
SBS 2011 is sensitive.
The client is okay with some downtime, so if the process is supported and works, then I am okay with doing the work.
Clustering or even Replicas will add:
Complexity to the environment
Patching needs to be carefully planned as it would not look good to have to failover due to a Windows update on the primary host.
The tech's that support that environment will now need to know about Clustering and/or Replication ontop of the SAN stuff
I am looking at Veeam, Double-Take to see if they can work with 2 @ 2012 Hyper-V hosts configured in a Workgroup.
The SBS 2011 is the "hinge" that will make or break the success of this project. I personally love the way 2012 Hyper-V works, but it would be great if a physical server outside of the HyperV hosts was not required.
Thanks !
G

0x0000007a Error for VMS inside a Hyper-V server in a failover cluster

Hi All,
This is my first time posting a question on this forum. Will provide more details if necessary.
Would appreciate any help for the below problem:
We have two servers operating on Win 2012 R2 datacenter. However one of them(host2) had all it's VMs crash with error code 0x0000007a. While the OS of the host itself was ok in a sense, trying to run any application or opening windows explorer would result
in a hang, We can still use ctrl+alt+delete to log off.
Both servers have been installed with similar windows update patches, and all the configurations are the same. However Host01 is running fine.
Booting on safe mode let's us run the server fine. Did a chkdsk /r and it found some errors on the disk, I did a restart to let it try and fix the issue but issues are still the same.
Dell hardware check came up with nothing.
Thank you!
Anton

Hi
Can you check if there are any hardware errors logged in event viewer?
Perhaps you have a faulty memory module. I had a similar issue with my host and it ended up being a combination of reseating the ram and replacing the Quad network adapter.
Are both you dells on the latest SUU?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

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] .

Guest VM failover cluster on Hyper-V 2012 Cluster does not work across hosts

Hi all,
We are evaluating Hyper-V on Windows Server 2012, and I have bumped in to this problem:
I have a Exchange 2010SP2 DAG installed on 2 vms in our Hyper-V cluster (a DAG forms a failover cluster, but does not use any shared storage). As long as my vms are on the same host, all is good. However, if I live migrate or shutdown-->move-->start one
of the guest nodes on another pysical host, it loses connectivity with the cluster. "regular" network is fine across hosts, and I can ping/browse one guest node from the other. I have tried looking for guidance for Exchange on Hyper-V clusters but have not
been able to find anything.
According to the Exchange documentation this configuration is supported, so I guess I'm asking for any tips and pointers on where to troubleshoot this.
regards,
Trond

Hi All,
so some updates...
We have a ticket logged with Microsoft, more of a check box exercise to reassure the business we're doing the needful. Anyway, they had us....
Apply hotfix http://support.microsoft.com/kb/2789968?wa=wsignin1.0 to both guest DAG nodes, which seems pretty random, but they wanted to update the TCP/IP stack...
There was no change in error, move guest to another Hyper-V node, and the failover cluster, well, fails with the following event ids I the node that fails...
1564 -File share witness resource 'xxxx)' failed to arbitrate for the file share 'xxx'. Please ensure that file share '\xxx' exists and is accessible by the cluster..
1069 - Cluster resource 'File Share Witness (xxxxx)' in clustered service or application 'Cluster Group' failed
1573 - Node xxxx failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available
The other node stays up, and the Exchange DB's mounted on that node stay up, the ones mounted on the way that fails failover to the remaining node...
So we then
Removed 3 x Nic's in one of the 4 x NIC teams, so, leaving a single NIC in the team (no change)
Removed one NIC from the LACP group on each Hyper-V host
Created new Virtual Switch using this simple trunk port NIC on each Hyper-V host
Moved the DAG nodes to this vSwitch
Failover cluster works as expected, guest VM's running on separate Hyper-V hosts, when on this vswitch with single NIC
So Microsoft were keen to close the call, as there scope was, I kid you not, to "consider this issue
resolved once we are able to find the cause of the above mentioned issue", which we have now done, as in, teaming is the cause... argh.
But after talking, they are now escalating internally.
The other thing we are doing, is building Server 2010 Guests, and installing Exchange 2010 SP3, to get a Exchange 2010 DAG running on Server 2010 and see if this has the same issue, as people indicate that this is perhaps not got the same problem.
Cheers
Ben
Name                   : Virtual Machine Network 1
Members                : {Ethernet, Ethernet 9, Ethernet 7, Ethernet 12}
TeamNics               : Virtual Machine Network 1
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
Name                   : Parent Partition
Members                : {Ethernet 8, Ethernet 6}
TeamNics               : Parent Partition
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Heartbeat
Members                : {Ethernet 3, Ethernet 11}
TeamNics               : Heartbeat
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Virtual Machine Network 2
Members                : {Ethernet 5, Ethernet 10, Ethernet 4}
TeamNics               : Virtual Machine Network 2
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
A Cloud Mechanic.

VM will not boot after moving using Failover Cluster Manager - "a disk read error occurred......"

My current Configuration:
3 node cluster, using clustered shared storage and about 22 VM's.   The Host servers are running 2012 Data Center while all guest are running 2012 Standard. The SAN is EqualLogic and we are using HIT Kit 4.5.
I have a CSV that is running out of space, so I created another CSV so that I could move some of the VM's to a new home.    I tested this by creating a test VM, and moved it successfully 3 times.     I then moved an actual
LIVE VM and while it seemed to move ok, it will now not start.   The message is "a disk read error occurred Press ctrl+alt+del to restart".     I moved the test VM and it failed as well.
I have read several things about this, but nothing seems to relate to my specific issue.   I have verified that VSS is working and free of errors as well.    From the Settings menu for the VM, if I select "Inspect" the drive,
the properties all look fine.    It is a VHDX and both the current file size and maximum disk size seem correct.
The VM's were moved using the "move - virtual machine storage" option within Failover Cluster Manager.
Suggestions?
Thanks.

Lets see if I can answer all of those and I appreciate the brain storming.   This really needs to work, correctly.
1. The Storage is moving.
2.   VM's and SAN are on same device.
3. No, my Clustered Shared Volume, CSV, is out of room, (more one that later)
4. No, I actually have 2 sans grouped together.   However, I'm moving the VM', form one CSV to another CSV on the Same san. EqualLogic PS 6110 is the one I am trying to move VMS around on, and the other SAN not involved in any way except
for it is in a SAN group is an EqualLogic PS6010.
5. No error During move, it took about 5-10 minutes, no error messages.   Note, I did a test and it worked GREAT 3 times.   Now both a live VM, and the test VM are doing the same thing.
6. No, the machine is not to large.   The test making was a 50 gig drive, just 2012 standard installed with updates.   The live VM was a 75 gig VM that was my Trend Micro Server, or anti-virus host.
7. Expand the existing SCV?   Yes I should be able to, but there is an issue there.   The volume was expanded correctly, Equallogic sees the added space, Fail Over cluster manager sees the added space, however disk manager only
sort of does.    When looking at disk manager, there are 2 areas that tell you a little bit about the drive.   The top part and then the bottom part.   The top part only shows 500G, the original size, while the bottom part
says that it is 1 TB in size.   I call Dell's technical support and after they looked at it I was told by the technician that they had seen this a couple of times and the only way to fix it was to move all the VM's to another CSV and delete the troubled
CSV.   I thought about adding more space to the troubled CSV, but its on a production server with about 12 VM's running on it and I did not want to take a chance.   The Trend VM was running on CSV-1 and working fine.
I must admit that the test VM, was on CSV-2.    I moved the Test VM from csv-2 to csv-3 back and forth several times with no errors.   The Trend Server was on CSV-1 and was moved to CSV-3, however it failed. Again, I then moved
the test VM from CSV-2 to CSV-3 and it failed the same way.   I could not test the "TEST - VM" on csv-1 due to csv-1 not having enough space.
8.   I did disable the network from the VM to see if that mattered it did not.
9.   I have not yet had a chance to connect the VHDX to a new VM, but I will do that in about an hour, hopefully.    Once I am able to test that suggestion I will post the results as well.
Again, thanks for all the suggestions and comments, as I had rather have lots to look at and try.   I hope I answered them well enough.
Kenny

Is it possible to Migrate Live VMs from a Windows 2012 Hyper-V Cluster to a different 2012 R2 Cluster?

At the moment I'm in a bit of dilemma because I know that Windows 2012 supports "Shared Nothing Live Migration" but recently I got to know that this feature is available for stand alone Hyper-V Servers. My Setup is that I have
3 Servers running Windows Server 2012 Hyper-v Failover Cluster and I need to migrate everything to a new cluster running on Windows Server 2012 R2 and offcourse some VMs can't be turned off during migration so I need to do this live during production hours.
Another note is that both clusters will be running on the different LUNs since each cluster has its own CSVs. I need to know if it is possible to migrate such VMs/Roles Live without have any downtime of the VMs/Roles?

Yes, but one exception - live migration works only on "compatible cpu's". There actually is a setting in CPU for forcing compatibility
mode. If that is not set, and you mvoe for example from AMD to Intel, then - this is not possible in live migration, cluster or not.

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]

Share my WiFi internet (from Windows 10 TP) to Hyper-V

Hi,
Since 1 month I'm using Windows 10 Technical Preview on my laptop.
Before I used Windows 8.1. There I had a Hyper-V. Thank of this blog(http://blog.credera.com/technology-insights/microsoft-solutions/using-your-windows-8-wireless-connection-inside-hyper-v/) I share the Internet of my Laptop to Hyper-V
I copy the hard disk of VM (with Windows Server) which I create at Windows 8.1 and I'm using it in Windows 10. The VM is working but I can't share the WiFi internet to it. I tried the manual from blog but without success.
After that I try to create a External Virtual switch. In this way the internet is not working on the Laptop and on the VM.
--------------------------------------EDIT----------------------------------------
Here is what I'm doing with all settings:
1. Enter to "Hyper-V Manager" > Select "Virtual Switch Manager" > "New virtual network switch" > "Internal" >"Create Virtual Switch" > Set name to "My Virtual switch" > Click
"OK"
2. Open "Network connection"> Select my Wi-Fi adapter and click on "Properties" > Open "Sharing" tab > Check checkbox "Allow other users to connect through this computer's Internet connection" > Select
from dropdown list "vEthernet (My Virtual switch)" > click "OK"
3. Now on my Wi-Fi Adapter I can see "Shared"
4. In "Network and Sharing Center", I have my Wi-Fi Adapter with "Access type: Internet" and "vEthernet (My Virtual switch)" with "Access type: No network access"
4.1 In "vEthernet (My Virtual switch)" Properties: "Hyper-V extensible Virtual Switch" and "Microsoft Network Adapter Multiplexor Protocol" are unchecked. The rest are checked. In "IPv4" is selected "Use
the following IP address" but they are blank. The same with DNS server addresses
5. In "Hyper-v Manager" I'm selecting my VM and opening "Settings"
5.1. "Add Hardware" > "Legacy Network Adapter" > "Add" > In "Virtual Switch" dropdown I select "My Virtual switch" (The "Enable virtual LAN identification" checkbox is unchecked ) > "OK"
6. Now I'm starting my virtual machine and I don't have access to Internet
I see that MAC of my "vEthernet (My Virtual switch)" is different than this of my Adapter in VM
Do you have some idea how can I share the WiFi Internet from Windows 10 Technical Preview to Hyper-V? It will be brilliant if I can have Internet on both machines?

On Tue, 20 Jan 2015 09:41:59 +0000, ko5monaft wrote:
I'm using client version of Windows 10.
Yesterday this question was in Hyper-V. I don't know why it's now in "Windows Server Technical Preview"
A Hyper-V moderator moved your question and has moved it to the wrong
forum. Although your question is about Hyper-V the Hyper-V forum is only
for released versions of Hyper-V. Since you're asking a question about
Client Hyper-V on Windows 10 then the correct forum to move it to would
have been one of the client Windows 10 forums.
Paul Adare - FIM CM MVP
Fachbegriffe der Informatik, Pull:
Das Notebook ruckartig am Kabel vom Tisch ziehen.
http://www-605.ibm.com/misc_includes/en_SG/drop_test.pdf

How to recover from accidental VM role removal in Hyper-V Failover Cluster Manager?

Hello
My VMs are still available in Hyper-V Manager but they are no longer available in Cluster Manager. I am curious if there's a way to move them back into the Failover Cluster Manager while retaining their GUIDs?
I know I can manually create a new VM and add the existing VHD but that process recreates a new GUID causing the VM to regard the stuff I wanted as old.
I have tried to follow
http://blogs.technet.com/b/heyscriptingguy/archive/2013/10/14/recovering-virtual-machines-in-hyper-v-server-2012-r2-part-1.aspx but I am curious if there's a faster way to do this without becoming a scripting genius overnight.
Thanks,
Prince

Thanks for the reply but that does not help.
I am not looking to move my VMs to a remote Host but rather looking to repopulate the fail-over cluster manager with the existing VMs in Hyper-V Manager. In a sense, I am looking to reuse the existing GUID without creating new ones.
Again, my VMs are alive in Hyper-V Manager but are currently not available in Failover Cluster Manager.
Any scripting assistance will be greatly appreciated.
Thanks,
Prince

Event Logs of VMs Migration in Failover Cluster of Hyper-V Hosts

Hello All,
We're running Failover Cluster of Hyper-V hosts of Windows Server 2012 R2. Using SCVMM 2012 R2 with UR5 for management.
If any host gets down unexpectedly (due to any reason power/bugcheck/hardware failure or what so ever), then the VMs on that host, of course, get migrated (either quick or live) to some other host within the cluster.
I want to have logs/events of this VMs migration. I want to know that which of the VMs were residing on that host at that time of failure. Of course, we can't have this info in the Cluster events is Failover Cluster Manager. I am unable to find this info
anywhere. I have searched in Event Viewer --> Administrative Roles --> Hyper-V. I have searched a lot in the SCVMM, but no success.
Please help me in finding the exact location of these logs/events. I would also like to know that if the VM was quick migrated or live migrated, and to which host the VM got migrated.
I'd be highly grateful.
Thanks in anticipation.
Regards,
Hasan Bin Hasib

This post was cross-posted in the clustering forum. As noted in that forum, a failure of a host does not initiate a quick or live migration. Migration requires both the source and destination nodes be operational during the entire migration
process. Should a host fail, it is impossible for that host to participate in a migration. In the case of a host failure, the VM is restarted on another node of the cluster. You can still use the information provided by Elton for viewing
events in the event log. If you want to see the exact sequence of log entries, perform quick/live migrations in a lab and notices the changes in the event log. You can also fail a host and see the sequence of log entries.
. : | : . : | : . tim

Removal of Node from Hyper-V Failover Cluster

Hello All....................I have a 8 node Hyper-V Failover Cluster based on Windows Server 2012 R2. I am facing some issues with one of the servers, so I have decided to take that node out of the Hyper-V Failover cluster. I would appreciate if someone
could share the steps that I should take to ensure smooth removal of node especially with respect to CSV Volume and Quorum. THanks.

Hi Sir ,
Please try the following command (before you do this please live migrate VMs to another nodes ):
Remove-ClusterNode –Name node4 -Force
For this command please refer to :
http://technet.microsoft.com/en-us/library/hh847251.aspx
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.

LUN can't be accessed after move it to another Hyper-V Failover Cluster without "remove from cluster shared volumes" on the original cluster

Hi all,
I have a old cluster, let's call it cluster01, and a new cluster, cluster02. There is a LUN attach to cluster01 as a CSV volume. I forgot to "remove from cluster shared volumes" in Failover Cluster console, then power off the cluster01 and
attach the LUN to the cluster02. Now the LUN can't be accessed in cluster02, it show as a RAW disk. I tried to attach the LUN to it's original cluster cluster01 but can't read it too.
Is there any way to get it back?

Hi Zephyrhu,
Can you run Clear-ClusterDiskReservation powershell cmdlet and see that helps?
http://technet.microsoft.com/en-us/library/ee461016(WS.10).aspx
Thanks,
Umesh.S.K

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 )

Moving VMs from Standalone Hyper-V to Hyper-v Failover Cluster

Similar Messages

Maybe you are looking for