Migrating the Masters

If you have client applications that write to the master you
want to migrate, reroute these applications to write to another master in
the topology.

Ensure that the master is no longer receiving write requests.
You can do this by enabling read-only mode on the master.

Check that replication is synchronized between the master
and all its consumers.

Migration of the change log is not supported
if you are migrating manually, so the preceding two steps are mandatory in
this case. Although automatic migration does migrate
the change log, you should still perform the above steps to avoid the risk
of losing changes.

Disable any replication agreements to and from the master
you want to migrate.

Figure 7–11 Migrating Master

Check that the replication on all hubs and consumers is in sync with
the rest of the topology before migrating another master. A server that has
just been migrated does not have a change log, and can therefore not update
servers that are out of sync. Allow the topology to stabilize and all servers
to synchronize before migrating the next supplier server.