Bacula Enterprise Edition 6.4.14
Ukazała się nowa wersja Bacula Enterprise Edition oznaczona numerem 6.4.14. Inteos oraz Bacula Systems zalecają swoim klientom upgrade do tej wersji. Poprawia ona kilka pomniejszych błędów znalezionych w poprzednich wydaniach. Aktualizacja dostępna jest dla wszystkich klientów posiadających aktualną subskrypcję oprogramowania Bacula Enterprise Edition dowolnego poziomu.
Dostęp do nowej wersji Bacula Enterprise, klienci Inteos Sp. z o.o. otrzymują po utworzeniu nowego zgłoszenia w systemie supportowym Bacula Systems.
Informacje szczegółowe:
Release Notes for Bacula Enterprise 6.4.14 Release 6.4.14 31 October 2013 - Fix bug #8106 bad JobMedia records created - Fix bvfs queries using delta files - Fix #89 about permissions on sql scripts - bweb: Fix #8889 about Accurate/SpoolData and Messages not saved when editing Schedule - Fix bdirjson output when using Wild list in FileSet - Fix compilation when using IP_TOS option - Fix initial problem in bug #8655 FD gets bad status from SD - Fix bug #39 start/stop scripts prevent traceback - bweb: handle Clients with spaces in bweb admin part - bweb: Fix #78 about ActionOnPurge configuration problem - bweb: fix copy button in schedule page Bugs fixed/closed since last release: 39 78 8106 8655 8889 89 Release 6.4.14 is a bug fix update to 6.4.13. The main bug fixed is #8105 in which bad JobMedia records caused restore problems. This occurred only when Volumes were expiring during a backup. As is always the case, all daemons on a given machine must be updated, but prior File daemons work with this new version. Due to the storage daemon hang bug that this release fixes, we strongly recommend that all users of 6.4.6 or later upgrade to 6.4.14. =================================== Release 6.4.13 20 October 2013 16Oct13 - Adjust debug to better trace open fail problem - bweb: Use %config(noreplace) for bweb.conf and httpd.conf - bweb: Select 6.4 by default in config_edit - Fix package-list to include new packages - Clear more cached_attribute on failures. Should fix bug #8870 - bweb: Fix false error in test_config when the Client table is empty - Fix for bug #8870 Director crach in db_end_transaction() - Fix OSX build Release 6.4.13 is a minor bug fix update to 6.4.12. It might possibly fix a Director crash 8870 as well as add addition trace output for the open fail bug. As is always the case, all daemons on a given machine must be updated, but prior File daemons work with this new version. Due to the storage daemon hang bug that this release fixes, we strongly recommend that all users of 6.4.6 or later upgrade to 6.4.12. Bugs fixed/closed since last release: 8870 === Release 6.4.12 11 October 2013 11Oct13 - Fix SD hang bug #8755 - Ensure that winbmr plugin is properly built - Fix #33/8788 about bad json output when using empty Options block - bweb: Fix #8786 about Password field not correctly checked - bweb: Allow custom options on install_bweb.sh script - bweb: set trace=0 when debug level is 0 - bweb: Try to avoid bad progress bar during backup - Ignore Director SharedStorage that points to itself - Display chown/chmod error only if root or debug_level > 100 - Put correct copyright - Add HasCache in llist job output - bweb: Fix LabelFormat using advanced format Release 6.4.12 is a bug fix update to 6.4.11. It fixes a number of bugs, most importantly a Storage Daemon hang. As is always the case, all daemons on a given machine must be updated, but prior File daemons work with this new version. Due to the storage daemon hang bug that this release fixes, we strongly recommend that all users of 6.4.6 or later upgrade to 6.4.12. Bugs fixed/closed since last release: 8755 8786 8788 ==== Release 6.4.11 18 September 2013 16Sep13 - Fix aligned disk address bug when changing volumes - Force aligned to have maxconcurrentjobs=1 - Fix new secure restore - Print more generic message on regress failure Release 6.4.11 is a bug fix update to 6.4.10. It corrects an implementation error in the secure restore that kept it from being fully secure, and most importanly this release fixes several obscure bugs in the Aligned Volume code that could cause the use of bad disk addresses and hence incorrect restores. These problems occurred only when a Maximum Volume Bytes size was reached, and even in that case, it was somewhat rare. ==== Release 6.4.10 12 September 2013 11Sep13 - Make Windows bfile work more like Unix for FIDs - Correct return status of plugins -- especially delta plugin - Define default plugin io status that fails - Turn ASSERT2 into Jmsg M_FATAL - Add ASSERTs in block.c for negative HoleBytes - Ensure StartBlock is correctly set for Aligned Vols - Fix deadlock (seg fault) in Aligned many-volumes-test - Turn on new fchmod, fchown and futimes restore security code - Add missing redirection on diff.pl call - Add security fixes to src/findlib/mkpath.c - Use diff.pl to detect time/date differences for restore - Detect new functions fchmod, ... Release 6.4.9-Beta: 08 September 2013 Release 6.4.9-Beta is a bug fix beta update to 6.4.8. The principal change is to add new restore security code. Release 6.4.8: 06 September 2013 05Sep13 - Probable fix for Dir crash ticket #8427 - bweb: Use "Edit Plugins" instead of "Add Plugin" in fileset edition page - Remove close_msg(NULL) that causes seg fault - winbmr: Fix bug #8294 special partitions were not always mounted and backed up - Add list joblog in list help command for bconsole completion - winbmr: parse plugin line using cmd_parser Bugs fixed/closed since last release: 8294 8427 Release 6.4.8 is a bug fix update to 6.4.7. The main change for this release is to add a fix for a crash in the Dir that occurs after it cannot connect to the FD. Release 6.4.7: 30 August 2013 30Aug13 - bweb: Sort the output of workset_list - bweb: Test the configuration before trying a restart - bweb: Add close button to bresto - Fix bug #8110 VerifyToVolume failed because RestoreObject not counted - Add makedocsonly release script - bweb: Do not use bad User Defaults value when filling forms - Fix #8344 about a limitation in bconsole when not using a tty - bweb: Add specific test for bweb_role in bweb_testconfig - bweb: Add SAP to the fileset edition box - Avoid possible seg fault if bad configuration - Fix seg fault bug 7901 bsock released during cancel Bugs fixed/closed since last release: 8110 8324 8344 Release 6.4.7 is a bug fix update 6o 6.4.6. The main changes for this release are fixes VerifyToVolume on Windows machines, allows arbitrary length lines input to bconsole, and fixes a Director crash during the cancel command. Release 6.4.6: 16 August 2013 16Aug13 - Include bweb release notes in main ReleaseNotes file - Fix seg fault in printf of vtape.c - Set default Heartbeat Interval to 300 seconds - Fix jobmedia bug #8106 + new_dcr bug + SD lock debug code - Add new jobmedia test for restore problems - bweb: Modify search box to handle bad queries - bweb: Fix incorrect duration display in job view - Create wrong file size restore in regress bug-7640 - Correct error reporting for bug #8227 (does not fix bug) - Sanity check to keep VolHoleBytes positive -- bug #8234 - Adjust restore command dynamically to allow long where/regexwhere Bugs fixed/closed since last release: 8106 8227 8234 Release 6.4.6 is a bug fix update to 6.4.5. This version fixes a restore bug if volumes are expired while being written and a new job starts needing a new volume. It sometimes caused incorrect restore indexes. It also corrects a bug where VolHoleBytes became negative causing a database error updating the Volume data at the end of a Job. New Features: Release 6.4.6 also includes our new SAP plugin. Please see the SAP white paper for details. Release 6.4.5: 2 August 2013 01Aug13 - Add auto-label-many-test to all-disk-tests - Add auto-label-many regression test for bug #8013 - Fix many auto label bug #8013 - Add regress test for bug #8103 - Fix VolFiles and job failure after volume/catalog out of sync bug #8013 - Always edit volume sizes with commas - Add additional content to create volume messages Bugs fixed/closed since last release: 8013 8103 Release 6.4.5 is a bug fix update to 6.4.4. This version fixes a bug with auto labeling and can in situations of lack of available Volumes significantly increase performance. If you are using autolabeling, we recommend that you upgrade from prior versions. ================================================== Released 6.4.4: 30 July 2013 28Jul13 - Fix bug #8033 duplicate volumes created during ActionOnPurge=truncate - Add new regression 2media-virtual-test to all-disk-tests - Create regression test for improper ActionOnPurge bug #8033 - Remove sql unneeded ASSERT that triggers in bscan - Fix seg fault in bscan at debug>=500 - Fix bdirjson ReadFifo output bug - Fix bug #2014 bad ctime on Windows - Use 755 default permission for bconsole - Upload BWebReleaseNotes with ReleaseNotes Bugs fixed/closed since last release: 2014 8033 Release 6.4.4 is an important bug fix update to 6.4.3. We recommend that all 6.4.3 or older users update to this version. ================================================== Released 6.4.3: 9 July 2013 08Jul13 - Lots of fixes to Bweb - Use quotes my.cnf for complex socket path, user or password in make_catalog_backup.pl - Fix AD restore not to fail - Add winbmr to winbacula.msi Release 6.4.3 is a minor bug fix to 6.4.2, primarily it should fix the AD Restore mode restores on Windows and a number of Bweb issues. ======================================================= Released 6.4.2: 15 June 2013 Release 6.4.2 is a significant bug fix to 6.4.1, that removes a restriction on simultaneous jobs and fixes a restore bug. All users of 6.4.0 and 6.4.1 are strongly urged to upgrade. 15Jun13 - Fix bug 7640 restore failures - Fix restraint on simultaneous volume writes ONLY to aligned Volumes - Add spec file for redhat static package - bat: Change Restore button to Restore... - Add #PluginDirectory= in bacula-fd.conf Bugs fixed/closed since last release: 7640 See below for 6.4.0 new features and usage ... ======================================================= Release 6.4.1: 23 May 2013 Release 6.4.1 is a minor bug fix to 6.4.0 that fixes the bconsole build on older systems. 20 May 2013 Release 6.4.0 Although the list of new features is not extremely long, there are significant enhancements to this version of Bacula. The changes touched on 809 files, and comprise nearly two thousand lines of differences. New Features since version 6.2.x: --------------------------------- - Deduplication Optimized Volumes (Aligned Volumes) - Prune Expired Volumes command - Read the same disk volume by multiple jobs - Migration/Copy/VirtualFull performance improvements in the SD For a complete list of changes, which is too long to present here, please see the ChangeLog. New Catalog format in version 6.4.0 and greater ----------------------------------------------- This release of Bacula uses a new catalog format. We provide a set of scripts that permit to convert a 4.0.x (version 12) and 6.0.x (version 1014) to the new 6.4.x (version 1015). The upgrade from 1014 to 1015 should be fast. Note, this catalog format is not compatible with beta 6.3.x versions that have been released. For those beta releases, you must start from an older production catalog or create a new catalog. The Bacula Enterprise rpm spec files have been modified to 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. If you want to have more control over the Catalog upgrade step when installing 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. The simplest way to upgrade the database assuming you are building from source (i.e. manually): 1. Stop any current version of Bacula from running. 2. Save a copy of your existing database. 3. Configure, build, and install the 6.0.1 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. New Directives in Storage daemon: - Aligned Device = This directive is similar to the Archive Device. It is optional, but if specified the Aligned Volume (xxx.add) will be placed in the Aligned Device directory specified, which is presumably different from the Archive Device where the Metadata Volume is placed. In the absence of the Aligned Device directive, both volumes will be placed in the Archive Device directory. Having two directives allows placing the Metadata volume in a directory (or partition) that is not deduplicated while the Aligned data volume can be deduplicated. - Minimum Aligned Size = This Directive is set to 4096 by default, and any file that is this size or smaller will be placed in the Metadata volume rather than the Aligned Volume. This allows you to put smaller files that are unlikely to deduplicate well into the Metadata volume rather than overload the Aligned volume with data that does not deduplicate well. - Device Type = Aligned This is required to make the Device write aligned volumes. - Padding Size = If a block is not full, it will be padded to the next multiple of this size by filling with zeros. If you want all blocks to be the same size as the Maximum Block Size, then set the Padding Size to the same value as the Maximum Block Size. The default for this is 4096 bytes. - File Alignment = Each new file that is written into the .add file will be aligned to a multiple of this size. Note: these directives *must* have a value (bytes) that is an exact multiple of 512 bytes, and in some cases, for optimum performance they should be very specifically set. See examples below. Restrictions: ------------- - Blocks are may be written in any size and the files can be aligned at any value, providing they are at multiples of 512 and 1024 bytes. See the new directives below. - The Catalog format of this version is different from prior versions of Bacula (i.e. version 6.2.x and lower). - If you are using the Virtual Disk Changer feature of Bacula, it should work fine. - If you are using the Bacula disk-changer script, it has been modified so that it should work fine. - If you are using any other sort of VTL software, it is very unlikely to work. If the VTL simulates a tape drive, it definitely will not work. You must work with Bacula disk Volumes. - The aligned Volume format works only for disk files (this restriction will remain in the production version). How Duduplication Optimized Volumes work: ----------------------------------------- - You must have the aligned-sd.so plugin loaded and the PluginsDirectory defined in the Storage daemon's conf file. - You enable Aligned Volumes by specifying in the bacula-sd.conf file a DeviceType = "Aligned". - This will create two files for each Volume. If the Volume name is Test001. The files will be named Test001 and Test001.add. Test001 will contain all the meta data and any data that is not a standard Linux/Unix file, and Test001.add will contain all the aligned data (i.e. it will be block aligned). - If you are writing the Volume with only one job each file will have its data stored contiguosly. - If you are writing the Volume with multiple simultaneous jobs, the blocks in the .add volume will be interleaved, but they will be properly aligned so should deduplicate equally well. However, running multiple simultaneous writes will use more space in the volume. - If you set a maximum volume size for an aligned volume device, Bacula will only allow one backup job at a time. In any case, it is probably *much* more efficient to only backup to aligned volumes with one job at a time. There is a Bacula Enterprise White Paper which describes the Aligned Volume format. Please ask for it. Note: these new directives *must* have a value (bytes) that is an exact multiple of 512 bytes, and in some cases, for optimum performance they should be very specifically set. See examples below. Example for ZFS: Device Type = Aligned Padding Size = 4K File Alignment = 128K Maximum Block Size = 128K Minimum Block Size = 0 Example for NetApp: Device Type = Aligned Padding Size = 4K File Alignment = 4K Minimum Aligned Size = 4K Maximum Block Size = 64K Minimum Block Size = 0 Things to note: --------------- - Blocks are may be written in any size and the files can be aligned at any value, providing they are at multiples of 512 and 1024 bytes. - If you are using the Virtual Disk Changer feature of Bacula, it should work fine. - If you are using the Bacula disk-changer script, it has been updated to work with aligned volumes, however, so of our tests fail with the disk-changer. We strongly recommend using the Virtual disk changer instead. Please see the Bacula Systems white paper that explains how to use the Virtual Disk Changer feature of Bacula (no script needed). - If you are using any other sort of VTL software, it is very unlikely to work. If the VTL simulates a tape drive, it definitely will not work. You must work with Bacula disk Volumes. - The aligned Volume format works only for disk files (this restriction will remain in the production version). - We recommend that you upgrade any older File daemons to version 6.4.0 if you are going to use them to write aligned volumes. If you do not, please be aware that the new Minimum Aligned Size directive will be ignored for those older File daemons and all files regardless of their size will be put into the Aligned volume.