This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 54%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELC%3C/text%3E%3C/svg%3E)
I have an environment formed by 8 servers, they are configured in DAG mode, that is, 4 A and 4 B...
Recently we are getting error 139, 159 and 152 related to ExchangeStoreDB - "The copy of database X on this server appears to be experiencing performance issues, possibly as a result of storage failture.
We have already analyzed the storage and antivirus and there is no problem.
Storage are SSD disks, I also ran perfwiz to validate the I/O behavior.
I tried to search for the question, but I didn't find anything that helps me.
Does anyone have a solution for this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
What's your Exchange server CU version?
You could firstly use command below to check the health of your DAG:
Get-MailboxDatabaseCopyStatus
I saw a related thread discussed this issue: False Database Performance Alerts
Reset search index catalog for affected MDB
And you may also consider moving database to a new hard drive.
If this issue still exist, I would suggest confirm with Windows server team to check whether there exist a tool that could monitor the performance of your Windows server. You will know whether there exist any service occupied too much resource.
Exchange 2019 CU 11.
I ran the copy status command and the dbs are mounted and healthy
Thanks for the help, but your discussions are aimed at exchange 2013, I don't know if you noticed, but my environment is 2019 and the indexing mode is direct through the big funnel search engine, that is, directly in the mailbox and not the databases.
Hi @ LucasCaparoz-0668
Is there any further update about this issue so far?
I asked my team to validate the storage part, but so far no progress... it seems that this forum will not be able to help...
Those events always mean storage :)
I know you say "We have already analyzed the storage and antivirus and there is no problem."
But I would explore storage deeper