- Release Notes for Bacula 1.33.4
-
- Bacula code: Total files = 306 Total lines = 90,715 (*.h *.c *.in)
-
-Major Features:
-- Data spooling which eliminates tape shoe-shine during Inc backups,
- and permits multiple simultaneous backups without interleaved blocks.
-- Polling of devices eliminating need to unmount and mount from
- console.
-- Native Win32 client -- much faster and restores permissions correctly
- (thanks to Christopher Hull)
-- PostgreSQL database driver (thanks to Dan Langille).
-- Improved Autochange support of Slots (update slots scan).
-- Autochanger support for multiple drives.
-- New conio code to implement Console command line editing and history.
-- JobDefs resource permits smaller .conf files for Director
-- Access console lists for the Console
-- Pool level overrides.
-- Daemon statistics memory.
-- Improved btape "test" and "fill" commands.
-
-New directives:
-- "Close on Poll = yes/no" in SD Device resource.
-- "Volume Poll Interval = time-interval" in SD Device resource.
-- "Two EOF = yes/no" in SD Device resource.
-- "Maximum Network Buffer Size = size" in SD Device resource.
-- "Maximum Network Buffer Size = size" in FD FileDaemon (or Client) resource.
-- "Console" new resource in Director conf file.
- New directives: Name, Description, Password, JobACL, ClientACL,
- StorageACL, ScheduleACL, RunACL, PoolACL, CommandACL,
- FileSetACL, CatalogACL.
-- "Max Run Time = duration" in Director Job resource.
-- "Max Wait Time = duration" in Director Job resource (not fully implemented).
-- "JobDefs = name-of-resource" in Director Job resource.
-- "Jobdefs" new resource in Director. Same directives as for a Job.
-- "Full Backup Pool = xxx" in Job resource in the Director.
-- "Incremental Backup Pool = xxx" in Job resource in the Director.
-- "Differential Backup Pool = xxx" in Job resource in the Director.
-- Three new options on the Run override statement in a Schedule resource:
- FullPool=xxx
- IncrementalPool=xxx
- DifferentialPool=xxx
-- SpoolData=yes/no in DIR Job resource
-- SpoolData=yes/no in Run override directive.
-- MaximumSpoolSize in SD Device resource
-- MaximumSpoolJobSize in SD Device resource
-- SpoolDirectory in SD Device resource.
-
-New Commands:
-- "SetIP"
-- Added "pool=xxx" to restore command line.
-- Added "fileset=xxx" to restore command line.
-- Fixed "storage=xxx" on restore command line.
-- "markdir" command in restore tree.
-- "unmarkdir" command in restore tree.
-- "quit" command in restore tree.
-- Trace option on "setdebug trace=1/0 ..."
-- Update slots scan
-
-
-Additional changes:
-- Implement Gnome 2.0 restore GUI
-- Add a missing unlock in the jobq handler.
-- Fix bug where a soft linked file and a directory had the same name
- by treating the soft link as a directory and putting the entries under
- it. This fixes the bug reported by Alexander Mueller.
-- Apply Jess Guardiani's second fix to list autochanger volumes without
- opening the drive (necessary on FreeBSD if no tape is in the drive).
-- Reworked the command line handler in restore to walk through the
- arguments one at a time. This makes the file= entries work correctly.
- Also reworked the code that takes the MediaType and finds a
- storage device.
-- Add quit command to restore tree handler.
-- Make restore tree handler remember if a hard link is present, and
- in doing a mark, only get database entry if there is a hard link.
- mark commands thus run at least 2 orders of magnitude faster.
-- Add files=xxx field to run command submitted for restore.
-- Add yes to restore run command if either yes or run is command line
- argument.
-- Make "yes" on command line argument skip prompt for modification of
- run job.
-- Add markdir and unmarkdir -- both affect only the directory in
- question and do not do a recursive descent.
-- Make tree command automatically mark all higher level directories to
- be restored when a directory or a file is selected. Such directories
- are indicated by preceding the name with a + to indicate that only
- the directory entry is selected and not the whole directory tree.
-- Modify a few tree commands to walk through all arguments rather than
- just taking the first one.
-- Improved btape "test" and "fill" commands.
-- The ability to ask the Storage daemon on a device by device basis
- to "poll" the tape drive at a given interval (minimum 1 minute). If
- a tape is found, its label is read and if appropriate it is used.
- This eliminates the need to do "mount" commands.
-- The ability to close and re-open the device when a poll occurs.
- This permits dealing with certain recalcitrant autochangers that
- invalidate devices (typically on FreeBSD).
-- Dan Langille has written a PostgreSQL driver for Bacula.
-- Implement "update slots scan" that reads the volume label(s).
-- The full form of the scan is "scan=1,2,4-5,7". With no specification,
- all occupied slots are scanned.
-- Turn off changer Volumes that are not current in the changer when
- an "update slots" is done, or if any tape operation discovers that
- the right volume is not in the slot.
-- The console program will run all commands it finds in ~/.bconsolerc
- at startup.
-- Add Dan Langille's changes to the bacula start/stop script that
- permit dropping root permissions just after startup.
-- New version 1.5.5-1 Cygwin.
-- Modify SD to update the catalog database when it is shutdown,
- even if the job is canceled.
-- Fixed seg fault in restore of multiple simultaneous jobs to
- a single Volume.
-- Fixed thread race problem in multiple simultaneous jobs to
- a single Volume where the volume label is not in the first
- tape block, so the tape is not recognized.
-- Restore directory tree automatically selects all higher level
- directories to be restored.
-- Implement conio.c to use in console program -- mini-readline.
-- Enhance "fill" command of btape -- simpler output. Use -v to
- cause last block to be dumped after write and after re-read.
-- Added an autochanger test to the btape "test" command. It is
- automatically invoked if the autochanger is properly configured. It
- is still a bit primitive but covers the essential of testing
- the mtx-changer script with your autochanger.
-- Select the oldest LastWritten volume during recycling.
-- Added forward space file test to btape "test" command.
-- All 1.32d patches applied.
-- Fixed seg fault in restore of multiple simultaneous jobs to
- a single Volume.
-- Fixed thread race problem in multiple simultaneous jobs to
- a single Volume where the volume lable is not in the first
- tape block, so the tape is not recognized.
-
-Items to note: !!!!!
-- FreeBSD users NOTE!!!!!
- You MUST add the following two records to your SD Device resource for
- tape drives.
-
- TWOEOF = yes
- Fast Forward Space File = no
-
-- The daemon protocol has changed, you must update everything at once.
-- The database level has been updated. You must either re-initialize
- your databases with:
-
- ./drop_bacula_tables
- ./make_bacula_tables
-
- which will delete ALL prior catalog information, or you can
- update your database with:
-
- ./update_bacula_tables
-
- Please save your old database before dropping the tables or doing
- an upgrade or you may regret it later.
-
-- smtp has now become bsmtp
-- console has now become bconsole.
-- console.conf is now bconsole.conf
-- Please don't underestimate the repercussions of the bsmtp and bconsole
- name changes!
+ Release Notes for Bacula 3.0.2
+
+ Bacula code: Total files = 1,009 Total lines = 205,726 (Using SLOCCount)
+
+Note, if you are not already running 3.0.x, read the 3.0.x release notes
+below. Important!!!
+
+Version 3.0.2 is primarily a important bug fix update to version 3.0.1 with
+some enhancements (see below).
+
+Changes since 3.0.1:
+
+Bug fixes:
+ 1029, 1285, 1298, 1303, 1304, 1305, 1306, 1307, 1308, 1309, 1311, 1315
+ 1317, 1318, 1323, 1325, 1331, 1333, 1335
+
+Fixed:
+ - Fix problem with the Postgresql driver that sometime displays <NULL> values
+ - Cleanup old job records when starting the Director
+ - Fix bugs in xattr code
+ - Fix encoding problem with Postgresql
+ - Fix that prevents restore by file selection from using Copy job
+
+Enhancements:
+ - Security enhancement for the File Daemon
+ - New directive to specify source address for outgoing connexions
+ - Show volume availability in autochanger when doing restore.
+ This is project 31 in the projects file.
+ - Add accurate=yes/no option to estimate command
+ - Add --with-hostname, --with-bsrdir, --with-logdir to ./configure
+ - Add a restore menu that contructs a full restore when entering a JobId.
+ This is project 2 in the projects file.
+ - Add new Nagios plugin
+
+Compatibility:
+Like always, both the Director and Storage daemon must be upgraded at
+the same time.
+
+Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 3.0.2
+Director and Storage daemons. It should be no need to upgrade older File
+Daemon.
+
+============ Documentation improvements needed ==================
+
+Note!!!!! The 3.0.0+ documentation needs rather extensive modifications in the
+following areas:
+
+1. Missing documentation.
+2. Correction of links within various manuals -- most fail.
+3. Integration of the new features into the main documents.
+4. Much more.
+
+The documentation will not be completed in the near future due to lack
+manpower. If you are unhappy with this situation as we are, we suggest
+you help by submitting patches to the documentation. Thanks.
+=====
+
+================== 3.0.1 Release Notes ========================
+
+Version 3.0.1 is primarily a minor bug fix update to version 3.0.0 with
+one enhancement.
+
+================== 3.0.0 Release Notes ========================
+
+The diff between 2.4.4 and 2.5.x is 208,340 lines, so this release
+represents an enormous effort.
+
+This Director and Storage daemon must be upgraded at the same time,
+but they should be compatible with all 2.4.x File daemons, unless you
+use some of the new features that affect the FD. In other words, you should
+not have to upgrade all your File daemons when you upgrade. However, any
+release of version 2.5.40 or greater requires a database upgrade.
+
+================== Warning !!!!!! ==========================
+
+New Catalog format in version 3.0.0 (2.5.40 or later)
+-----------------------------------------------------
+
+This release of Bacula uses a new catalog format. We provide a set of
+scripts that permit to convert a 2.4.x (version 10) catalog to 3.0.0 (version
+11). The Bacula project rpms distributed on Source Forge will automatically
+detect the database change and do the upgrade for you. We strongly
+recommend that you save a copy of your existing database before upgrading
+using rpms.
+
+The simplest way to upgrade the database assuming you are building from
+source:
+1. Stop any current version of Bacula from running.
+2. Save a copy of your existing database.
+3. Configure, build, and install the 3.0.0 version of Bacula
+ Note the new ./configure options in the manuals see the link
+ at the bottom of this file.
+4. cd <your-scripts-installation-directory>
+5. ./update_bacula_tables
+6. If you have multiple catalogs, edit the update_bacula_tables
+ script and put the name of another database, and then
+ execute the script again. Repeat this until all Bacula
+ catalogs have been updated.
+7. Start the new Bacula. If everything worked, it should
+ not print any error messages.
+
+The upgrade operation will convert the FileId index field of the File table
+from 32 bits to 64 bits. This operation will take TIME and will *temporarily*
+DOUBLE THE SIZE of your catalog. Bacula must be shutdown during this update,
+so, won't be able to run jobs during this period. For example, a 3 million files
+catalog will take 2 mins to upgrade on a normal machine. Don't forget to
+backup it before executing the script.
+
+If you start from scratch, you don't need to run the update_bacula_tables
+script because the create_bacula_tables script automatically creates the new
+table format. However, if you are using a version of Bacula older than 2.5.40
+(e.g. 2.4.4) then you need to run the update_bacula_tables script that will
+be found in the <bacula>/src/cats directory after you run the ./configure
+command. As mentioned above, before running this script, please backup your
+catalog database, and when you do running it, be sure shutdown Bacula and be
+aware that running the script can take some time depending on your database
+size.
+
+
+Important New configure options :
+----------------------
+
+This release of Bacula 3.0.0 uses libtool by default
+to generate the Bacula libraries as shared objects rather than
+being directly linked in as in prior versions. This means that
+the Bacula shared objects, must either be in a shared object
+directory known to the loader or they must be in the directory
+where the Bacula binaries are installed. It is also possible
+to explicitly specify the libraries directory on the ./configure
+line (--libdir=/full-path/dir), but this should not be necessary.
+
+ ./configure --libdir=<full-path>
+
+If you have problems with libtool or you wish to use the old
+way of building libraries and linking them into Bacula, you
+can do so by disabling libtool on the configure command line with:
+
+ ./configure --disable-libtool
+
+During the installation of Bacula 3.0.0, it will now install
+bat help files (if you have configured bat). These files
+are placed in /usr/share/doc/bacula/html by default. If you
+want to put them elsewhere use:
+
+ ./configure --htmldir=<full-path>
+
+During the installation of Bacula, it will now install the
+ReleaseNotes, License, technotes, ChangeLog, and similar
+files in /usr/share/doc/bacula by default. If you
+want to put them elsewhere use:
+
+ ./configure --docdir=<full-path>
+
+During the installation of Bacula, any plugins will be
+installed in the plugindir, which is by default the
+same as libdir (/usr/lib). You can specify an alternate
+location with:
+
+ ./configure --with-plugindir=<full-path>
+
+==============================================================
+
+This release includes large number of new features and changes.
+It should be more or less compatible with previous xx.conf files
+and File daemons providing that you are not using any of the new
+features.
+
+Please see the New Features chapter of the new manual, which documents
+some but not all the new features (we are still working on it):
+
+http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
+
+
+
+
+The ChangeLog has more details.
projects / bacula / bacula / blobdiff