Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

Chapter 8: Upgrading from 7.5 or 7.6 to 8.5
Upgrading Replicated (Fault Tolerant) Broker Pairs
While a standalone broker can be licensed for fault tolerance and enable fault tolerant
client connections, fault tolerant broker pairs replicate data from the active member to the
standby, as illustrated.
As continuous availability is the obvious goal of this strategy, Sonic lets you upgrade the
peers hot—after you upgrade one, it synchronizes with the other even though their
versions do not match, and then stands alone until the other peer resumes after its upgrade.
◆ To upgrade 7.5 or 7.6 fault tolerant replicated brokers to 8.5:
1. In the Sonic Management Console, review the broker peers to see they are performing
as expected—both running, one in the ACTIVE role and the other in the STANDBY role.
2. Confirm that the primary broker has the STANDBY role. If not, force failover by
restarting the primary broker’s container.
3. On the primary broker’s system, perform the broker upgrade tasks:
a. Install the Sonic 8.5 Container Launcher
b. Extract the broker’s container’s properties.
c. Enter the 8.5 SonicMQ CAA license in the upgrade.properties file.
d. Specify the working directory if the Version 7 data store and log locations are
relative paths.
e. Run the upgrade. When the 7.5 or 7.6 broker is stopped, the backup broker is
STANDALONE. When the upgrade logic brings the broker up in 8.5, it passes through
STANDBY_SYNC and then takes the STANDBY role. The backup resumes the ACTIVE
role.
The upgrade forced upgrade of backup broker. The primary broker’s installation is
8.5, while its backup is version 7. Do not use any features introduced in 8.5 until all
the cluster members have been upgraded.
208 Progress Sonic Installation and Upgrade Guide 8.5