Basic concept
Bacularis is a web interface for the Bacula software. It consists of two main components:
- Web component - responsible for the user web interface
- API component - responsible for communication with Bacula and the operating system
Although these are two separate components, they are delivered as a single application simply called Bacularis. During the installation process, both components are installed and configured to work together on the same host.
Why this architecture?
This separation allows for flexible deployments - from simple single-host installations to distributed environments with centralized management.
Which components should you start with?
On each host, the user can configure and use either both components together or only a single selected Bacularis component.
For proper operation in a Bacula environment, a single host with a configured web interface and API is sufficient. Additional hosts are required when there is a need to use extra features on remote hosts, such as:
- configuring remote Bacula Storage Daemons or Bacula Clients from a central web interface
- using Bacularis plugins for backup on remote hosts
- managing tape devices with a changer (loading and unloading tapes from slots, moving tapes to I/O ports, and more)
- starting, stopping, and restarting Bacula components
- installing, updating, and removing Bacula software on remote hosts
In the most common scenario, the user runs one central web interface and API on a single host (usually the host with the Bacula Director) and several API instances on remote hosts with installed Bacula Storage Daemons or Bacula Clients.
Component dependencies
The API component provides data for the web interface. Communication between the web interface and the API is performed using the HTTP(S) protocol, regardless of whether the communication is local or remote.
