locked
Live Migration fails with 2TB VM RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I'm running into a problem migtrating a large 2TB VM on a volume which is 2.3TB.

    The migration fails at the end of the process whether I do a Live Migration or Quick Migration.  At the same time, on the same cluster node I have smaller VMs which migrate fine.

    When I Move the large VM to a different node, it looses the Virtual Network even though the Virtual Network name is identical on each node.  (There is an entry in the Notes field, though it appears I can't remove the entry while servers are running on that node.)

    This problem appears on two different clusters.  The cluster nodes are all running Windows Server 2008 R2 SP1 Data Center Hyper-V.  One cluster has two nodes, the other is a four node cluster.  Each cluster has a 2, 2TB VMs and at least 3 smaller VMs.

    Any thoughts on how to correct this?

    Thanks!

    • Moved by BrianEhMVP Friday, September 27, 2013 4:28 PM
    Friday, September 27, 2013 4:08 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi! By a 2TB machine you mean a VM who has a 2TB vhd? This is the maximum ammount of size for a VHD and this might be a part of your problem. Also the partition where you are moving the VM supports files larger than 2TB? Most of file systems don't.

    If you can, try to split the data in 2 or more vhd's.

    Good luck!

    Luis Ezequiel Pignataro - Especialista en IT de entornos Microsoft

    Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ud. asume los riesgos.

    This posting is provided "AS IS" with no warranties, and confer no rights. You assume all risk for your use.

    Friday, September 27, 2013 5:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Luis.

    Yes, I do mean a 2TB VHD which I understand is the max supported size for a VHD.  BUT, my understanding is it IS supported, so the question still remains, why doesn't it migrate?  The volume is formatted as GPT.

    Thanks again for the reply!

    Friday, September 27, 2013 5:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If the partition is formatted as GPT I don't see any reason for this behavior... You can do a offline migration? Remove the VHD from the VM, and moveit independently.

    I think it fails because you are pushing the limits, and as we know this things can happen haha

    Luis Ezequiel Pignataro - Especialista en IT de entornos Microsoft

    Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ud. asume los riesgos.

    This posting is provided "AS IS" with no warranties, and confer no rights. You assume all risk for your use.

    Friday, September 27, 2013 5:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    the original location of the VHD you said is GPT formatted drive what about the destination? Maybe it's time to move to a vhdx 64tb max size, but that's a huge amount of data.
    Saturday, September 28, 2013 12:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Darren,

    Thanks for the reply, but I'm not sure I follow your question about formatting of the destination, probably because I wasn't clear.

    My cluster nodes have an iSCSI connection to a 2.2TB GPT formatted Lun hosted on a NetApp FAS2040. To include this LUN in my cluster its formatted via the Windows 2008R2SP1 DataCenter nodes as a 2252.76 GB NTFS partition. On this partition I created my 2TB VHD and virtual machine.

    All nodes in the cluster can take ownership of this cluster shared volume. So in my mind the VM/VHD stays on the same CSV - yes?

    Also the VM/VHD can be hosted on all nodes if I take it off-line move it to the next node and re-apply the Virtual Network settings. But it fails to Live Migrate when the process tries to bring it online after the migration process reaches 100%.

    Does this spark any ideas to solve the Live Migration failures?

    Thanks!

    Monday, September 30, 2013 2:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    So, what is the actual error being reported in the Event logs after the failed migrate?

    Jason A.

    Monday, September 30, 2013 6:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jason,

    There's not much, basically there are four errors listed but without any error numbers, just event IDs, as follows. But it starts with an Information entry:

    Event ID: 22508 , Source: Hyper-V-Worker '8984A81C-A0E7-474F-AB03-78C7BB56C240' migrated with a Brown-Out time of 453.136 seconds.

    Event ID: 22026 , Source: Hyper-V-Worker The live migration did not succeed at the remote node.

    Event ID: 21100 , Source: Hyper-V-Worker Live migration of 'SData2' did not succeed. (Virtual machine ID 8984A81C-A0E7-474F-AB03-78C7BB56C240)

    Event ID: 21111, Source: Hyper-V-High-Availability 'VM SData2x' live migration did not succeed at the source.

    Event ID 21502, Source: Hyper-V-High-Availability 'VM SData2x' live migration did not succeed at the source.

    What's it suggest to you?

    Thanks!

    • Edited by DCBB Monday, September 30, 2013 8:03 PM more Info
    Monday, September 30, 2013 7:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    FYI,

    There's a bit more listed on the target server. But it also starts with an Information entry:

    Event ID: 21120 , Source: Hyper-V-High-Availability 'SData2' Microsoft Emulated Ethernet Controller started successfully. (Virtual machine ID 8984A81C-A0E7-474F-AB03-78C7BB56C240)

    Event ID: 12080 , Source: Hyper-V-Worker 'SData2' Microsoft Synthetic Ethernet Port (Instance ID {49F39284-399B-40C0-B934-E2AB515EBD58}): Failed to restore with Error 'The system cannot find the path specified.' (0x80070003). (Virtual machine ID 8984A81C-A0E7-474F-AB03-78C7BB56C240)

    Event ID: 21100 , Source: Hyper-V-Worker Live migration of 'SData2' did not succeed. (Virtual machine ID 8984A81C-A0E7-474F-AB03-78C7BB56C240)

    Event ID: 21107, 'VM SData2x' failed to start.

    Event ID 21114, 'VM SData2x' live migration did not succeed at the destination.

    Event ID 22506, Migration failed at target for cluster resource 'VM SData2x' with events ''VM SData2x' live migration did not succeed at the destination.'. (Virtual Machine ID 8984A81C-A0E7-474F-AB03-78C7BB56C240)

    Event ID 19050, 'SData2' failed to perform the operation. The virtual machine is not in a valid state to perform the operation. (Virtual machine ID 8984A81C-A0E7-474F-AB03-78C7BB56C240)

    The last listed event ID, repeats 8 more times

    What's it suggest to you?

    Thanks!

    Monday, September 30, 2013 8:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'd say take a look at this KB: Hyper-V Live Migration fails on Windows Server 2008 R2 with Event ID 12080

    This could be what's causing the problem.  Maybe try removing the vNIC, then re-adding it through the Cluster Manager MMC?

    Jason A.

    • Marked as answer by DCBB Tuesday, October 1, 2013 4:59 PM
    Tuesday, October 1, 2013 12:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Jason!

    You're my hero! Need to test it a little more, but that seems to have corrected the situation!!

    Thanks for the suggestion!! 

    Tuesday, October 1, 2013 4:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You're quite welcome, glad I could help!

    Jason A.

    Tuesday, October 1, 2013 6:33 PM