Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IS Maintenance Problem

Status
Not open for further replies.

cmiddl1

IS-IT--Management
Oct 16, 2003
20
US
Hi,

I have a problem, my priv.edb file is way too big, even after deleting/moving a lot of email from the server. IS maintenance has been setup, but I don't see the event log, does anyone know that ID number?? Is it 1221??

Also, I need to run the eseutil, but don't have emough space on the current drive to do this. I have added another 2 drives, and think that I know what parameters to set, but any help would be appreciated. Once I run this defrag, what becomes of the old and new priv.edb files, and I think that I can set it to replace the old, fat db with the compacted one in it's original location, correct??

Appreciate the assist!!!!
 
Yep, I just ran an offline defrag in the same situation you're in.

MS article Q244525 tells you exactly how to run Eseutil on a completely different server. I copied my 33 GB priv.edb over to the other server with a few other files the article mentioned (eseutil.exe, etc). Ran it from there, deleted the original, copied the new smaller DB back to the original's location and I was back in busines!!!

Here's the link to the article:


Hope this helps!

There are 10 types of people in the world,
those who know binary, and those who don't!


Vos [peace]
 
Thanks Vos, I will let you know how it goes. One last thing, the article says that I would need to delete the log files after the defrag, is there anyway that I could avoid this?? Isn't there switches when running the eseutil that would put the new, defraged DB in place of the original bloated one??
 
cmiddl1, you don't need to delete the log files after the defrag. The steps in the article are:

1 - Create a scratch folder on the computer that does not have Exchange Server installed on that particular computer.
2 - Copy the Eseutil.exe utility, Ese.dll file and Exchmem.dll files from the Exchange Server computers drive:\Winnt\System32 folder (where drive is the drive that houses Microsoft Windows NT server files) to the scratch folder.
3 - Open a command prompt and change directory to the scratch folder that contains the copied files
4 - Run eseutil from this folder against any databases copied over from the Exchange Server computer.

Then once you've got the compacted DB on the other computer, delete the original, and copy the defragged DB in it's place. Make sure you name the defragged DB priv.edb to match the original. Startup your services and you're off to the races!


There are 10 types of people in the world,
those who know binary, and those who don't!


Vos [peace]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top