Bacula Enterprise Upgrade Procedure

The following article aims at proving you with necessary information about BE upgrade, and instructing you on how to perform it safely.

Important

Always have the Director and Storage Daemon(s) at the same version level. You can upgrade the File Daemons of your clients afterwards.

On the Director and any Storage Daemon machine(s), the File Daemon version must also match the DIR or SD version on that machine. For other machines, the FD version may be less than or equal to the DIR and SD, but not greater.

Note

It is recommended to have a testing environment and to upgrade it first, prior to upgrading a production environment.

Steps

Configuration files backup.

Backup your main configuration file folder (the content of /opt/bacula/etc) as well as any other files (script, services) you have created or modified. If you are using Bacula Enterprise plugin(s), backup the /opt/bacula/working directory too.

The upgrade will overwrite your service files, startup files, and some scripts, but it will not overwrite any .conf files.
Catalog backup if you upgrade the Director.

You can back it up to temporary media following these instructions:
```
sudo -u bacula /opt/bacula/scripts/make_catalog_backup.pl MyCatalog
```
```
cp /opt/bacula/working/bacula.sql /tmp
```
Change /tmp to any mount point you prefer.
Repository update.
- BIM usage
  
  If you used BIM to install the Bacula Enterprise components, simply run BIM again and it will propose to install the new Bacula version. Do run BIM again for any plugin installed on that system.
- Package manager usage
  
  Modify your package manager configuration file(s) in order to reflect the version you want to upgrade to. Do so for all plugins and products installed as well.
Upgrade.
- Patch or minor
  
  If you upgrade to a new version of Bacula Enterprise and only the last digit changes, for instance from 12.2.1 to 12.2.2, the process is straightforward. Just use your package manager to upgrade different Bacula components and plugins. Install new binaries and libraries. You should schedule a maintenance window for this, and restart the Bacula daemons that have received package upgrades, so that the latest versions are up and running.
- Major
  
  If you upgrade your Bacula environment to a new feature release (change of minor version digit) or a new major release, the procedure may involve a schema update of the Bacula Catalog database: Migration to a new major version of Bacula.

Note

If you run into trouble or have any error messages while upgrading your Bacula Enterprise infrastructure, open a ticket from your Customer Portal.