Limitations

• When performing backup at the KVM domain controller (hypervisor) level, some Bacula features such as client RunScripts will not execute commands at the guest level. Dumping a MySQL database on a guest VM before the backup will require the use of custom scripts, using SSH for example or simply make us of the Bacula Enterprise MySQL Plugin. The same can be applied to any application running on the VM with any Bacula Enterprise plugin.

• Virtualization tools (qemu-ga) must be installed on the guest, and you may have to configure the guest to quiesce the file system properly during the snapshot phase.

• Virtual machines cannot be restored in a bare metal recovery way using the KVM Plugin.

• CD ROMS must be disconnected from VMs before attempting backup with the KVM Plugin. Else, the system might report the error “guestmount: multi-boot operating systems are not supported”.

• The KVM Plugin uses snapshots while backing up guest VMs. During a snapshot, blocks modified by the guest VM need to be copied in temporary space, the space required depends on the guest disk activity. By default the space is allocated under /var/tmp.

• The restart command has limitations with plugins, as it initiates the Job from scratch rather than continuing it. Bacula determines whether a Job is restarted or continued, but using the restart command will result in a new Job.

See also

• Go back to KVM Scope

• Go back to KVM Features

• Go back to KVM Installation

• Go back to KVM Configuration

• Go back to KVM Operations

Go back to the main KVM Plugin page.

Go back to the main Dedicated Backup Solution page.