-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WPB-4379] Rabbitmq backup and restore process #712
Conversation
offline/rabbitmq_backup_restore.md
Outdated
``` | ||
rabbitmqadmin import definitions.json | ||
``` | ||
To restore the data - |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: node needs to be stopped before restoring files
suggestion: ensure rabbitmq node is stopped before and restarted after restoring the mnesia directory.
offline/rabbitmq_backup_restore.md
Outdated
Now, save these files on your host machine with scp command - | ||
``` | ||
mkdir rabbitmq_backups | ||
cd rabbitmq_backups | ||
``` | ||
Fetch the backup files for each node one by one, | ||
``` | ||
scp -r <node_name>:<path_to_store_backup>/ <node_name>/ | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this not be part of the playbook as well? I know you have node_name
as the scp target folder, but it's not created prior to the command, which might end up overwriting backups between nodes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
scp -r
command will create the directories, also just to avoid the overwriting, updated docs to use new path for restore, instead of /path/to/backup
``` | ||
|
||
|
||
## Restore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the restoration process, I'd honestly link the official documentation as there's several potential pitfalls (such as shutting down the node highlighted by @lwille).
Perhaps it would be a good idea to add a few points on how the cluster is expected to behave with definitions and message restores.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added official docs link.
Co-authored-by: Jan Schumacher <[email protected]>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Create backup and restore process for ansible based RabbitMQ deployment outside Kubernetes cluster - https://wearezeta.atlassian.net/browse/WPB-4379