Migration of LCR-enabled databases

You can move the databases, transaction logs, and system files with Local Continuous Replication (LCR) replicas to LUNs. You can follow the same procedure as you use for the production Storage Group for migrating the databases, transaction logs, and system files.

• Prerequisites for configuring an LCR-enabled Exchange server
  Before you use SnapManager to enable Local Continuous Replication (LCR) on Exchange, ensure that the Exchange server is LCR-enabled, the databases in the Storage Group are seeded, and that you put the database, transaction logs and replica database on a different volume from the LCR environment.
• Comparison of moving production and LCR replica storage groups
  The main difference between the production Storage Group and an Local Continuous Replication (LCR) replica Storage Group is the way that it is represented on the SnapManager user interface. A Storage Group with an LCR replica appears as "Storage Group (LCR)."
• Database seeding in an LCR
  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.