I have a new server that I just installed and deployed Exchange 2010. The only thing on the server is Windows 2k8 R2, the required Roles to install exchange, Exchange 2010 SP1 Standard with all Roles but edge installed. If I recall, the space required by exchange was 4gigs tops. I have a 140GB Windows System partition installed. THe install of Server 2k8 and Exchange took about 90Gigs. The mailbox database is on a seperate partition so that can't be it. Does it seem normal for an install to be 90gigs? I feel like something isn't right.

When you first install Exchange, it creates a mailbox database and maybe a public folder database in the partition where Exchange is installed unless you directed othewise, but it's nowhere near 90 GB. The installed size is like 4 MB. You are welcome to walk thorugh the C:\Program Files\Microsoft\Exchange Server\V14 tree and see if you can find where the huge amount of space is being consumed. I've never seen an Exchange Server installation take more than a couple of gigabytes if that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

That's what I figured. The intial database was installed on the C drive. After I migrated form exchange 2003, I moved the mailbox store to it's own partition. There's a folder under v14\mailbox that has the default name of the Mailbox Database that exchange assigned. That's taking up 47GB. I've since renamed and moved the database. It looks like all log files and such. I don't see an edb file. WIll those log files flush once a backup has been made?

If you used the cmdlet to move the database, then it should have moved both the database and the transaction logs if you told it to. That's the best way to do it. Perhaps you moved the database file but forgot to move the logs?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yeah, I used the cmdlet to move the db. But I only specified the edb file. move-databasepath -identity "my db" -edbfilepath "New path" Is there a seperate cmdlet for logs?

Yes you will have to move the log file for the storage group assocated with that DB. Note all DB's assocated with that storage group will be dismounted. Move-StorageGroupPath -Identity "MyStorageGroup" -LogFolderPath "D:\MyNewLogFolder" How to Set or Change the Location of Storage Group Log Files http://technet.microsoft.com/en-us/library/bb201703(EXCHG.80).aspxJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Alright, if I try through EMC or cmdlets I get errors. If i try to move the logs or the mailbox store individually or both at the same time. I get a call cancelled error. The FQErrorID is 7025d023. What gives? Is there certain permissions that need to be set? I did dismount the store first... Could I create a second store, putting the paths where I want and move all the mailboxes there?

When referring to error messages, always post the complete error message along with an explanation of exactly what you did.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yes you can create a new storage group and point the logs to the desired location during the creation of the storage group; create the database and move mailboxes to this new database. Post the error in full, the eventviewer also might yield additional info as to why its failing.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi PHE Admin, Any updates? If you are using Exchange 2010, please see: Move the Database Path http://technet.microsoft.com/en-us/library/dd351168.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I honestly have no idea what it was but I have a feeling it was the size of my log files. I waited until early this morning after the backups were done and everything went smoothly. Thanks for the help and I apologize for not posting error codes in the first place.