Archive for October 24th, 2010


Since I now have a server with 2 drives instead of 1, it makes sense to move my Exchange data stores over to the new drive, getting them off my O/S drive and taking advantage of the extra spindles and free space. NOTE: I’m doing this with Exchange 2003, so if you have a different version, it may not be suitable, so check first.

It is actually a pretty easy task, with the Exchange System Manager (ESM) doing all the hard work for you.

I’ll be moving the transaction logs, mailbox store and the Public folders.

To do this, start off by firing up the ESM and locating the storage group. Mine was called ‘First Storage Group’, which is the default, but yours may be called something else.

In ESM, right click on ‘First Storage Group’ and select ‘Properties’. There will be a tab labelled ‘General’. Click the ‘Browse’ button, and select the new location. In my case, I had pre-created all the folders I needed under a folder in the root of my new D: drive, so I pointed it to D:\Exchange\Logs. I also pointed the system path here in the same manner so it would use this directory for temporary Ecxhange files.

Click ‘Apply’ and Exchange will make the necessary changes, and that’s the transaction logs moved.

Next, right click on the ‘Mailbox Store’, and select properties. Once the dialog has opened, select the ‘Database’ tab. In the same manner as for the transaction logs, use the ‘Browse’ button to point to the folder where you want the database to be relocated to. You can move just the Exchange database if you want, or move the Exchange Streaming database too. I did both, and pointed at the folders I’d created before starting on my D: drive.

When you hit ‘Apply’, you will (Unless you’ve already dismounted the data store) receive a warning that the datastore will be dismounted. Anybody using Exchange will be disconnected at this point, so be sure to do this when it’s not going to disturb a lot of people.

Click ‘Yes’ to continue, and Exchange will move your data store to it’s new home. Once complete, you’ll need to go in to ESM and remount the store.

Do the same for Public folders if you wish, the procedure is identical, and again the store will need to be remounted afterwards.

Once completed, ensure your new folders have the following permissions to ensure everything works correctly:

Administrators: Full Control Authenticated Users: Read and Execute, List Folder Contents, Read Creator Owner: None Server Operators: Modify, Read and Execute, List Folder Contents, Read, Write System: Full Control.

Although I chose not to delete the old MDBdata directory, you can do so, but you will need to do some registry editing. I recommend this article: Moving Exchange Data Store to a new disk as it has some useful links to aid in troubleshooting this kind of operation.

So, Exchange is now all moved to my D: drive, and so far so good. If I hit any errors, I’ll post here.

Now my Windows installation has been moved to its new hardware home, in order to improve perfomance, I decided to do the following:

1. Move my Exchange information stores to the new second drive.

2. Move my MSSQL databases to the new second drive.

3. Move my MySQL databases to the new second drive.

4. Move my IIS6 website content to the new second drive.

This should improve overall performance since these items will no longer reside on the same drive as the O/S, and more spindles means better read/write performance.

Since each one of these tasks is not that difficult, I thought I’d share with the world! So keep an eye open, they are coming soon.