Bacula-users

[Bacula-users] Bacula BETA 2.5.42-b2 released to Source Forge

2009-03-18 14:25:30
Subject: [Bacula-users] Bacula BETA 2.5.42-b2 released to Source Forge
From: Kern Sibbald <kern AT sibbald DOT com>
To: "bacula-devel" <bacula-devel AT lists.sourceforge DOT net>, "bacula-users" <bacula-users AT lists.sourceforge DOT net>
Date: Wed, 18 Mar 2009 19:18:49 +0100
Hello,

We have just released Bacula BETA version 2.5.42-b2 to the bacula download of 
Source Forge.  It includes the source tar file, the Win32 binaries, and new 
Win64 binaries.

One major point to be aware of is that you must run upgrade scripts to upgrade 
your catalog -- see the release notes below.

We expect this to be the last beta release before the official release, which 
we are targetting for sometime between the end of March and mid-April.

This is the first release of the Win64 binaries.  Having 64 bit binaries are 
required for VSS to work on 64 bit Windows machines.  Since it is the first 
release, we would appreciate feedback (even if everything goes fine).  If you 
have installed a previous win64 test version or a 32 bit version, we 
recommend that you deinstall them before installing the 64 bit version.  
Please don't try to install the 64 bit binaries on a 32 bit Win OS.  Finally, 
for the moment, there is a bug in the NSIS installer version we are using 
such that for 64 bits it proposes to install in "c:/program files (x86)".  
You might want to change this to be "c:/program files".  Note, that with this 
version (unlike the 32 bit version) everything is installed in that one 
directory rather than the multiple diverse directories as with the old 32 bit 
installer.

As most of you know, the Rescue CDROM is pretty much dead.  My original idea 
was to build it from the kernel and data on your system, but in the end, this 
was just too much work, because every distro does booting different, and even 
within a single distro the boot procedures change over time.  However, I have 
now started remastering the Kubuntu livecd onto a USB key, and it looks 
really promising.  It has the advantage that it uses a single OS that already 
works, knows how to detect most hardware, and can be relatively easily 
remastered (add/remove packages, apply updates, or upgrade, ...).  In 
addition, the USB key is written so that changes to the OS and your home 
directory are rewritten dynamically to the key -- giving it a persistence.

This USB rescue key is still under development, but can now be tested.  Simply 
download the rescue tar file and look in the linux/usb directory where you 
will find a README on how to make such a key.

Our documentation is still lagging a bit behind the development, so please be 
patient.

Finally, the documentation is posted on the web site, but is not uploaded 
because Source Forge upload is very unreliable lately.

Best regards,

Kern


       Release Notes for Bacula 2.5.42

  Bacula code: Total files = 521 Total lines = 204,881 (*.h *.c *.in)

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 2.5.40
------------------------------------

This BETA 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 2.5.x (version
11). If you are using already a 2.5 version, you can drop the JobHistory
table before upgrading your catalog (if you are using the new "long term
statistics" module, you can upgrade this table the same way we do with 
the Job table, see the src/cats/update_bacula_tables script).

The simplest way to:
1. Stop any current version of Bacula from running.
2. Save a copy of your existing database.
3. Configure, build, and install the 2.5.42 version of Bacula
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.  However, if you are using a version of Bacula older than 2.5.40,
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.


New configure option :
----------------------

This BETA release of Bacula 2.5.x development code uses libtool
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.

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
==============================================================

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.

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users