I lost track of how much space was left on my Exchange 2003 box. Priv.edb is 85 GB and Priv1.stm is 40 GB, and I have 2 GB left on the drive they both reside on. It won't last me through another day. Yes, I screwed up. I'm currently moving the priv1.edb to an external drive (USB 1.0, it's taking hours and I realize it won't be fast enough for my 100 users so it's not a viable solution even a temporary one). It's also not large enough to give me the 110% space I need to defrag the database. I'm open to solutions. I don't have another server with more space, they're all the same drive capacity. I can't move one of the large files to another server because it appears it has to be local to the email server (tried that, had planned on that working, it didn't). I don't have room in the server (Dell 2650) to throw in another drive, no bays left.

Hi,Ooh! I'd hate to be in your shoes... sounds like a tough bind to be in!How aboutdrop in a SCSI card into the 2650 (if you have an expansion slot open) and an external SCSI hard drive. It would be local, external and fast. You'll need a SCSI card, an External SCSI drive a cable and a terminator.Miguel Miguel Fra / Falcon ITSComputer and Network Service and Support, Miami, Fl

Hi,I think it's the time to set limitation on users' mailbox capacity,and let your users tomove mails to .PST file. Thus it can increase the white space of the database.After finishing these, you can follow this KB to defrag your database.How to run Eseutil on a computer without Exchange Serverhttp://support.microsoft.com/kb/244525/EN-US/Frank Wang

I agree with Frank. you need to implement Mailbox Quota or create PST's and then opt for defrag. see below articles Create PST Files Using Outlook 2003 or Outlook 2007 http://www.groovypost.com/howto/microsoft/outlook/create-pst-files-using-outlook-2003-or-outlook-2007/ HOW TO: Use System Policies to Configure Mailbox Storage Limits in Exchange Server 2003 http://support.microsoft.com/kb/822938 Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

I lost track of how much space was left on my Exchange 2003 box. Priv.edb is 85 GB and Priv1.stm is 40 GB, and I have 2 GB left on the drive they both reside on. It won't last me through another day. Yes, I screwed up. I'm currently moving the priv1.edb to an external drive (USB 1.0, it's taking hours and I realize it won't be fast enough for my 100 users so it's not a viable solution even a temporary one). It's also not large enough to give me the 110% space I need to defrag the database. I'm open to solutions. I don't have another server with more space, they're all the same drive capacity. I can't move one of the large files to another server because it appears it has to be local to the email server (tried that, had planned on that working, it didn't). I don't have room in the server (Dell 2650) to throw in another drive, no bays left. Hi there,On top of what everyone is saying, I'd step back and look at your situation.You have an 85GB EDB and a 40GB STM, but you do not say if you have Exchange 2003 Standard or Enterprise.If Exchange Standardyou should:1. Have PLENTY of whitespace, you can see how much whitespace you have in the EDB only by looking for Event ID 1221 in your Application Log, and you will be likely close or surely really near the 75GB logical limit (if you have SP2 and applied the reg fix)as you cannot have a 125GB combined EDB and STM without massive whitespace.2. So seeing you must have whitespace - this doesn't explain your 2GB size increase you expect within a 24 hour period - check your are backing up your database, as Transaction Logs files will not purge until you do so. People always seem to get caught on space and then realise they have to back up their databases to clear Tran Logs.3. If you have a large proportion of whitespace, as others have said, schedule an outage window and perform an offline defrag to reclaim it. There is no point moving the database now tothe external drive as you already note that the 2GB will last you the day - so youshould be planning for your scheduled outage during offpeak hours tonight. You can still use thatexternal drivewhen performing the offline defrag by using the /T switch to point the temp edb at it. and just to say, although I expect you don't have any other Exchange Servers, if you have other Exchange 2003 Servers available consider moving mailboxes instead.If you have Exchange Enterprise:1. Still check your whitespace, and if you do not see Event ID 1221 then ensure online maintenance is running succesfully.2. Rather than moving the entire database to that external disk, create a new database and move selected users to it, instantly giving whitespace if you immediately engage database maintenance and making any outage to your users a far far smaller window.3. Still check your backups to ensuring Transaction Logs are purging.Hope that gives you a clearer picture, and should help give you a smaller outage window to remedy.If you need anymore information, let us know.Oliver Oliver Moazzezi | Exchange MVP, MCSA:M, MCTS:Exchange 2010, BA (Hons) Anim | http://www.exchange2007.com | http://www.exchange2010.com | http://www.cobweb.com |

And to add,If you haven't already:1. Set mailbox limits so you can manage your Exchange resources better. Remember different people can have differrent sizes. Set one policy for the store, then any individuals that need more set specifically on the user in ADUC.2. You can age items in users mailboxes by creating Mailbox Manager policies in ESM.Good luck,OliverOliver Moazzezi | Exchange MVP, MCSA:M, MCTS:Exchange 2010, BA (Hons) Anim | http://www.exchange2007.com | http://www.exchange2010.com | http://www.cobweb.com |

I created another Exchange server and moved mailboxes to it, but it didn't create any more space on the originating drive.