Libvirt Plugin: Installation

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

In order to use the Libvirt Plugin, a Bacula File Daemon must be installed on a hypervisor that is compatible with Libvirt.

Note

See the List of Bacula Enterprise Plugins for plugin package names and information on where to install each plugin.

Prerequisites

The Plugin Directory directive of File Daemon resource in /opt/bacula/etc/bacula-fd.conf must point to where the libvirt-fd.so plugin file is installed. The standard Bacula plugin directory is /opt/bacula/plugins.

FileDaemon {
  Name = bacula-fd
  Plugin Directory = /opt/bacula/plugins
  ...
}

Additionally, the plugin must properly execute third-party software, specifically these binaries:

virsh
qemu-img
qemu-nbd

In some cases, the plugin may also require the following:

sudo
nbdfuse
fusermount
fuser
getenforce
chcon
aa-status
aa-complain
aa-enforce

Remote Backup

This plugin is capable of performing backups remotely. To enable this functionality, the following preparations are required:

On remote hypervisor: Add the SSH public key of the Bacula FD host to the authorized_keys SSH file.
On Bacula FD host: Establish the SSH connection at least once to ensure that the remote hypervisor’s fingerprint is added to the known_hosts file.

When using this method, the third-party software listed in the previous section must be installed on the remote hypervisor.

Additionally, the parameters related to nbd_server and nbd_client must be configured appropriately. In summary:

The nbd_server_* parameters define where the hypervisor exposes the data.
The nbd_client_* parameters define where bacula-fd connects in order to retrieve that data.