General discussion

Locked

Exchange 5.5 eating up c: drive

By gsolu ·
I am running an Exchange 5.5 server on NT 4.0 sp6a. It works really well. I have about 50 user mailboxes. The private information store is app. 3.3 Gb.

The problem is the information store is on c: and d:. I inherited this system. It has been running for about 2 years and now we are using a lot more email, some with large attachments.

I tried to move the files to the d: drive but the Exchange Optimizer says the files already exist on the d: drive (they do, there is an almost equal amount on both drives). I am stuck. I only have about 795 Mb of available hard disk space left on the c: drive (less every day). I even compressed the c: drive because I had gottne down to about 150 Mb of free space. I cannot run the eseutil without having at least free disk space equal to the size of the information store.

What's a guy to do?

Help

Thanks,

Grahamz

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Exchange 5.5 eating up c: drive

by rlevesque In reply to Exchange 5.5 eating up c: ...

Grahamz,

I can suggest a couple of things.

1) Log files. If you keep them or use tracking, move them or delete the older ones of you can

2) If your D drive has lots more room, then run the Optimize, and regardless of what it suggests, you can force it to move all the data files to your D drive

3) The best suggestion, would be to add another good size drive, and then optimize and place your information stores on the D and new "E" drive.

I've done #2 before and it will work. But ultimately, I needed to add an extra drive a few months later anyways so I ended up doing #3 anyways.

Good luck,

Richard

Collapse -

Exchange 5.5 eating up c: drive

by gsolu In reply to Exchange 5.5 eating up c: ...

You cannot force the drive the files are located on if the files already exist. The database is on both drives. Mebudman@home.com had the best answer.
Thanks for responding

Collapse -

Exchange 5.5 eating up c: drive

by dcAdmin In reply to Exchange 5.5 eating up c: ...

Try and see if there is a postmaster account that has a mailbox (it may be hidden). Attach to that mailbox and clean it out. It keeps a copy of every e-mail sent and can grow very large quickly(especially if there are large attachments).

Good Luck!

Collapse -

Exchange 5.5 eating up c: drive

by dcAdmin In reply to Exchange 5.5 eating up c: ...

Also if there is an account with tons of mail, it will eat up the processor when deleting a lot of mail, so do delete messages when it is not busy as it can slow down mail delivery.

Collapse -

Exchange 5.5 eating up c: drive

by gsolu In reply to Exchange 5.5 eating up c: ...

Thanks for your ideas. It was not the problem.

Collapse -

Exchange 5.5 eating up c: drive

by mebudman In reply to Exchange 5.5 eating up c: ...

The active information store is on C: correct?

Here is how you move it to d: with out running the optimizer.
Ensure you have a good backup before doing this.
1. Shutdown the Information store service.
2. Delete the files from \exchsrvr\mdbdata
3. Copy the files for c:\exchsrvr\mdbdata to d:\exchsrvr\mdbdata
4. Here is the infamous registry part.
start regedt32
5. Goto HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\Services\MicrosoftIS\ParametersPrivate
change DB Path from c:\exchsrvr\mdbdata\priv.edb to d:\exchsrvr\mdbdata\priv.edb

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\Services\MicrosoftIS\ParametersPublic
change DB Path from
c:\exchsrvr\mdbdata\pub.edb to d:\exchsrvr\mdbdata\pub.edb

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\Services\MicrosoftIS\ParametersSystem
change DB Log Path from
c:\exchsrvr\mdbdata to d:\exchsrvr\mdbdata

change pop3 log path, imap4 log path and the nntp log path to this value also, also found under ParametersSystems.
Closeout of registry.

6. Restart the information store.

You have now moved Information store from c: to

Hope this helps.

Collapse -

Exchange 5.5 eating up c: drive

by gsolu In reply to Exchange 5.5 eating up c: ...

This was the answer I needed. I was going crazy. The only problem with the answer is the regedt32 key is HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\Services\ExchangeIS\ParametersPrivate. Good call though got me where I needed to be.

Thanks,
grahamz

Collapse -

Exchange 5.5 eating up c: drive

by gsolu In reply to Exchange 5.5 eating up c: ...

This question was closed by the author

Back to Software Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums