Re: priv1.edb, Offline Defrag, and Low Hard Drive Space
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 15:03:20 -0400
Gibs <DalkoTester@xxxxxxxxx> wrote:
I have been running SBS 03 R2 Standard for only one week. On Friday,
I noticed that my 'd' drive (where I put the shared users folder and
MDBDATA folder) was rapidly shrinking.
How big is the volume in question?
After a little research, I
learned that my priv1.edb was growing (I guess because it is a new
network, and all email accounts were migrated over at once), and
needed defraged.
No....this is not something you should be doing on a regular basis. Your
Exchange databases & logs ought to be on a volume where no user accessible
shares/data is stored, so they can't be bumped into by the file system
growing in leaps and bounds...
What you probably need are good mailbox quotas, set as defaults on the
store, and any exceptions made on a per-mailbox level.
You can see how big each mailbox is, by looking at the mailboxes in ESM.
I looked at the event logs, and noticed that online defrags had
occured, which also froze the SBS server in the morining sometime.
Hmm - that isn't good....check for event log errors.
After five days of operation (after I noticed the problem), the
priv1.edb had grown to 45 gb!!!
I'm presuming you went through and enabled this in the registry, so you must
have known it could grow up to 75GB....and hence, it would have been a good
time to implement quotas. Perhaps you also need more disk space
I read a bit about offline defrag,
but when I tried it, it started to eat away at the 'C' drive available
space, and of all things, the 'D' drive (where the exchange data is)
kept shrinking in size, when I expected it to increase in available
size.
Do not use eseutil /d unless:
* You know what you're doing
* You can see whether it's even *worth* doing, by checking the online
defrag event log messages - 1221 will tell you how much free/whitespace is
available
* You have enough temp space free (110% size of the database) - if you
map a network drive for this, it will take a lot longer to run
* You have a good full online backup of the Exchange stores
I am fairly certain that my problems and answers will end with doing
an offline defrag of these data bases,
From what you've written, this sounds unlikely. Did you bring over a lot ofdata ...and *then* did users *delete* a lot of data? If not, there's not
enough whitespace for it to matter. And since Exchange reuses whitespace
quite happily, offline defrags are rarely necessary.
but it is the options
surrounding this defrag that I don't like, because I don't have enough
room on this server to run an offline defrag. I also tried 'copying'
the MDBDATA folder to another networked server (it had more available
hdd space), and I copied the eseutil.exe and its dll to this server,
but it would not run. I also started to use the /p switch with
eseutil, to rebuild the temp data base to a separate server and then
move it back, but I got nervouse when I was warned about loosing data.
I am currently building a replacement SBS server that has more hdd
space available, and am looking for some advice (UNLESS someone can
guide me to shrinking this data base without starting over with a new
server):
Seriously, pull back and don't do anything else yet. If online defrag isn't
running, you have a problem. Check your quota settings, and remember that
deleted item retention will also eat up space in the DBs.
1) What is the best (safest and easiest) to migrate the users Windows
and Exchange profiles over to the new server (FYI: the new server
will be identicle to the old server--same IP's, domain name, etc).
You're veering a bit off topic; these might be best posted as individual
questions.
By profiles, what do you mean? Roaming profiles?
If you have an entirely different AD domain, the SIDs are different - so it
doesn't matter what you see the name as - it's a different server, etc.
2) Can I simply copy the MDBDATA folder from the old server, and
paste it to the new one, and expect everything to work?
No...
3) Would http://server.connectcomputer work for me, considering they
will be migrating from a domain by the same name? This seems too
easy...
No - you'd have to disjoin the old domain first.
I hope I was able to describe my scenario clear enough, and would be
happy to elaborate.
Thanks all for any input you may have!
Gibs
Is this a test server?
.
- References:
- Prev by Date: Re: priv1.edb, Offline Defrag, and Low Hard Drive Space
- Next by Date: Re: WSS 3.0 question
- Previous by thread: Re: priv1.edb, Offline Defrag, and Low Hard Drive Space
- Next by thread: Using Dialig Rules when sending a fax by MS Server 2003
- Index(es):
Relevant Pages
|
