Exchange Server 2007 Mailbox database drive almost full ?

Hi People,

I got Exchange Server 2007 SP1 with CCR implementatio, and now my Mailboxe Database drive is almost full with just 1 GB less but the transaction log drive is fine 10 GB free.

It is a Physical RDM attached drive to the SAN LUN.

So what is the best approach to keep the email service working ?

LVL 11
Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

I believe that your mailbox database and transaction log file are on different LUN compare to mine where both on same drive. So for your case, just make sure that your mailbox database LUN has bigger freespace.
Senior IT System EngineerIT ProfessionalAuthor Commented:
yes they're both in different LUN, but i just wonder what should I do to make it bigger or decrease the size of the mailbox database with minimal downtime?
Add another drive to Active and Passive node with same drive letter which is the basic requirement.

Create additional storage group, move mailboxes to the new one.

Dismount the primary storage group database.. Remove the database and log files completly (take a backup copy). Mount the database blank (dial tone).

Move few mailboxes to this database if you want to keep both the drives running.

No down time required.

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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Senior IT System EngineerIT ProfessionalAuthor Commented:
Hi  KalluSureshKumar,

Thanks for the suggestion to create a temporary Storage Groups (which consists of DB and Logs).

So based on your suggestion I believe during the business hours the mailbox migration from one SG to another SG shouldn't cause any impact or downtime for the users ?
Senior IT System EngineerIT ProfessionalAuthor Commented:
so what about in the mean time if I redistribute the Mailbox users across the other SG ? does that also helps in the mean time so that the disk space is not consumed further?
If you are not using legacy clients like Outlook 2003 then you shouldn't have problem . Autodiscover will take care of Outook 2007 an Outlook 2010.
Senior IT System EngineerIT ProfessionalAuthor Commented:
no all of the client is using 2007.

So in this case the only effect is that the users will not receive and send email during the migration ?
Mohammad Ishtyaq khatriSr. Systems EngineerCommented:
Have you checked the white space ? If its enough to occupy the space then i'll suggest you to create a new database & move the mailboxes over & delete the old database this will help in regaining the size & eliminate the white space.
Senior IT System EngineerIT ProfessionalAuthor Commented:
Hi  agentmik, so how do I check the size of the whitespace ?
is there any way to reduce it apart from mailbox migration ?
White Space :-- Please check Event ID 1221 in the Application on the server. Event the event ID doesn't appear. Please try to improve the Diagnostic Logging level to Maximum, then check it again.

Set-EventLogLevel MSExchangeIS Public\General -Level 5

So after enabling the diagnostic logging the Event ID will appear only when your online maintenance is finished.

I dont see any other way of reducing database size either by adding additional storage or checking white space and if it has enough then move the mailbox to different database and delete the old one .

When the mailbox are under migration, the user will still be able to access his e-mail and send but the mails will sit in outlook outbox folder until the mailbox is moved and mails on the server will sit on the server .
Senior IT System EngineerIT ProfessionalAuthor Commented:
Thanks man for the suggestion to run Set-EventLogLevel MSExchangeIS Public\General -Level 5 so if I forgot to turn off that command, will it affects the production performance ?
If shouldt be, it will be unnoticeable. But once you collected the white space details you can turn off.

This command is for PublicFolder database :
Set-EventLogLevel MSExchangeIS Public\General -Level 5

This is for Private / mailbox database:
Set-EventLogLevel MSExchangeIS Private\General -Level 5

To revert back the settings. Please use

Set-EventLogLevel MSExchangeIS Public\General -Level 0

This is for Private / mailbox database:
Set-EventLogLevel MSExchangeIS Private\General -Level 0

I have forgot to ask you about the passive node drive space on this thread. Do have enough free space on the passive node or its same. If you have enough space that would be awsome.  You can just failover. Suspend replication then reseed.
Senior IT System EngineerIT ProfessionalAuthor Commented:
Yes I do have same enough drive space in the DR node. My Mailbox Server is set with CCR.
Senior IT System EngineerIT ProfessionalAuthor Commented:
and this is the current log setting for my MBX server:

Identity                                        EventLevel
--------                                        ----------
MSExchange Common\General                       Lowest    
MSExchange Common\Configuration                 Lowest    
MSExchange Common\Logging                       Lowest    
MSExchange Extensibility\Transport Address Book Lowest    
MSExchange Extensibility\MExRuntime             Lowest    
MSExchange EdgeSync\Synchronization             Lowest    
MSExchange EdgeSync\Topology                    Lowest    
MSExchange EdgeSync\SyncNow                     Lowest    
MSExchange Management Application\Shell         Lowest    
MSExchange Management Application\Console       Lowest    
MSExchange Process Manager\ProcessManager       Lowest    
MSExchange System Attendant Mailbox\General     Lowest    
MSExchange Topology\Topology Discovery          Lowest    
MSExchange ADAccess\General                     Lowest    
MSExchange ADAccess\Cache                       Lowest    
MSExchange ADAccess\Topology                    Low       
MSExchange ADAccess\Configuration               Lowest    
MSExchange ADAccess\LDAP                        Lowest    
MSExchange ADAccess\Validation                  Low       
MSExchange ADAccess\Recipient Update Service    Lowest    
MSExchange ADAccess\Site Update                 Lowest   

Open in new window

What is your plan now ? Do you still need any assistance from our side.. or did you get enough information needed. If yes , please close the thread with points :-)
Senior IT System EngineerIT ProfessionalAuthor Commented:
Thanks man !
Senior IT System EngineerIT ProfessionalAuthor Commented:
hi, so if i migrated the DB out from the old SG into the new SG, Do I have to re-create the SG or just create new database to shrink the white space ?
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
Active Directory

From novice to tech pro — start learning today.