<div>
If your first server is only a DC, you don't necessarily have to get an identical server. &nbsp;You can bring up another virtual server or a physical server patch it completely, join it to the domain, promote it as another domain controller, &nbsp;it will replicate with your original domain controller and you are good to go.<br />
<br />
ref link: &nbsp;<a href="http://kpytko.pl/active-directory-domain-services/adding-additional-domain-controller-windows-server-2012/" rel="ugc">http://kpytko.pl/active-directory-domain-services/adding-additional-domain-controller-windows-server-2012/</a>
</div>


If your first server is only a DC, you don't necessarily have to get an identical server.  You can bring up another virtual server or a physical server patch it completely, join it to the domain, promote it as another domain controller,  it will replicate with your original domain controller and you are good to go.

ref link:  http://kpytko.pl/active-directory-domain-services/adding-additional-domain-controller-windows-server-2012/ [http://kpytko.pl/active-directory-domain-services/adding-additional-domain-controller-windows-server-2012/]

<div>
Since you only have a single server I'll assume that your organization is fairly small. &nbsp;In that case don't get another server to solve this problem. &nbsp;Use something like a Datto Backup Device.<br />
<br />
<a href="http://www.datto.com/" rel="ugc">http://www.datto.com/</a><br />
<br />
It will cost you much less and will do exactly what you want.<br />
<br />
Jeff<br />
TechSoEasy
</div>


Since you only have a single server I'll assume that your organization is fairly small.  In that case don't get another server to solve this problem.  Use something like a Datto Backup Device.

http://www.datto.com/ [http://www.datto.com/]

It will cost you much less and will do exactly what you want.

Jeff
TechSoEasy

<div>
<div class="content wysiwyg-content">
Dear All <br />
<br />
I was wondering if you could assist me. My current infrastructure environment consist of one server running server 2102. I user Hyper-V which has my virtual DC, my question is if I get a second server that is identical how can I have that as a fail over for the first server which is replicated every 5 minutes so in the even the first server die all my services will run with as little intervention.
</div>
</div>


Dear All 

I was wondering if you could assist me. My current infrastructure environment consist of one server running server 2102. I user Hyper-V which has my virtual DC, my question is if I get a second server that is identical how can I have that as a fail over for the first server which is replicated every 5 minutes so in the even the first server die all my services will run with as little intervention.

Fail Over Server

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.

Hyper-V

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

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.