Extension:Bacula rev 02

The Bacula extension adds a self-contained Bacula Enterprise backup environment to the storage server. It runs as an isolated container providing a Bacula Director, Storage Daemon, and File Daemon, together with the Bacularis web GUI for managing backup jobs, clients, schedules, and storage devices.

Note: Bacula is delivered as an optional Small Update (the xc-bacula2 module). This article describes revision 02. If your system was updated to a newer revision, refer to the matching Extension:Bacula_rev_NN article.

Requirements

Before the container can complete its setup, a dedicated ZFS dataset must exist on the storage server:

• Dataset name: _bacula_sys (exact name required)
• Location: any pool on the storage server

The dataset stores the Bacula catalog database, configuration secrets, and working files. It is detected automatically — no further manual configuration is needed.

Note: Actual backup data is stored on storage devices you configure later through Bacularis, not on the _bacula_sys dataset.

Getting started

Step 1: Install the Small Update

1. Navigate to System Settings → Update tab.
2. Click Upload update, then use the Browse button to select the previously obtained Bacula Small Update file (.upd).
3. Upload and wait for the installation to complete.

Step 2: Create the ZFS dataset

Create the dataset using either method:

Option A — LXC Admin tool (recommended):

1. Navigate to https://<server-ip>:4250/containers.
2. Select the bacula2 container.
3. Follow the prompts to create the required _bacula_sys dataset on the pool of your choice.

Option B — Storage GUI:

1. Navigate to Pools, select the pool where you want to store the Bacula catalog, then open Datasets.
2. Click Add dataset and enter the name _bacula_sys.
3. Click Confirm. Leave all other settings at their defaults.

Once the dataset exists, the container detects it automatically and finishes its initial configuration. This takes approximately one minute.

Step 3: Open the Bacula GUI

After setup completes, access Bacularis in either of two ways:

• Click Bacula GUI in the Launchpad (main dashboard).
• Navigate directly to https://<server-ip>:9097/ in a browser.

Log in with the same administrator username and password used for the main storage server GUI.

Using Bacularis

Dashboard

The Bacularis dashboard shows an overview of recent backup job status, registered clients, storage pools, and volumes. Use it to confirm that scheduled jobs are completing successfully and to spot any failures.

Configuring storage

The container includes file-based virtual autochangers pre-configured for disk-to-disk backup. To use tape hardware:

• Connect tape drives or tape libraries to the storage server.
• They appear automatically inside the container.
• Configure them as storage resources on the Storage page in Bacularis.

Adding backup clients

Install the Bacula File Daemon on each client you want to back up, then register the client through the Clients page in Bacularis. Refer to the Bacularis documentation for detailed client setup instructions.

Schedules and jobs

Create and manage backup schedules, job definitions, and retention policies on the Jobs and Schedules pages in Bacularis.

Email notifications

Bacula sends job completion and failure notifications through the storage server's built-in email gateway. To configure the destination address and SMTP settings:

1. In the main storage server GUI, navigate to System Settings → Administration → Email notifications.
2. Enter your SMTP server and recipient address, then save.

No additional email configuration is required inside Bacularis.

Factory reset

The container can be reset to its initial state using the LXC Admin tool. During a factory reset:

• The _bacula_sys dataset is preserved — all catalog data and configuration secrets remain intact.
• The container re-initialises itself automatically on next boot using the existing dataset.

Use this procedure to recover from a misconfigured container without losing backup history.

Known issues and limitations

• Dataset name is fixed. The dataset must be named exactly _bacula_sys. A dataset with a different name is not detected and setup will not proceed.
• Setup delay. Initial configuration takes up to one minute after the dataset becomes available. The Bacularis GUI is not accessible until setup completes.
• Self-signed certificate. The HTTPS endpoint at port 9097 uses a self-signed TLS certificate. Browsers will show a certificate warning on first access; this is expected. Add a permanent exception or install a trusted certificate if required by your security policy.

Changelog

rev 02

• Automated Bacularis configuration — no manual setup wizard required after dataset creation.
• Email notifications routed through the storage server's email gateway.
• Factory-reset support with catalog data preserved on the ZFS dataset.

rev 01

• Initial release. Bacula Director, Storage Daemon, File Daemon, and Bacularis web GUI running as a self-contained LXC container.

---

For further customization or troubleshooting, refer to the upstream Bacularis documentation or contact Open-E support.