10.02.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8: Upgrading from 7.5 or 7.6 to <strong>8.5</strong><br />

Zero-Downtime <strong>Upgrade</strong>s of 7.5 <strong>and</strong> 7.6 Clusters <strong>and</strong><br />

Replicated Brokers<br />

In version 7, upgrades could not be applied to a running cluster or replicated brokers. You<br />

had to stop all the brokers, then upgrade them as a unit. For clustered brokers, it meant<br />

that the entire node was out briefly, all the configurations were forced to upgrade, <strong>and</strong> that<br />

the node did not return to full force until all the member broker installations had been<br />

upgraded. For replicated brokers, it meant that the peers were both offline until they were<br />

both upgraded.<br />

In version 8, the Launcher installed on every system that runs components in the domain<br />

means that administrators will never have to run upgrade software on each system ever<br />

again. The Domain Manager is where the upgrade takes place. Then, the Domain<br />

Manager provisions the remote systems with the upgraded software.<br />

The transition from version 7 to version 8 does require installation of the <strong>8.5</strong> Launcher on<br />

each system to establish participation in the new paradigm. And it does require running<br />

some scripted tasks to complete the change for each container, hosted component, <strong>and</strong><br />

data store.<br />

<strong>Sonic</strong> <strong>8.5</strong> simplifies the upgrade of clusters <strong>and</strong> replicated brokers by enabling a <strong>Sonic</strong> <strong>8.5</strong><br />

domain to tolerate both version 7 <strong>and</strong> version 8 brokers cooperating in different versions.<br />

You install a Launcher on a system where a broker member is running, extract its<br />

configuration from the domain, <strong>and</strong> then run a smart upgrade that stops the version 7<br />

broker at the moment when it needs perform database actions, <strong>and</strong> then restarts the broker<br />

as a <strong>8.5</strong> container. That provides administrators with a resilient non-stop topology that can<br />

be fully upgraded from version 7 to <strong>8.5</strong> at a more measured pace. You don’t have to have<br />

administrators all dispersed at systems that host participating cluster members or<br />

replicated peers, trying to orchestrate a simultaneous upgrade event.<br />

The upgrade functions on distributed hosts require that the Domain Manager has been<br />

upgraded to <strong>8.5</strong>. Administrative tools must also be Version 8 to monitor the Domain but<br />

have no actual role in the upgrade process.<br />

The upgrade process first connects to the <strong>8.5</strong> Domain Manager to extract the 7.5 or 7.6<br />

configuration, <strong>and</strong> then to upgrade the configuration <strong>and</strong> provision the <strong>8.5</strong> installation<br />

location with the appropriate <strong>8.5</strong> functionality.<br />

206 <strong>Progress</strong> <strong>Sonic</strong> <strong>Installation</strong> <strong>and</strong> <strong>Upgrade</strong> <strong>Guide</strong> <strong>8.5</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!