Mails que is increasing for a particular database in exchange server 2010-Urgent help please
I am using exchange server 2010. Since last 3 days, I am facing problem that mails for a particular database is going in que.
I have two mailboxes in same location in DAG and two hubtransport/cas server. Memory utilization is around 91 %.
I have 6 exchange DB, all are working fine except DB06. Mails are going in que for DB06. IT IS GOING HIGH ON BOTH TRANSPORT SERVER. 1.jpg
ExchangeDatabases
Last Comment
Arif Khan
8/22/2022 - Mon
Leslie Maclachlan
IS the database mounted?
viktor grant
Hi,
Do you have any events regarding Backpressure?
Check if you have events around 15000-15010?
Cheers
Arif Khan
ASKER
Yes, I had back pressure of Memory but increased it. And there is back pressure then all the database mail flow will be stopped but here problem is with only one database , DB06.
The resource pressure increased from Normal to Medium.
The following resources are under pressure:
Version buckets = 139 [Medium] [Normal=80 Medium=120 High=200]
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 path ("D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\mail.que") = 16% [Normal] [Normal=95% Medium=97% High=99%]
Queue database logging path ("D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\") = 82% [Normal] [Normal=95% Medium=97% High=99%]
Private bytes = 14% [Normal] [Normal=71% Medium=73% High=75%]
Physical memory load = 37% [limit is 94% to start dehydrating messages.]
Batch Point = 0 [Normal] [Normal=2000 Medium=4000 High=8000]
Submission Queue = 0 [Normal] [Normal=1000 Medium=2000 High=4000]
Arif Khan
ASKER
The resource pressure increased from Normal to Medium.
The following resources are under pressure:
Version buckets = 134 [Medium] [Normal=80 Medium=120 High=200]
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 path ("D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\mail.que") = 16% [Normal] [Normal=95% Medium=97% High=99%]
Queue database logging path ("D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\") = 82% [Normal] [Normal=95% Medium=97% High=99%]
Private bytes = 9% [Normal] [Normal=71% Medium=73% High=75%]
Physical memory load = 30% [limit is 94% to start dehydrating messages.]
Batch Point = 0 [Normal] [Normal=2000 Medium=4000 High=8000]
Submission Queue = 0 [Normal] [Normal=1000 Medium=2000 High=4000]
Arif Khan
ASKER
The resource pressure increased from Normal to Medium.
The following resources are under pressure:
Version buckets = 110 [Medium] [Normal=80 Medium=120 High=200]
Physical memory load = 91% [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 path ("D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\mail.que") = 16% [Normal] [Normal=95% Medium=97% High=99%]
Queue database logging path ("D:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\") = 82% [Normal] [Normal=95% Medium=97% High=99%]
Private bytes = 14% [Normal] [Normal=71% Medium=73% High=75%]
Batch Point = 0 [Normal] [Normal=2000 Medium=4000 High=8000]
Submission Queue = 0 [Normal] [Normal=1000 Medium=2000 High=4000]
Thank you. I followed the same process but nothing helped. I have logged case with Microsoft team. They are still not able to give any solution but corrupted STORE service. They are working on it.