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

Chapter 1: Overview of Installations and Upgrades
4. Choose to Setup an already configured container, and then enter (or navigate to) the
container configuration that was lost—in this example, /Containers/ct1.
5. Click OK. The container is setup on the ‘remote’ system.
6. Right click on HOST MANAGER, and then choose Operations > Launch Container.
7. Enter ct1, and then click OK.
The container that you set up on the ‘remote’ host is launched. The container starts, and
then starts the broker it hosts, and—because it is a new deployment—creates the tables in
the broker’s data store.
The broker console indicates the broker is started and accepting connections and
replicating.
Note In a broader topology, you would delete the replication connection and define a new one
with the machine names of the current machines that host the primary and backup
brokers. If the ‘lost’ machine was rediscovered and attempted to resume replication, it
would be stalled in WAITING state.
8. Observe in the container windows of ct2 and ct3 that they connect and synchronize:
■ Container ct2 indicates in its console window that Broker A is seeking its peer.
■ Container ct3 indicates in its console window that Broker A (Backup) has left
WAITING state, and is performing deep synchronization with its peer.
The brokers are setup, running, and replicating. The primary broker takes the STANDBY role,
and its backup takes the ACTIVE role.
The container cache was provisioned with the libraries to run a broker, created the
broker’s data stores, and then completely recovered the continuous availability brokers
with no loss of data, and—if the clients specified fault tolerant connections—no loss of
session states.
44 Progress Sonic Installation and Upgrade Guide 8.5