Unable to purge TotalDeletedItems / Exchange EDB Consistancy test fails

Got a weird one at one of our customers and looking for some ideas.
 One mailbox on exchange 2010 shows the TotalDeletetItemSize as 47.27GB. have tried moving their mailbox to a new mail store and it fails. I have tried all the normal things like checking legal holds and cleaned up the Recoverable Items with MFCMAPI (however unable to delete from the purges folder) tried the Managed Folder / Mailbox Assistant (even -force) to remove but nothing happens.

To throw a spanner in the works the database this mailbox is on fails the consistency check and given the size and space constraints we cannot take the database offline. Most other mailboxes on this servers databases are okay and can move them to the new DAG group without issue. Have also identified some other users where their TotalDeletedItemSize is excessive

 Any ideas on a way to purge these items / move the mailbox without taking these deleted item would be of great help.

Or am I going to have to export their mail to a PST and create a new mailbox for these users?.

Kind Regards

Steve
Mailbox-Stats.png
MFCMAPI.png
Steve McIntyreSenior EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve McIntyreSenior EngineerAuthor Commented:
Source Server is Exchange 2010 SP1 running on Server 2008 R2 Std. New DAG-Group is running Exchange 2010 SP3 with latest rollups on Server 2012
0
Will SzymkowskiSenior Solution ArchitectCommented:
What I would recommend is try Exporting the mailbox for this user and exclude the Delete Items Container. From there create a new mailbox and import the PST into this new mailbox you created.

Commands to use...
New-MailboxExportRequest
and
NewMailboxImportRequest

Once you have done this delete the entire mailbox.

Will.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AmitIT ArchitectCommented:
You cannot run Exchange server with different service pack and RU. It need to be consistence on all servers. So, first you upgrade you old server to same SP and RU level and try again.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Will SzymkowskiSenior Solution ArchitectCommented:
@Amit
You cannot run Exchange server with different service pack and RU. It need to be consistence on all servers.

This is not true. Exchange will operate on different services pack levels per-server. These SP and RU are backward compatible, so it will work. However is it recommended to have all Exchange servers to be at the same SP version and RU.

The only time it is 100% necessary to have an Exchange server at a specific SP version or RU is when you are in a co-existence environment and the legacy Exchange is required to be at a specific SP version or RU update to communicate properly with the new Exchange environment.

Will.
0
AmitIT ArchitectCommented:
@Will

If servers are on different AD site, I agree to run with different SP level, but that also not for long time. However, if it is on same site, all server should be running at same SP level and RU's. I have seen lot of issue while supporting my clients. Let me share one issue. Emails were not submitting from DB1 on SRV1 to DB2 on SRV2 in same site. I spends hours to find out what is the issue and finally, I found SRV2 was running with different RU. Higher than SRV1. I confirmed with Microsoft tier-3 engineer and they confirmed that you should not run Exchange with different SP and RU level. Else you will see such issues.
0
Will SzymkowskiSenior Solution ArchitectCommented:
@Amit - I completely agree that they should be up to the same level, even for Exchange servers in different AD-Sites. However, When you install a SP version it is designed to be backward compatible with other SP version releases, best practice is doing this one at a time, so they have to be able to communicate to old SP versions.

That being said it is they should not be left in a inconsistent state.

Will.
0
AmitIT ArchitectCommented:
You are right.
0
Steve McIntyreSenior EngineerAuthor Commented:
Agree that SP levels should be the same ideally. However given the issues on the source server the client  does not want to introduce additional risks by attempting the upgrade. All mailboxes are being migrated to the new DAG group on new servers I'm the same site. Once all mailboxes have been migrated this server will be reconfigured as transport and client access roles only and updated to latest service packs

Ideally would like to be able to do the local move without having to export to cut out any reconfigurations at the client end, also some of the shared mailboxes are very large ( 20-50gb) giving the potential for  of a lot of manual work and exporting to several PSTs.

But if mailbox export and import into a new mailbox is the only way will have to be
0
Will SzymkowskiSenior Solution ArchitectCommented:
Yeah, I would not recommend doing this for all of the mailboxes just this one in question. Although it might be a manual command you only need to do it for this mailbox in question. This might be the easiest/quickest approach in your circumstances.

Will.
0
AmitIT ArchitectCommented:
What is your deleted item retention period on source DB?
0
Steve McIntyreSenior EngineerAuthor Commented:
Retention was set to 30 days, changed this to 1 day with no changes, however since the databases in question are have failed the consistency test the purge runs and returns complete with 0 items straight away.

@Will - thanks I did have a feeling that I would end up exporting the mailboxes in question (currently sitting at 3) hopefully there will not be too many more with this issue.

Thanks everyone for their comments on this issue. awarding Will the points for this :)
0
Steve McIntyreSenior EngineerAuthor Commented:
Thanks Will, was hoping there was a way to avoid export and import but that's the joys of our profession. Many thans
0
Will SzymkowskiSenior Solution ArchitectCommented:
Glad this solution will work for you!

Will.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.