Exchange Database

lancon

lancon

Senior Member
Joined
Jun 30, 2011
Messages
799
Reaction score
397
Location
Cape Town
Middag middag.

I have a question regarding exchange db.
I got some of the users to delete quite a bit of emails.
I checked and 2 users mail box sizes drop quite significantly, yet the exchange files ,(priv1.edb and priv1.stm), stay at 42GB and 22GB respectively.

Any reason for this as the server has a serious space issue again.

Just a side note, I moved the page file to D: earlier and cleaned up 2GB. Its all gone again.

Tx Gents.
 
They stay that size until defragged (which takes at least that amount of free space).
 
Which version of Exchange are you running?

I used Exchange2003 - and to shrink its DB you'll need to defrag it, which can easily run a long, long time.

You can implement mailbox size quotas for all users. If their mailboxes reach a certain limit, they will get a warning. If they continue, then they will get a second warning, and will not be able to send, but receive only. Third warning, unable to send/receive.

Until they do either an archive or (the preferred method) export their older data to a PST file.

A big issue with Exchange, especially if you don't have any maibox size quotas enabled.
 
Claymore said:
They stay that size until defragged (which takes at least that amount of free space).
Click to expand...

According to a technet blog, that's not actually their recommended method:

http://blogs.technet.com/b/exchange/archive/2012/01/30/3470667.aspx

How can I reclaim the whitespace?
Naturally, after seeing the available whitespace in the database, the question that always ensues is – how can I reclaim the whitespace?

Many assume the answer is to perform an offline defragmentation of the database using ESEUTIL. However, that's not our recommendation. When you perform an offline defragmentation you create an entirely brand new database and the operations performed to create this new database are not logged in transaction logs. The new database also has a new database signature, which means that you invalidate the database copies associated with this database.

In the event that you do encounter a database that has significant whitespace and you don't expect that normal operations will reclaim it, our recommendation is:

Create a new database and associated database copies.
Move all mailboxes to the new database.
Delete the original database and its associated database copies.
Click to expand...
 
Firstly are you running daily backups of the Exchange server? This will clear the Exchange log files if you don't have circular logging enabled.

As for the databases, the best way to reduce their size would be to create a new database and move the users into it which will then only take up the required space and remove the old database files once everyone has been moved. Looking at the file names I'm guessing you're still on Exchange 2003 which means that the users being moved won't have access to their mailbox until the move is completed as it doesn't support online mailbox moves.
 
Morning gents.
I will discuss the problem with the boss lady when she is in later today.
After restarting the server again this morning I had a look and found two dyndns log files.
DynDNS20140312.log 686?Mb and
DynDNS20140411.log.

Are these log files safe to delete or maybe move to the D drive???
Seems rather large for a log file. Tx in advance.
 
DynDNS App installed on that server? Any specific reason for that? Could move it to another server perhaps?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X