12.0.0 to ważne wydanie major udostępnione 30 kwietnia 2019 r. Najważniejsze zmiany obejmują Support for Client behind firewalls or NAT; Automatic TLS encryption for all network communications oraz Android File Daemon support.
Producent klasyfikuje to wydanie jako major release, więc warto zaplanować aktualizację z odpowiednim wyprzedzeniem.
Aktualizację środowisk produkcyjnych warto wcześniej zaplanować, zwłaszcza przy przejściu z dużo starszych wersji. Wydanie dostępne jest dla wszystkich klientów posiadających aktualną subskrypcję Bacula Enterprise Edition dowolnego poziomu oraz dla odbiorców usługi Inteos Backup.
Informacje szczegółowe
Release Notes for Bacula Enterprise 12.0
============== !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===================
The Director (Dir) and all Storage Daemons (SDs) must all be upgraded to
version 12.0 because they are not compatible with prior versions.
Catalog format in version 12.0 and greater:
------------------------------------------
The major release 12.0 of Bacula uses a new catalog format. We provide a set
of scripts that convert 6.6.x and earlier catalog versions to the new 12.0
format (1021). Please see the white paper "Migration-to-12.0" for detailed
instructions on the migration process.
The database upgrade from 1020 to 1021 is fast and simple for most users.
The Bacula Enterprise RPM spec files have been modified to detect the database
change and do the upgrade for you (from 8.10, 10.0, 10.2). We strongly
recommend that you save a copy of your existing database before upgrading using
RPMs. If you want to have more control over the catalog upgrade step when
upgrading using RPMs, you may want to contact the Bacula Systems support team
to get the update_bacula_tables script and run it before the RPM installation
step.
If you upgrade BWeb Management Suite from 8.x and you use the MySQL catalog,
you must update the BWeb SQL tables with the script upgrade-8.8_10.2_mysql.sql.
If you are starting from scratch, you don't need to run the
update_bacula_tables script because the create_bacula_tables script
automatically creates the tables using the new format.
Restricted Console users must modify their existing Console resources to specify
DirectoryACL=*all* and UserIdACL=*all* in order to continue to use the restore
command. If these two directives are not set, the restore command will return
an error.
On Suse Linux, the Director and the Storage Daemons are now started with the
unix account "bacula". To upgrade a Suse system to Bacula Enterprise 8.8 or
later, the ownership of the Bacula volumes and the configuration files must be
changed to "bacula:bacula" and the PostgreSQL/MySQL configuration may have to
be adapted. More information can be found in the Migration-to-12.0 whitepaper
available in your download area.
Redhat 5, SLES 10, SLES 11, SLES 11.1, SLES 11.2 are no longer supported in
version 12.0. Old filedaemons are still compatible and can be used to protect
these systems.
If you are upgrading from 10.x, please read the ReleaseNotes from the last 10.2
version.
----------------------------------------------------------------
Release 12.0.0 30 April 2019
12.0.0 is a major release.
New Features:
-------------
- Support for Client behind firewalls or NAT
- Automatic TLS encryption for all network communications
- Android File Daemon support
- Linux BMR UEFI Support
Plugin:
- Docker Plugin
- Sybase ASE File Daemon Plugin
- CDP (Continuous Data Protection) File Daemon Plugin
- vSphere Plugin ESXi 6.7 Support
- MySQL Percona Plugin enhancements
- Azure cloud driver update
- New MSSQL Plugin options to deal with Recovery Models
- New NDMP history file scanner
BWeb Features:
- BWeb Management Console Dashboards
- Proxmox Clustering support
Misc Features:
- New Swift Cloud Storage driver
- New global Autoprune directive
- New AllowIncompleteJobs directive
- Ability to run a Virtual Job based on a single Job
- New Storage Daemon file driver directive (SyncOnclose) to use fsync() when
a backup job closes the device
- Ability to specify a program in the Client Address directive
- New Documentation where external references should be automatically
handled in PDF as well as in HTML
Important Changes:
- New Catalog format 1021
- All network communications are now encrypted by default using TLS AES256-CBC-SHA
The secret key used for the communication is the password shared between
the client and the daemon. If network speed is a key factor, it is possible
to deactivate the TLS encryption for a Client.
- The Copy/Migration/Restore Job performance with a large number of files or with
complex BSR files has been greatly improved.
- The procedure to send a cancel signal to the FileDaemon and the Storage Daemon
has been improved. Jobs that are running on FileDaemon/StorageDaemon waiting for
a timeout should be more easily canceled by the Director.
- #2367 The VirtualFull based only on Incremental/Differential issue with Accurate mode
is now fixed.
More information and examples may be found in the "New Features" section of the
main manual.
Known Issues and Workarounds:
-----------------------------
- #1723 The hardlinks=yes FileSet option is not compatible with VirtualFull jobs.
This incompatibility might lead to problems during a restore.
The error message displayed during a restore job is:
Error: create_file.c:327 Could not hard link /path: ERR=No such file or directory
To restore the file correctly, it is required to select the first occurrence
of the hardlink file in the backup manually. The procedure to distinguish
hardlinks in the catalog is available from the Bacula Systems support team.
- #4957 VirtualFull, Copy/Migration jobs based on Incomplete jobs potential issue.
Under some circumstances a Copy/Migration/VirtualFull job may not be able to
copy the data from a Job that was interrupted and restarted using the
Incomplete Job feature. In version 10.2.3 and above, the
Copy/Migration/VirtualFull job is aborted with the following error message:
Fatal error: catreq.c:691 SHA1 digest not same FileIndex=344 as attributes FI=343
or
Fatal error: catreq.c:691 MD5 digest not same FileIndex=344 as attributes FI=343
It is recommended to re-execute the Job that was interupted then restarted to
be able to copy/migrate the data. We do not recommend to include an
Incomplete Job into a Progressive Virtual Full chain of jobs.
The automatic rescheduling of Incomplete Jobs can be disabled to avoid
restarted Incomplete jobs to finish successfully and be selected to be
copied/migrated/consolidated in Virtual Full using the
"RescheduleIncompleteJobs=no" Job directive.
Please contact the support team for more information.