From: Eric Bollengier Date: Fri, 8 Jul 2011 12:36:58 +0000 (+0200) Subject: update releasenotes X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=375ad6d6d18e325f05941985a7a0ccf5729f6a75;p=bacula%2Fbacula update releasenotes --- diff --git a/bacula/ReleaseNotes b/bacula/ReleaseNotes index 00a1c24421..7f37d5150f 100644 --- a/bacula/ReleaseNotes +++ b/bacula/ReleaseNotes @@ -15,13 +15,52 @@ Compatibility: As always, both the Director and Storage daemon must be upgraded at the same time. - The new pruning algorithm will not allow to prune jobs that are essential to - restore since the last Full backup. (TODO: see for an option...) - Older 5.0.x and 3.0.x File Daemons are compatible with the 5.2.0 Director and Storage daemons. There should be no need to upgrade older File Daemons. +================== Warning !!!!!! ========================== + + The new pruning algorithm will not allow to prune jobs that are essential to + restore since the last Full backup. (TODO: see for an option...) + +New Catalog format in version 5.2.0 +----------------------------------- +This release of Bacula uses a new catalog format. We provide a set of +scripts that permit to convert a 5.0.x (version 12) catalog to 5.2.0 (version +14). 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 5.2.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. + +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 5.0.0 +(e.g. 3.0.3) 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. + +================================================================ + Changes: Speed and Memory Usage Enhancements: