Solved

Exchange 2013 - Large mail.que file but get-queue reports zero?

Posted on 2016-08-10
3
308 Views
Last Modified: 2016-08-10
Got this on a few of mailbox servers. LArge mail.que file (sometimes as big as 10Gb) yet get-queue reports 0 items waiting to be processed.

Is this right?
0
Comment
Question by:paulfoel
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 35

Assisted Solution

by:Kimputer
Kimputer earned 250 total points
ID: 41750529
10 GB is normal for about 50-60 users.
5 GB for about 30 users.

So yes, don't worry.
1
 
LVL 14

Assisted Solution

by:Schnell Solutions
Schnell Solutions earned 250 total points
ID: 41750537
Yeap.

It is that at some point in time there were many messages in your queue, as far as these messages are stored in the .que file it took that size. Later your queue normalized, but the point is that the .que file increments its size each time that it needs more space, but it does not free up the physical disk that it took before.

So, you have a relatively big file with just a few messages inside.

There you have many options...

a) Probably it is the normal size that your .que file grow under normal operations. Therefore, you can just leave it like this, there are just empty spaces inside that DB file, when the system requires it, then it will be consumed.

b) Assuming that you had a temporal issue, where there was a problem and many messages were queued, and that was the reason why your .que files took that size. Then you can reduce the .que file size, one method of doing it is defragmenting the .que file. It is done in the same way that you make it with the .ese files of your exchange database files. (Using eseutil)
1
 
LVL 14

Accepted Solution

by:
Schnell Solutions earned 250 total points
ID: 41750547
In case that you want to defrag, here is the process:

1. Dismount the Transport Queue DB stopping the Microsoft Exchange Transport Service (It will allow you to make a maintenance on your file. However, be aware that this server is not going to route messages while your maintenance is in place).

2. Defragment your file using eseutil:
Eseutil /d "c:\program files\exchange server\TransportRoles\data\queue\mail.que"
(This example is assuming that your file is located at the default location, if this is not the case you just need to change the path).

3. Start the Microsoft Exchange Transport Service.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question