Exchange database reaches 16Gb

[Calb]

I've ran the defrag tools for the exchange database, this shrunk the tempory database down to 13Gb, only problem is it deleted the original and wont let us move, copy, rename the tempory database so exchange will start back up.

Any Ideas?

 

[rdroske]

What command and switches did you use? A normal defrag should not have deleted the origional.

 

[Qphan]

Action Plan for hard repairing on Databases :

1) Shut down all the Exchange server services from the source server.

2) Copy the following files onto other server
a) original priv.edb and pub.edb
b) c:\winnt\system32\eseutil.exe
c) c:\winnt\system32\ese.dll
d) c:\winnt\system32\exchmem.dll

2) To perform a hard recovery, follow these steps:
To return Priv.edb to a consistent state, type the following command at the
command prompt(after going to the directory) (The speed for the command is
4-5hrs\gig) , and then press ENTER:
a)eseutil /p priv.edb
b)eseutil /p pub.edb

3) Check the consistency of the databases after running the eseutil /p on
the database(State : Consistent), type the following command at the command
prompt, and then press ENTER after each line:
a)eseutil /mh priv.edb |more
b)eseutil /mh pub.edb |more

4) On the Command prompt, run the following command [run this command till
you get zero errors & zero fixes]. (The speed for the command is 5mins\gig),
and then press ENTER after each line:
a)Isinteg -fix -pri -test alltests
b)Isinteg -fix -pub -test alltests

5) To defrag the database, type the following command at the command
prompt(after going to the directory) (The speed for the command is
4-5hrs\gig) , and then press ENTER:
a)eseutil /d priv.edb
b)eseutil /d pub.edb

6) In the production system rename exchsrvr\mdbdata to mdbdata.new.(Or move
mdbdata.new to some other location). Create a blank exchsrvr\mdbdata

7) Move the repaired databases to production (original) server's
exchsrvr\mdbdata

8)Recheck the consistency of PRIV.edb database by running command (State :
Consistent).
a)eseutil /mh priv.edb |more
b)eseutil /mh pub.edb |more

9) Now try starting the Exchange services as normal, Incase you get error
1011 while starting the services, then you will require to run Isinteg
-patch command from exchsrvr\bin directory to get the services up and
working.

That's it every thing should be working now, except loss of few
mails/attachments due to execution of eseutil/p

 

[BlueManOp]

You can set your deleted items retention time on your private information store to zero days. This will flush out everyone’s deleted/deleted items from the server side. This will not empty their trash bin from within Outlook but only kill off any recovery if they need any files recovered from an empty trash folder.

Open Exchange 5.5 admin, expand your site and find the mail server that is at its 16gb limit. Expand the server so the "Private Information Store" is listed and choose "File" and "Properties" from the top menu. This will now show you the Private Information Store "General" tab.

The first option there is the "Item Recovery" section. Set the "Deleted item retention time (days):" to 0 and uncheck the "Don't permanently delete items until the store has been backed up" option. I believe the factory setting is 35 days. Doing this will force exchange to purge the space immediately. This may give you the extra breathing space you need.

Also you can also upgrade to Exchange 5.5 Enterprise which has no 16gb limit.

 

[spuddym]

Just get the old file from the backup you must have before you started. Restore it and try again.