Xen Plugin: Installation

Bacula Enterprise Only

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

The following chapter explains how to install the Xen Plugin.

Prerequisites

File Daemon Host Requirements

The Bacula File Daemon must be installed and configured on a backup machine with access to the XenServer API and XAPI-NBD services.

It is not recommended to install the File Daemon and plugin on the hypervisor dom0 because NBD connections do not work when an NBD client is in dom0 on the same host as the NBD server (source: https://support.citrix.com/article/CTX230619/how-to-troubleshoot-changed-block-tracking-in-xenserver) .

Because all backup interactions are network based, any Bacula Enterprise File Daemon with access to the required XenServer endpoints can run the plugin.

File Daemon Plugin Directory

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

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

RHEL-Based System Support Note

On RHEL-based systems, Bacula Systems support for the XenServer Plugin covers only the plugin itself and Bacula-related code maintained by Bacula Systems. The EPEL-provided nbd component is an external dependency and is not covered by Bacula Systems support.

XenServer Backup Preparation

Before configuring backup jobs, complete the XenServer/XCP-ng preparation described here.

Instructions

See general instructions to install this plugin.