Upgrading a Distributed Deployment

Overview

Every component in a distributed deployment, including the Central Server, all Distribution Servers, and all Remote Collectors, must run the same operating system and the same version of Tufin Orchestration Suite. We recommend that you schedule the upgrade for a time that has the least impact on your daily network operations, such as during the weekend or late evening, to minimize the impact of the small amount of downtime inherent during an upgrade. Do not upgrade the servers simultaneously. Each upgrade on each individual device must be run sequentially. Do not start the next server upgrade until the prior server has completed its upgrade and is up and running.

For supported upgrade paths to the current version, see Tufin Orchestration Suite Lifecycle.

Direct Upgrade

If you can upgrade directly from the installed release to the target upgrade, you must upgrade the servers in the following order - Central Server, then Distribution Servers, then Remote Collectors. For example, if you have one Central Server, two Distribution Servers and three Remote Collectors, the sequential order for the server upgrades will be:

  1. Central Server

    If your central server is configured for HA, follow the instructions for Upgrading in High Availability.

  2. Distribution Server 1
  3. Distribution Server 2
  4. Remote Collector 1
  5. Remote Collector 2
  6. Remote Collector 3

Upgrade Process

The upgrade described in the following steps is to a version supported by a direct upgrade.

  1. Upgrade the Central server. If the server is configured for HA, see Upgrading in High Availability.

    When the Central Server upgrade has completed, the other servers (distribution servers and remote collectors) will disconnect from the database until they are upgraded.

  2. Upgrade each Distribution Server sequentially.

    Wait for the upgrade of one distribution server to complete before starting the upgrade of the next distribution server.

  3. Upgrade each Remote Collector sequentially.

    Wait for the upgrade of one remote collector server to complete before starting the upgrade of the next remote collector.