Offline defragmentation of Active Directory, Active Directory series VII

Active Directory is a relational database designed for querying, and Active Directory uses a period of time to maintain database content to reduce data fragmentation and improve query efficiency, so today we'll show you how to Directory's database for offline maintenance.

The default database and transaction log path for Active directory creation is C:\Windows\NTDS, and we open the domain controller created in the previous Florence and navigate to the C:\Windows\NTDS directory. Let's take a look at the roles of the files in the diagram below. The Ntds.dit is the database file for Active Directory, EDB. Log is a transaction log file, and transaction log files record changes in the contents of the database, which is very important. The default transaction log file size is only 10M, and if the transaction log file is full, the system automatically generates Edb00001.log to continue to store the transaction log, and if the Edb00001.log is full, the edb00002.log is generated, and so on. Incidentally, in a production environment, we should store database files and transaction files separately, which can improve performance or increase data security, but Win2003 requires Active Directory databases and transaction logs to be stored on the same hard drive. Databases and transaction logs that do not resemble Active Directory in Win2000 can be stored on different hard disks.

EDB. CHK is the checkpoint file for the transaction log, which records the differences in content between Active Directory on the hard disk and Active Directory in memory, which is typically used for initialization or restoration of Active Directory. RES1. Log and RES2.LOG are system-reserved transaction log files, which take up 20M of space, primarily to reserve 20M space for Active Directory transaction logs, and to avoid shutting down normally when hard disk space is exhausted.