How can I determine the source of a problem with version buckets in Exchange 2013?

Question

Microsoft Exchange

Good afternoon! Recently, a strange thing has been happening to the exchange server: the version segment counter starts to go off scale and stops the transport. Previously, I corrected the "medium" and "high" state of the segment counter of versions up to 2000 and 3000, respectively, everything was in order (we have a slightly strange system of mailers and occasionally there are mass mailings from one server (which is not an exchange) to another - but in this there were no such distributions).
Now, judging by the logs, the version buckets counter successfully exceeds 3000, message circulation stops. In the transport folder at this moment there are about a hundred 5-megabyte trn files.
How can one determine the source of such a situation? Considering that when the transport stops and the queue begins to accumulate, there is no huge number of messages with large attachments in the queue, well, that's all. Transport can stand still with the message "resource load (version segments) has increased to high", and 20-30 letters without attachments can hang in the queue.

Answer 1

The problem is with the disk subsystem. First, check that there is enough free space on the disk. Secondly, make sure that the disks are sufficiently productive, there is no fragmentation. If the drives are old and slow, replace them with new and fast ones. If you already have a normal RAID or storage system, check if everything is in order with the storage, whether they give out enough IOPS at the time the problem occurs.