A Exchange Database contains multiple user mailboxes EDB Files. There can be multiple databases within an Exchange Server. Exchange Server is efficient enough to handle multiple databases. However, as the size of the database grows, performance of Exchange reduces, causing problems with performance. These are the ones that are discussed below:
- Dismount of the database abruptly: If it is discovered that the Exchange Server is unable to access data from the database because of its huge size, it will then demount the database, which means that connections between database users and Exchange Server is lost. It is quite typical for large databases to be dismounted by Exchange Server. Exchange Server.
- slow search: It’s hard to search for mailbox items within an EDB file with multiple GB in size. If you are trying to search for a distinct item, the result of your search will show you a variety of items within the same search category. It also slows down the entire process of searching.
- corruption in a database: A huge database is extremely susceptible to corruption, and it could impact the information in a negative way. Sometimes, the corruption within the database doesn’t display any error message, however, it is rendered impossible to access.
The benefits of reducing the Exchange EDB file
If you can reduce your EDB File size not just allows for more email but also adds more value on your Exchange Server.
- The time to respond of Exchange Server increases. Exchange Server increases for the mailbox request. Likewise, the email message is more efficient.
- The white space of the EDB file is reduced, which allows more space for the email as well as other data.
- The data that was previously stored is moved into a new folder, which allows the mailbox to be more manageable.
- The data that was previously stored is moved into a new folder, which makes the mailbox easier to manage.
The most effective methods to follow for Exchange Server Administrators
If administrators follow these guidelines, the administrator can get rid of numerous EDB issues with the file effortlessly.
- Run Exchange’s Best Practice: Analyzer Execute Exchange Best-Practice offers an application named Exchange Best Practices Analyzer that administrators must utilize to gain a complete picture regarding the Exchange Server condition and configuration. It will gather details of Exchange Server, the Active Directory, registry settings and performance metrics, among others. Administrators will have an overview of the way in which Exchange Server is using its resources and the steps to take to improve the environment.
- Examine the SMTP queues and logs The SMTP queues and logs hold details related to communications that are sent via Exchange Server. Exchange Server. If an administrator examines the queues and logs, it will be able to identify numerous aspects that could be the reason for failures in messages. If messages are trapped in queues, and are not being processed, the queues and logs could aid the administrator.
- Make sure you are checking for anti-virus and anti-malware software updates There’s professional anti-virus software and anti-malware that helps Exchange Server Exchange Server and protects its environment. Sometimes, the software needs an update manually, and administrators fail to have time to update the software; it may not give additional security to users of the Exchange Server. If the administrator is able to update the antivirus frequently, it will aid in making the Exchange run more efficiently.
Three simple ways to decrease Exchange database size
Exchange administrators, from time to time they aren’t aware of the growing size in their Exchange databases. The unpredictability of this growth usually results in a rise in size and inaccessibility issues. There are a variety of ways to cut down on the size of databases. The following are some of them:
- Eliminate undesirable data in the database This is among the most obvious ways to decrease the EDB file size efficiently. Eliminating unwanted data can create more space for the addition of new data. Be careful not to accidentally erase crucial data by accident. Incredibly that even after deletion you might not notice any decrease in the size EDB files. EDB file. However, the space that was freed from the deletion remains and Exchange will make use of it to add new information (instead in the process of adding to database’s size).
- Perform offline defragmentation or transfer data to a different database Offline defragmentation can help recover the space that is left (known in the form of white space) within exchange. Exchange database. This process compresses databases by eliminating the empty and unutilized space, and also reduces the size of the database. It effectively provides the continuity of storage. Also, Eseutil will be the Microsoft tool that aids in defragmenting. But, this method has the disadvantage of being an extremely slow process that is only available after removing the database (it implies that all mailboxes in the database will not be accessible for a significant amount in time).
Performing defragmentation using Eseutil
You can determine how much whitespace that is in databases by running the following command-line tools within the Exchange Management Shell:
Get-MailboxDatabase -Status | Format-List Name, DatabaseSize, AvailableNewMailboxSpace -Auto
Before you begin defragmentation, be sure that you have sufficient free space (110 percent in the total size of your Database) accessible on your Server (or your network). Stop your Exchange Information Store service, and follow the steps below to complete the defragmentation:
- Inside the Exchange Management Shell, navigate to the directory in the Database File.
- Unmount the Exchange database on the purpose of defragmentation to take place:
- Defragmentation is performed by performing:
- “Eseutil /d ” “/t “
- The database should be re-mounted.
- Mount Database
- After the the defrgamentation procedure, you can start with the Information Store service.
- Make sure the database is properly mounted. Then, verify whether emailing is functioning.
- Then, you can check the white space for confirmation of the effectiveness of the defragmentation.
Be aware: The speed of Eseutil software is usually 9 GB/hour , but it can vary in accordance with the system’s hardware and environment EDB Files.
Instead of defragmenting instead, many Exchange administrators create a brand new database, and then transfer mailboxes of the old database to the brand new (the older one may be deleted afterward). It allows them to get the same results through defragmentation. Its advantage is that downtime for mailboxes is very minimal. Additionally, it is performed via through the Exchange Interface (like Exchange Management Console).
- Save the data, then delete this from your server – Exchange administrators can save the data that is not used in another location, and then delete it from the server in order to decrease the size of the database. To backup their data it is possible to use Microsoft’s Windows Server Backup facility. For exporting, they can use ExMerge or export cmdlets based what version they are using of Exchange.
Exchange 2010: In Exchange 2010, you can use these cmdlets to export mailboxes into PST files: PST file:
New-MailboxExportRequest -Mailbox-FilePath < network share path of PST file >
Alternately, they can backup to EDB documents by exporting the data into PST files with a powerful third-party program such as Regain EDB to PST Converter. It is an Exchange Server Recovery tool makes the entire process simple by providing a range of different options.
To decrease Exchange Database size there are many options to remove unwanted data, carry out defragmentation, shift data into a new database, remove data that isn’t needed after creating backups or backup. For backups it is possible to try a Windows backup software, utilize the built-in export tools and convert EDB files to PST file by using an external software.