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

x
?
Solved

Remove Exchange 2003 Information Store

Posted on 2013-01-10
10
Medium Priority
?
410 Views
Last Modified: 2013-03-26
I have had a single Exchange 2003 Standard server running on Server 2003 R2 in a VM.  The mailboxes have grown rapidly and filled most of the drive.  I added a second exchange 2003 server and move all the user mailboxes to it.  The old exchange server is configured as a front end for OWA/OMA, however the information store is still the same size.  Can I decrease the size of that database safely?  Do I need to abandon that server entirely?
0
Comment
Question by:zachreisman
  • 4
  • 3
  • 2
  • +1
10 Comments
 
LVL 49

Accepted Solution

by:
Akhater earned 2000 total points
ID: 38764911
if the database has no users you can simply dismount the databases delete the edb and stm file and mount it again it will create blank files
0
 
LVL 18

Expert Comment

by:Sushil Sonawane
ID: 38765072
You can safely delete the database if you are not use. Microsoft also recommend  on the front end server information store never keep.
0
 
LVL 4

Expert Comment

by:Sabi Goraya
ID: 38765091
to reduce the database to the actual size of the contents in it use eseutil

C:\program files\exchsrvr\bin> eseutil /d c:\progra~1\exchsrvr\mdbdata\priv1.edb

 The above command should do the job, for detailed switches check the link below.

http://support.microsoft.com/kb/192185 

I would recommend eseutil instead of deleting because an empty database don't do you any harm as long it doesn't consume unnecessary space

Take the database offline
Run eseutil
You can do this without any downtime as you don’t have any mailbox on the database

I don’t go for deleting as you can optimise first, Once the space is reduced just dismount it for 5-10 day till you are sure that everything is normal and if our want then go ahead and delete it…

Hope that helps
Thanks
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
LVL 49

Expert Comment

by:Akhater
ID: 38765094
loosing time in defraging an empty database doesn't make sense at all
0
 
LVL 4

Expert Comment

by:Sabi Goraya
ID: 38765133
at Akhater..

I completely agree with you but I always take a safe approach, we don't know the complete scenario and there may be some dependencies which may be the user is not aware at this time as well.
when you have time on your hands I always prefer a safe approach...
Hope you understand...

u are right but it’s just the way I prefer....
Thanks
0
 
LVL 26

Expert Comment

by:Leon Fester
ID: 38766185
Nice idea of mitigating the low disk space on Exchange server #1, but without the proper maintenance tasks, you'll find that you'll run into the same disk space issues again.

In order to prevent this from happening again, add regular maintenance plans for offline defrags to reduce the size of your Information store.
http://support.microsoft.com/kb/328804

Regarding the old server...if it's not in use then delete the information store.

However before deleting, I'd suggest first unmounting the store for a few days just to confirm that there are no dependancies on the information store. After about 1 week/month or whatever time you feel comfortable, if no issues then delete the store. Monitor the event logs daily on both servers to confirm that there are no errors/dependancies.
0
 
LVL 49

Expert Comment

by:Akhater
ID: 38766197
No offence but offline degrag should not be done as it is totally useless starting 2003 sp2
0
 
LVL 26

Expert Comment

by:Leon Fester
ID: 38766222
No offence but offline degrag should not be done as it is totally useless starting 2003 sp2

[hijack]
Hey ANTOINE, off topic discussion, why do you say the above?
Do you have any links to this discussion?

We still use offline defrag for reducing mailstore sizes on Exc2007
I'm interested in the reasons so I can explain it to others at my Company.
[/hijack]

@zachreisman, sorry about the hijack
0
 
LVL 49

Expert Comment

by:Akhater
ID: 38766251
I don't think there is any hijack and the purpose of this site is to share info and ideas

1. pre exchange 2003 sp2 the database limit calculation was done on the edb size and not the used space inside the database so we needed defrag to stay within the maximum size limit in standard edition. In sp2 the limit is based on the actual used size and not the edb size

2. offline defrag needs down time for all the database and all the users

3. in exchange 2003 standard edition we are limited to 1 database so, if the physical drive comes to a limit, we had little choices to extend the drive or do an offline database defrag. In 2007 you can create more than one DB even in standard so the better option is to simply create a new database and move all the users to it. advantages? No downtime at all and you end up with one clean database
0
 
LVL 26

Expert Comment

by:Leon Fester
ID: 38766333
Thanks for the update, while adding additional databases is one of the methods we already use to manage store growth. SAN storage comes at a premium cost, which management often doesn't understand and then they start questions capacity planning capabilities. The issue we face is constantly having to justify why we need additional space.

In mail intensive environments with Rightfax connectors sending faxes directly to mailboxes we often still had capacity issues.

I already use stubbing and journaling through Mimecast, and previous sites I've used Zantaz EAS for the same tasks. But even with those solution inplace our main processing mailbox, for incoming faxes, used to regularly consume about 30GB in a week.

In a scenario where there is limited available storage; what else would you suggest as a means to manage/reduce storage requirements for Information stores?
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

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

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses
Course of the Month19 days, 11 hours left to enroll

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