Exchange database store bloated, real slow refrag

Defrag runs around 4-5GB but very much depends on the server performance.

How to run Eseutil on a computer without Exchange Server
http://support.microsoft.com/kb/244525

Exchange Server 2003 (Check for this)

- Rancy

Is there something I need to do to this store before defragging it? maybe something involving isinteg? - Not needed :)

Let me know if you have any doubts or Queries

- Rancy

What I am looking for is maybe a way of sorting this without it taking several days to defrag... 10 hours it only got to 10% done.

There is nothing else that you need to do before you start for the defrag other than a full healthy backup.

But, Instead of a defrag I would suggest you to(since you said the DB size is 150GB, you are running enterprise version),

1. Create additional mailbox database
2. Move all mailboxes to new database
3. Delete the empty database.

This is what is being recommended most of the time to ensure there are no downtime to the end users.

Did you make a copy of the database before running the defrag ?
If its in middle of the eseutil there isnt much we can do as stopping might also corrupt the database.

If you are using "Exchange Enterprise edition" you could always create a New Mailbox database and move mailboxes and delete the one. But if its the Default Database than you will have to rehome the "System Attendant" mailbox also if you have "Exchange Standard edition" then also you can mount the database with blank and then put this 150GB Database into RSG and merge ..... only thing you have to make sure is that users are informed of the downtime they will have.

If you have any doubts please get back to us with concerns :)

- Rancy

Hi Rancy :)

It is standard not enterprise and I reverted to a VM snapshot I took prior to starting the defrag.

Am I able to create a new database store and move the contents of the current one into it?

thanks
Tracy

PraveenBalan: mentioned Enterprise so i got confused :)

Am I able to create a new database store and move the contents of the current one into it? - Exchange 2003 Standard only allows one Mailbox and PF DB .....

However you can do the second part ... user must be aware that its going to take sometime for their data to show without downtime required for Defrag.

I mean using RSG and Merge :)

- Rancy

sorry, not quite clear about this. I can't create another database store so what do I do??

cheers

tracyprier: Please check it with ESM and if any issues please check with event 1216 or 1217 in App logs :)

- Rancy

Excuse the dumb question... but what is RSG?

this sounds like a good solution.

Praveen; it is standard. As per original post a users mailbox got corrupted somehow (still gotta find out what happened exactly) and it blew up to 85gb . This size was not real but the database store files still add up to 157gb... even though they aren't actually this big.

Tracy

Before you proceed with the plan to move ahead with the RSG plan kindly check the event id 1221 in application logs and see what is the amount of white space on your database. That would help you understand where exactly you stand in terms of your actual Database size. It of course is within 75Gb that is why is mounts. Reason why I suggest you to check the event id 1221 is:
1. You would come to know the actual size of your Database (current size minus the white space as shown by the event id)
2. SIS (Single Instance Storage) would break and the blank database mounted by you would bulge post the merge thing that you would go ahead with.

Don't you thing this is kind of a short term solution.

Rather than planning to come over this problem for only a short period why not going with the plan to mounting the Blank database. Using RSG export the data to PST and provide to individual users and set up some sort of Mailbox size limit at store level that would save you from such issue in near future..at least not soon enough.

:)

Regards
- SKS

thanks SKS... what is RSG?

A Recovery Storage Group is a specialized storage group that can exist parallel with regular storage group. it is similar to a normal Storage group but is mainly used in recovery scenarios where you can work with it without hampering your production.

Reading this article might help you with a fair bit of understanding
http://support.microsoft.com/kb/824126

You would need to perform few of the steps provided on this article (Exmerge part precisely).
http://www.simple-talk.com/sysadmin/exchange/exchange-recovery-storage-groups/

Feel free to ask for assistance if things are not clear and we would try our best to assist.

Great :)  thanks for that. I'll read up on it and get back to you if I have any questions.

RSG is Recovery Storage Group and this is somewhat like not a part of your production environment .... so if your using it will not hamper the Production ability to Send\receive or any other functions.

You can go through the lings and if any queries can consult us.

- Rancy

Great, thanks Rancy :)