We recommend that you create RLINKs between hosts london and tokyo when setting up the RDS.
Before migration, the configuration of the RDS looks like this:
To migrate the Primary RVG hr_rvg to host london:
# vxrlink -g hrdg status rlk_london_hr_rvg # vxrlink -g hrdg status rlk_tokyo_hr_rvg
The vradmin migrate command fails if the Primary RLINKs are not up-to-date or not in the CONNECT state. It also fails if the data volumes are active.
# vradmin -g hrdg migrate hr_rvg london
Otherwise, you must manually add tokyo as a Secondary to the new Primary london. To do this, create RLINKs between london and tokyo and associate them to the respective RVGs using the following commands.
On host london:
# vxmake -g hrdg rlink rlk_tokyo_hr_rvg local_host=london \ remote_host=tokyo remote_rlink=rlk_london_hr_rvg \ remote_dg=hrdg # vxrlink -g hrdg assoc hr_rvg rlk_tokyo_hr_rvg
On host tokyo:
# vxmake -g hrdg rlink rlk_london_hr_rvg local_host=tokyo \ remote_host=london remote_rlink=rlk_tokyo_hr_rvg \ remote_dg=hrdg # vxrlink -g hrdg assoc hr_rvg rlk_london_hr_rvg
By default, the vxmake rlink command creates the RLINK with the protocol set to TCP/IP. If necessary, you can change the protocol to UDP/IP.
# vradmin -g hrdg -f startrep hr_rvg tokyo
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 migration, the configuration of the RDS looks like this: