Hi,
I'm having connection issues with archiving / retrieval tasks.
Environmeant:
2 EV servers (both clustered active/passive failover) version 11.0.1 / Outlook 2013 SP1
12 Exchange 2013 CU5 nodes (DAG) + 4 CAS servers that actually handles the connections to the 12 mail server nodes.
Each EV server handles 6 exchange mail nodes archiving tasks
1# EV server handles also storage and indexing alone, the 2# EV servers has been added purely to handle the archiving tasks (thread account restriction reasons)
In article http://www.symantec.com/docs/TECH198553
(I know it's about exchange version previous than 2013 CU1 and should not concerne our environmeant) BUT at the bottom of that article is section:
Option 2
Configure each Exchange archiving task to run under a different user. This means that the 32 MAPI session store limit per user should not be reached because each task has its own 32 session limit, rather than sharing a single 32 session limit.
- Stop all Exchange archiving tasks.
- For each Exchange archiving, mailbox, journal, and public folder task, create a new user with an Exchange mailbox.
- Grant each user the required Enterprise Vault and Exchange Server permissions using the Enterprise Vault documentation.
- Go to the each Exchange archiving task's Log on tab.
- Click Use this account.
- Enter the newly user account to be used with the task.
- Enter the password for the user account.
- Click OK to commit the task properties changes.
- Restart the Exchange archiving tasks.
Do you think doing that would have any benefits at all? And if it is something to try, can the Log in account be same as system mailbox account or does it need to be separate account? What additional permissions would the system mailboxes need if those can be used here?
Sani B.
