X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=bacula%2FReleaseNotes;h=fe281432e7b52a794e99ec775404f98b8e6fbf25;hb=1e32b9b18aa40e516767aae2503fe3d8620ef286;hp=3220ac2652b2423540ff2716302a8b98461dc3e8;hpb=ef10d3f810beb54c9a2bcc286e1407cac004b87e;p=bacula%2Fbacula diff --git a/bacula/ReleaseNotes b/bacula/ReleaseNotes index 3220ac2652..fe281432e7 100644 --- a/bacula/ReleaseNotes +++ b/bacula/ReleaseNotes @@ -1,84 +1,177 @@ - Release Notes for Bacula 1.32b - - Bacula code: Total files = 259 Total lines = 77,984 (*.h *.c *.in) - -Changes since 1.32a: -- Improve forward space file/block during restore, many - optimizations. -- Fix a bug that did not allow appending to a tape - on FreeBSD systems. -- Fix pruning so that it will not prune the current job. - -Major Changes 1.32a Release: -- Implemented forward space file/block whenever possible - during restore. Restoring a small number of files is now - much faster. -- There is a new option to restore that allows you - to restore files based on their Filename. You can - also specify a file to read which contains the list. -- Added ClientRunBeforeJob and ClientRunAfterJob. -- Implemented Include | and < in File daemon. -- Automatic labeling of tape Volumes should work now. -- Recycling has been completely restructured and should work. -- Implemented full length time interval qualifiers (e.g - "5n is now "5 min" or "5 minutes". A modifier is now required! -- Fixed gnome-console to compile with RH9 (Gnome 2.0) -- Implemented "list nextvol job=xxx", which displays the - next volume to be used by job xxx. The Volume name to - be used is also added to the "status dir" output. -- Lots of fixes with variable expansion and counter variables -- Implemented a new Include/Exclude syntax. -- While writing a tape, an end of file mark will be written - every 1Gb. This makes restores faster. If you want to - change this use "Maximum File Size" in the SD Device - resource. - - -Other Changes 1.32a Release: -- Fixed sparse file bug. -- A warning message is sent when a job starts that will be - blocked because the user did an "unmount". -- Block checksum errors if any are printed in the job report. -- Implemented a single routine to read_records. It also returns - a different record packet for each session. This means - that multiple simultaneous jobs should work. -- Added SDConnectTimeout to FD. -- Lots of doc enhancements -- Fixed a PurgeOldestVolume bug (VolStatus not returned) -- Don't crash if DB address record not specified. -- Return VolStatus on find_next_volume. -- Use alist for incexe name_list. -- Use bget_dirmsg() everywhere possible when talking to FD. -- Delete old semaphore job and workq job scheduling code. -- edit_run_codes in one place (/lib) Add Job name -- Update query.sql to find current backups correctly. -- Correct ambiguous SQL statement for pruning. -- Set heartbeat interval to zero by default. -- Fix a possible race condition in stopping the - heartbeat thread. -- Eliminate gnome2-console directory. Everything is in gnome-console -- Enhanced "packet too big" message to indicate who sent it. -- Corrected console prompt problem in non-readline versions. -- Correct a number of variable expansion problems. -- Added a number of new regression tests. -- In an attempt to make configuration a bit less confusing, I've changed - the name of a number of variables. The old ones still work, but will - be phased out over time. FDAddress, FDPassword, SDAddress SDPassword, - SDDeviceName, and DBPassword. -- A possible fix to the very intermittent SD crashes that Alex gets. - - - -Items to note: !!!!! -- Modifiers (sec, min, hour, day, ...) are now required on conf file - time interval specifications. -- Duplicate names within the same conf resource are prohibited. -- If you have used a prior BETA version of 1.32, please do - the following to cleanup any zero length spool files: - - cd - rm -f *.spool.* - - Please be sure there are no spaces between the asterisks - and the periods. + 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 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 +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 /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= + +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= + +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= + +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= + +============================================================== + +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.