[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Exchange 2013 pst import looping

Posted on 2014-02-18
9
Medium Priority
?
343 Views
Last Modified: 2014-02-26
Hi Everyone

Please can you help with the following :

OS : Server 2013 Std / Exchange 2013 Std { loaded in same environment - inherited from previous admin }
Updates : Fully updated

We recently took over a site that could'nt be administrated by the internal admin.
The problem we encountered is that the Exchange database grows by atleast 20GB every 2 - 3 days.
I've read up on this a bit and have picked up that it could be a pst import that is looping.
If so how can i resolve this.

The previous Exchange DB on SBS2003 was 25GB in size holding all user mail.
The DB on the Exchange 2013 is now sitting at 184GB.
Something is very wrong.

Thanks
0
Comment
Question by:aNaLyz3R
  • 6
  • 3
9 Comments
 
LVL 14

Expert Comment

by:Don Thomson
ID: 39867354
Go into the Exchange Management Shell

Paste this into the cmd line

Get-MailboxStatistics | Sort-Object TotalItemSize -Descending | ft DisplayName,@{label="TotalItemSize(MB)";expression={$_.TotalItemSize.Value.ToMB()}},ItemCount

It will give you the size and number of items for each user - Find out which user has nmore than any other and check their workstation
0
 

Author Comment

by:aNaLyz3R
ID: 39869675
It prompts for Identity:

Do i have to go through each mailbox accordingly?
0
 

Author Comment

by:aNaLyz3R
ID: 39870489
Ok i have run the above and went through each user account.
If i check the amount of items in each user account it ranges from 432 to 17391 items.
What is regarded as high?
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 14

Expert Comment

by:Don Thomson
ID: 39870843
I would say that 17391  is a bit high but if the one with 432 items all have 10 meg attachments then it could be the problem.   Look at the total size rather than the number of items.

Also have you done a full backup of the exchange - If not do so - the transaction log files could be getting in the way of giving you a proper size.

How many users does the Exchange box have?
0
 

Author Comment

by:aNaLyz3R
ID: 39870878
I've checked the size of the mailboxes, they range from 40mb to 2900mb.
The logs files which are on a separate drive are 90gb in size, I'm going to do a full backup on that exchange ASAP.
The server hosts 18 users....
0
 
LVL 14

Expert Comment

by:Don Thomson
ID: 39871337
With only 18 users the average size looks to be over 10 gig per user.  I would say do a backup and then use eseutil.exe /d <databasename> to defrag it

You may want to run the eseutil /g  and eseutil /p   as required

the eseutil.exe is located in the C:\Program Files\Microsoft\Exchange Server\Bin
folder.

My Database is in the C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group

folder so you would typically start by doing an integrity check using

cd \C:\Program Files\Microsoft\Exchange Server\bin

eseutil /g "..\mailbox\first storage group\Mailbox Database.edb"

to check the integrity of your db
0
 

Author Comment

by:aNaLyz3R
ID: 39872853
At this stage i doubt defragmentation of the DB is going to help as the DB is still growing at approximately 4 GB per day.

I've read the below article, right at the bottom the person that experienced the same issue confirm how he resolved it, my question is, isnt there a faster way to resolve it and find the mail account that has the "loop" in it?

http://community.spiceworks.com/topic/438942-extremely-fast-database-growth-exchange-2013
0
 

Accepted Solution

by:
aNaLyz3R earned 0 total points
ID: 39876844
The fastest way to complete this at the moment is to migrate all the mailboxes to a new DB. It may take some time as you need to find the mailbox that is causing the white space within the old DB. Once found, i exported the mailbox data of the faulty mailbox, deleted the mailbox, recreated and restored the data.
Once i migrated all mailboxes, i deleted the DB that grew to a size of 300GB from 19GB.
0
 

Author Closing Comment

by:aNaLyz3R
ID: 39888285
Worked for my specific issue
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

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

Recently, I was assigned the task of performing a hardware refresh in the datacenter. The previous Windows 2008 systems were connected to the SAN via fiber channel HBA’s and among other thing, had PowerPath installed in order to provide sufficient f…
The article will show you how you can maintain a simple logfile of all Startup and Shutdown events on Windows servers and desktops with PowerShell. The script can be easily adapted into doing more like gracefully silencing/updating your monitoring s…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Suggested Courses

873 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