Link to home
Start Free TrialLog in
Avatar of BJMagill
BJMagill

asked on

Exchange 2010 Back Pressure issues

Every so often I get the following event in the Application Log on our Exchange 2010 SP1 server.

The resource pressure increased from Normal to Medium.

The following resources are under pressure:
Version buckets = 120 [Medium] [Normal=80 Medium=120 High=200]
Physical memory load = 94% [limit is 94% to start dehydrating messages.]

The following components are disabled due to back pressure:
Inbound mail submission from the Internet
Mail submission from Pickup directory
Mail submission from Replay directory
Mail delivery to remote domains
Content aggregation

The following resources are in normal state:
Queue database and disk space ("C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\mail.que") = 67% [Normal] [Normal=94% Medium=96% High=98%]
Queue database logging disk space ("C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\") = 68% [Normal] [Normal=92% Medium=94% High=96%]
Private bytes = 5% [Normal] [Normal=71% Medium=73% High=75%]
Batch Point = 0 [Normal] [Normal=1000 Medium=2000 High=4000]
Submission Queue = 0 [Normal] [Normal=1000 Medium=2000 High=4000]

Any ideas on how to stop this from stopping mail flow?
Avatar of Beyond Next Solutions
Beyond Next Solutions
Flag of United States of America image

If version buckets are under pressure, this is a measure of the I/O pressure on the system because of the database reads and writes. Therefore the system will recover itself in a short time. If you trigger this state very frequently, consider changing the VersionBucketsHighThreshold to larger values in the EdgeTransport.exe.config file. The default location of the Edgetransport.exe.config file is C:\Program Files\Microsoft\Exchange Server\bin.

Taken from: http://technet.microsoft.com/en-us/library/bb218336(EXCHG.80).aspx
ASKER CERTIFIED SOLUTION
Avatar of Beyond Next Solutions
Beyond Next Solutions
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I notice you have placed the Hub Transport mail que file on your 'C' drive. If you have also got the mailbox database and log files all on that same drive you will run into problems like you're getting now. You should consider moving the database and log files (and the hub transport database) to a different drive on your server.
but if i move the database and log files on a separate drives the problem will be solved?