TMS
asked on
Exchange Services restart
On the odd occasion Exchange on SBS2011 suffers back pressure. Probably to do with the Popcon app I have (which works very well). When I turn back pressure monitoring off and try and restart the services they always get stuck and I have to restart the server.
I wondered if anyone have any thoughts as to why or suggest the order of restarting.
I wondered if anyone have any thoughts as to why or suggest the order of restarting.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As I am sure you know, back pressure is the result of insufficient free space on the C: drive. Do you have another drive with lots of free space? If so, have you run the wizards in the SBS console to move things like exchange mailboxes and WSUS data to the other drives?
Actually, Backpressure is not only caused by disk space issues. This is a list of reasons:
Free space on the hard drive that stores the message queue database.
Free space on the hard drive that stores the message queue database transaction logs.
The number of uncommitted message queue database transactions that exist in memory.
The memory that's used by the EdgeTransport.exe process.
The memory that's used by all other processes.
The number of messages in the Submission queue.
The articles I posted earlier mentions all this and more, on handling Backpressure.
Free space on the hard drive that stores the message queue database.
Free space on the hard drive that stores the message queue database transaction logs.
The number of uncommitted message queue database transactions that exist in memory.
The memory that's used by the EdgeTransport.exe process.
The memory that's used by all other processes.
The number of messages in the Submission queue.
The articles I posted earlier mentions all this and more, on handling Backpressure.
gellisson, how are you doing with your Backpressure problem?
ASKER
Thanks for the follow up. Thanks also for your initial reply. At the moment it is not an issue so this was more a preventative question.
In your first reply you mentioned changing the monitoring interval. The exchange book I have doesn't mention this. What is the consistence of say changing it to 5? And when would you set this to 30?
In your first reply you mentioned changing the monitoring interval. The exchange book I have doesn't mention this. What is the consistence of say changing it to 5? And when would you set this to 30?
Changing the level does not really fix an issue if there is one, it just looks at it less. So that you may not get it as often, but also in doing so, it can make your system a bit more susceptible to being overwhelmed. It really is only a work around for you till you can actually fix the issue, but freeing up Disk Space, Memory or Submission issues.
ASKER