We have deprecated VM-based event broker services in PubSub+ Cloud. You must migrate your VM-based event broker services to another service in a Kubernetes-based datacenter (region).
You have the following options to migrate your VM-based event broker services:
- Use the PubSub+ Cloud v2 REST APIs for Migration (Beta)
- In this option, you use the REST API to create a clone of the VM-based event broker service in a Kubernetes-based datacenter. You can use this option when you want migrate event broker services using custom hostnames and where messages in a queue don't need to be copied over to new event broker service or where you can safely drain the queues.
- After you create your event broker service and validate its configuration, you can move the custom hostnames to the newly cloned event broker service. For more information, see Migrating VM-Based Event Broker Services Using the Clone API (Beta).
- Use Replication for Migration (Controlled Availability)
- Solace offers replication as one possible solution for the migration of VM-based event broker services. You can use replication to migrate event broker services where client applications cannot tolerate message loss and where messages that are queued on the event broker service cannot be lost. You must manually create a clone of the VM-based event broker service in a Kubernetes-based datacenter and then configure replication using the Solace CLI.
- You can configure replication for any of the supported deployment ownership models (Public Regions, Dedicated Regions, and Customer-Controlled Regions).
-
Using replication to migrate VM-based event broker services is available as Controlled Availability (CA). Contact Solace to evaluate if this option meets your migration requirements and to get more information about using this solution.