<div>
Do you have a required hardware for the second site that you can run all the time? At the very least AD server and Exchange, or your resources are limited only to disaster state, which only then you'll be able to power-up some servers?
</div>


<div>
I have the resources required to run the DC server and Exchange server all the time
</div>


<div>
No unfortunately 1Gbps is not available without a hefty price tag. &nbsp;That type of availability would be nice but its not required.
</div>


<div>
Issue seems to be solved, no more replies from author
</div>


<div>
<div class="content wysiwyg-content">
Hi. &nbsp;I'm currently running Exchange 2013 onsite with a Windows 2008 DC. &nbsp;I have a hot site where I use VEEAM to replicate both the Exchange server and DC. &nbsp;Lately I have been having issues with AD services not starting correctly when restoring the DC with VEEAM. &nbsp;After reading that restoring DC's from replica's can be problematic, I have built a DC that sits at the hot site, which I will use in the event of a disaster recovery. &nbsp;However I'm not sure the best way to go about testing that everything will work correctly in my scenario. &nbsp;Can I disconnect my hot site from my production site, seize the FSMO roles on my DR DC, and start Exchange? What do I need to do when its time to bring the DR DC back online (and connect to my production network)? Is it better just to kill the DR DC and promote a new server once the testing is complete?
</div>
</div>


Hi.  I'm currently running Exchange 2013 onsite with a Windows 2008 DC.  I have a hot site where I use VEEAM to replicate both the Exchange server and DC.  Lately I have been having issues with AD services not starting correctly when restoring the DC with VEEAM.  After reading that restoring DC's from replica's can be problematic, I have built a DC that sits at the hot site, which I will use in the event of a disaster recovery.  However I'm not sure the best way to go about testing that everything will work correctly in my scenario.  Can I disconnect my hot site from my production site, seize the FSMO roles on my DR DC, and start Exchange? What do I need to do when its time to bring the DR DC back online (and connect to my production network)? Is it better just to kill the DR DC and promote a new server once the testing is complete?

Offsite restore testing of Exchange 2013

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.