pronto Posted February 27, 2006 Report Share Posted February 27, 2006 Hi Community, we tested a desaster recovery from a microsoft based domain controller and printed out the retrospect step by step guide. This paper contains a from microsoft unsupported restore szenario for the active directory database. Retrospect means to roll out the snapshot and *after* this reboot the client in the active directory recovery mode. In contrast microsoft specify the supported way to restore a DC is, *first* to bring it in the AD recovery mode, roll back the snapshot and *before* reboot the machine you have to run ntdsutil in athoritative mode. The workaround discribed in the step by step guide, seems to be the same as you recover a DC from an image, which ends in an USN roll back szenario. In this case the AD is in a broken status. The question is, what do i have to do after rebooting the machine in the AD recovery mode to prevent an USN roll back without running ntdsutil in authoritative restore mode? Thanks for your attention Bye Tom Link to comment Share on other sites More sharing options...
natew Posted March 1, 2006 Report Share Posted March 1, 2006 Hi If you are using Retrospect you need to run the restore, boot into directory services restore mode and then reboot again. Thanks nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.