Optimize Maintenance and Backup Windows
Step No. 3: Optimize maintenance and backup windows Exchange system maintenance is generally configured to run during off hours when there is reduced load on the server. The following is a simple checklist of four items that can be used to ensure that maintenance is running during an optimal timeframe:2. Implement a stop time that corresponds with the start of business when users add load to the server. The maintenance should be completed or halted before users need the server resources. 3. Check the event log and verify that maintenance is starting and completing successfully. Look for "Event ID 700" and verify that it is followed in sequence by "Event ID 701" and finally by an "Event ID 1221." If "Event ID 701" does not appear, then online maintenance is not completing. Online maintenance should complete at least once per week. 4. Regularly monitor database white space. After online maintenance is complete, look for "Event ID 1221" which lists how much white space is available in the database. Many administrators will run offline defragmentation of the Exchange database when white space reaches 25 percent. This is not recommended. If a database has more than 50 percent white space, users should be moved to a newly created database. Only in very rare cases should the ESEUTIL tool ever be run.
1. For starters, review the configured maintenance window to verify that it is running during a period of low load and that it is not running during the backup window. Maintenance should never be run on a server while backups are taking place.