With ServAssure Collection Platform2.14 and later, custom queues, vhosts, exchanges, bindings, permissions, vhosts, and users that were created outside of those required by ServAssure NXT or ServAssure Collection Platform are preserved upon a re-install of RabbitMQ.
When you run the following playbooks, that may involve re-installing the RabbitMQ software, the custom settings are re-applied:
- site-upgrade.yml
- upgrade-rabbitmq.yml
- uninstall-rabbitmq.yml, followed by install-rabbitmq.yml
The only scenario where all custom RabbitMQ settings are not preserved is when the site-uninstall.yml playbook is run.
Running RabbitMQ upgrade playbooks have no effect on an up-to-date system, but if the RabbitMQ version is upgraded in the future, that prompts a re-install. Updating an existing RabbitMQ to run on a non-default interface also prompts a re-install.
While reloading custom configuration is handled automatically as a part of ServAssure Collection Platform upgrades, the RabbitMQ configuration can be backed up manually to a file prior to upgrading. The endpoint to manually backup is:
Manual backup should be performed on all RabbitMQ nodes.
Please contact CommScope Technical Support for instructions on how to manually reload from the backed up settings.