We recommend that you create RLINKs between the hosts london and tokyo when setting up the RDS.
In this example the Primary host seattle has failed. The example explains how to take over from the original Primary host seattle to the Secondary host london. This example also explains how to start replication from the new Primary london to the additional Secondary tokyo.
To take over from the Primary seattle to Secondary RVG on host london
# vxprint -l rlink_name
# vxprint -g hrdg -ht hr_rvg
# vradmin -g hrdg takeover hr_rvg
The vradmin takeover command enables fast failback.
# vxprint -l rlink_name
If fast failback is enabled, the dcm_logging flag is set.
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
# vradmin -g hrdg stoprep hr_rvg tokyo
On the new Primary london:
Synchronize the data volumes in the Secondary RVG hr_rvg on tokyo with the data volumes in the original Primary RVG hr_rvg using the difference-based synchronization and Storage Checkpoint. To do this, use the following command on any host in the RDS:
# vradmin -g hrdg -c checkpt syncrvg hr_rvg tokyo
The -c option when used with the vradmin syncrvg command automatically starts a Storage Checkpoint with the specified name, checkpt, in this example. After the data volumes are synchronized, the Storage Checkpoint is ended.
Start replication to tokyo using the Storage Checkpoint created above:
# vradmin -g hrdg -c checkpt startrep hr_rvg tokyo