Overview

Here you will find details 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, are applicable to backups.

Define backup datastores by using the available options for backends or datastore drivers:

  • Restic: based on the restic backup tool
  • Rsync: relies on the rsync utility to transfer backup files.
  • OpenNebula-Veeam® Backup Integration: provides robust, agentless backup and recovery for OpenNebula VMs using Veeam Backup & Replication.

Basic Guide Outline

Before reading this guide, you should have installed your Frontend, the KVM Hosts and have an OpenNebula cloud up and running with at least one virtualization node.

To configure your backup system, find about datastore driver options to save your VM backups:

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 and Storage Compatibility

Performing a VM backup requires 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

Yes***

Yes***

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.

*** LVM Incremental backups only supported in thin mode.

† Live LVM backups only supported in thin mode.