Re: Exchange 5.5 maintenance

Tech-Archive recommends: Fix windows errors by optimizing your registry

Actually, Scott...no...do you have plans to get all your users off this
server soon? You might still want to check for how much whitespace you
have, just so you know how much "breathing room" you've got...online
maintenance is typically run on a schedule that's set on the Information
Store...I don't blame you, and you are probably right not to bother with the
defrag, in your circumstance...

--
Susan Conkey [MVP]



"Scott McBride" <ScottMcBride@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C202CD6-3608-43F0-BD48-82079EE52305@xxxxxxxxxxxxxxxx
Susan,

Thanks for the answer. Again...sorry for my ignorance, but another
question
in this thread:

If I'm correct, the online maintenance will happen automatically (correct
me
if I am wrong there and forgive me if I am mistaken). However...is there
a
necessity or any benefit in reducing the physical size of the priv.edb
file
if hard drive storage space isn't an issue and the IS is running okay?
I'd
rather not mess with it if I don't have to. It's been twitchy enough
lately
without me giving it any excuses to go completely bottom up.

A musically inclined friend of mine once gave me a piece of wisdom that I
try to live by: "If it ain't baroque...don't fix it".

Thanks a bunch.

Scott McBride

"Susan" wrote:

running eseutil /d will shrink the size of the file, if all your online
maintenance has completed...look for event 1221 in your event log to
find
how much whitespace is in the database - that's how much you can expect
eseutil to shrink the file size...do a full online backup before and
immediately after running the defrag...

--
Susan Conkey [MVP]



"Scott McBride" <ScottMcBride@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:140FA2B4-260A-498F-AFDB-1BD3D1751C53@xxxxxxxxxxxxxxxx
Good day.

I am running Exchange 5.5. Standard in an NT 4.0 environment. I have
a
couple of 2000 and 2003 servers, but they are member servers, not DCs.

Yesterday, our priv.edb smacked the 16 GB limit hard. I got it all
working
again by running the eseutil to do an offline defrag. After about 4.5
hours
I was able to get all the services running again. The physical size
of
the
priv.edb went from about 17.5 GB down to about 16.8 GB, but I was
still
able
to get it running.

I performed a full online brick level backup last night, which was
fully
successful.

Today, I am having users delete/archive a lot of their old files.
When I
checked the mailbox resources, useage is now down to about 12.5 GB and
dropping as more stuff is deleted/archived. However, the physical
size of
the priv.edb file is still holding at 16.8 GB.

I am new to the eseutil program in Exchange 5.5. Is there another
step I
need to take to clean out the "white space" from the file? Do I even
need
to? Hard drive storage is not really an issue in this case.

Will re-running the eseutil to do another defrag lower the physical
size
of
the priv.edb file after everything's been deleted, or is that
something
that
Exchange will do itself over a few days?

Just an aside note...I am really pushing now for a new Exch 2003
server
(hardware and software). Our existing server is quite old and I fear
that
next time I may not be alble to recover so easily.

I apologize for my rookie questions. I've had training and experience
in
Exg 2000/2003, but everything I've learned about 5.5 has been from the
"School of Hard Knocks". The versions of Exg are a little similar,
but I
prefer 2000/2003 myself.

Regards,
Scott McBride
IT Specialist
ABCO Automation, Inc.





.

Relevant Pages