- Release Notes for Bacula 1.39.22
+ Release Notes for Bacula 1.39.26
Bacula code: Total files = 447 Total lines = 149,711 (*.h *.c *.in)
-New Features in 1.39.22:
-- Fix opening of database in console to respect ACL.
-- Permit multiple console/director resources in bconsole.conf.
- patch from Carsten Paeth calle@calle.in-berlin.de
-- Character substitution in Job/JobDefs WriteBootStrap.
- from Eric Bollengier.
-- Apply patch supplied in bug #656 to pass priority field
- in the run dialog to the Director in gnome console.
-- Add support of encrypted data stream to bscan from Eric.
- display data_len instead of data content (may be binary)
-- Add Enabled=xxx on update slots command.
-- Add host:port to connect failure messages to FD and SD from Dir
-- Add WhereACL to console ACL list. If nothing is specified, only
- the default is permitted for restore. Otherwise, *all* allows any
- path, or you can specify permitted paths. This should allow control
- over where users can restore files. This is untested.
-- Install man pages with 'make install'
-- Add Media.Enabled flag to client backups for dotcmds.c
-- Enforce Media.Enabled=1 for a current restore to work
-- Require restore case 3 to have sqlquery permission to work.
+Version 1.39.26 contains mainly bug fixes to 1.39.24. Please
+ see the ChangeLog for more details.
-Fixes to 1.39.22:
-- Lots of fixes -- see ChangeLog.
-- Lots of work on DVD writing.
-- Lots of work on documentation in the manual.
-- Lots of work on the rescue disk.
+==== IMPORTANT a stock SuSE 10.1 kernel may crash =====
+- A stock SuSE 10.1 kernel may crash when Bacula runs and accesses
+ the tape drive. Workaround, load a Fedora kernel, which works fine,
+ or load the SuSE 10.2 rc5 kernel which also works fine.
==== IMPORTANT Catalog update required =====
- The database format has been updated from what was used in
./update_bacula_tables
- It is necessary to run it only once the first time you move to a
- 1.39.x beta or to 1.40.0. Upgrading the Bacula version thereafter
- does not require updating the database again. Depending on the size of your
- database the script make take a bit of time, to run, but in
- general, it should be very fast.
+ It is necessary to run it only once the first time you move to
+ a 1.39.x beta or to 1.40.0. Upgrading the Bacula version
+ thereafter does not require updating the database again.
+ Depending on the size of your database the script make take a
+ bit of time, to run, but in general, it should be very fast.
+
+==== IMPORTANT DVD Volume format changed ====
+- The current Volume format written by 1.39.22 is different from
+ the format written by previous versions. The two formats
+ are not compatible. Thus any DVDs written prior to 1.39.22 will
+ be unreadable by version 1.39.22.
+
+==== IMPORTANT miscellaneous ====
+- The Gnome console program (gconsole) no longer functions as it
+ should. If you have multiple catalogs, you will need to select
+ the catalog (this I will fix). More importantly, in restore
+ mode, the restore tree is no longer shown in the left pane. I
+ suspect this is due to incompatible changes in the GTK+ API,
+ and hence have given up on gnome and gtk+, as this has already
+ happened several times previously. At some point there
+ will be a new GUI console.
+- The bacula-dir.conf directive Accept Any Volume has been
+ removed because it was never implemented. You must delete all
+ occurrence of this directive for the Director to run.
+- The --mandir ./configure option now points to the top level man
+ directory. The man files will be installed under mandir/man8 and
+ mandir/man1 as appropriate.
+- The "Accept Any Volume" directive has been removed. It was never
+ implemented. Bacula will always accept any valid tape that is in
+ the drive for appending.
+- You *should* be able to use 1.38.x FDs with version 1.39.18 Director
+ and SD providing you do not use any of the new features (runscript,
+ data encryption). It seems to work here, but we do not guarantee it.
+- Your Director and SD must be simultaneously upgraded.
+- The restore command no longer uses the MediaType as the primary method
+ of finding a suitable Storage device. Normally it will select the last
+ device used to write a Volume. If no storage device is defined, it
+ will use the old algorithm which selects the first Storage resource
+ with the correct MediaType.
+- The MD5/SHA1 hash codes kept in the database are now kept in a binary
+ format compatible with the rest of the world. If you are running verify
+ jobs, you *must* do an InitCatalog or all files will show an MD5
+ difference. Also, authentication uses the new algorithm by
+ default, but *should* accept connections from older components (FD) using
+ the old non-compatible algorithm. This has been tested, but more
+ more testing is still needed.
==== IMPORTANT new Win32 install procedure =====
For Win32 migrations from versions prior to the new installer nothing special
the new Bacula.
-New Features in 1.40.0 (beginning of release info)
+New Features in 1.40.0:
+- Windows tray status windows are scrollable and resizable.
+- Win32 external script excution is much more flexible -- handles
+ spaces in names better, ...
+- Lots of DVD fixes -- I think they now work!
+- Fix opening of database in a restricted console to respect
+ any Catalog ACL.
+- Permit multiple console/director resources in bconsole.conf.
+ patch from Carsten Paeth calle@calle.in-berlin.de
+- Character substitution in Job/JobDefs WriteBootStrap.
+ from Eric Bollengier.
+- Apply patch supplied in bug #656 to pass priority field
+ in the run dialog to the Director in gnome console.
+- Add support of encrypted data stream to bscan from Eric.
+ display data_len instead of data content (may be binary)
+- Add Enabled=xxx on update slots command.
+- Add host:port to connect failure messages to FD and SD from Dir
+- Add WhereACL to console ACL list. If nothing is specified, only
+ the default is permitted for restore. Otherwise, *all* allows any
+ path, or you can specify permitted paths. This should allow control
+ over where users can restore files. This is untested.
+- Install man pages with 'make install'
+- Add Media.Enabled flag to client backups for dotcmds.c
+- Enforce Media.Enabled=1 for a current restore to work
+- Require restore case 3 to have sqlquery permission to work.
- The basic features of Migration are now complete.
- There is a Migration chapter in the doc.
http://www.bacula.org/dev-manual/Migration.html
do a rewind on Solaris when no tape is in the drive (Solaris does not
have the detailed errno found on Linux). Added Solaris specific code.
Note, this may apply to other OSes as well.
-
-
-==========================================
-
-Beta version 1.39.20:
-- Writing DVDs should work much better thanks to Richard Mortimer.
-- Many cleanups/enhancements for Win32 systems.
-- Correct improperly formated list command output reported by Dan.
-- Eric fixed RunScripts, which I (Kern) had broken in the last beta.
-- Correct Client migration SQL as pointed out by Marc.
-
-
-Warning for version 1.39.18 and greater:
-- If you have an old pre 1.39.18 database, you must update it using
- the update_bacula_tables script. Please backup your database before
- updating just in case.
-- You *should* be able to use 1.38.x FDs with version 1.39.18 Director
- and SD providing you do not use any of the new features (runscript,
- data encryption). It seems to work here, but we do not guarantee it.
-- Your Director and SD must be simultaneously upgraded.
-- The restore command no longer uses the MediaType as the primary method
- of finding a suitable Storage device. Normally it will select the last
- device used to write a Volume. If no storage device is defined, it
- will use the old algorithm which selects the first Storage resource
- with the correct MediaType.
-- The MD5/SHA1 hash codes kept in the database are now kept in a binary
- format compatible with the rest of the world. If you are running verify
- jobs, you *must* do an InitCatalog or all files will show an MD5
- difference. Also, authentication uses the new algorithm by
- default, but *should* accept connections from older components (FD) using
- the old non-compatible algorithm. This has been tested, but more
- more testing is still needed.
-- The --mandir ./configure option now points to the top level man
- directory. The man files will be installed under mandir/man8 and
- mandir/man1 as appropriate.
-- The "Accept Any Volume" directive has been removed. It was never
- implemented. Bacula will always accept any valid tape that is in
- the drive for appending.
-
-
-A Lot of New features for 1.39.18:
- Switch the Win32 build from using Microsoft C++ to using mingw32
- cross-compiling. The inital work was done by Howard Thomson,
+ cross-compiling. The initial work was done by Howard Thomson,
then tweaked by me. Robert Nelson then totally reworked the
cross-compiling code so that it not only cross-compiles, but
also compiles on Visual Studio, and at the same time, he added
or
"status dir days=xx"
My use case is to be able to preview the next scheduled job (and the
- next tape to be used) on fridays if there are no scheduled jobs during
+ next tape to be used) on Fridays if there are no scheduled jobs during
the weekend. This patch was probably back ported to 1.38.x
- Add nagios plugin to the examples directory. Submitted by
Christian Masopust.
- Modify most restore error messages to be queued so that they
- appear at the end of the job rather than mixted with the restore
+ appear at the end of the job rather than mixed with the restore
listing where they could be "lost".
- Apply patch supplied by user (slightly modified) to fix
correct detection of holes in block devices and FIFOs.
bacula-ctl-fd -- starts/stops the File daemon
bacula-ctl-sd -- starts/stops the Storage daemon
- Remove automatic case folding on Windows FDs. You must
- explictly use the 'Ignore Case = yes' option.
+ explicitly use the 'Ignore Case = yes' option.
- Implement wild program in tools directory for testing
wild-cards. Almost identical to the regex program.
- Use the new bregex.c to implement Regex expressions on Win32.
- If using GCC (actually g++) add the following compiler flags
-fno-strict-aliasing -fno-exceptions -fno-rtti
- Turn on new bsnprintf() code. This could cause print output
- to look different.
+ to look different. The reason for this code is to eliminate the
+ security problems associated with using the system libraries
+ print routines.
- Implement job report that indicates where Storage and Pool
came from -- with overrides and Pool storage and NextPool,
it is all very complicated.
projects / bacula / bacula / blobdiff