Help, AD database corrupted on one DC

mrbios · 29 May 2012 at 12:14

Had 3 DCs with issues caused by the failure of vmware iSCSI storage (cache memory module in the storage unit failed causing all sorts of issues), two were fixed with an offline defrag and integrity check, but one is having bigger problems...

I'm getting the error: "-1206 (JET_errDatabaseCorrupted)" when i attempted to run offline defragmentation and integrity checks

I've attempted the esentutl repair options but they also fail, am i best off just demoting this DC and re-promoting it in hope that fixes the problem? or can any suggest anything i can do to fix this?

sidethink · 29 May 2012 at 12:55

If this DC doesnt have any FSMO roles (or they can be easily moved) a depromo and promo would get you the cleanest results.

Do you have the option of a restore from backup (C and System State)?

mrbios · 29 May 2012 at 12:58

sidethink said:
If this DC doesnt have any FSMO roles (or they can be easily moved) a depromo and promo would get you the cleanest results.

Do you have the option of a restore from backup (C and System State)?

The only backup i have of the full system state is from last thursday...the same day this error occoured :/ recently rebuilt the backup server after various upgrades etc so it's all a bit bad timing really.

I still have the old backup exec database so i could restore a much older version of this machine but it's a lot of hassle.

I think i'll go for the dcpromo option then, just wanted to be sure it would work before i did it

and yes there's no FSMO roles on this one.

thanks

Uhtred · 29 May 2012 at 20:55

If you have any trouble removing it use dcpromo /forceremove and then clean up the meta data etc (plenty on the web about this)

Had to do it the other day in fact as my infrastructure engineer p2v'd two domain controllers without consulting me :rolleyes:

mrbios · 29 May 2012 at 21:00

Nearly had a problem as it couldn't see the PDC to begin with, think i was just being impatient in trying to repromo it though

All sorted now.

ended up having to run chkdsk on 4 other servers, the memory module dieing in our iSCSI storage really did a number on our VMs, luckily though we've already put a new solution in place.