You should consider the following when upgrading replicating servers:

  • Upgrade affects only the server being upgraded.

    The process does not alter the configuration of other servers.

  • The update tool verifies that the version of Java that is installed meets the new server requirements.

    To simplify the process, install the version of Java that is supported by the new server before running the tool.

  • To be safe, backup the user data (userRoot) before an upgrade.

    Restoring from a backup could be necessary if all other servers in the replication topology have been upgraded and a database or encoding change in the new server version prevents the database from being used with the older server version. The update and revert-update utilities issue a warning when this is the case.

  • Temporarily raise the replication purge delay for all servers in the topology to cover the expected downtime for maintenance.

    This results in a temporary increase in disk usage for the replicationChanges database stored in <server-root>/changelogDb.

  • Replication does not need to be disabled on a server before an upgrade.
  • Ensure upgraded servers are working as expected before upgrading the last server in the topology.
  • Enable new features after all replicating servers are upgraded.

For additional considerations, see the Planning your upgrade guide.