Microsoft makes available methods for restoring Active Directory databases such that the Domain Controller can properly resynchronise with its replication partners afterwards. If you just want the summary version, basically a USN rollback condition can occur when the Active Directory database is restored to an earlier version in an improper fashion. How to detect and recover from a USN rollback in Windows Server 2003 If you want to get deeply technical with the concept you can read this article from Microsoft: I specifically mention Domain Controllers twice there because both of these very common scenarios introduce the serious risk of a “USN rollback” condition occurring (USN stands for “update sequence number”). This includes recovery of their Domain Controllers. This often means they are relying on some ad-hoc Ghost or Acronis images for server recovery. Secondly, some companies are too cheap (or just haven’t gotten around to it yet) to setup a proper backup and recovery solution for their servers. Everyone seems to be virtualising their infrastructure as much as possible, particularly their servers such as Domain Controllers. Firstly virtualisation is pretty hot right now. There are two things I tend to see a lot of at the moment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |