This page covers installation for the Bacula Enterprise trial Kickstart, along with a first basic tutorial after the installation notes. The tuturial-scenario is designed to demonstrate the basic functionality of Bacula Trial Edition. Many more tutorials are available in the Trial download documentation.
Step 1: Pre-installation
Fill the form from the following URL (http://www.baculasystems.com/download-kickstart-standalone-trial-version); download the Bacula ISO installation file according to the instructions send by email.
The following settings need to be available to ensure a successful installation.
Using incorrect settings will result in an unusable installation.
* Keyboard Layout
The country-specific keyboard code used by the Bacula server. Please refer to this list, in the chapter named “Keyboard”.
The system timezone for the Bacula Trial Edition server. Please refer to this list.
The un-qualified “short” hostname for the Bacula server.
* Domain (not required if using the DHCP feature)
The DNS domain name for the your network.
* IP Address (not required if using the DHCP feature)
The IPV4 network address for the Bacula server.
* Netmask (not required if using the DHCP feature)
The IPV4 network mask for the Bacula server.
* Primary and secondary DNS servers (not required if using the DHCP feature)
The IP addresses for the DNS servers on your network.
* NTP Server (optional)
The IP address of your network time protocol (NTP) server.
* SMTP Server (optional)
The IP address of your mail server.
* Passwords for the root user on the system and for the Bacula Enterprise users
The passwords that will be used for root and bacula accounts in the Linux
operating system and PostgreSQL database.
Step 2: Installation
If you are installing the Trial Kickstart in a Virtual Machine, please use the downloaded ISO to boot the VM. If you don’t want to use a 100Gb partition as indicated in the requirements, please use the boot option in step 4 to install on a physical server to have the option to choose the partition’s size. If you are using a physical server, select the media type your would like to boot your server on this ISO image.
- Boot from ISO image. The installer offers you the choice to install to a physical machine or to a virtual machine.
- Follow the wizard asking for your keyboard layout and time zone.
- Hard disk configuration.
- If installing on a virtual machine, a single hard disk will be assumed and a default partition layout used. It is assumed that virtual machines will mainly be used for testing Bacula Enterprise, not for production. We strongly recommend to install Bacula Enterprise on a physical server for better performance.
- If installing on a physical server (or using the bare metal boot option on a virtual machine with multiple disks), you will be prompted to specify the size of the OS partitions, optionally mirror their root disk, and create storage space using RAID. The number of choices provided depends on the number of disks detected.
- The CentOS system is installed. It should take about 15 minutes and certainly no more than 30 minutes.
- Account passwords.
- You will be prompted to enter the passwords for the root and Bacula Entreprise Edition catalog. The entered passwords will be set both for the local Linux accounts as well as PostgreSQL accounts of the same name.
- Network Identification
- You will be prompted for the hostname, domain, and dns settings.
- Network Interfaces
- You will be prompted for the IP address and netmask information if you don’t use DHCP as proposed.
- If installing on bare metal, choices will be provided for optionally configuring jumbo frames or ethernet trunking. These should only be used if the environment supports it and you really require them.
- Network Time Protocol (optional)
- You will be prompted for the IP address of their NTP server.
- Email Settings (optional)
- You will be prompted for the address of your SMTP server. Choices will also be provided to enable SSL and SMTP authorization if the mail server supports them.
- Catalog Database
- You will be prompted for the databases supported by Bacula Trial Edition. We strongly advise to use PostgreSQL database, which is more efficient with a Bacula Enterprise infrastructure.
- Default Volume Pool
- The default volume pool is where your backed up data will be stored if you don’t use a Virtual Tape Library or ZFS.
- Virtual Tape Library Settings (optional)
- A portion of your storage can be configured as a virtual tape library. This emulates a real tape library.
- Dedupe Device creation (required to use the Global End Point Deduplication Plugin)
- The Global End Point Deduplication require the creation of dedicated Dedupe Devices and Storage. Please check the scenario 6 or the Global End Point Deduplication White Paper for more information.
- Demo Config
- If you wish to follow the scenarios in this guide, please install the demo config.
- Installation complete. A reboot of the system is required after its update. It can take time due to some recompilation.
Step 3: Using Bacula Trial Edition
In the following scenario, you will get the opportunity to use Bacula Trial Edition to backup and recover data using BWeb Management Suite and BConsole.
After the reboot, the Trial Kickstart displays a welcome page that gives you the information you need to access BWeb Management Suite, the monitoring and administration web tool.
You can connect to BWeb Management Suite from Firefox (version 10 or above) from your desktop.
Test Scenario: Backing up files from /usr folder using BWeb Management Suite
1. BWeb Management Suite is a web interface that interacts with the Director and offers tools to run backup and restore jobs, to monitor and to configure the Bacula Trial Edition infrastructure.
- Open BWeb Management Suite using the link available on the Trial Kickstart’s welcome page.
3. Let’s back up the /usr directory. Click in the main menu on Jobs->Defined Jobs tab. Select usr from the drop-down menu of defined jobs.
4. Let’s click Run now to start it immediately.
5. The window refreshes to display the job options available. Accept the default values by clicking Run Now once again.
6. You will be taken to the running job information window. You can click Refresh to watch the progress. NOTE: THIS JOB BACKS UP >75,000 FILES WHICH MIGHT TAKE A FEW MINUTES DEPENDING ON THE PERFORMANCE OF YOUR SYSTEM.
7. Once the job is complete, an automatic refresh will take you to the job information window where you can see the outcome of the backup job. You can also find this information by navigating to Jobs->Jobs History and clicking on the status icon.
Additional Steps: adding Linux & Windows Backup Clients to other machines
The same kickstart ISO used to deploy the Bacula Server contains Clients for Red Hat (CentOS), SLES and Windows machines. They are located at the path: /bs/bacula/clients
If using the kickstart 8.2.8 version you can also download those clients from this link.
a) Install the desired Bacula client. Edit the bacula-fd.conf file (/opt/bacula/etc if Linux, Start Menu> Bacula Configuration if Windows); Check or modify the directive Director – Name to bacula-dir (actual Name kickstart Director). Also, copy the Director Password (at the same resource) to a notepad: we are needing this information later to attach this client to the Director.
Restart the client daemon if you made any changes to bacula-fd.conf (service bacula-fd restart on Linux; services.msc > Restart Bacula Service Daemon file on Windows).
b) Now proceed to the exclusive Bacula Enterprise interface: the Bweb. At the configuration menu, Director configuration, add a new Client Resource. Give a name to the client; fill the address with the client machine IP; paste the password that you copied to a notepad earlier to the password field.
Commit the changes in order to reload Bacula and make the Director talk to the new client.
Back at the Director configuration, create a new FileSet (list of directories of the client to be copied). If you made everything right until now you can browse the clients machines files and choose what paths should be copied during the backup.
At least, still at the Director Configuration, add a new Job. Make sure it uses the same new Client and FileSet created in the previous steps. Commit changes and test the new created Job, running it through the Job menu.