Hi Bryan, You are right, the upgrade procedure only requires stopping all nodes, replacing the Qpid broker binaries and starting the nodes again. On first start-up, the required upgrade changes should be applied automatically. It is a good practice to do the backups of node working directories before the upgrade. In case of any unexpected issues, you can restore the data from backups and revert to 7.0.2 version.
Kind Regards, Alex On Mon, 13 Jan 2020 at 13:17, Bryan Dixon <[email protected]> wrote: > I'm wanting to upgrade/migrate our current Qpid Broker-J 7.0.2 environments > to 7.1.6 (or 7.1.7 when it is released). > > Our current 7.0.2 environment is BDB HA (3 nodes) running on Windows > Server > 2012 R2 with Oracle JDK 1.8. As part of the move to Broker-J 7.1.6 I want > to move to Adopt OpenJDK 11. > > To perform the upgrade, do I just do the following: > 1. stop all nodes of the 7.0.2 environment > 2. start the 7.1.6 environment (one node at a time) pointing to the > existing > qpid work environment that we were using with 7.0.2. > > Also, if I wanted to do a backup of the qpid work environment that I can > use > for a restore in case we have some type of unexpected issue after the > upgrade, can I simply copy the qpid work directory on each node while all > nodes are down and then restore that directory on each node and use with > 7.0.2 in case there are upgrade issues? > > Thanks > Bryan > > > > -- > Sent from: > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
