Disk fragmentation is a process of reorganizing the data stored on the server's hard disk to make files more continuous and increase the speed of data access and retrieval. When you fragment a hard disk, you can improve disk performance and ensure that the servers in your organization, including those running Exchange 2000, are running smoothly and effectively. However, detailed disk fragmentation may cause performance problems, therefore, you may need to run the defragmentation program, such as Microsoft Windows 2000 disk defragmentation program, periodically or when the server performance level falls below the expected performance level ). For more information, the Exchange 2000 database also needs to be fragmented. By default, the Exchange 2000 database runs the fragment process every day. This process can more effectively arrange mailbox storage data and public folder storage data to sort out unused buckets. You can also manually fragment the Exchange 2000 database offline.
The online fragmentation of the Exchange 2000 database automatically occurs during database maintenance. Online fragment allows you to detect and delete database objects that are no longer in use, so that you can obtain additional database space. The online fragment process can provide more database space without changing the size of database files. By default, Exchange 2000 is configured to run online fragment between and every day.
Remarks: To improve the efficiency of maintenance and backup processes, you may need to schedule maintenance processes and backup operations to run at different times.
There are two ways to arrange database fragmentation:
- To arrange database fragmentation for a single database, useDatabaseTabMaintenance IntervalTo configure the maintenance interval.
- To arrange database fragmentation for a group of mailbox storage and public folder storage, useDatabase (Policy)TabMaintenance IntervalTo configure the maintenance interval.
Offline fragmentation although online fragmentation can provide additional database space, you must perform offline fragmentation on the Exchange 2000 database to reduce the physical size of the Exchange 2000 database. When mailbox storage and public folder storage are offline, you can use the Ese utility (Eseutil) to perform offline fragment.
For example, if you recently moved a large number of users from a server running Exchange 2000, you may perform offline fragmentation. In this case, offline fragmentation will rearrange the data on the server's Exchange 2000 database and discard any unused database pages to reduce the size of the Exchange 2000 database.
Remarks: Eseutil is an Exchange 2000 utility used to fragment, repair, and check the integrity of the Exchange 2000 database. You can find Eseutil on the Exchange 2000 disc. For information about how to use Eseutil, see Eseutil. rtf in the Support \ Utils folder of the Exchange 2000 disc.
By default,
Eseutil/dBy creating a new database, copying old database records to the new database, and discarding any unused database pages, you can fragment the database to obtain a new and compact database file.
When you use Eseutil to fragment an Exchange 2000 database, you may want to use the following options:
- You can use/D/pSelect the Eseutil option to configure Eseutil in a separate location, such as a location on another hard disk) to create a new database that has been fragmented. If the placement overwrite function is disabled, for example, if you use/D/pThe offline defragmentation process retains the uncompressed original database. The temporary files created are the database's defragmentation version. With the standard offline fragment process (Eseutil/d) Is different, if you use/D/pOption to run Eseutil. After the offline fragmentation process is completed, the new database after the fragmentation will not overwrite the original database.
Option
/D/pIt can also significantly reduce the time it takes to fragment large databases, because you do not have to copy the database that has been fragment from a temporary location and overwrite the fragmented original files. However, if you want to mount a fragmented database after using this option, you must manually refresh it. edb and. import the stm file to the database path and rename it to the correct database file name. For example, if Tempdfg. edb and Tempdfg. stm are run
/D/pYou must rename the files created by the option to Priv1.edb and Priv2.stm if Priv1.edb and Priv1.stm are databases that initially run Eseutil on them ). The following command example is named Mailbox Store. edb databases and their accompanying streaming files are defragmented, the overwriting function is disabled, and the defragmentation database is created on drive D,
No space after/t):
Eseutil/d/p "c: \ program files \ exchsrvr \ mdbdata \ mailbox store. edb"/t "d: \ tempdfg. edb"
Remarks: If you do not use
/TOption. The Tempdfgxxxx. edb file and the Tempdfgxxxx. stm file xxxx are random numbers ).
Because the offline fragmentation process re-arranges data in the Exchange 2000 database, use the backup tool to create a standard backup of the database immediately after the fragmentation to ensure the security of the new data arrangement. Previous incremental backups or differential backups are no longer useful because they reference the database pages rearranged by the fragment process. The information in this article applies:
- Microsoft Exchange 2000 Server
