We recommend that you create RLINKs between hosts
tokyo when setting up the RDS.
Note Create SRLs of the same size on the Primary and Secondary hosts.
Before migration, the configuration of the RDS looks like this:
| * Indicates active RLINKs
To migrate the Primary RVG hr_rvg to host london
statuscommand. On the Primary
seattle, issue the following commands:
vxrlink -g hrdg status rlk_london_hr_rvg
vxrlink -g hrdg status rlk_tokyo_hr_rvg
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.
hr_rvgby typing the following command from any host in the RDS:
-g hrdg migrate hr_rvg london
londonand the additional Secondary
tokyois automatically added to the new configuration.
Otherwise, you must manually add
tokyo as a Secondary to the new Primary
london. To do this, create RLINKs between
tokyo and associate them to the respective RVGs using the following commands.
vxmake -g hrdg rlink rlk_tokyo_hr_rvg local_host=london \
remote_host=tokyo remote_rlink=rlk_london_hr_rvg \
vxrlink -g hrdg assoc hr_rvg rlk_tokyo_hr_rvg
vxmake -g hrdg rlink rlk_london_hr_rvg local_host=tokyo \
remote_host=london remote_rlink=rlk_tokyo_hr_rvg \
vxrlink -g hrdg assoc hr_rvg rlk_london_hr_rvg
By default, the
rlink command creates the RLINK with the protocol set to UDP/IP. To change the protocol to TCP/IP, see Setting the network transport protocol.
tokyousing the following command:
-g hrdg -f startrep hr_rvg tokyo
Ensure that the above command is run before starting the application on the new Primary
Because the application was stopped properly before the migration, an application recovery is not required.
By default, the
migrate command enables replication from the new Primary
london. To start the application before enabling replication, first, issue the
pauserep command, start the application, and then resume replication.
After migration, the configuration of the RDS looks like this: