Overview
This Chapter contains documentation on how to configure the available backends for Virtual Machine Backups. Backups are managed through the datastore and image abstractions, so all of the concepts that apply to these objects (such as access control or quotas) also apply to backups.
Backup Datastores can be defined using two backends (datastore drivers):
- restic, based on the restic backup tool
- rsync, that uses the rsync utility to transfer backup files.
How Should I Read This Chapter
Before reading this Chapter, you should have already installed your Frontend, the KVM Hosts and have an OpenNebula cloud up and running with at least one virtualization node.
For configuring your backup system, you can first learn how to setup a datastore to save your VM backups, for the restic backend and for the rsync datastore.
Then, consult the Virtual Machines Operation section to find out how to perform, schedule and restore VM backups.
Finally, if you need to backup a large number of VMs you can manage them effectively through Backup Jobs.
Hypervisor & Storage Compatibility
Performing a VM backup may require some support from the hypervisor or the disk image formats. The following table summarizes the backup modes supported for each hypervisor and storage system.
Hypervisor | Storage | Full | Incremental | ||
|---|---|---|---|---|---|
Live | Power off | Live | Power off | ||
KVM | File* (qcow2) | Yes | Yes | Yes | Yes |
File* (raw) | Yes | Yes | No | No | |
Ceph | Yes† | Yes† | Yes† | Yes† | |
LVM | Yes‡ | Yes | No | No | |
LXC | File (any format) | No | Yes | No | No |
Ceph | No | Yes | No | No | |
LVM | Yes‡ | Yes | No | No | |
* Any datastore based on files with the given format, i.e. NFS/SAN or Local.
** Ceph full/incremental backups are currently stored in a different way, see backup types for more details.
† Live LVM backups only supported in thin mode.
We value your feedback
Was this information helpful?
Glad to hear it
Sorry to hear that