KVM Guests Backup - CentOS7
-
@dafyre Would you backup the host or each VM?
-
@aaronstuder said in KVM Guests Backup - CentOS7:
@dafyre Would you backup the host or each VM?
I would do each VM. Once done, it's set it & check it every now and again to make sure it works.
-
@dafyre I need to learn a config management package.... suggestions?
-
@aaronstuder said in KVM Guests Backup - CentOS7:
@dafyre I need to learn a config management package.... suggestions?
SaltStack.
The Python way is THE way. -
@aaronstuder said in KVM Guests Backup - CentOS7:
@dafyre I need to learn a config management package.... suggestions?
I'll have to defer to others for that one, lol.
-
@Francesco-Provino What about puppet, anisble, etc?
-
@aaronstuder said in KVM Guests Backup - CentOS7:
@dafyre Would you backup the host or each VM?
I want to say that you never backup the host - but who knows.. you might want to backup the host config so if it dies you can quickly rebuild it.
One of the manage advantages of hypervisors is that the host doesn't really matter. if it dies, you spin up another box, install your hypervisor in it, do some quick configuration - set IP, build vSwitches, etc and then restore your VMs.
-
@aaronstuder said in KVM Guests Backup - CentOS7:
@Francesco-Provino What about puppet, anisble, etc?
I've tried to get puppet working several times, but never get right. Over-complicated, and I dislike the DSL language.
Salt is simpler and easier, and better than Ansible IMHO. I don't like the Ansible push-mode, is slow and tracking issues is hard. -
@aaronstuder said in KVM Guests Backup - CentOS7:
What's the best way to backup KVM Guests on CentOS 7?
No simple answer. Backups don't work that way. There are three really popular approaches, all of which have tons of merit:
- Agentless / Host backups. This uses KVM and it's storage layer to take a backup of the device. This is super popular on VMware because of its native change block tracking. Not so popular on other hypervisors because they lack this (but might add it, Hyper-V is just adding it now.)
- Agent Based / Guest backups. These are the traditional backups we've used for years. Treat the VMs just like physical devices. This is the most popular for KVM.
- DevOps style. Use scripts or agents to backup only the core data on a box and only backup VMs that have changing data on them like databases or file servers, no backups of all of stateless systems like application servers.
-
@Francesco-Provino said in KVM Guests Backup - CentOS7:
@aaronstuder said in KVM Guests Backup - CentOS7:
@Francesco-Provino What about puppet, anisble, etc?
I've tried to get puppet working several times, but never get right. Over-complicated, and I dislike the DSL language.
Salt is simpler and easier, and better than Ansible IMHO. I don't like the Ansible push-mode, is slow and tracking issues is hard.Ansible will pull, too. But I am liking Salt a lot, too. And a friend of ours is one of the Salt developers.
-
@aaronstuder said in KVM Guests Backup - CentOS7:
@dafyre Would you backup the host or each VM?
Each VM. Each workload is unique, they each have unique needs (most of the time.)
-
@dafyre said in KVM Guests Backup - CentOS7:
@aaronstuder said in KVM Guests Backup - CentOS7:
@dafyre I need to learn a config management package.... suggestions?
I'll have to defer to others for that one, lol.
Salt and Ansible seem to be the most interesting. We are getting into Salt, here. Chef is decent.
