When exporting large Exchange Mailboxes to PST, you may often come across timeout errors. These glitches may abort the export and leave behind the corrupted or partial PST files. At times, it may also cause the export request to stall or loop infinitely. Prompt resolution of these errors is critical to ensure data integrity and avert possible business obstacles. It would be even better if you could perform the export tasks without encountering timeout errors. Let’s get into the skin of the topic and find out ways to avoid the error from halting the export through this blog.
How can the timeout error affect the export of large Exchange mailboxes to PST?
Exporting large Exchange mailboxes to PST can experience a significant obstruction because of timeout errors. While the Mailbox Replication Service (MRS) is responsible for the asynchronous handling of the export operation, several timeout situations can still delay or hamper the process. Here are some crucial timeout-related issues that leave an adverse impact on the export.
Incomplete export of PST files
A timeout error may terminate the export request much before it could finish writing the entire mailbox data to the PST file. This may give way to several issues:
Incomplete PST file
Missing emails and other mailbox items like contacts, calendars, or folders
Compulsion to opt for export restart
Failed export requests
A session timeout after long export requests may lead to several interruptions or errors:
StalledDueToTarget
StalledDueToSource
Failed
Suspended
Increased export duration
If tasked to export large mailboxes, the Exchange server would need additional time to complete the process. This will slow down the speed significantly due to several reasons:
Disk I/O transforms into a bottleneck
The MRS may throttle the export process to protect overall Exchange server performance
Sharing of the memory and CPU resources with other Exchange services and mailbox operations
Added administrative overhead
Frequent timeout failures will need the admin to execute several operations in quick succession:
Remove failed export requests
Initiate new export requests
Check export statistics and Exchange logs
Find out the performance issues with the server
These operations will lead to an increased administrative overhead, specifically in the case of large mailboxes in bulk.
Delayed routine tasks
Admins carry out mailbox export to PST for some crucial routine jobs:
Mailbox migration
Legal discovery
Mailbox Backup
User Offboarding
Repeated failure of export requests due to timeout-related errors will eventually delay these important tasks
Excess resource consumption
Mailbox export in bulk can consume significant server resources, including
CPU
RAM
Disk throughput
Network bandwidth and
This will affect the other routine Exchange operations.
Timeout error in Microsoft Exchange: Reasons and Resolutions
This error occurs when the Exchange Server fails to respond to the service request of the client, such as Outlook or a mobile device, within a specified duration. If the request crosses this time limit, it leads to a timeout connection. This hampers tasks like sending and receiving emails, running admin scripts, and performing mailbox synchronization. Several reasons can cause the Exchange server to throw this error:
Slow storage performance
The Exchange database disk fails to keep up with the lengthy read/write operations of large mailboxes. This leads to a slow or unstable network and high packet loss. To fix this issue, your storage infrastructure should have sufficient I/O capabilities. During off-peak hours, isolating the export process can also minimize server load and fix the timeout error.
Mailbox corruption
Often, corrupted emails, broken calendar items, or oversized attachments can stall the processing of the Mailbox Replication service (MRS). To deal with this issue, the admins use Exchange Management Shell to bypass corrupt items through -BadItemLimit and -AcceptLargeDataLoss parameters
Unstable network or dropped connections
Excessive volume of data export over unstable networks or firewalls can cause instances of network latency, dropped connections, or premature connection resets. Using a stable UNC path for the target PST and avoiding high-latency WAN connections for the export can resolve this issue.
Server throttling
Multiple export requests running in parallel can cause server throttling, leading to dropped or queued requests. To remedy this situation, you can reduce the number of concurrent exports.
Extremely large sizes of PST files
PST files exceeding 50 GB may face file corruption and performance degradation issues, leading to export timeouts. To avert this situation, it is better to break large exports into smaller chunks according to date ranges or folders by using the -ContentFilter parameter. This will reduce the size of the resulting PST files, making it easy to manage them.
Export large Exchange mailboxes to PST without timeout errors
Here are a few manual ways that can help the admins serve this purpose with success:
Dividing the mailboxes into smaller groups based on dates
If you have the task of exporting large mailboxes, such as having a size of 100 GB or more, they are likely to cause interruptions because of network instability, corrupted files, or server load. To avoid such obstructions, it is better to separate the mailboxes into small batches. For instance, you can categorize them according to folders or date ranges.
New-MailboxExportRequest -Mailbox “John Smith” ` -ContentFilter {(Received -lt ’01/01/2022′)} ` -FilePath “\ServerPSTUser01_2022.pst”
New-MailboxExportRequest -Mailbox John Doe -ContentFilter (Received -lt ’01/01/2022′)” -FilePath “\SERVER01PSTFileShareJohn.pst”
The PowerShell command creates a mailbox export request to export all emails received before January 1, 2022 from an Exchange mailbox of ‘John Doe’ to a PST file named John.pst
Once this request is complete, you can create similar requests for other mailboxes in a similar manner. This will reduce the time for export, ensure manageable PST files, and reduce the risk of timeout errors. In case a particular file fails to export, it will be easier to find the file and troubleshoot the issue.
Handling corrupted mailbox items
Large mailboxes are more likely to have oversized or corrupted items collected over the years. During the export, these items can influence the request adversely. This will require the admin to configure the export request to tolerate a selected number of bad items instead of instantly failing the entire request. This is possible by using the BadItemLimit, LargeItemLimit, and AcceptLargeDataLoss parameters. Here is the syntax:
New-MailboxExportRequest -Identity <MailboxIdentity><MailboxExportRequestName> [-BadItemLimit <value>] [-LargeItemLimit <value>] [-AcceptLargeDataLoss]
Example 1:
New-MailboxExportRequest -Identity “Mohammad SalahMailboxExport” -BadItemLimit 10
This specific example will modify the failed mailbox export request for the mailbox of Mohammad Salah to accept a maximum of 10 corrupted mailbox items.
Example 2:
New-MailboxExportRequest –Mailbox “Cristiano Ronaldo –FilePath \SERVER01PSTFileShareRonaldo.pst -LargeItemLimit 10
This example will modify the failed export request for the mailbox of Cristiano Ronaldo to skip up to a maximum of 10 oversized items.
Example 3:
New-MailboxExportRequest –Mailbox “Erling Halland” –FilePath “\SERVER01PSTFileShareHalland.pst” -BadItemLimit 100 -AcceptLargeDataLoss
This example will skip up to 100 corrupted mailbox items while continuing the export for the rest items. It also acknowledges the possibility of significant data loss. Since BadItemLimit is more than 50, it will need AcceptLargeDataLoss
Example 4
New-MailboxExportRequest -Mailbox “Kylian Mbappe” –FilePath “\SERVER01PSTFileShareMbappe.pst” -BadItemLimit 60 -LargeItemLimit 40 -AcceptLargeDataLoss
This example will skip up to 60 corrupted or bad items, 40 large or oversized items, and continue to export the remaining mailbox items.
Using EDB to PST converter to export Exchange mailbox items to PST
Manual ways to resolve the timeout during mailbox export can be time-consuming, especially involving large mailboxes. It may cause data loss and require the admin to possess deep technical knowledge of the Exchange environment. To overcome these hassles, Exchange administrators use EDB to PST converter tools as suitable alternatives. Stellar Converter for EDB is a feasible option in this regard. It can export an Exchange mailbox to PST without causing a timeout error. It also ensures a satisfying export of mailboxes at a comparably quicker speed.
Conclusion
When exporting large mailboxes from the Exchange server to a PST file through a mailbox export request, you are likely to face troubles. One of the common issues in this context is the timeout error, which happens due to the excessive delay in executing the mailbox export request. It can cause significant issues, such as incomplete or failed export requests, increased administrative overhead, excessive resource consumption, and so on.
The reason behind this error may range from slow storage performance to unstable network, server throttling, large PST files, and more. To deal with the situation, admins try several manual methods. For instance, splitting the mailboxes into smaller groups based on dates is a common resolution. Handing corrupted mailbox items through various crucial parameters is another probable method.
While these solutions are successful, they consume significant time and need penetrating technical knowledge. To avoid such hassles during the export of Exchange mailbox to PST, an EDB to PST converter such as Stellar Converter for EDB can be a useful alternative.
