Well if you don't have enough free space to temporarily hold the defragged .edb, then you have a problem.
How close is the space on c:? I assume since you mentioned C:, that is where your PRIV and PUB databases reside. If you can free up more space on c:, so there's as much free space as your PRIV database is in size, that's safest. If it's close, well presumably the defragged database will be smaller, and may still make it.
Let's put the capacity problem aside for a moment, the process is:
Go into Exchange System Manager, dig down to Administrative Groups / First Administrative Group / Servers / / First Storage Group / Mailbox Store, and stop the Mailbox Store. NOTE: this WILL kill anyone's live Outlook session or OWA for the duration of the DEFRAG.
Open a CMD prompt and CD to the location of the stores, which in your case is probably c:\program files\exchsrvr\mdbdata.
Since the path to ESEUTIL is not typically in your path, run the command
PATH=%PATH%;c:\program files\exchsrvr\bin so you can find ESEUTIL.
Next, the defrag:
ESEUTIL /D priv1.edb
This will essentially start copying the database into a new database, thereby defragging it. So during the defrag, another copy of the database is created, that's why the space need. This copy may take a few hours depending on the size of the database, so clearly something you want to do outside of normal Production hours.
During the defrag, the original database files (the .edb and .stm) are READ and copied to a TEMP database; Once the copy is completed successfully, the original database is renamed, the temp database is renamed to the production database, and finally the original (renamed) database is deleted. If the drive runs out of capacity during the defrag, the job will fail, but the original database is left intact.
If you can't get enough capactity on C:, then you need to somehow get that capacity, even temporarily. In extreme cases, I have moved the databases to another computer that had enough capacity, and run the defrag either across the network or locally on the other machine. I don't recommend running the defrag over a network share, again I said this was an extreme case.
Also let's not forget ...Backup backup backup. Make sure you make a good backup before you start, in fact, this may help your capacity problem as a good backup will flush logfiles that may be holding the capacity that you need. When the defrag is complete, do another backup.
That's enough for now. If you have any other specific questions, post back.
--C