Automate entire broker service using terraform and backup

General Discussions
,
1

Hi , we have a solace message VPN it has all acl,acl profiles, queues, susbscriptions and all, we are trying to automate entire solace infra using terraform, if anything happened to existing VPN need to spin up new service with same infra details , is there any recommended approach to automate everything, in current solace-terraform version it is supporting one attribute for one resource i believe like if we want to fetch one particular queue (we can pass one in solacebroker_msg_vpn_queue) what if we have n no of queues , subscriptions and all and we want to fetch all using terraform data source? could you please suggest , we are using only one message VPN service as of now so we are planning for HA/DR..
What is the most effective approach for backing up Solace message broker configurations using terraform ? and what strategies should be used to ensure quick recovery in case of failures.?

2

Hi Suresh, take a look at the Solace configuration generator, using this command you can generate a copy of your entire message-vpn as a Terraform tf configuration file:

3

Many Thanks @paul, i was able to take the backup of entire solace configuration with config generator binary ,

.terraform/providers/registry.terraform.io/solaceproducts/solacebroker/1.1.1/darwin_arm64$ ./terraform-provider-solacebroker_v1.1.1 generate --username admin --password admin --url=http://localhost:8080 solacebroker_msg_vpn.demo solace-cluster vpn-config.tf

quick follow-up like what is the most effective approach for backing up Solace message broker configurations.? like periodic backups using same config generator and storing in external source (ex. AWS-S3) ? and what strategies should be used to ensure quick recovery in case of failures.?

thanks for your time.

4

Hi Suresh, the backup and restore strategy depends on whether you are using Solace Cloud - if you are not using Cloud you can use our configuration backup facility: Refer to - Backing Up and Restoring Event Broker Configurations. If you are using Cloud, currently our documentation recommends using Cloud API & SEMPv2: Refer to - Backing up Event Broker Services, however dSEMP (which is a Terraform based SEMPv2 wrapper) is a better option. The best strategy to ensure quick recovery in case of failures is to use Solace clustering and replication (HA/DR): Refer to - Event Broker Redundancy for High Availability & Data Center Replication for Disaster Recovery.

5

Thank you @paul for quick guidance, we are using cloud, let us explore on SEMPv2 .