none
Move VMs from one cluster to another cluster in different forest and domain RRS feed

  • Question

  • Hi all 

    I am working on a project with special requirement and need suggestions on how to achieve it.

    Following is current configuration 

    Hyper-V Infrastructure A 

    1. Domain: aa.co
    2. No of Hyper-V hosts: 3 
    3. Failover Cluster Configured for VMs: Yes
    4. No of VMs: 20
    5. Networks: Management NW(192.168.2.0), iSCSI NW(192.168.1.0), Cluster Live Migration NW ( 172.18.1.0), Cluster NW (172.18.2.0)
    6. SCVMM Installed: Yes, running as Virtual Machine
    7. Domain Controllers : 1 Physical , 2 Virtual Machine 
    8. DC OS Version : Windows Server 2012 R2 
    9. Hyper-V Host OS Version : Windows Server 2012 R2 (GUI)
    10. Storage Type : iSCSI ( Dell EMC)

    Hyper-V Infrastructure B

    1. Domain: bb.co
    2. No of Hyper-V hosts: 3
    3. Failover Cluster Configured for VMs : Yes
    4. No of VMs: 10
    5. Networks: Management NW(192.168.3.0),iSCSI NW(192.168.1.0), Cluster Live Migration NW (172.16.1.0), Cluster NW (172.16.2.0)
    6. SCVMM Installed: Yes, running as Virtual Machine
    7. Domain Controllers: 1 Physical, 2 Virtual Machines
    8. DC OS Version : Windows Server 2016 
    9. Hyper-V Host OS Version : Windows Server 2016 Data Center (Core)
    10. Storage Type : iSCSI ( Pure Storage)

    Additional Information 

    • Hyper-V hosts in both infrastructure has access to Storage Network 
    • Hyper-V hosts in aa.co domain can reach Hyper-V hosts in bb.co
    • Hosts in both domains have similar number of NICs ( NIC teaming is also configured). Hosts in bb.co have more capacity in terms of CPU, RAM and Storage
    • All hosts are in one rack, connected to same switch stack, external traffic is routed by one firewall.

    Requirement 

    • Move all VMs from aa.co domain / cluster to bb.co domain / cluster in new Hyper-V infrastructure. The reason is that aa.co infrastructure is old and had couple of hardware parts failure. 
    • They don't want two domains to talk to each other but consolidate everything in one Hyper-V infrastructure for simplicity and management purpose. one domain (aa.co) will be for internal purpose and (bb.co) for external purpose.

    Questions

    • What do I need to do in bb.co Hyper-V Cluster in terms of physical and virtual network in order to facilitate aa.co Hyper-V VMs to continue communication in same subnet after move. The goal is not to change anything on subnet level since this is production network and have live internal clients connected to DC and other applications.
    • What method of Hyper-V migration I should use in this scenario ?
    • Do I need to configure anything on VMM in both cluster ? Is there any other consideration I should undertake since all VMs are managed by VMM in both infrastructure ?

    I have worked with Hyper-V in limited scale such as same domain, replication, export and import of VMS etc. This is new large scale migration for me and would like to explorer my options and maintain best practice as well. 

    Your suggestions and ideas are appreciated. 



    Thursday, February 13, 2020 3:16 AM

All replies

  • Hi nn58,

    Thanks for your post!

    Please check if my understanding is correct:

    cluster A in domain aa.co, 2012 R2 host;

    cluster B in domain bb.co, 2016 host.

    You would like to migrate VMs in cluster A to cluster B in different domains.

    If I misunderstood it, please feel free to let me know.

    ====================

    1. Clustered VMs in different domains unable to migrate to each other. 

    2. After serious consideration, I think the most easy way to migrate the VMs to the cluster B is export the VMs from cluster A, then import them to Cluster B. And in this way, if the IP address of the VMs are static, then the IP address will not change.

    Thanks for your time! If you have any concerns or questions, please feel free to let me know.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, February 13, 2020 8:10 AM
    Moderator
  • Hi Anne

    Thank you for your reply. I did some more research and I think the best way is indeed export and import the VMs. 

    now - I would to have some more clarification on the network part of it.

    Do I have to create new Virtual Switch and NIC teaming on physical servers ? or use existing switches with VLAN configuration. 



    Friday, February 14, 2020 1:38 AM
  • Hi nn58,

    >Do I have to create new Virtual Switch and NIC teaming on physical servers ? or use existing switches with VLAN configuration. 

    Yes, we need to create virtual switches on the hosts manually as the VMs originally connect to in the original hosts in domain aa.co.

    Thanks for your time! If there's any other things unclear, please feel free to let me know.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, February 14, 2020 7:14 AM
    Moderator
  • Thank you Anne
    Friday, February 14, 2020 2:17 PM
  • Hi nn58,

    You are welcome! 

    If you have any other questions or concerns, please feel free to feedback. If there's not, please mark the useful reply as answer. :)

    Thank for your time!

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Saturday, February 15, 2020 1:50 AM
    Moderator