Today we are announcing the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013. These releases include fixes to customer reported issues and updated functionality. Exc...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi, we are fighting with exchange 2013 since 2 years, and with this enviroment :
64 databases (around 200 Gb each) , 55 users per database, 3 servers in 1 DAG
VIRTUAL SERVER (in VMWARE ESX)
server 1 (32 db active copy, 32 db passive copy) + CAS ROLE : 18 Cores (AMD OPTERON 8174) 2.2 GHz - 48 GB RAM
server 2 (32 db active copy, 32 db passive copy) + CAS ROLE : 18 Cores (Intel XEON e5-2620v3 ) 2.2 GHz - 48 GB RAM
server 3 (64 db passive copy - lagged 10 days) + CAS ROLE : 8 Cores (AMD OPTERON 8174) 2.2 GHz - 32 GB RAM
in order to have a stable and quite acceptable performance, we have stopped the health service and search service, otherwise the cpu and ram seems to soffer (outlook clients disconnect, databases unmount and keep switching between servers).
Applying the formulas posted here :
https://technet.microsoft.com/en-us/library/ee712771(v=exchg.141).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part1.html
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part2.html
seems that the correct sizing should be a total (all servers) of 218 Cores and 256 Gb RAM
is that right ?
thank you