mckeough
asked on
Exchange Server 2000 Offline Defragmentation Batch File
Is it possible to let a batch file do an offline defragmentation of our server every Friday night? I need this script to re-mount the Exchange databases automatically if it is possible.
250 pts if anyone can explain why this can not be done OR 500 pts for anyone that can write the batch file for me.
If a batch file can do this you guys should know that when I defragment, I use the following command line:
E:\>eseutil /d "d:\exchsrvr\mdbdata\priv1
As you can see, I need to switch to the server's E drive, and copy the database to the G drive for defragmentation.
I appreciate the help!
250 pts if anyone can explain why this can not be done OR 500 pts for anyone that can write the batch file for me.
If a batch file can do this you guys should know that when I defragment, I use the following command line:
E:\>eseutil /d "d:\exchsrvr\mdbdata\priv1
As you can see, I need to switch to the server's E drive, and copy the database to the G drive for defragmentation.
I appreciate the help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can put general limits on most people and then special limits on certain individuals if you want.
Before doing an offline defrag, look for event id 1221 in the application log. The value listed in the description is the approx. amount of space you will reclaim.
Remember that Exchange will reuse this space before increasing the size of the database.
I may be blunt, but I am sure that they will sing a different tune when the databases reach 16 GB and there is no space that will be availiable to reclaim with an offline defrag, and the server is down for a couple of days.
I feel you pain. Email never seems to be important until the users don't have it.
Before doing an offline defrag, look for event id 1221 in the application log. The value listed in the description is the approx. amount of space you will reclaim.
Remember that Exchange will reuse this space before increasing the size of the database.
I may be blunt, but I am sure that they will sing a different tune when the databases reach 16 GB and there is no space that will be availiable to reclaim with an offline defrag, and the server is down for a couple of days.
I feel you pain. Email never seems to be important until the users don't have it.
MCKEOUGH -
What you can do after running a defrag (eseutiul) once is to put a few processes into place:
- Archiving old e-mail : At least ask the individuals with the LARGEST mailboxes to take everything older than 9mo. or 1yr. and archive it off to a .pst file. It is readily available to view on their local PC. Default name = archive.pst.
- Ask users not to keep large attachments in "Sent Items" and "Deleted Items". E-mail text itself takes up small space. It's the attachments that really eat free space. Nothing irked me more than users that would send 5-10mb attachments on a regular basis and keep them *forever* in "sent items".
What you can do after running a defrag (eseutiul) once is to put a few processes into place:
- Archiving old e-mail : At least ask the individuals with the LARGEST mailboxes to take everything older than 9mo. or 1yr. and archive it off to a .pst file. It is readily available to view on their local PC. Default name = archive.pst.
- Ask users not to keep large attachments in "Sent Items" and "Deleted Items". E-mail text itself takes up small space. It's the attachments that really eat free space. Nothing irked me more than users that would send 5-10mb attachments on a regular basis and keep them *forever* in "sent items".
Going on ZabagaR's notes...
One great thing is Zantaz EAS. A few of my co-workers really like it. It takes those 5-10MB attachments and, if they are the same, creates a single instance store of sorts. Yes, it is quite a bit extra and requires extra hardware...which may not be in your bag for now.
Bob
One great thing is Zantaz EAS. A few of my co-workers really like it. It takes those 5-10MB attachments and, if they are the same, creates a single instance store of sorts. Yes, it is quite a bit extra and requires extra hardware...which may not be in your bag for now.
Bob
ASKER
OK. Thanks for the comments guys. I'll be taking this information to a meeting later today, and convince them that this is not the best idea. This will put a fair amount of pressure back on them to actually implement a solution.
ASKER
Anyway, I'll just tell them that this is not an acceptable solution. If, er, I mean when we get to our 16 gig limit again, I'll just have to take the server offline the night before it would go down.
If anyone has any other comments, feel free to post them. I'll wrap this post up either later today or tomorrow.