Follow me on Twitter...
Have a look at a my blogs on 'You Had Me At EHLO...' Protecting Exchange Data with DPM, CCR Decision Making Flowcharts, SCR Decision Making Flowcharts, On email archiving. ...and a few more here High item counts - what do you do about it?, Archive v Big Mailboxes, Getting your Exchange 2007 Project Approved, (and the follow up 7 blogs), Recovery Scenarios Part 1, Recovery Scenarios Part 2, Recovery Scenarios Part 3, How quick will DPM backup?, Synchronous or Asynchronous Replication?, Why not stretch CCR?, Backup solutions for Exchange 2007..., Do we actually need to backup Exchange?, SAN v DAS.
...and a few more here High item counts - what do you do about it?, Archive v Big Mailboxes, Getting your Exchange 2007 Project Approved, (and the follow up 7 blogs), Recovery Scenarios Part 1, Recovery Scenarios Part 2, Recovery Scenarios Part 3, How quick will DPM backup?, Synchronous or Asynchronous Replication?, Why not stretch CCR?, Backup solutions for Exchange 2007..., Do we actually need to backup Exchange?, SAN v DAS.
This is a great blog if you are wondering about some unusual behaviour in Active Directory – specifically the following:
“- Why has my AD database size increased by 500MB in the last three weeks? - I see lots of AD replication in Domain Controller monitoring. What are all these changes?”
Go to the Ask the Directory Services blog on Technet;
“In order to find the cause for the problems, you should find what has changed in the AD database recently. Now Active Directory assigns an "Update Sequence Number" (USN) to each change. These USNs are 64 Bit Integers and are specific to a Domain Controller. The DC GUID and USN together uniquely identify a database change. A USN is both assigned to originating changes and replicated changes. So even for read-only GC content, you see local USNs getting written. You can use these USNs to identify recent changes in the database of each DC. ….” “Based on this number, you can query for the most recently changed Objects using an LDAP query.”
“In order to find the cause for the problems, you should find what has changed in the AD database recently. Now Active Directory assigns an "Update Sequence Number" (USN) to each change. These USNs are 64 Bit Integers and are specific to a Domain Controller. The DC GUID and USN together uniquely identify a database change. A USN is both assigned to originating changes and replicated changes. So even for read-only GC content, you see local USNs getting written.
You can use these USNs to identify recent changes in the database of each DC. ….”
“Based on this number, you can query for the most recently changed Objects using an LDAP query.”
Great blog!
PingBack from http://blog.a-foton.ru/index.php/2009/03/24/what-are-all-these-changes-to-active-directory/