nn58

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

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. 

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3613