A database (either blank, or a copy of a production database) is added to the Storage Group copy by seeding. SnapManager performs database seeding in an LCR copy during a SnapManager migration operation, if a Storage Group is configured for LCR, and if a replica database is not seeded.
The added database becomes the baseline database for the copy. In Exchange Server 2007, after an LCR replica is enabled on the Storage Group, the LCR replica is automatically seeded.
When seeding is complete, the copy is given a status of good health. To reduce the I/O burden on the active Storage Group volumes, seed the database during an off-peak time. The existing database needs to be deleted before the seeding process.
SnapManager uses the Exchange cmdlet Update-StorageGroupCopy to seed the LCR replica. The Update-StorageGroupCopy cmdlet initiates or re-synchronizes the copying for a specified Exchange Server 2007 LCR.