Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2006-12-21

This topic explains how to seed a local continuous replication (LCR) copy. Seeding is the process in which a database, either a blank database or a copy of the production database, is added to the storage group copy. This becomes the baseline database for the copy. Depending on the situation, seeding can be an automatic process or a manual process that you initiate. You can use the procedure in situations where you determine that seeding is required. Seeding is required under the following conditions:

When the system has detected a corrupted log file that cannot be replayed into the database copy.
After an offline defragmentation of the production database occurs.
After a page scrubbing of a database on the active node occurs, and you want to propagate the changes to the passive node.

The size of the database that is being copied directly correlates to the amount of time it takes for the seeding task to complete. Seeding in Microsoft Exchange Server 2007 can be performed by any of the following methods:

Using Update-StorageGroupCopy The Update-StorageGroupCopy cmdlet uses the Extensible Storage Engine (ESE) streaming backup functionality to make a copy backup of the storage group. When the copy backup is complete, the passive copy is moved to the LCR database folder.
Using Enable-StorageGroupCopy When the Enable-StorageGroupCopy cmdlet is run on a Mailbox server, it seeds the database by default, unless the -SeedingPostponed option is used. The Enable-StorageGroupCopy cmdlet uses the Update-StorageGroupCopy cmdlet internally as part of the enable process.
Manually copying offline database This method involves dismounting a database and copying the database file to the LCR database folder. If you use this procedure to seed the LCR database folder, there will be an interruption in service because the procedure requires that you dismount the database, which temporarily makes it inaccessible to users.

This topic contains two procedures: One procedure that explains how to use the Update-StorageGroupCopy cmdlet to seed the LCR database folder, and another procedure that explains how to use the Exchange Management Console to dismount the databases for offline copying to the LCR database folder.

Before You Begin

Before you perform the following procedures, the account you use must be delegated the following:

Exchange Organization Administrator role

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

In addition, note that the Update-StorageGroupCopy cmdlet always copies the data to a locally available location. We recommend that you perform these procedures on the server containing the storage group copy that is being seeded.

Procedure

To seed an LCR database using the Exchange Management Shell

Open the Exchange Management Shell.

Suspend replication and replay activity using the following command:

	Copy Code
Suspend-StorageGroupCopy -Identity:<Server>\<StorageGroupName> -SuspendComment:"Seeding"

Remove database files, all log files, and checkpoint files from the passive node. Remove *.log, *.jrs, *.chk, and the .edb file from the LCR database folder. If you are confident that storage configuration is correct, this step can be accomplished by using the –DeleteExistingFiles option of the Update-StorageGroupCopy cmdlet.

Seed the passive copy of the database using the following command:

	Copy Code
Update-StorageGroupCopy -Identity:<Server>\<StorageGroupName>

Note:
The Update-StorageGroupCopy cmdlet automatically resumes replication to the storage group copy. If you do not want this behavior, run the cmdlet with the ManualResume parameter. For more information, see Update-StorageGroupCopy. To resume replication manually after running the Update-StorageGroupCopy cmdlet, run the following command:

	Copy Code
Resume-StorageGroupCopy -Identity:<Server>\<StorageGroupName>

Note:
If you receive errors when you run the Update-StorageGroupCopy task, for more information see the errors table in this topic Update-StorageGroupCopy.

After the Update-StorageGroupCopy command is complete and the storage group copy is resumed, verify that replication is working correctly by using the Get-StorageGroupCopyStatus cmdlet. For more information, see Get-StorageGroupCopyStatus.

Important:

It is critical that you make sure that log files are actually replicating and being replayed into the passive copy of the database.

Important:
It is critical that you make sure that log files are actually replicating and being replayed into the passive copy of the database.

To seed the database folder by dismounting the database and copying the database file using the Exchange Management Console

Start the Exchange Management Console.
Expand Microsoft Exchange, expand Server Configuration, and then select Mailbox.
In the result pane, select the mailbox server that contains the database that you want to dismount.
In the work pane, right-click the database that you want to dismount and select Dismount Database.
Suspend replication on the dismounted database. Follow the steps for suspending replication that are shown in How to Halt Replication for a Storage Group Enabled for Local Continuous Replication.
Remove database files, all log files, and checkpoint files from the passive node (LCR copy). Remove *.log, *.jrs, *.chk, and the .edb file from the LCR database folder.
After dismounting the database and deleting existing files in the LCR database folder, copy the database file from the production database folder to the LCR database folder.
After the database file has been copied from the production database folder to the LCR database folder, right-click the database and select Mount Database.

Note:

Seeding is complete when the file is copied. Client access is restored after the production database has been mounted.
Resume replication for the dismounted LCR database. Follow the steps for resuming replication in this topic, How to Restart Replication for a Storage Group That is Enabled for LCR.

Note:

Seeding is now complete, and transaction log replication and replay will now occur automatically.

Note:
Seeding is complete when the file is copied. Client access is restored after the production database has been mounted.

Note:
Seeding is now complete, and transaction log replication and replay will now occur automatically.

For More Information

For more information about managing your LCR environment, see Managing Local Continuous Replication.