<div>
Site-to-Site VPN set up between the DR site and the main site would be one way to do this.<br />
<br />
Another would be to set up a DC on the Hyper-V host's local storage, configure a greenfield AD, and then set up a second DC on another node's local storage to provide some redundancy.<br />
<br />
<a href="http://blog.mpecsinc.ca/2014/10/cluster-why-we-always-deploy-physical.html" rel="ugc">We always deploy a DC in cluster settings</a>.
</div>


<div>
Hi Philip,<br />
<br />
I understand all these.<br />
<br />
But my question is HYPER-V Hosts in Disaster Recovery Site must be join in domain of production environment?
</div>


<div>
The Hyper-V hosts need to be in the same domain as the hosts they are replicating from for the failover clustering to work. &nbsp;<br />
<br />
Virtual machines would not need to be in the same domain as the hosts. &nbsp;Often they will be though.
</div>


<div>
@John Hyper-V replica can be set up to run between systems and clusters in the same domain or not.<br />
<br />
Once a cluster is stood up a DC is not required for a cold-boot though one is required at some point down the road.
</div>


<div>
Thank you guys for your help
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I am in progress to install a Disaster Recovery Site with HYPER-V. The HYPER-V Hosts in Disaster Recovery Site want to be with Failover Clustering.<br />
<br />
<br />
But to use Failover Clustering must be a member of a Domain,<br />
<br />
So i must create a new domain name in Disaster Recovery Site for my HYPER-V Hosts? or must use the same as in Production?<br />
<br />
I talk only for the <b>HYPER-V Hosts</b> not for the Virtual Machines.
</div>
</div>


Hi,

I am in progress to install a Disaster Recovery Site with HYPER-V. The HYPER-V Hosts in Disaster Recovery Site want to be with Failover Clustering.


But to use Failover Clustering must be a member of a Domain,

So i must create a new domain name in Disaster Recovery Site for my HYPER-V Hosts? or must use the same as in Production?

I talk only for the HYPER-V Hosts not for the Virtual Machines.

Disaster Recovery Site HYPER-V Hosts and Domain

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.

Disaster Recovery

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.