I'm relatively new to using the Windows Server 2016 Recovery Wizard to restore backups. I attempted to restore the Active Directory system state from a backup dated June, and the restoration process completed successfully. However, after restarting the server, it enters an Automatic Repair loop. We recently replaced the hard drives on the server and were testing the local backup, but now we're in this bind. Has anyone encountered this issue before? I'm looking for possible solutions or insights into what might be causing this loop, as I'm still learning the ropes and would appreciate any help.
5 Answers
I remember having a similar issue; I had to run edbutil or eseutil on the AD database while in DSRM. Active Directory requires a clean database with all its log files in order.
Are you restoring from a local backup of the only domain controller? That could complicate things, especially if you're relying solely on that backup.
It sounds like you might be facing the 0xc00002e2 error. If the backup is from June, it's possible that it's past the tombstone lifetime for Active Directory. This could make recovery tricky, so it's something to keep in mind.
Did you try booting into Directory Services Restore Mode (DSRM)? It's a specific mode for restoring Active Directory, and it might help you get out of that loop.
Yes, I've managed to boot into safe mode and selected AD Repair.
It might be that the NTDS database needs a repair if you only restored the Active Directory state. If the system doesn't boot, DSRM is the way to go. You could consider copying the event logs elsewhere to analyze them. Running an offline DISM could also help ensure your registry hives are intact.
Yes, it is the only domain controller we have.