How to Move a Database in a CCR Environment
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2007-09-12
This topic describes how to use the Exchange Management Shell to reconfigure a database's file location. In a cluster continuous replication (CCR) environment, there is only a single set of database configuration information that applies to both copies. This creates the additional complexity of needing to relocate both copies. Under some circumstances, one copy may not be available at the time the other copy must be moved.
You can use the procedure in this topic to change the location of a mailbox or public folder database.
To perform this procedure, the account you use must be delegated the Exchange Server Administrator role and local Administrators group for the target server. For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
Although we recommend that you perform this procedure when both active and passive nodes are available, it is not required.
This procedure performs the following actions:
Changes the configuration
Moves the copy on the active server
Moves the copy on the passive server
Open the Exchange Management Shell, and then halt replay and log replication for the storage group by using the Suspend-StorageGroupCopy cmdlet. To halt replication activities for the storage group, run the following command:
Suspend-StorageGroupCopy -Identity <Server\StorageGroupName>
Dismount the database by using the Dismount-Database cmdlet:
Dismount-Database -Identity <Server\StorageGroupName\DatabaseName>
Use the Move-DatabasePath cmdlet to change the configuration in the Active Directory directory service. Make sure the database is dismounted prior to performing the move operation. Run the cmdlet as follows:
Move-DatabasePath -Identity <Server\StorageGroupName\DatabaseName> -EdbFilePath <NewPath> -ConfigurationOnly
Note: In a CCR environment, you must use the -ConfigurationOnly parameter. The new location must not be the root directory of a volume.
Move the files to their new locations on both the active node and the passive node.
Mount the database in the storage group by using the Mount-Database cmdlet.
Restart replication using the Resume-StorageGroupCopy cmdlet. To restart replication activities for the storage group, run the following command:
Resume-StorageGroupCopy -Identity <Server\StorageGroupName>
Verify that replication for the storage group is proceeding normally by following the procedures detailed in How to View the Status of a Clustered Mailbox Server.
For more information about managing your CCR environment, see Managing Cluster Continuous Replication. For more information about viewing the status of a passive copy, see How to View the Status of a Storage Group in a CCR Environment.
For more information about the Dismount-Database cmdlet, see Dismount-Database.
For more information about the Move-DatabasePath cmdlet, see Move-DatabasePath.
For more information about the Mount-Database cmdlet, see Mount-Database.
For more information about the Suspend-StorageGroupCopy cmdlet, see Suspend-StorageGroupCopy.
For more information about the Resume-StorageGroupCopy cmdlet, see Resume-StorageGroupCopy.