Performing planned migration
Prev Part 4: Maintaining normal operations and recovery procedures Next

Performing planned migration

For maintenance purposes or for testing the readiness of the secondary host, you may want to migrate the application to the secondary host. The following are a generic set of tasks that you may need to perform the following procedure.

To migrate the application to the secondary host

  1. Take the Application resource offline on both the clusters. Stop the application so that volumes are not in use and secondary is up-to-date.
  2. Transfer the primary role to the host at the secondary site by using the Migrate option.

    • 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.

  3. Assign drive letters to the volumes on the new primary.

    Make sure that these drive letters are the same as those of the original primary.

  4. Bring the application group online on the new primary.

You can now verify that the application functions properly on the new primary with the replicated data. After verifying its functioning, you can revert the roles to what they were originally by repeating the procedure.

Note:

Any changes that you make to the data on the new primary will get replicated to the original primary, which is now the secondary.
Prev Up Next
Normal operations: Monitoring the status of the replication Home Disaster recovery procedures