< Previous  | TOC | Index | Next  >

Example 1—Migrating from a healthy Primary

This example explains how to migrate the original Primary seattle to the Secondary host london.

  Note   Create SRLs of the same size on the Primary and Secondary hosts.

Before migration, the configuration of the RDS looks like this:

 To migrate the Primary RVG hr_rvg to host london

1. Stop the applications that use the Primary data volumes. For example, if the application is a file system, unmount it.
2. Verify that the Primary RLINK is up-to-date by using the vxrlink status command. On the Primary seattle, issue the following command:

   # vxrlink -g hrdg status rlk_london_hr_rvg

   The vradmin migrate command fails if the Primary RLINK is not up-to-date or not in the connect state. It also fails if the data volumes are active.

3. Migrate the Primary RVG hr_rvg by typing the following command from any host in the RDS:

# vradmin -g hrdg migrate hr_rvg london

london is the name of the Secondary host displayed by the vradmin printrvg command.

4. Restart the application.

   Because the application was stopped properly before the migration, an application recovery is not required.

   By default, the vradmin migrate command enables replication from the new Primary london. To start the application before enabling replication, first, issue the vradmin pauserep command, start the application, and then resume replication.

After the migration, the configuration of the RDS looks like this: