Steps for Configuring Replication

The following basic steps are required to initially configure replication service for Message VPNs used at two replication sites:

  1. PubSub+ event brokers used by the replication sites should be the same:
    • PubSub+ appliances should be the same model (for example, both Solace PubSub+ 3530s or both Solace PubSub+ 3560s) and use the same model Network Acceleration Blades (NABs), Assured Delivery Blades (ADBs), and Host Bus Adapters (HBAs).
    • PubSub+ software event brokers should have the same system resources and scaling parameters.

    Using matching event brokers avoids potential reductions in messaging performance and/or the number of available client connections if a switchover occurs and the event brokers at the site providing service do not offer the same capabilities.

  2. Solace recommends using same Solace PubSub+ version while setting up data replication for redundancy groups. If you need to upgrade an event broker's version, refer to the upgrade procedures for the appliance or software event broker for the version you want to upgrade to.

  3. To use replication, each event broker in both replication sites must be identically configured. Therefore, enable Config-Sync for all event brokers in both replication sites. In addition, if you are using high-availability (HA) at a replication site, you must assert one event broker’s system configuration over its mate's. See Enabling Config-Sync.
  4. Specify the replication mates for each event broker at both replication sites. See Configuring Replication Mates.

    When using Solace PubSub+ appliances, the static IP interfaces of the event brokers on the remote replication site must be able to reach the IP interface of the event broker on the local replication site acting as the primary for Guaranteed Messaging.

  5. Set the compatibility mode to "transacted" for both sites. See Configuring Replication Compatibility Mode for Transactions.
  6. Create corresponding Message VPNs on one event broker at both replication sites. For example, if you create a Message VPN named blue at one replication site, you must create another Message VPN named blue at its mate replication site. See Configuring Message VPNs.
  7. Although a Message VPN created at one replication site is not automatically propagated to the other replication site through Config-Sync, when HA redundant event brokers are used at a site, a Message VPN created on one event broker is automatically propagated to its mate.

    Message VPN configuration parameters are synchronized through the Config-Sync facility, but Message VPNs must be created and deleted manually. The existing configuration on the active site automatically overwrites the configuration of the standby site via Config-Sync.

  8. Configure the replication bridge connection that is automatically created for each Message VPN at both replication sites. See Configuring Replication Bridges.
  9. If you want to implement SSL encryption on Message VPN replication bridge connections, refer to TLS/SSL Encryption Configuration for Replication Bridges.

    You can also use SolAdmin to configure the replication and Config‑Sync parameters for the event brokers at both replication sites.

  10. Set the replication state for each Message VPN. Each Message VPN must be active at one replication site and standby at the other site (that is, a Message VPN cannot have the same replication status at more than one replication site). See Configuring VPN Replication States.
  11. Enable replication service for each Message VPN at both replication sites. See Enabling Replication.
  12. On a Message VPN with an active replication status, configure the durable endpoints to which the published Guaranteed messages will be spooled to. See Message VPN-Level Guaranteed Messaging Configuration.
  13. These durable endpoints will be automatically configured on the corresponding Message VPNs with standby replication states through Config-Sync.

  14. Configure the topics to replicate for the Message VPNs with active replication states. These topics will be automatically configured on the corresponding Message VPNs with standby replication states through Config-Sync. See Configuring Replicated Topic Subscriptions.
  15. If you will use transactions, configure the transaction replication mode. See Configuring Transaction Replication Mode.

Once replication and Config-Sync are running, clients that connect to a replication standby Message VPN are not allowed to create durable endpoints. They are also not allowed to modify the configuration of existing endpoints (for example, they cannot add or modify topic-to-queue mappings or change the topic or selector associated with a durable topic endpoint). Clients can only create or modify durable endpoints on a Message VPN that has a replication active state.