Migration of CCR-enabled databases

You can migrate Cluster Continuous Replication (CCR) databases and transaction logs to a specified location to enable SnapManager to manage it. The configuration is similar to that of the production Storage Group; SnapManager internally migrates databases to the specified location on both the nodes.

CCR uses three computers or nodes combined in a single cluster. Two nodes host a clustered mailbox server. CCR uses the third node, referred as "voter," to avoid an occurrence of network partition within the cluster. A node that is currently running a clustered mailbox server is an active node, and a node that is not running a clustered mailbox server is a passive node.

You can connect to both the CCR active node and passive node at the same time. You can also migrate Storage Groups from either node.

• Prerequisites for configuring a CCR-enabled Storage Group
  Ensure that you enable the Continuous Cluster Replica (CCR) feature on the Exchange server, the cluster continuous replication Storage Group copy is seeded and is healthy, SnapManager is installed on both nodes of the CCR, and the CCR active and passive nodes have identical dedicated LUNs before configuring a CCR-enabled Storage Group.
• Considerations for configuring SnapManager in a CCR-enabled Storage Group
  Before configuring SnapManager in a CCR-enabled Storage Group, ensure that database verification server is configured and enable all of the automatic event notification options.
• Configuring SnapManager in a CCR-enabled Storage Group
  You can configure SnapManager in a Storage Group that has Cluster Continuous Replication (CCR) enabled.