Important notes for migrating the Primary role
We recommend that you set the size of the SRL the same on the Primary and Secondary nodes because any of the Secondary nodes could be later converted to a Primary by using the
vradmin migrate or the
vradmin takeover command. To resize the SRL for an existing RVG, see Resizing the SRL.
We recommend that you configure the Primary and Secondary data volumes with the same names. However, if the names of the data volumes on the Primary and the Secondary do not match, map the names of the Secondary data volumes with the differently named Primary data volumes. For more information, see Mapping the name of a Secondary data volume to a differently named Primary data volume.
For an RDS with multiple Secondaries:
We recommend that you wait until all the Secondaries are up-to-date before migrating the Primary role. The
migrate command fails if all the Secondaries are not up-to-date. If the additional Secondaries were out of date before performing the migrate operation, then you would need to perform a complete synchronization.
After successful migration, if you had already created RLINKs between every pair of secondaries while setting up replication, you do not need to manually reconfigure the additional secondaries as a part of the RDS. Otherwise, you must reconfigure them manually. For more information, see Example 2—Migrating the Primary role in a setup with multiple Secondaries.