From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: tomjbe@gentoo.org
Subject: Re: [gentoo-dev] rfc: news item for app-backup/bacula
Date: Fri, 30 Dec 2011 10:11:58 +0100 [thread overview]
Message-ID: <20111230101158.7ef6e723@pomiocik.lan> (raw)
In-Reply-To: <20111230095633.18c4316d@ham>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Fri, 30 Dec 2011 09:56:33 +0100
Thomas Beierlein <tomjbe@gentoo.org> wrote:
> The 5.2.x release series of Bacula uses a new database catalog format.
^^^ use (singular)
> 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.
Link would be useful.
> 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.
More details or even a script to do that would be great for users.
> The simplest way to upgrade the database:
>
> 1. Stop Bacula from running (at least director and storage daemon).
^ the ^-s
> 2. Save a copy of your existing database.
> 3. Emerge new version of Bacula.
^ (probably) the
> 4. Run the appropriate upgrade script
> from /usr/libexec/bacula/updatedb/.
> 7. Start the new Bacula.
It saved us two steps!
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2011-12-30 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 8:56 [gentoo-dev] rfc: news item for app-backup/bacula Thomas Beierlein
2011-12-30 9:11 ` Michał Górny [this message]
2011-12-30 9:43 ` Thomas Beierlein
2011-12-30 10:44 ` Michał Górny
2011-12-30 11:09 ` Thomas Beierlein
2011-12-30 17:02 ` [gentoo-dev] " Jonathan Callen
2011-12-31 10:51 ` Thomas Beierlein
2011-12-31 14:56 ` [gentoo-dev] " William Hubbs
2011-12-31 15:54 ` Alexandre Rostovtsev
2012-01-01 19:54 ` Thomas Beierlein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111230101158.7ef6e723@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=tomjbe@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox