List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Fri, 30 Dec 2011 10:11:58 +0100
Michał Górny <email@example.com> wrote:
> On Fri, 30 Dec 2011 09:56:33 +0100
> Thomas Beierlein <firstname.lastname@example.org> wrote:
> > It is strongly recommended that you save a copy of your existing
> > database before upgrading.
> More details or even a script to do that would be great for users.
Not as easy as it depends on users decision to use mysql, sqlite or
postgresql. But added a hint to look into database documentation (see
The other minor corrections got also applied. Thanks.
Title: Bacula-5.2.3 Upgrade
Author: Thomas Beierlein <email@example.com>
The 5.2.x release series of Bacula use a new database catalog format.
If you're upgrading from a 3.x.x or 5.0.x release, you must upgrade your
bacula catalog database.
Please read the manual chapter for how to upgrade your database (see
You can find database upgrade scripts in /usr/libexec/bacula/(updatedb/).
It is strongly recommended that you save a copy of your existing database
before upgrading. For details how to do it please look into your database
The simplest way to upgrade the database:
1. Stop Bacula from running (at least the director and storage daemons).
2. Save a copy of your existing database.
3. Emerge the new version of Bacula.
4. Run the appropriate upgrade script from /usr/libexec/bacula/updatedb/.
7. Start the new Bacula.