| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2022-06-20 |
messages, backups, rabbitmq backups, messages for rabbitmq backups |
messages-for-rabbitmq |
{:external: .external target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:codeblock: .codeblock} {:pre: .pre} {:tip: .tip}
{: #backups-for-rabbitmq}
The {{site.data.keyword.messages-for-rabbitmq_full}} backups do not contain the actual messages. Your {{site.data.keyword.messages-for-rabbitmq}} deployment backups contain only configuration data.
For more information on backing up your {{site.data.keyword.messages-for-rabbitmq}} service configurations, see the Managing backups section of the {{site.data.keyword.cloud}} documentation.
Review the management responsibilities and terms and conditions that you have when you use {{site.data.keyword.messages-for-rabbitmq}} service.
{: #concepts-suggestions}
The expected operation for a {{site.data.keyword.messages-for-rabbitmq}} deployment is to keep queues short: messages are written and read in a short cycle with focus on throughput. {{site.data.keyword.messages-for-rabbitmq}} deployments are not intended as a data store like other {{site.data.keyword.cloud}} offerings.
For message delivery with durability and consistent quality of service, you must use quorum queues.
The Shovel plug-in can also help move messages across instances. While not a backup mechanism, this plug-in can aid in message retention.
Remember, messages are not part of the {{site.data.keyword.messages-for-rabbitmq}} deployment backups regardless of the queue types or plug-ins implemented.
More information on {{site.data.keyword.cloud}} can be found in the high availability and disaster recovery section.