Ok, so I have a client and didn't realize application awareness wasn't enabled on one job. We have a secondary domain controller off a sbs 2011 server.
All servers run on a local disk on the main server but the secondary domain controller was set to store the disks on a synology station. Something happened to the synology and it went offline and even though it came back up it corrupted the disk on the secondary domain controller and now it won't boot. I restored the secondary domain controller using a backup and after the restore I got the error code 0xc00002e2. I went an looked and the job set to backup this server didn't have application awareness turned on so it doesn't know how to restore the server with the AD database in tact.
It is enabled on the other jobs so the other domain controllers will be fine if we need a restore.
I can easily build a new box and promote it so it will be the new secondary domain controller. But this server also has the azure sync tool on it and I would like to export the azure settings so I can reinstall on the new server and import the config.
I have read a lot of articles on using the Directory Services Repair mode but I am unclear on what approach to take as most seem to be for the primary controller. I found one article where he talks about deleting that role using DSR and then it will boot. Should I just go that route so I can get it up and running to export the config or is there a way of saving the server without having to rebuild a new box?
I found this post but this seems to be recovering a domain controller where it is the primary and not the secondary.http://blog.msallal.com/2015/02/windows ... error.html
Obviously my concern is performing the wrong function using DSR and I corrupt the primary domain controller db as well, if that is even possible.