This guide can be used to update any version. However, for the difference between major releases, you may need to run a script to update tables from your Catalogs after upgrading (for example: /opt/bacula/scripts/update_bacula_tables).
You must upgrade the Director and the Storage Daemon at the same time and always to a common version. However, customers can be upgraded gradually. in other words: Director and Storage versions must be equal and never inferior to File Daemons. The configuration files of the older installed versions are always maintained during the process.
General Update Steps
a) OPTIONAL: run Bacula server Catalog and configurations successful backup Jobs to safeguard the process.
b) In case of Bacula.org or Bacula Enterprise repositories installations, simply modify the version used in the yum or apt repository, update the repositories (yum clean all/apt update), and perform the package update.1 Example:
sed -i 's/10.0.8/10.2.2/g' /etc/yum.repos.d/Bacula-Enterprise.repo yum clean all yum update `rpm -qa | grep bacula-enterprise`
In case of missing packages, make sure that all plugins and drivers are registered in the package manager repository. In the latter case use the –skip-broken option, download and install it manually.
yum update --skip-broken `rpm -qa | grep bacula-enterprise`
c) Update your Bacula database structure if needed (5.0 to 5.2, 7.0 to 7.2, 9.0 to 9.2, 8 to 10.x etc. – releases that have already required this update). This database script may vary depending on your Bacula scripts folder and the database authentication method.
sudo -u postgres /opt/bacula/scripts/update_bacula_tables
d) Restart the Bacula daemons.
e) Test everything. Use the status and the estimate listing commands to test the status of your clients, storage, and jobs. Run a test backup job.
1In the case of the Linux distributions installations, the Bacula stable packages updates follows the process of upgrading the operating system version. Please proceed accordingly.