I have an exchange 2013 server with 30 appx user taking 200 GB of DB file and 300 GB of logs. Looks like log files are little two big than usual.
Last week, I had couple of users trying send 45 mb attachment and immediately after that server pegged up on both CPU and RAM. After that I ended up assigning 4 vcpu from vsphere web client and 32 gb ram instead of 24 gb.
Assigning 32 GB to compensate for IO looks way too much than required as it seemed to drop down after resources were and performing good.
Could exchange just be reacting and pegging up resources when users are trying to send big attachment. Could this be easily addressed by limited send and receive items? or It has something to do with growing log files and needs to be addressed differently .
I do not see major error on apps and system event log on exchange server