Ok, since my work on integrating KVS (or Enterprise Vault) into my interop environment is almost at an end – I resumed the configuration of my first (and primary CCR database cluster).

My primary task today was to create and define the Disks that would house the Database files which are located on a pair of SANS (in separate Data centre’s) – however with these drives finally in place I needed to move the existing (created by default “Mailbox Database.edb” file from the DAS Log Drives to my new spanky RAID 10 SAN based storage.

I have supplied the following diagram to give you an overview of the scenario that I was facing:

Essentially as I had installed CCR clustering on both my nodes PRIOR to finalising the disk configuration, Exchange setup had placed the default “Mailbox Database” on one of the locally attached drives of my Nodes (actually it had placed the drives where I told it to during setup). However, these local drives are configured as x 3 RAID 1 pairs (with the view they will hold the transaction logs) so now I had my Database LUNS I needed to move the default database.

Now, some of you may have found that moving CCR databases from their existing locations to new locations is not that straight forward.

In fact there is no provision within the Exchange Management Console (unlike Exchange 2003) for moving CCR database between locations (there is for other server types) – if you wish to move a CCR Exchange database you have to use the Exchange Management Shell and a little manual intervention.

Moving the Database:

Open an Exchange Management Console [ START -> Programs -> Microsoft Exchange Server 2007 -> Exchange Management Shell ] and then type the following command line:

suspend-StorageGroupCopy -identity “First Storage Group” -confirm:$false

dismount-Database -identity “First Storage Group\Mailbox Database” confirm:$false

NOTE: BEFORE YOU BEGIN THE NEXT STAGE ENSURE THAT YOU HAVE A FULL BACKUP OF YOUR DATABASES AND CCR CONFIGURATION

At this stage you need to locate your “Mailbox Database” (the actual edb file) within the file system and then physically MOVE the database to it new location – so for example if your database is located in “C:\Program Files\Microsoft\ExchageSrvr\MDBDATA\Mailbox Database.edb” you will need to physically move this file to its new location (actually I would copy it to be on the safe side).

When you have copied (or moved) the database you will need to return to the Exchange Management Shell and then type in the following command:

Move-DatabasePath -Identity “First Storage Group\Mailbox Database” -EdbFilePath:”<new file system path\mailbox database.edb” -configurationOnly:$true

You will then be prompted twice for confirmation – enter A (for all) in both instances – see below:

You should at this point allow for Domain Controller replication (about 15 minutes) – then within the Exchange Management Shell type in the following commands:

Mount-Database -Identity “First Storage Group\Mailbox Database”

Update-StorageGroupCopy -Identity “First Storage Group” -deleteExistingFiles

You might receive a message about obsolete checkpoint file – at this stage enter in “A” for all to proceed – see below:

When done type in the following command line in to the Exchange Management Shell:

resume-StorageGroupCopy -Identity “First Storage Group” -confirm:$false

You should at this stage have a fully functioning (and correctly moved) database in a new location.