Need for Exchange Server Maintenance
The need for Exchange database maintenance is to keep safe it from getting into the corruption situation. There are some following factors which could lead to Exchange database corruption or damage:
- Unexpected Hardware Failure
- Unexpected Power changes or Improper Shutdown
- Deletion of Exchange Server Transaction Logs
- Manual Modification of Exchange Database
Microsoft Exchange Server Maintenance Checklist
- Always Keep Windows Server OS Updated
- Always Keep MS Exchange Server Updated
- Keep Monitoring Used Disk Drive Space
- Keep Monitoring Hardware Resource Utilization
- Keep Record of Document License Usage
- Backup the Exchange Database Regularly
- Perform Exchange DB Defragmentation Regularly (Once or Twice in an Year)
- Schedule Exchange Server for Periodic Reboot
- Tasks which should be performed Every Day for maintenance
- Check Event & Backup Logs
- Monitor Performance
- Monitor Performance
- Check available disk drive space
- Check Badmail folder and Queues
- Check for any updates
- Test the mail flow
- Backup the Exchange Server
- Tasks which should be performed Weekly for maintenance
- Verify backup data with recovery database
- Tasks which should be performed Monthly for maintenance
- ESEUTIL file dump
- ESEUTIL integrity check
- ISINTEG all tests default mode
- Tasks which should be performed according to need (Once or Twice in an Year)
- Disaster recovery test
Microsoft Exchange Server Maintenance
In Exchange Server, The database requires routine maintenance or we can say that it should be maintained regularly for better performance. In earlier versions before MS Exchange 2010 Server, it need for a planned maintenance and scheduled downtime. But in Exchange Server 2010, 2013 & 2016, there is no need for any scheduled downtime and planned maintenance because of following functionalities:
- Continuous Online Database Defragmentation
- Continuous Online Database Compaction
- Continuous Online Database Contiguity Maintenance
Automatic Exchange Database Maintenance
Automatic Exchange Server Database Maintenance is really an amazing feature of Exchange 2010/2013/2016. This features is also available in Exchange 2007, but during performing Automatic Exchange DB maintenance, it effects on the input/output latency of Exchange database, which cause the low performance during data access. While in Exchange 2010/13/16 Server, Automatic Maintenance of Exchange Database is done at night or at that time when very few users are accessing the data.There are two different activities which are performed by Exchange Server 2010 for Automatic maintenance:
- Online Maintenance (OLM) : It starts automatically at 1:00 AM and finishes at 5:00 AM on daily basis.
- Online Defragmentation (OLD): It is always in processing (24 x 7). But you can Schedule it with OLM time.
- Disk Cleanup: It is performed automatically whenever any items are hardly deleted.
- Database Size Compaction: It compacts the sizes for freeing up more space and autothrottle the users for avoiding the impact of compactions during data access.
- Maintain Contiguity: During storing the data, it is saved in contiguous manner like one after another. If the stored data is not in contiguous manner, then the defragmentation process again bring all data in contiguous manner & autothrottle the users for avoiding the impact of de-fragmentation.
Schedule Automatic Database Maintenance in Exchange 2010
There are the following steps which an Exchange Administrator need to follow for scheduling Automatic Microsoft Exchange Server maintenance:
- Run the Exchange Management Console from Start menu.
- Now in left tree in console, Expand Organization Configuration and Select Mailbox.
- Now click on Database Management tab then select the desired database.
- Now go to the Action pane and click on Properties and select Maintenance tab and then select Maintenance Schedule.
- Now select any option from Drop Down List for customizing or creating new schedule.
What if Exchange Server is Configured in DAG?
In below section we will discuss performing maintenance on DAG members in Exchange server 2010 SP1. Before putting all DAG members in maintenance mode, we would bring out or move the Active databases first to other DAG members and after completion of maintenance we will reconnect the database again with Exchange server. Let see the process for DAG members maintenance:
- Run below command to move active databases to other DAG members.
.\StartDagServerMaintenance.ps1 -serverName abcServer
- Run below command after completion of maintenance to bring the Exchange server out from maintenance mode.
.\StopDagServerMaintenance.ps1 -serverName abcServer
- Now run below command to redistribute the Active databases among DAG members.
.\RedistributeActiveDatabases.ps1 -DagName ABCDAG -BalanceDbsByActivationPreference -ShowFinalDatabaseDistribution -Confirm:$false
In this article “Microsoft Exchange Server Maintenance” we discussed the need for Exchange server maintenance, checklist which an Exchange Admin should follow before Exchange server maintenance. We also discussed about automatic Exchange database maintenance method and how a DAG member should put into maintenance mode for improving the performance.