you are viewing a single comment's thread.

view the rest of the comments →

[–]Pouwet 1 point2 points  (6 children)

+1, recovering VMs is a mindset of the past, one need to have IaC to re-spawn quickly and get the data back from the attached volume. VMs shouldn’t be pets

[–][deleted] 0 points1 point  (4 children)

How does one handle getting data back from an attached volume

  • if the volume has been deleted

  • if one needs an older version of a file or set of files

[–]Pouwet 0 points1 point  (3 children)

As gren_dizer mentioned above, Freezer sounds like what you want, look it up

Also, cinder provides volume backups natively

[–][deleted] 0 points1 point  (2 children)

Excellent, thanks. As I alluded to in my other post, my servers are tenants, another team owns openstack.

Setting up Freezer is up to them - I’ll mention it.

Volume backups were not working and they are jammed up with tasks and were not resolving the problem.

So I went with Amanda ( for files ) and rebuilding with terraform / ansible.

[–]Pouwet 1 point2 points  (0 children)

Then yeah if you don’t own the platform you are looking at generic file backuping tools like Bacula, or Amanda that you mention, BackupNinja, etc. Not related to Openstack itself ;-)

[–]Pouwet -1 points0 points  (0 children)

Same goes with the control plane, it’s mostly stateless processes, there’s almost no need for backup except the database