Overview
This article describes the issue and its resolution when high resource consumption is observed when Mailbox Folder Structure Retrieval (UMPolling) is enabled.
Environment
- Archiver
- All supported environments
Root Cause
The feature connects to all mailboxes and scans a high amount of emails which requires additional system resources, especially when the feature is initially enabled and while the first scan cycle has not yet completed.
Resolution
Several settings can be tweaked to decrease resource utilization based on this feature.
NOTE: Please take a backup of any file before editing it.
- Open the GFI Archiver web site.
- Navigate to Configuration > Mailbox Folder Structure Retrieval.
- Note which protocol is configured (it is either EWS or MAPI).
- Open the folder: ..\GFI\Archiver\Core\Data\
- Depending on which protocol is configured for Mailbox Folder Structure Retrieval, open the file with a text editor:
- EWS protocol: EWSPollingSettings.xml
- MAPI protocol: ExPollingSettings.xml
- Find and modify the following settings so that they reflect the values given below:
<PollingDelay>5</PollingDelay>
<PollingMailboxDelay>30</PollingMailboxDelay>
<RefreshUsersPass>9</RefreshUsersPass>
<RefreshFoldersPass>5</RefreshFoldersPass> - Save a close the file.
- Restart the GFI Archiver Core Service from the services console.
Below is a description of the settings mentioned:
Setting | Description |
PollingDelay | Time spent sleeping (in minutes) after polling all mailboxes. Default is 1 minute. |
PollingMailboxDelay | The delay (in seconds) between polling one mailbox and another. Default is 1 second. |
RefreshUsersPass | The number of cycles (on the same mailbox) before UMPolling will fetch the set of mailboxes again. Default is 4 cycles. |
RefreshFoldersPass | The number of cycles (on the same mailbox) that the UMPolling module will perform before it refreshes the folders of a user mailbox. Default is 3 cycles. |
Note: When upgrading to a newer version of GFI Archiver, installation files mentioned in this procedure will be overwritten with default versions making the changes void and ineffective. It is therefore suggested to keep a record of this procedure and follow it once again directly after upgrading to keep this functionality intact.