Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
edb and stm files growing quickly
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
edb and stm files growing quickly - 29.Dec.2006 5:27:16 AM
|
|
|
trevorc
Posts: 64
Joined: 11.Jul.2006
Status: offline
|
I have two Exchange 2000 Standard running on two Win2K Server SP3 servers (MAIL1 and MAIL2). MAIL1 is a DC and MAIL2 is a member server. MAIL1 is an internet facing machine and has no mailboxes on it. All the mailboxes are on MAIL2. Since both machines are on the same AD, if someone sends an outside email, it will first be received by MAIL1 and since the mailboxes are on MAIL2, it will be forwarded to it's respective mailbox on MAIL2. I am noticing that my .edb and .stm files on MAIL1 are growing very quickly...nearly 12Gb. I cannot understand why because there are no mailboxes on this server. I am afraid that with time, i reach the 16Gb limit! On MAIL2, the .edb and .stm files are about 10.5Gb. I cannot understand why the internet facing server has bigger db files that the server having the mailboxes! When MAIL1 forwards emails to MAIL2, does it keep a copy of the mail too? Thanks in advance for any given help.
|
|
|
|
RE: edb and stm files growing quickly - 1.Jan.2007 4:16:25 AM
|
|
|
jassyca
Posts: 227
Joined: 20.Jul.2006
Status: offline
|
Couple questions for you.. On Mail1, did you tell it it was a "front end" server? There's a check box for that. (I'm not in front of my server just now but I think it's something like Exchange System Manager --> Administrative Groups --> Servers --> Mail1 then the properties of Mail1 and it seems to me I remember seeing that check box on that very first tab-page). What do you see when you expand the "Mailboxes" for Mail1? (Again, I'm not sure where that's at but something like Exchange System Manager --> Admin Groups --> Servers --> Mail1 --> First Storage Group --> Private Storage Group --> Mailboxes.)
|
|
|
|
RE: edb and stm files growing quickly - 2.Jan.2007 6:27:01 AM
|
|
|
trevorc
Posts: 64
Joined: 11.Jul.2006
Status: offline
|
Thanks for replying. I do not remember specifing to MAIL1 that it is a 'Front End' Server. I looked in Exchange System Manager -> Administrative Groups -> Servers - MAIL1 properties but there isn't this option. Can it be that it is not for Exchange 2000 Standard? When i expand the mailboxes on MAIL1, there are only 5 mailboxes. ie: - System Attendant
- EUQ_MAIL1
- SMTP (MAIL1-{34CEC4EC-****-****-****-************})
- SystemMailbox{34CEC4EC-****-****-****-************}
- Administrator
The first 3 mailboxes are 0KB whilst SystemMailbox and Administrator are 2,610KB and 28,182KB respectively.
|
|
|
|
RE: edb and stm files growing quickly - 3.Jan.2007 10:18:53 AM
|
|
|
jassyca
Posts: 227
Joined: 20.Jul.2006
Status: offline
|
Oh oh oh!! Stupid me! I didn't look at your message history. That would've explained things. Duh! If you have a storage group with mailboxes and someone deletes a ton of messages or, on the other hand, if you get rid of a bunch of mailboxes, the storage group's database won't shrink. Once it grabs drive space for itself, it's going to stay that size until you defragment it. The idea is that Exchange can always re-use the space because, internally, those database records are "blank". So if MAIL1 had all the mailboxes and they've been moved to MAIL2, no wonder MAIL1 is so large. You're not going to get that space back until you defrag. And, if I'm right and understand properly how it defrags, it should not take 12 hours because there really isn't 12 gig worth of data in the database. It only has to work through the valid messages which used, what, 23 something meg? It's still an "after hours" project, though. Always better to do this type of thing when there's less chance of the dreaded "is email down?" phone calls from users. Less pressure, more time to think.. incase something goes wrong. Let us know how it goes.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|