Upgrading from Release 6.x

You can upgrade to FTL Release 6.10.1 directly from FTL Release 6.3.1 HF 4 or Release FTL 6.4.0 HF1, or later.

If you are upgrading from a release earlier than Release 6.3.1 HF 4 or Release FTL 6.4.0 HF1, and using auth-only or secure mode, you must first upgrade to Release 6.3.1 HF 4 or Release FTL 6.4.0 HF1 before upgrading to FTL Release 6.10.1. You can use this same procedure for both upgrades.

This procedure uses a rolling upgrade, which is to upgrade one server at a time. This lets you upgrade a network without a total service interruption.

Note: To migrate from Release 5.4 or earlier, see instead the sections that follow.
    Procedure
  1. Determine which core servers are leaders, and plan the order in which you will upgrade host computers to the new release of FTL. A recommended sequence is as follows:
    a. disaster recovery location, non-leader core servers
    b. disaster recovery location, leader core server
    c. disaster recovery location, auxiliary server
    d. primary location, non-leader core servers
    e. primary location, leader core server
    f. primary location, auxiliary server
    g. satellite location, non-leader core servers
    h. satellite location, leader core server
    i. satellite location, auxiliary server
  2. Check the persistence clusters status table and its services list sub-table to verify that all the persistence services in the cluster are a) running, b) part of the quorum, and c) up to date.

    See Persistence Clusters Status Table , FTL Servers Status Page, and Servers List.

  3. Address the first or next host computer in your plan and stop its FTL server process.
    This stops all services under that FTL server automatically.
  4. Uninstall the old TIBCO FTL installation package from that server’s host computer. See instructions in TIBCO FTL Installation.
  5. Install the new release of the full TIBCO FTL product on that host computer. See instructions in TIBCO FTL Installation.
  6. Ensure that all server computers in the cluster have their clocks synchronized.
  7. Repeat steps 2-6 for the next FTL server in your plan. Continue for each server until you have upgraded all the FTL servers.
  8. Restart (and upgrade, if needed) all application clients.

During the period where the network is running with a mix of both old- and new-version servers, and if you are using auth-only or secure mode, the new-version servers run in a temporary compatibility mode. When the final server in the network has been upgraded, all servers automatically exit compatibility mode. After all servers have been upgraded it is no longer possible to start older servers.

If needed, to manually force a server to exit compatibility mode, run the following POST server command:

POST http://<host>:<port>/api/v1/server -d '{"cmd":"exit_compatibility_mode"}'

Compatibility with Earlier Releases of TIBCO FTL

  • If using insecure mode, components of FTL Release 6.7.1 can communicate with those of Release 5.4 or later.

  • If using auth-only or secure mode, components of FTL Release 6.7.1 can communicate only with those of Release 6.3.1 HF4, or Release 6.4.0 HF1, or later.
  • If using auth-only or secure mode, we recommend upgrading all clients to FTL Release 6.7.1 or later.

  • If using auth-only or secure mode, clients developed at FTL Release 6.7.1 or later cannot communicate with FTL servers at any earlier release.

Migration With Disk Persistence

When migrating from 6.7.0 or later where disk persistence is enabled, for data center migration or upgrades, you can shut down the servers and copy the disk persistence related database files for data center migration use cases. You must shut down all servers before copying these files.

When migrating from in-memory persistence to disk-based persistence, two rolling upgrades are required. First, upgrade to 6.7.0 (or later), next, enable disk persistence and/or disk swap, then restart the servers again.