Dear All,
I need opinion and help.
For the purpose of testing my backup solution, I have created a virtual test averment to restore the servers.
My network contain two DC’s, one virtual Exchange Server 2010 SP3 and virtual Database SQL2012. The primary domain controller, DC1 is physical Server 2008 R2 Enterprise, GC with all FSMO roles except infrastructure master. The second DC is virtual Server 2012 Standard and is GC with Infrastructure master role.
For creating the backups I use SCDPM 2012 SP1, is installed on Server 2008 R2 and is virtualized on another Hyper-V host. For all servers I created a bare metal backups plus, separate database backups for the Exchange server, SQL server and files.
My test scenario is:
If I assume that after catastrophe strikes, the only surviving backups are the bare metal for the DC1 and the backups for the Exchange databases, SQL databases and files.
The plan is to recover everything, if it is possible, on new hardware.
In reality, I’m performing this recovery on Hyper-V host on a separate network.
First, I want to recover the DC1 and to seize remaining FSMO role. The procedure goes fine, the server boots and I can open ADUC. I configure the network adapters as they were. After successful seizure of the infrastructure FSMO role, I restart the DC1 server and the problems starts to occur.
First I can’t open the ADUC or any other MMC console connected with AD and I receiving error message:
“Naming information cannot be located for the following reason: The server is not operational”.
DNS is working.
After several restarts, AD starts and stops working. In the moments, when everything seams fine, if I try to join another server to the domain, I can’t, due to the similar error:
All server can ping each other, the DNS is working fine and name resolution works ok.
I’m stuck here and I can’t continue with my recovery process. My backup/recovery solutions is not working.
Can, someone tell me what I’m doing wrong and what I should do?
Aleksandar B. MCITP/MCSA