I've upgraded the operating system from Server 2012R2 to 2019, and have now IIS 10.0 instead of 7.5 (its about time).
Migration was flawless as it should be, server were offline under 30 mins.
C: is OS and Smartermail Program Installation (NVMe)
D: is SmarterMail data Installation and spool files (NVMe)
E: is for customer / domain 1 (SSD)
F: is for customer / domain 2 and up (SSD)
Storage System of the domains "idles" at around 1-8MBps reading when syncing via MAPI.
Active Time around 1-2.5% (SSD). the NVMe idles at under 0.5% time.
Yesterday Monday, everything worked fine as it should until around 16:00, then MAPI stopped synchronizing on domain 1.
Today Tuesday, MAPI stopped synchronizing on domain 2 on around 10:15, after a reboot of the server.
This means, I have to resynchronize Domain 2 too from scratch.
Tried "Resync User Protocols", but no new E-Mails came into Outlook 2019/365, just the old ones.
Deleted Outlook OST File, E-Mail synchronization begins from scratch.
For me, these are annoying issues:
- why stopped MAPI on domain 1 - nothing into the logs
- why stopped MAPI on domain 2 after a simple reboot (no Windows Update, just a reboot)
- why cannot the server use more CPU cores (runs on 50-60% CPU) when under heavy load
Furthermore, how much RAM is recommended with MAPI, because I see now huge RAM usage levels during the synchronization of 88-92% which is unusally high (7.3GB of 8.0GB, 4.8GB is SmarterMail Service alone).
I have plenty of ressources, but now I'm afraid to shut down the Server and allocate more RAM due to the incident this morning.
Unfortuanlly, the MAPI mailboxes are huge: 60 / 57 / 13 / 11 / 10 / 9 / 6 / 5 etc. GB which makes the download even more annoying.
Does just I have this problems or do my customer use too big Mailbox sizes for Outlook or SmarterMail?
Webmail runs flawless, just MAPI doesn't run smooth as it should.
Thank anyone for additional information for optimizing my installation.