Bacula Enterprise Edition 6.0.3

Ukazała się nowa wersja Bacula Enterprise Edition oznaczona numerem 6.0.3. Inteos oraz Bacula Systems zalecają swoim klientom upgrade do tej wersji. Poprawia ona kilka 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.0.3

Release Notes for Bacula 6.0.3

8 May 2012

This is a very quick bug fix to 6.0.2 that primarily
removes some new MySQL library detection code in the
./configure process that did not work on all systems.

It also ensures the Autochange flag is set in Storage
resources that are part of an Autochanger.

Finally, it ensures that shared storage is unlocked on
error exit paths.

Please read the notes for version 6.0.2 below.

Release Notes for Bacula 6.0.2

General:
--------
This is a bug fix upgrade from version 6.0.1

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you are using an autochanger and mtx-changer, please
be aware that you must upgrade to the new version of
mtx-changer.conf, possibly including any changes that
you made to the prior mtx-changer.conf. This must
be done manually since the install process does not
overwrite your old mtx-changer.conf. Normally you will
find the new script in /opt/bacula/scripts/mtx-changer.conf.new.
If you do not upgrade the script, you will get shell
syntax errors due to a missing configuration variable.

Please note, if you are upgrading from 6.0.1 to 6.0.2
you will also need to get the new version of mtx-changer.conf
If you have not modified that file, the easiest way is
to delete the file before upgrading. If you have modified
it, you can simply add a line that reads:
version=2
to the mtx-changer.conf file and it will then work with
the new mtx-changer script.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Please note that with this version of Bacula, during the install
of the shared libraries from the src/cats, src/lib, and src/findlib
directories, any old Bacula libraries in the installation
destination directory will be removed. This should not cause
any problems and at least keeps the installation library cleaner.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
For packagers, if you change options, naming, and the way
we link our shared object files, as at least one of you does,
you are creating a situation where the user may not be able
to run multiple versions of Bacula on the same machine, which
is often very useful, and in addition, you create a configuration
that the project cannot properly support.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you are upgrading from a version older than 6.0.1, please
read all the old ReleaseNotes of all versions released
after the version you are upgrading from. There area
many important notices sumarized here, and we do not
repeat them each bug fix release.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Changes:
--------

01May12
- Update po files
- Add version to mtx-changer.conf
- Ensure that StorageId is updated after write
- Fix updating of cached slots + error message numbering
- Remove old shared objects before install
- Fix mysql config for older versions of mysql+config.
- Fix problem in BVFS with concurrent queries
- Add more checks to bvfs
- Apply MSQL detection fixes from bug #1829
- Fix bug #1805 cannot specify hostname in ./configure
- Allow plugin to backup a directory
- Remove the Shared Storage Director directive
- Add Autochanger alias for Storage in bacula-dir.conf
- Fix #1857 about restore cd command that blocks on empty directory
- Deprecate SharedStorage Director directive
- Remove restore command from cmd_parser()
- update bacula32/64.def for ConfigFile object
- Add autochanger group code
- More definitive fix for update slots bug
- Fix component info orphanned buffer bug
- Fix old update slots bug
- Add plugin bVarPrefixLinks variable
- Fix #4062 on make_catalog_backup.pl script when user/password are empty
- Fix restorejob restore command keyword
- Add seconds to times as reported in bug #1854

Bugs fixed/closed since release 6.0.1:
1805 1829 1854 1857 4062

================================================================
Release Notes for Bacula 6.0.1

General:
--------
This is a major version upgrade from version 4.0.9

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you are upgrading from Bacula Enterprise 4.0,
please be aware that the database needs to be
upgraded. In general if you are installing rpms
or debs, it will be done automatically. If you
are upgrading from a community version, there
may be more than one database update needed,
so the procedure may require manual intervention.

In addition to the database upgrade, there is a difference
in packaging the SQL shared libraries (there is one more)
as well as other packaging differences. When updating
with rpms or debs this should be automatically
handled.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you store .bsr or .mail files in the Bacula working
directory, please be aware that they will all be deleted
each time the Director starts.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Compatibility:
--------------
As always, both the Director and Storage daemon must be upgraded at
the same time.

Older 4.0.x, 5.2.x, 5.0.x and 3.0.x File Daemons are compatible
with the 6.0.x Director and Storage daemons. With the exception
of Windows FDs, there is no requirement to upgrade older
File daemons. However, by not doing so, some of the new features
Bandwidth Limitation, percent restore completion, ...
For Windows, we strongly recommend that you upgrade you File
daemons as quickly as possible. If you are using the VSS plugin
or any other plugin with Windows you must update your FD.

================== Warning !!!!!! ==========================

The new pruning algorithm will not allow pruning of jobs that are
essential to restore since the last Full backup. This is, of course,
correct and desirable, but it is different from older Bacula versions
that could inappropriately prune jobs. Pruning of volumes is not
affected.

Autochanger:
============
If you are using an autochanger, please be aware that there is
a new mtx-changer script, and that in order for it to work,
you will need to replace your existing mtx-changer.conf with the
new one that comes with Bacula version 6.0.1.

working directory cleanup:
==========================
Please note that each time the Director starts, it will
remove old *.bsr and *.mail files that it has created in
the working directory that it no longer considers useful.
If you have been storing files in the Bacula working directory,
please ensure that they are moved to an alternate location
prior to starting the Director.

Building Bat:
-------------
To build Bat, you need Qt4 version 4.7.4. If you build with any other
version it is likely not to work. If you do not have version 4.7.4,
on your system, you can download the Bacula depkgs_qt version 24Dec11.

Packaging the SQL backend:
--------------------------
The main Bacula Director code is independent of the SQL backend in
this version. This means that the Bacula Director can be packaged by
itself, then each of the different SQL backends supported can be
packaged separately. It is possible to build all the DB backends at
the same time.

- configure can be run with multiple database configure options.
--with-sqlite3
--with-mysql
--with-postgresql

Note: SQLite3 is not supported by Bacula Systems.

Order of testing for database is
- postgresql
- mysql
- sqlite3

Each configured backend generates a
libbaccats-<backend_name>-<version>.so A dummy catalog library is
created named libbaccats-version.so

At configure time the first detected backend is used as the so called
default backend and at install time the dummy libbaccats-<version>.so
is replaced with the default backend type.

If you configure all three backends you get three backend libraries
and the postgresql gets installed as the default. When you want to
switch the default you can copy one of the three backend libraries
over the libbaccats-<version>.so e.g.

cp libbaccats-postgresql-<version>.so libbaccats-<version>.so

And update the default backend in the following files:

create_bacula_database
drop_bacula_database
drop_bacula_tables
grant_bacula_privileges
make_bacula_tables
make_catalog_backup
update_bacula_tables

New Catalog format in version 6.0.1 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) catalog to 6.0.1
(version 1014). The Bacula project 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.

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

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

================================================================

Changes:

Feature Enhancements:
- Restart failed jobs from failure point
- Stop/Restart Jobs (extension of restart jobs)
- Delta plugin (save only changed blocks)
- SAN Shared Storage option (SAN tape locking)
Lan Free Backup
- Differential backup for MSSQL (please do not try Incremental backups)
- Incremental backup for MS Exchange (please do not try Differential backups)
- Log error output from VSS plugin
- Use of PostgreSQL cursor when doing large queries, should reduce
the memory usage during restore and accurate backups.
- limit command in some list commands
- Bacula Virtual File System for fast catalog access
- New safer and faster pruning algorithm
- New CRC32 implementation (much faster)
- New LZO compression (faster than gzip)
- Job Bandwidth Limitation
- New SQL backend and ./configure that permits building multiple
catalog backends in one build, and has the main Bacula core code
totally independent of the SQL backend, which should simplify
packaging (only the libbacsql.so/dll needs to be changed to
switch from one database backend to another (e.g. MySQL to
PostgreSQL).

Security Enhancements:
- Additional security against injection of illegal characters

Other Enhancements:
- Compatibility with MySQL 5.5
- Includes better handling for Windows repares points, mount
points, and junction points.
- New database format
- Many new plugin API features
- Significant stability enhancements to bat
- xattr/ACL restore failure are now printed as Warning
- A few path name length limits in Windows have been removed.
- Andrew Filesystem (AFS) for Universities ready for Beta testing

For more details, please see the New Features section
of the manual.

Changes since version 4.0.9:

- Please see the ChangeLog for the details.

Bugs fixed/closed since last release:
1841 1842 1848
1389 1444 1448 1466 1467 1468 1476 1481 1486 1488 1493 1494 1497 1499 1501
1502 1504 1509 1511 1513 1516 1524 1526 1527 1532 1536 1538 1541 1542 1549
1551 1553 1554 1558 1559 1560 1564 1567 1568 1569 1571 1577 1581 1582 1584
1587 1594 1595 1600 1601 1602 1603 1604 1606 1608 1610 1612 1623 1624 1633
1643 1648 1655 1661 1664 1666 1669 1672 1675 1684 1695 1696 1699 1700 1703
1735 1741 1749 1751 1761 1762 1764 1768 1770 1771 1774 1778 1792 1801 1802
1806 1807 1810 1811 1815 1821 1822 2492 2710 2713 3210 3308 3322 3325 3419