Performing planned migration

You may want to migrate the application to the Secondary host for maintenance purposes and for testing the readiness of the Secondary host. The following procedure describes the generic set of tasks.

To migrate the application to the Secondary

  1. Detach the user database. See the Microsoft documentation for instructions.

    Note that the master, model, and tempdb, databases cannot be detached.

  2. Bring the RVG resource offline on both clusters.
  3. Transfer the Primary role to the secondary using the Migrate option as follows:

    • From the VEA screen, right-click the Primary RVG and select Migrate.

    • Select the Secondary host and click OK. The replication role is migrated to the Secondary host.

  4. Assign drive letters to the volumes on the new Primary. Ensure that these drive letters are the same as that of the original Primary.
  5. Bring the RVG resource online on both the clusters.
  6. Bring the SQL group online on the new Primary.
  7. Attach the databases. See the Microsoft documentation for instructions.

    You can now verify that the application runs fine on the new Primary with the replicated data. After verifying, you can revert back the roles to its original state using the same set of tasks described above.

    Any changes that you make to the data on the new Primary will get replicated to the original Primary, which is now the Secondary.